Re: Client's that can't conect to JMS service (openjms 0.7.6.1)

No. They are not compatible.

Fernando Zuriaga wrote:
> Can I upgrade only the server side to 0.7.7, with the clients with the
> 0.7.6.1 jars?? Thanks in advanced...
>
> -----Mensaje original-----
> De: openjms-user-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:openjms-user-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] En nombre de Tim
> Anderson Enviado el: martes, 24 de julio de 2007 15:12
> Para: [email protected]
> Asunto: Re: [openjms-user] Client's that can't conect to JMS service
> (openjms 0.7.6.1)
>
>
> The 0.7.6.x releases has an issue in the connection management that can
> cause deadlocks between
> clients and the server. This has been corrected in 0.7.7. I'd suggest
> upgrading.
>
> -Tim
>
> Fernando Zuriaga wrote:
>   
>> Hi, I have a big problem with a system in production enviroment: when
>> client's try to connect with the jms server, jms server create the
>> subscriber....
>>
>> 10:16:30.940 DEBUG [server-30] -
>> createSubscriber(topic=GisNotifications-true, name=null, clientId=1,
>> selector=RESOURCE_TYPE LIKE......
>>
>> ...but the following line doesnt's apperar in the server (it appear
>> when the server runs o.k)
>>
>> 10:16:30.940 DEBUG [server-30] -
>> createConsumerEndpoint(session=[sessionId=2b9088c9-c321-1004-8c7d-2bbb
>> 929ca3
>> 1c], clientId=1....
>>
>> The client wait in the line "subscriber =
>> session.createSubscriber(destination, selector, false);" forever.
>> Clients can connect to the server until stop-start the openjms server.
>> This error happens aleatory, when the server is running for 1 or 2
>> days.
>>
>> Thanks in advanced:
>> F.Zuriaga
>>
>>
>>
>>     


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/