You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Lenin David Lozano Argel <ld...@avansoft.com> on 2009/01/30 20:47:06 UTC
Re: Problem with EJB container and JMS
Hi, I have the same problem with Geronimo or Wasce. The server never
shutdown, when a JMS Message is sent, and I cannot undeploy any module or
jms resource group. The only thing that I can do is re-install the server.
Beniamin Mazan wrote:
>
>
>
> Beniamin Mazan wrote:
>>
>>
>>
>> Kevan Miller wrote:
>>>
>>>
>>> On Aug 20, 2008, at 8:49 AM, Beniamin Mazan wrote:
>>>
>>>>
>>>>
>>>>
>>>> Kevan Miller wrote:
>>>>>
>>>>>
>>>>> On Aug 20, 2008, at 6:54 AM, Beniamin Mazan wrote:
>>>>>
>>>>>>
>>>>>> I've found strange Geronimo 2.1.2 behaviour with using JMS.
>>>>>>
>>>>>> 1) When message is waiting for delivery to MDB i cannot undeploy
>>>>>> module with
>>>>>> this MDB from command line. I have to stop module via G-console and
>>>>>> then
>>>>>> undeploy
>>>>>>
>>>>>> 2) If messages are waiting for delivery and I shutdown server
>>>>>> (geronimo
>>>>>> stop) and the run it again none of messages are delivered to
>>>>>> listener
>>>>>>
>>>>>> 3) When MDB onMessage method throws i.e. NullPointerException, the
>>>>>> transaction is rolledback but a) message is not being redelivered
>>>>>> anymore,
>>>>>> b) module couldn't be restarted == application stops working
>>>>>>
>>>>>> :(
>>>>>> Geronimo 2.1 hadn't these "features".
>>>>>
>>>>> Heh. Thanks Beniamin.
>>>>>
>>>>> 1). Do you have any undeploy failure information? stacktrace, etc
>>>>>
>>>>> 2). These are persistent messages?
>>>>>
>>>>> --kevan
>>>>>
>>>>>
>>>>>
>>>>
>>>> 1) No, only never-ending wait.
>>>> 2) yes
>>>
>>> So, is this the the scenario? The MDB in an onMessage() invocation and
>>> you're trying to undeploy?
>>>
>>> --kevan
>>>
>>>
>> Not exactly. I don't know where message directly is. I can't say that MDB
>> is in an onMessage() invocation but rather not. The message is waiting
>> during it's redelivery time.
>>
>
> I think that the better order for my cases is :
>
> 1A) If messages are waiting for delivery and I shutdown server (geronimo
> stop) and the run it again none of messages are delivered to listener
>
> 1B) When MDB onMessage method throws i.e. NullPointerException, the
> transaction is rolledback but a) message is not being redelivered
> anymore, b) module couldn't be restarted == application stops working
>
> and then
>
> 2) When message is waiting for delivery to MDB (not delivered after
> module's start) i cannot undeploy module with this MDB from command line.
> I have to stop module via G-console and then undeploy
>
>
--
View this message in context: http://www.nabble.com/Problem-with-EJB-container-and-JMS-tp19067050s134p21754350.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.