JMSListenerResourceAdapter on SJAS8.1EE

Question

Hi folks,
Application Server : Sun Java Application Server 8.1 EE
Node agent is not running. Using a single instance in a stand-alone mode.
No cluster setup done.
Operating System : Windows XP Prof.
IDM version : 6.0
Resource Adapter being configured : The JMSListener Resource Adapter
JMS Administered Objects Setup : I've set a ConnectionFactory (for Topics) and a
Topic via the Admin Console and created the corresponding Physical Destination.
When I set the following attributes on the JMSListenerResourceAdapter :
JNDIProperties (for InitialContext creation)
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
java.naming.provider.url=localhost:1099
and specify the correct JNDI name for the ConnectionFactory and the Destination, I get
an error on the JSP :
Test connection failed for resource(s):
InboundTicketsListener: com.sun.messaging.jms.JMSException: MQRA:CA:Unsupported-setClientID()
Unfortunately, I dont get a complete Exception Stack Trace anywhere (even after a level 4
trace on the Adapter class) .
On researching the above exception, I found the following bug opened by Nokia on SJAS 8.1 EE.
Note the developer's comments when closing the bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6197813
The IDM Resource Adapter for JMS does the same thing as com.nokia.oss.ossj.sa.ri.order.OrderScheduler
tried .
In the JMSListener Resource Adapter, is it possible that we doing something like ....?
connection.setExceptionListener(...);
As per Section 6.6 of the J2EE1.4 spec :
<from14Jee>
The following methods may only be used by application components
executing in the application client container:
javax.jms.Session method setMessageListener
javax.jms.Session method getMessageListener
javax.jms.Session method run
javax.jms.QueueConnection method createConnectionConsumer
javax.jms.TopicConnection method createConnectionConsumer
javax.jms.TopicConnection method createDurableConnectionConsumer
javax.jms.MessageConsumer method getMessageListener
javax.jms.MessageConsumer method setMessageListener
javax.jms.Connection method setExceptionListener
javax.jms.Connection method stop
javax.jms.Connection method setClientID
A J2EE container may throw a JMSException (if allowed by the method) if the
application component violates these restrictions
</from14Jee>
Looking at the support for setting up a MessageListener to monitor the Message Consumption lifecycle and the support for Durable subscriptions, the JMSListenerResourceAdapter also probably calls setMessageListener and setClientID(for Durable subscriptions),both of which are illegal in a non ACC scenario .
Has the JMSListenerAdapter been tested on SJAS8.1 EE (one of the supported Application server platforms)?
It's possible that WebLogic and Websphere may not be throwing the above error since the spec says :
A J2EE container "may" throw a JMSException.... in the above case ..
Any pointers or tips on how we can get around this issue would be really helpful !
Ciao

Answer 1

Thanks Wilfred .
Wilfred : On version 6 these kinds of exceptions should be logged in the syslog table (new logging table in the database) check if you have an exception there.
CB : I did try to run lh syslog and didnt retrieve any records. Do I need to make any configuration changes to have all exceptions go to syslog or does every exception out of the box go into syslog ?
Wilfred : The other possibility is that the html source does contain the full stacktrace as a comment. Please check that also.
CB: Checked that too - View Source doesnt give the full stack unfortunately.
Wilfred : If it is reproducible log a support case with the traces.
CB: It is reproducible. We are in the process of filing a support case
Wilfred : FYI bug 6197813 has been closed as not a bug as the app server is allowed to throw that exception if the component is not in the client container of the app server.
CB: Yes, I understood that .. I know that it's not an Application server bug.
However you didnt answer my main questions :)
The J2EE spec says that the application server "may" throw the exception if the component calling connection.setExceptionListener() is not an AppClient.
First - Isnt it true that the IDM Resource adapter is not running in an appclient? Isnt it running inside a WebContainer?
Second - Is it possible that SJAS throws the exception but WebLogic/Websphere dont in the above scenario?
Third - Has the JMSListener Resource adapter been tested and certified on Sun Java Application Server?