.5 was meant to be this week, but I expect it will be a week or two late.

Carl.

ffrenchm wrote:
> I just updated the trunk and there is no exception raised currently - the session is only closed :
>
> INFO [apache.qpid.client.AMQSession] Closing session: org.apache.qpid.client.AMQSession_0_10@df1832 ...
>
> Do you have an idea when QPID M5 will be available ?
>
>
> ffrenchm wrote:
>   
>> Do I need to raise a JIRA for this exception problem (if it's one) or is there any convolution ?
>>
>> Thanks !
>>
>>
>> I test again exclusive queue through JNDI. My first listener create an exclusive queue. My second listener is blocked and wait that my first listner unlock my queue. I would prefer to get an exception in this case and not an simple debug message like this : 
>>
>> IoReceiver - /127.0.0.1:26969 2009-03-24 10:38:08,859 DEBUG [apache.qpid.transport.Connection] RECV: [conn:1c86be5] ch=0 ExecutionException(errorCode=RESOURCE_LOCKED, commandId=2, classCode=8, commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant exclusive access to queue TEST (qpid/broker/SessionAdapter.cpp:388), errorInfo={})
>>
>> is this possible ? 
>>
>> The problem is that after I get this exception because of timeout : 
>>
>> IoReceiver - /127.0.0.1:26969 2009-03-24 10:40:08,597 DEBUG [apache.qpid.transport.Connection] RECV: [conn:1c86be5] ch=0 ConnectionHeartbeat()
>> Exception in thread "main" org.apache.qpid.transport.SessionException: timed out waiting for sync: complete = 1, point = 3
>> 	at org.apache.qpid.transport.Session.sync(Session.java:684)
>> 	at org.apache.qpid.transport.Session.sync(Session.java:653)
>> 	at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:324)
>> 	at org.apache.qpid.client.AMQSession.close(AMQSession.java:647)
>> 	at org.apache.qpid.client.AMQSession.close(AMQSession.java:488)
>> 	at com.axway.test.queuer.QueueListener.JMSQListener.main(JMSQListener.java:168)
>>
>> And unfortunately it could be confusing and bad interpreted...
>>
>> Do I need to raise a JIRA ?
>>     
>
> This should be fixed on trunk and will be part of the 0.5 release. It 
> was an issue with the JMS clients exception handling tracked by QPID-1708.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>
>
>