Re: Entity bean can not remove itself

[mahu2425 <ma...@lycos.de>]

Hello,

has nobody an idea if this migh be a bug or if I'm doing anything wrong? I really need this feature, that an entity bean can remove itself.

Could anybody help me?   ;-)


Best regards,

Markus



>  Hi there, 
>  
>  I have an entity bean (CMP) that uses the TimerService and includes 
>  the TimedObject interface. When the callback function ejbTimeout(Timer timer) 
>  on the entity bean is executed, the bean should remove itself. 
>  
>  
>  
>  My code looks like: 
>  
>  public void ejbTimeout(Timer timer) {
>    ejbRemove();
>  }
> 
> 
> I inserted a few debug statements and I'm sure that ejbTimeout() is executed. Unfortunally the 
> bean will not be removed.
> 
> Has anybody an idea what's going wrong or if this might be a bug? 
> 
> I also tried to remove the bean using the remove() method from the remote interface as well as
> removing it using the remove() method from the home interface. In both cases an exception will be 
> thrown (transaction rolled back, could not remove timer) and the server will be completly crash 
> (GBean DESTROYED message) and will no longer successfully startup at a restart. So, calling remove() 
> seems to be a bad idea, but ejbRemove() doesn't work (the Sun J2EE tutorial says ejbRemove() should 
> work).
> 
> What can I do to let the entity bean remove itself?
> 
> 
> Greets, Markus

Benachrichtigung bei E-Mail Empfang! - http://mail.lycos.de/app/lycosinside/setupLI.exe

Re: Failover of a JMS queue in Geronimo

[Aaron Mulder <am...@alumni.princeton.edu>]

Geronimo currently uses ActiveMQ 3.x, so anything you can configure
there can be used by Geronimo.  It would be possible, for example, to
set up an ActiveMQ cluster and point Geronimo at that rather than
using the embedded ActiveMQ broker in the Geronimo server.  We're
currently working on ActiveMQ 4.x integration, which offers still more
robust clustering/fail-over support.

Can you explain a bit more about what you're looking for?  Do you want
to just have a list of brokers so if Geronimo can't dispatch a message
to the first in the list it tries the second?  Or do you want Geronimo
to send every message to two brokers so if one fails the other can
take over?  Or something else?

Thanks,
    Aaron

On 7/4/06, Paul Craton <CR...@uk.ibm.com> wrote:
> Does anyone know if there is a way inside Geronimo to handle the failover
> of the JMS Queue ?
>
> I have a feeling the current answer is no but I was wondering if there were
> any plans to introduce this support in later releases?
>
> Any docs/additional information would be useful.
>
> Thx
>
> Paul Craton
>
>
>

Failover of a JMS queue in Geronimo

[Paul Craton <CR...@uk.ibm.com>]

Does anyone know if there is a way inside Geronimo to handle the failover
of the JMS Queue ?

I have a feeling the current answer is no but I was wondering if there were
any plans to introduce this support in later releases?

Any docs/additional information would be useful.

Thx

Paul Craton

Re: Entity bean can not remove itself

["D. Strauss" <ge...@ds-2.de>]

Hello, Markus

It's just a little bit difficult to understand why you (the user) should
handle the instance of a bean :-/ That's the job of the EJB container
(greetings to the OpenEJB people). Or can you post a scenario where you
definitely need to remove an EJB? Share your idea :P

AFAIK it's not your business to know too much of the EJB container and
its EJB instances :P

Best regards

Dirk

mahu2425 schrieb:
> Hello,
> 
> has nobody an idea if this migh be a bug or if I'm doing anything wrong? I really need this feature, that an entity bean can remove itself.
> 
> Could anybody help me?   ;-)
> 
> 
> Best regards,
> 
> Markus
> 
> 
> 
>>  Hi there, 
>>  
>>  I have an entity bean (CMP) that uses the TimerService and includes 
>>  the TimedObject interface. When the callback function ejbTimeout(Timer timer) 
>>  on the entity bean is executed, the bean should remove itself. 
>>  
>>  
>>  
>>  My code looks like: 
>>  
>>  public void ejbTimeout(Timer timer) {
>>    ejbRemove();
>>  }
>>
>>
>> I inserted a few debug statements and I'm sure that ejbTimeout() is executed. Unfortunally the 
>> bean will not be removed.
>>
>> Has anybody an idea what's going wrong or if this might be a bug? 
>>
>> I also tried to remove the bean using the remove() method from the remote interface as well as
>> removing it using the remove() method from the home interface. In both cases an exception will be 
>> thrown (transaction rolled back, could not remove timer) and the server will be completly crash 
>> (GBean DESTROYED message) and will no longer successfully startup at a restart. So, calling remove() 
>> seems to be a bad idea, but ejbRemove() doesn't work (the Sun J2EE tutorial says ejbRemove() should 
>> work).
>>
>> What can I do to let the entity bean remove itself?
>>
>>
>> Greets, Markus
> 
> Benachrichtigung bei E-Mail Empfang! - http://mail.lycos.de/app/lycosinside/setupLI.exe