[jboss-jira] [JBoss JIRA] Closed: (JBAS-4328) Message expiration doesn't work with a message listener on a session

[Adrian Brock (JIRA)]

     [ 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