IllegalStateException thrown from JmsSession.checkStrict()

[myoung]

I'm using Jboss-3.2.5 and I am getting an IllegalState Exception when trying to set the message listener. I am using the default JMS Resource adapter bound at java:/JmsXA. What is causing this? I've search through the Wiki and forums but I haven't found anything similar:

 topicConnectionFactory = CacheInvalidatorTCFUtil.getTCF(null);
 topic = (Topic) CacheInvalidatorTopicUtil.getTopic(null);
 topicConnection = topicConnectionFactory.createTopicConnection();
 topicSession = topicConnection.createTopicSession(false,
 Session.AUTO_ACKNOWLEDGE);
 topicSubscriber = topicSession.createSubscriber(topic);
 topicSubscriber.setMessageListener(this);

15:41:37,562 INFO [STDOUT] javax.jms.IllegalStateException: Method not allowed
15:41:37,562 INFO [STDOUT] at org.jboss.resource.adapter.jms.JmsSession.checkStrict(JmsSession.java:388)
15:41:37,562 INFO [STDOUT] at org.jboss.resource.adapter.jms.JmsMessageConsumer.setMessageListener(JmsMessageConsumer.java:111)
15:41:37,562 INFO [STDOUT] at com.oakwood.cms.jms.CacheInvalidatorSubscriber.subscribe(CacheInvalidatorSubscriber.java:27)
15:41:37,562 INFO [STDOUT] at com.oakwood.cms.web.action.OakwoodRequestProcessor.init(OakwoodRequestProcessor.java:18)
15:41:37,562 INFO [STDOUT] at org.apache.struts.action.ActionServlet.getRequestProcessor(ActionServlet.java:872)
15:41:37,572 INFO [STDOUT] at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
15:41:37,572 INFO [STDOUT] at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
15:41:37,572 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
15:41:37,572 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
15:41:37,572 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:72)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
15:41:37,572 INFO [STDOUT] at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:275)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
15:41:37,572 INFO [STDOUT] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
15:41:37,572 INFO [STDOUT] at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
15:41:37,572 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
15:41:37,572 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
15:41:37,572 INFO [STDOUT] at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
15:41:37,572 INFO [STDOUT] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
15:41:37,572 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534)

[dannyyates]

What is causing this is stated quite clearly in the first 3 lines of the stacktrace. The call to setMessageListener() is not allowed.

If you want to receive messages asynchronously, you should write a message driven bean (MDB).

[myoung]

I've had this work correctly when using the connection factory bound at XAConnection factory. I can't use an MDB because I need to access resources at the Servlet level.

[myoung]

Also, the fact that I'm not using a MDB to do asychronous messaging should not be the cause of this problem. I'm hoping there's something simple I'm doing wrong that someone may be able to quickly address. What I'm doing seems to be a pretty simple operation.

[dannyyates]

Errr... what happens if the Servlet container throws away your servlet instance whilst it's still registered to receive the messages? What happens once the specific servlet call has returned? Does the servlet continue to receive JMS messages?

Seems a bit dicey to me...

[myoung]

That's actually okay, because we're using messaging to cache results of servlet invocations. So if the container trashes the servlet instance, we'll close the jms resources and re-init them on the servlet init. I don't have it set up that way right now, but I'm trying to get this to work first.

Aside from that, why should jboss be deciding where i set up my message consumer?

[myoung]

I after looking in the jboss src I was finally able to get this to work, however, I'm not sure if this is something I was supposed to do. I added the following to my remote-jms-ds.xml <tx-connection-factory>:

<config-property name="Strict" type="java.lang.Boolean">false</config-property>

Adrian, is this not recommended?

[dannyyates]

Dunno. Probably something buried in a spec somewhere.

[javajedi]

Hmm...I just ran into the same problem. Anyone who actually has a clue what the "strict" property is for care to comment on this?

[adrian.brock]

Well I changed the error message in 4.0.2 to try to avoid this FAQ.
Guess it didn't work...

"This method is not applicable inside the application server. See the J2EE spec, e.g. J2EE1.4 Section 6.6"

[mikeg123]

Hello,
ok, I guess, I'm missing something here, what if I have a service that is going to publish to the topic and I have multiple other services within the same sever side application that need to recieve notifications, (so they need to subscribe to that topic). Are you saying it can not be done, or can not be done with "JmsXA"? because it works fine with "ConnectionFactory"?

[adrian.brock]

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
HIJACK and not read the spec(s)

[mikeg123]

Hi,
I'm not sure what you mean by HiJACK, and I did read the spec but the spec is vary vague, it does mention that you can only use this method from a client container, so if JMX is not considered a client container, then why when use "ConnectionFactory" instead of "JmsXA" and use MBean to subscribe to the topic it works fine?
using jboss 3.2.6

also, would I be screwing anything up by adding the line in bold to the jms-ds.xml file?

<tx-connection-factory>
<jndi-name>JmsXA</jndi-name>
<xa-transaction/>
<adapter-display-name>JMS Adapter</adapter-display-name>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
<config-property name="Strict" type="java.lang.Boolean">false</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
</tx-connection-factory>

[adrian.brock]

Try reading the link I posted. This isn't the first time I've posted it to you.
You lack netiquette.

http://wiki.jboss.org/wiki/Wiki.jsp?page=BadPostHijack
Not helping the original poster, instead hijacking the thread for your own problem.