[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1229) Remoting exception with JMS subscription
Remoting exception with JMS subscription
----------------------------------------
Key: JBSEAM-1229
URL: http://jira.jboss.com/jira/browse/JBSEAM-1229
Project: JBoss Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 1.2.1.GA
Environment: JEMS Installer 1.2 ejb3 profile, JBoss Portal 2.6.0ALPHA1, JBoss
Seam 1.2.1GA running on Fedora Core 6, Firefox 1.5
Reporter: Alex Mateescu
Assigned To: Shane Bryzak
Priority: Minor
I am deploying an EAR with multiple (the number is probably irrelevant) JARs and WARs that
use Seam Remoting and subscribe to a JMS topic.
The subscribe calls work fine, they send the correct topic name and receive a token. On
the first poll, though, there is an exception:
2007-04-23 14:08:29,602 ERROR [org.jboss.seam.remoting.Remoting] Error
java.lang.IllegalArgumentException: Invalid token argument - token not found in Session
Context. [undefined]
at
org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:179)
at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:45)
at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:83)
at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:110)
at org.jboss.seam.servlet.ResourceServlet.doGet(ResourceServlet.java:68)
at org.jboss.seam.servlet.ResourceServlet.doPost(ResourceServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
Upon closer inspection, the polling request looks like this:
<envelope><body><poll
token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll
token="undefined" timeout="10"/></body></envelope>
which is the cause of the exception.
Subsequent calls look fine:
<envelope><body><poll
token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll
token="3922899d-1e6b-4bc1-96ab-3713f4460446"
timeout="10"/></body></envelope>
I think the error was there before, when using Seam 1.1.0GA, but it was random. I may be
wrong, but now it is always there.
Of course, remoting works fine after the initial call.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira