[JBoss JIRA] Created: (JBAS-4328) Message expiration doesn't work with a message listener on a session
11:06 a.m.
Message expiration doesn't work with a message listener on a session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.0.GA
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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
12:11 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Adrian Brock closed JBAS-4328.
------------------------------
Fix Version/s: (was: JBossAS-4.2.0.GA)
Resolution: Rejected
The expiration handling on the client side was removed a while ago
http://jira.jboss.com/jira/browse/JBAS-2204
It is now done on the server.
The linked EJB3 test is just stupid, it shows a message that is ~90ms over expiration.
This is not an expired message according to JMS.
While the MDB is handling the message the jms server is probably saying
"this message looks like it has expired, no hang on a minute
I've already given it to a client so it didn't expire".
JMS is NOT a real time system.
Write a real test where you don't even deploy the MDB until 10 or 20 seconds
after the message is due to expire. Otherwise your test is always going to fail
randomly due to the race condition between the delivery thread processing the message
and the expiration thread checking the expiry of the message.
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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
1:25 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Carlo de Wolf reopened JBAS-4328:
---------------------------------
I'm not going anything client side, this is all server side.
Message should have expired 5 seconds ago.
20:15:11,556 INFO [STDOUT] *** ExpirationTestMDB onMessage 1 in
org.jboss.ejb3.test.mdb.ExpirationTestMDB@15ef3ab
20:15:11,556 INFO [STDOUT] *** now = 1176401711556
20:15:11,557 INFO [STDOUT] *** message = SpyTextMessage {
Header {
jmsDestination : QUEUE.expirationtest
jmsDeliveryMode : 1
jmsExpiration : 1176401706536
jmsPriority : 4
jmsMessageID : ID:80-11764017015362
jmsTimeStamp : 1176401701536
jmsCorrelationID: null
jmsReplyTo : null
jmsType : null
jmsRedelivered : false
jmsProperties : {foo=bar, currentTest=testExpiration, null=null}
jmsPropReadWrite: false
msgReadOnly : true
producerClientId: ID:80
}
Body {
text :expire on server
}
}
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:09 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Adrian Brock closed JBAS-4328.
------------------------------
Resolution: Rejected
I don't care. The issue is whether it was expired when the server got the receive()
request not when the mdb processes the message.
org.jboss.mq.server.BasicQueue::receive()
[code]
synchronized (messages)
{
// find a non-expired message
while (messages.size() != 0)
{
messageRef = (MessageReference) messages.first();
messages.remove(messageRef);
if (messageRef.isExpired())
{
expireMessageAsync(messageRef);
messageRef = null;
}
else
break;
}
[/code]
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:12 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=comments#action_12359160 ]
Adrian Brock commented on JBAS-4328:
------------------------------------
If you really think you have a bug in JMS write a test for it in the jms testsuite.
But, I think you'll find these tests already exist.
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:40 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Carlo de Wolf reopened JBAS-4328:
---------------------------------
And that's the exact problem. Because it's a sessionConsumer it bypasses receive.
2007-04-12 21:35:50,247 ERROR [STDERR] java.lang.Exception
2007-04-12 21:35:50,247 ERROR [STDERR] at
org.jboss.ejb3.test.mdb.ExpirationTestMDB.onMessage(ExpirationTestMDB.java:47)
2007-04-12 21:35:50,247 ERROR [STDERR] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2007-04-12 21:35:50,248 ERROR [STDERR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2007-04-12 21:35:50,248 ERROR [STDERR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2007-04-12 21:35:50,248 ERROR [STDERR] at
java.lang.reflect.Method.invoke(Method.java:585)
2007-04-12 21:35:50,248 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
2007-04-12 21:35:50,249 ERROR [STDERR] at
org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
2007-04-12 21:35:50,249 ERROR [STDERR] at
org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
2007-04-12 21:35:50,249 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2007-04-12 21:35:50,249 ERROR [STDERR] at
org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
2007-04-12 21:35:50,250 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2007-04-12 21:35:50,250 ERROR [STDERR] at
org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
2007-04-12 21:35:50,251 ERROR [STDERR] at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
2007-04-12 21:35:50,251 ERROR [STDERR] at $Proxy221.onMessage(Unknown Source)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.mq.SpySession.run(SpySession.java:323)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
2007-04-12 21:35:50,252 ERROR [STDERR] at
org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
2007-04-12 21:35:50,252 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
2007-04-12 21:35:50,252 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:45 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=comments#action_12359166 ]
Carlo de Wolf commented on JBAS-4328:
-------------------------------------
And that's the exact problem. Because it's a sessionConsumer it bypasses receive.
java.lang.Exception
at org.jboss.ejb3.test.mdb.ExpirationTestMDB.onMessage(ExpirationTestMDB.java:47)
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.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
at
org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
at
org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy221.onMessage(Unknown Source)
at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
at org.jboss.mq.SpySession.run(SpySession.java:323)
at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:595)
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:45 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Carlo de Wolf updated JBAS-4328:
--------------------------------
Comment: was deleted
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:27 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=all ]
Adrian Brock closed JBAS-4328.
------------------------------
Resolution: Rejected
Look. Unless you are going to write a testcase that proves your assertions
this issue is going to remain closed.
I know for a fact that it is untrue because the server side of JBossMQ
doesn't care what type of consumer it is.
It has a simple addMessage()/receive() api, where the processing is done
regardless (receive/message listeners/connection consumers, etc.).
The JMS semantics are a facade on top this.
I'm going to say what I should have in the beginning. Which is:
Take your help/discussion to the forums.
JIRA is for confirmed bug reports not speculative guesses into why your code doesn't
work.
You can re-open this bug report when you have some evidence that proves what you are
saying is true.
If that doesn't include a testsuite testcase then it should at least include some
TRACE logging
that shows the JMS Server got the request *after* the expiry time of the message.
I don't care what happened after that. If the MDB due to pool throttling or sleep()s
tried to delay delivery, this is not an issue for the JMS Server.
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:36 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=comments#action_12359201 ]
Adrian Brock commented on JBAS-4328:
------------------------------------
And if you want more real time behaviour it is trivial to write an interceptor that does:
if (isExpired(message))
{
log.warn("I'm not processing this messasge because it expired between being
received from the jms server and delivery to the mdb instance");
ejbContext.setRollbackOnly(); // NACK The message
return;
}
Once the message is NACKed backed to the control of the jms server, it is eligible again
for expiry processing.
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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:13 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4328) Message expiration doesn't work with a message listener on a session
[ http://jira.jboss.com/jira/browse/JBAS-4328?page=comments#action_12361433 ]
Dimitris Andreadis commented on JBAS-4328:
------------------------------------------
Forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042774
Message expiration doesn't work with a message listener on a
session
--------------------------------------------------------------------
Key: JBAS-4328
URL: http://jira.jboss.com/jira/browse/JBAS-4328
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBoss MQ
Reporter: Carlo de Wolf
Assigned To: Adrian Brock
The JCA uses session.setMessageListener which creates a SpyMessageConsumer with
sessionConsumer = true.
Messages are received and added to the SpyMessageConsumer (addMessage).
If it's a sessionConsumer do special logic (excluding expiration) else
put it on queue and receive() does expiration logic.
--
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
6450
days inactive
6472
days old
10 comments
3 participants
participants (3)
-
Adrian Brock (JIRA) -
Carlo de Wolf (JIRA)
-
Dimitris Andreadis (JIRA)