RE: Werent current caller

2002-04-08 Thread Jeff Lowcock
2002 09:06 To: Orion-Interest Subject: Re: Werent current caller Hello. By the message, I would assume (correct me), that you have a parent/child relation. I may _guess_, that you are trying to use the parent to set something in the child (like the parent ID). If this is the case, you might

Re: Werent current caller

2002-04-08 Thread Lachezar Dobrev
can't remember which though). However, this is no-cost test and is worth trying. Lachezar. - Original Message - From: "Jeff Lowcock" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Saturday, April 06, 2002 9:56 AM Subject: RE:

RE: Werent current caller

2002-04-05 Thread Jeff Lowcock
This is the stack trace from the server. java.lang.InternalError: Werent current caller, server stacktrace (to disable this message, use -Dejb.assert=false at startup): java.lang.Throwable: Werent current caller void NetNwkEjb_EntityBeanWrapper41.setEntityBean(javax.ejb.EntityBean

Re: Werent current caller

2002-04-05 Thread Scott Farquhar
Can you post the stack trace? Jeff Lowcock wrote: > I'm getting this exception and message raised in the server when I'm attempting to >create a new CMP instance. I cannot find any documentation on this message and way >too much on the exception java.lang.InternalError, can anyone direct me to

Re: Werent current caller

2002-04-05 Thread Ray Harrison
Oddly, I've only run into this using OC4J (I don't remember what the problem was off hand, its been a while). But you may want to join the OTN (Oracle Technology Network) (its free) and search their J2EE forum. Since the two products are kissing cousins, what has worked for OC4J will point you in

Werent current caller

2002-04-05 Thread Jeff Lowcock
I'm getting this exception and message raised in the server when I'm attempting to create a new CMP instance. I cannot find any documentation on this message and way too much on the exception java.lang.InternalError, can anyone direct me to a source where I can identify possible sources of thi

RE: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller]

2000-04-11 Thread Alex Paransky
Use java -jar autoupdate.jar in the orion directory. -AP_ -Original Message- From: Garret Wilson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 11, 2000 7:51 AM To: Orion-Interest Subject: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller

Re: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller]

2000-04-11 Thread James Birchfield
.InternalError: Werent current caller] > - Original Message - > From: Jens Stutte <[EMAIL PROTECTED]> > To: Orion-Interest <[EMAIL PROTECTED]> > Sent: Tuesday, April 11, 2000 5:53 AM > Subject: Error in ejbPassivate: java.lang.InternalError: Werent current >

Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller]

2000-04-11 Thread Garret Wilson
- Original Message - From: Jens Stutte <[EMAIL PROTECTED]> To: Orion-Interest <[EMAIL PROTECTED]> Sent: Tuesday, April 11, 2000 5:53 AM Subject: Error in ejbPassivate: java.lang.InternalError: Werent current caller > i tried out orion 0.9.6. I still have a problem wit

Error in ejbPassivate: java.lang.InternalError: Werent current caller

2000-04-11 Thread Jens Stutte
bPassivate: java.lang.InternalError: Werent current caller, server stacktrace: java.lang.Throwable: Werent current caller at EntityBeanWrapper2.setEntityBean(EntityBeanWrapper2.java, Compiled Code) at com.evermind.server.ejb.EntityEJBHome.aam(JAX, Compiled Code)

Error in ejbPassivate: java.lang.InternalError: Werent current caller

2000-03-29 Thread Jens Stutte
on the server side everything seems to be ok: no exceptions, no core dumps... Meanwhile the client recieves a: java.rmi.RemoteException: Transaction was rolled back: Error in ejbPassivate: java.lang.InternalError: Werent current caller at com.evermind.server.rmi.a3.invokeMethod(