[
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