activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: Killing activemq with connected JMS listener
Date Wed, 18 Mar 2009 18:37:02 GMT
You've registered a JMS ExceptionListener with the Connection ?

On 18 Mar 2009, at 18:06, mffrench wrote:

>
> must add I tested the same code with other queuers (QPID, ...) and I  
> get
> exception with these queuers ...
>
>
> mffrench wrote:
>>
>> yes my client is connected... and it only receive message (it's a jms
>> listener).
>> can you tell me what options I must set to enable the log level in  
>> the
>> activemq client ?
>>
>> Some netstat
>>
>> Before killing :
>>
>> tcp6       0      0 *:61611                 *:*                      
>> LISTEN
>> 18673/java
>> tcp6       0      0 localhost:35073         localhost:61611
>> ESTABLISHED18727/java
>> tcp6       0      0 localhost:61611         localhost:35073
>> ESTABLISHED18673/java
>>
>> After killing :
>>
>> tcp6       0      0 localhost:61611         localhost:35073
>> TIME_WAIT  -
>>
>> The listener is alway running and no exception is raised...
>>
>>
>> Gary Tully wrote:
>>>
>>> Is your client really connected? Has it sent or received a  
>>> message. With
>>> activemq, the connection is created on demand on first but not  
>>> when the
>>> connection factory is created.
>>> Can you enable debug logging and see what additional information  
>>> you can
>>> gather?
>>>
>>> 2009/3/18 mffrench <mffrench@axway.com>
>>>
>>>>
>>>> Here's my JNDI configuration :
>>>>
>>>> java.naming.factory.initial =
>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>> java.naming.provider.url = tcp://127.0.0.1:61611
>>>> connectionFactoryNames = MICHEL
>>>> queue.TEST = TEST
>>>>
>>>> As you can see I provide a brokerUrl with tcp://... and I never  
>>>> get any
>>>> exceptions...
>>>>
>>>>
>>>> Gary Tully wrote:
>>>>>
>>>>> If this is 5.2, and you do not provide a brokerUrl to your  
>>>>> activemq
>>>>> connection factory then the failover transport will be used by  
>>>>> default
>>>> and
>>>>> it will block waiting to reconnect.
>>>>> Provide a brokerUrl and use "tcp://..." and you will get the  
>>>>> exception
>>>> you
>>>>> require.
>>>>>
>>>>> 2009/3/18 mffrench <mffrench@axway.com>
>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> if I kill ActiveMQ, there is no exception raised to my  
>>>>>> connected JMS
>>>>>> listener and so my client doesn't detect the link is broken with
>>>>>> ActiveMQ.
>>>>>> I
>>>>>> think this is a bug which should be corrected. Is there any issue
>>>> about
>>>>>> this
>>>>>> ?
>>>>>>
>>>>>> Thanks
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>>> http://www.nabble.com/Killing-activemq-with-connected-JMS-listener-tp22576446p22576446.html
>>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://blog.garytully.com
>>>>>
>>>>> Open Source SOA
>>>>> http://FUSESource.com
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Killing-activemq-with-connected-JMS-listener-tp22576446p22583895.html
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>> -- 
>>> http://blog.garytully.com
>>>
>>> Open Source SOA
>>> http://FUSESource.com
>>>
>>>
>>
>>
>
> -- 
> View this message in context: http://www.nabble.com/Killing-activemq-with-connected-JMS-listener-tp22576446p22585097.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Mime
View raw message