11:25 a.m.
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
11:34 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1144:
--------------------------------------
Can you explain what the problem is on the JIRA task please?
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
11:51 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1144:
----------------------------------------------
When you run BrowserTest::testMessageOrderOnBrowser you have this exception:
There was 1 error:
1)
testMessageOrderOnBrowser(org.jboss.test.messaging.jms.BrowserTest)javax.jms.JMSException:
Failed to route Reference[2]:RELIABLE to Queue1
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:722)
at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:421)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at
org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at
org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:90)
at
org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.remoting.Client.invoke(Client.java:536)
at
org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187)
at
org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158)
at
org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$send$aop(ClientSessionDelegate.java:474)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:632)
at
org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28.invoke(SessionAspect28.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java)
at
org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:266)
at
org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspect39.java)
at
org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at
org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:164)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:207)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:145)
at
org.jboss.test.messaging.jms.BrowserTest.testMessageOrderOnBrowser(BrowserTest.java:318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58)
FAILURES!!!
Tests run: 1, Failures: 0, Errors: 1
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
11:53 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1144:
----------------------------------------------
Another exception seen on logs:
java.lang.ArrayIndexOutOfBoundsException: 10
at
org.jboss.messaging.util.prioritylinkedlist.BasicPriorityLinkedList.addLast(BasicPriorityLinkedList.java:90)
at
org.jboss.messaging.core.impl.ChannelSupport.addReferenceInMemory(ChannelSupport.java:738)
at
org.jboss.messaging.core.impl.PagingChannelSupport.addReferenceInMemory(PagingChannelSupport.java:384)
at
org.jboss.messaging.core.impl.ChannelSupport.handleInternal(ChannelSupport.java:626)
at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:144)
at
org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2192)
at
org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:489)
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:720)
at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:421)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at
org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at
org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:90)
at
org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.remoting.Client.invoke(Client.java:536)
at
org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187)
at
org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158)
at
org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$send$aop(ClientSessionDelegate.java:474)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:632)
at
org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28.invoke(SessionAspect28.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java)
at
org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:266)
at
org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspect39.java)
at
org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at
org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:164)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:207)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:145)
at
org.jboss.test.messaging.jms.BrowserTest.testMessageOrderOnBrowser(BrowserTest.java:318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.textui.TestRunner.doRun(TestRunner.java:121)
at junit.textui.TestRunner.start(TestRunner.java:185)
at
org.jboss.test.messaging.tools.junit.SelectiveTestRunner.main(SelectiveTestRunner.java:58)
@m
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
11:59 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=all ]
Tim Fox closed JBMESSAGING-1144.
--------------------------------
Resolution: Rejected
The test is failing with the excepton since the message is being sent with a JMS priority
of 10 which is illegal.
It is therefore valid for it to throw a JMSException.
JMS legal priorities are 0-9 (See JMS spec 3.4.10).
Having said that it will improve the exception message so it is more obvious to the user
why the exception is being thrown
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
2:21 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1144:
--------------------------------------
The test is invalid-
JMS ordering guarantees specifically only apply to messages of the same delivery mode.
See JMS 1.1 Spec 4.4.10.2:
"• If both PERSISTENT and NON_PERSISTENT messages are sent to a
destination, order is only guaranteed within delivery mode. That is, a later
NON_PERSISTENT message may arrive ahead of an earlier PERSISTENT
message; however, it will never arrive ahead of an earlier
NON_PERSISTENT message with the same priority.
"
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
4:11 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=all ]
Tim Fox reopened JBMESSAGING-1144:
----------------------------------
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Stable branch
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
4:13 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1144?page=all ]
Tim Fox closed JBMESSAGING-1144.
--------------------------------
Fix Version/s: Unscheduled
(was: Stable branch)
Resolution: Rejected
Routing problem on Browsing when using mixed deliveries..
---------------------------------------------------------
Key: JBMESSAGING-1144
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: Unscheduled
I believe the error is due to mixed delivery modes... but that's just a guess as I
didn't have time to look at logs.
I'm committing a testcase on BrowserTest for this.
This testcase was reported by Carlo.. I just converted this testcase from his original
test on EJB3.
--
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
6168
days inactive
6273
days old
7 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Tim Fox (JIRA)