RE: Werent current caller
Thanks for the hint, I'll give this a go. You must be intuitive as this parent child setting is what I'm trying to do, although I've also tried extracting the parent ID on the client side and then setting (via create) the parent key in the chils record as it's being created and this also throws the same exception. However OC4J may also be trying to reference the parent during this operation so the test is still worth conducting. I'll let you know the result. -Original Message- From: Lachezar Dobrev [SMTP:[EMAIL PROTECTED]] Sent: 08 April 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 _need_ to set the parent to be "reentrant=true". That helped me. My code required to create the child with a parameter like: (XML_Tag)entityContext.getEJBObject() so that the child knows it's parent... That requires reentrant=true. It _may_ be a shot in the dark, because I've not come upon this exception, but rather some other (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: Werent current caller 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) void com.evermind.server.ejb.EntityEJBHome.passivateAndRelease(com.evermind.serve r.ejb.EvermindEntityContext, boolean) void com.evermind.server.ejb.EntityEJBObject.releaseContext(boolean) com.neowurks.network.ejb.NetNwkEjb NetNwkEjbHome_EntityHomeWrapper57.create(long, java.lang.String, java.lang.String) java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread) void com.evermind.util.ThreadPoolThread.run() I've also received a mail that seems to indicate that the responder has only seen this in the oracle version of orion, which is the version I'm using. However OTN has been unavailable for the last day or so and I've not been able to check if there is any information there as well. This exception is being raised when I've successfully created the parent CMP and then try and create the child CMP, which then throws this. I'm working now to produce a focused piece of code to illustrate the client and server side without all of the other application baggage. -Original Message----- From: Scott Farquhar [SMTP:[EMAIL PROTECTED]] Sent: 06 April 2002 02:05 To: Orion-Interest Subject: Re: Werent current caller 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 a source where I can identify possible sources of this error and where I'm going wrong. > > I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. > > where to now? > > > -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World msg18676/bin0.bin Description: application/ms-tnef
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 _need_ to set the parent to be "reentrant=true". That helped me. My code required to create the child with a parameter like: (XML_Tag)entityContext.getEJBObject() so that the child knows it's parent... That requires reentrant=true. It _may_ be a shot in the dark, because I've not come upon this exception, but rather some other (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: Werent current caller 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) void com.evermind.server.ejb.EntityEJBHome.passivateAndRelease(com.evermind.serve r.ejb.EvermindEntityContext, boolean) void com.evermind.server.ejb.EntityEJBObject.releaseContext(boolean) com.neowurks.network.ejb.NetNwkEjb NetNwkEjbHome_EntityHomeWrapper57.create(long, java.lang.String, java.lang.String) java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread) void com.evermind.util.ThreadPoolThread.run() I've also received a mail that seems to indicate that the responder has only seen this in the oracle version of orion, which is the version I'm using. However OTN has been unavailable for the last day or so and I've not been able to check if there is any information there as well. This exception is being raised when I've successfully created the parent CMP and then try and create the child CMP, which then throws this. I'm working now to produce a focused piece of code to illustrate the client and server side without all of the other application baggage. -Original Message- From: Scott Farquhar [SMTP:[EMAIL PROTECTED]] Sent: 06 April 2002 02:05 To: Orion-Interest Subject: Re: Werent current caller 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 a source where I can identify possible sources of this error and where I'm going wrong. > > I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. > > where to now? > > > -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World
RE: Werent current caller
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) void com.evermind.server.ejb.EntityEJBHome.passivateAndRelease(com.evermind.server.ejb.EvermindEntityContext, boolean) void com.evermind.server.ejb.EntityEJBObject.releaseContext(boolean) com.neowurks.network.ejb.NetNwkEjb NetNwkEjbHome_EntityHomeWrapper57.create(long, java.lang.String, java.lang.String) java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread) void com.evermind.util.ThreadPoolThread.run() I've also received a mail that seems to indicate that the responder has only seen this in the oracle version of orion, which is the version I'm using. However OTN has been unavailable for the last day or so and I've not been able to check if there is any information there as well. This exception is being raised when I've successfully created the parent CMP and then try and create the child CMP, which then throws this. I'm working now to produce a focused piece of code to illustrate the client and server side without all of the other application baggage. -Original Message- From: Scott Farquhar [SMTP:[EMAIL PROTECTED]] Sent: 06 April 2002 02:05 To: Orion-Interest Subject: Re: Werent current caller 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 a source >where I can identify possible sources of this error and where I'm going wrong. > > I've searched the Orion support site and the only mails I can find are for 0.9.4 and >0.9.6 versions, and none fo these mails actually describe the conditions I have. > > where to now? > > > -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World msg18666/bin0.bin Description: application/ms-tnef
Re: Werent current caller
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 a source >where I can identify possible sources of this error and where I'm going wrong. > > I've searched the Orion support site and the only mails I can find are for 0.9.4 and >0.9.6 versions, and none fo these mails actually describe the conditions I have. > > where to now? > > > -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World
Re: Werent current caller
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 the right direction for Orion. What version of Orion are you using? Can you tell us a little more about what you are trying to do? If you have a test case (just a simple ear that I can deploy, and a separate zip'd source code file), send it to me at [EMAIL PROTECTED], and I'll look at it when I get a chance. Cheers Ray Jeff Lowcock <[EMAIL PROTECTED]> 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 a source where I can identify possible sources of this error and where I'm going wrong.I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have.where to now?Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax
Werent current caller
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 this error and where I'm going wrong. I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. where to now?
RE: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller]
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] - 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 with beans calling other Where is everyone getting 0.9.6? The latest at www.orionserver.com that I can find is 0.9.4. Furthermore, has anyone at Orion (or anyone else) seen the auto-reload problems I reported earlier? Thanks, Garret Wilson GlobalMentor, Inc.
Re: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.InternalError: Werent current caller]
run 'java -jar autoupdate.jar' in the orion directory to update. - Original Message - From: Garret Wilson <[EMAIL PROTECTED]> To: Orion-Interest <[EMAIL PROTECTED]> Sent: Tuesday, April 11, 2000 10:51 AM Subject: Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.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 > caller > > > > i tried out orion 0.9.6. I still have a problem with beans calling other > > Where is everyone getting 0.9.6? The latest at www.orionserver.com that I > can find is 0.9.4. > > Furthermore, has anyone at Orion (or anyone else) seen the auto-reload > problems I reported earlier? > > Thanks, > > Garret Wilson > GlobalMentor, Inc. > > >
Orion 0.9.6 [was: Re: Error in ejbPassivate: java.lang.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 caller > i tried out orion 0.9.6. I still have a problem with beans calling other Where is everyone getting 0.9.6? The latest at www.orionserver.com that I can find is 0.9.4. Furthermore, has anyone at Orion (or anyone else) seen the auto-reload problems I reported earlier? Thanks, Garret Wilson GlobalMentor, Inc.
Error in ejbPassivate: java.lang.InternalError: Werent current caller
Hi again,
i tried out orion 0.9.6. I still have a problem with beans calling other
beans (see the attached mail). I noticed that the error message changed a
bit, so I assume, that you are currently searching for an error ?
I want to know, if this error may be caused due to conceptional design
errors of my beans or if it is a real error of orion. I must know this as
soon as possible since changing the whole design of my software should be
done as soon as possible. The "new" error message is:
java.rmi.RemoteException: Transaction was rolled back: Error in
ejbPassivate: 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)
at com.evermind.server.ejb.EntityEJBObject.releaseContext(JAX,
Compiled Code)
at com.evermind.server.ejb.EntityEJBObject.removeFromCache(JAX)
at com.evermind.server.ejb.EntityEJBObject.aal(JAX)
at com.evermind.server.ApplicationServerTransaction.commit(JAX)
at com.evermind.server.ApplicationServerTransaction.end(JAX,
Compiled Code)
at EntityBeanWrapper0.setVars(EntityBeanWrapper0.java, Compiled
Code)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.a8.run(JAX)
at com.evermind.server.rmi.a6.gk(JAX, Compiled Code)
at com.evermind.server.rmi.a6.run(JAX, Compiled Code)
at com.evermind.util.e.run(JAX, Compiled Code)
at com.evermind.server.rmi.a6.invokeMethod(JAX)
at com.evermind.server.rmi.ay.invoke(JAX)
at __Proxy1.setVars(Unknown Source)
at de.netmedia.ejb.test.clienttest.main(clienttest.java:88)
I also had a look at the setEntityBean function generated by orion:
public void setEntityBean(EntityBean entitybean)
{
if(entitybean == null && object != null && ThreadState.getCurrentState()
!= currentCaller)
{
throw new InternalError("Werent current caller, server stacktrace: "
+ EJBUtils.toString(new Throwable("Werent current caller")));
} else
{
object = (NMejbBaseBean)entitybean;
return;
}
}
Obviously the problem has something to do with thread handling. Is there a
possibillity to force orion to use just one thread ? This should resolve the
problem (at least i could use the new orion to test it further - testing
0.9.4 isn't worth the effort any more) until the real problem is solved...
Kind regards,
Jens Stutte
P.S.: Concerning the "lack of response": Sometimes it would be very useful
just to send an answer like "we are working on it", "we know this problem"
etc. especially for bug-reports. This ejbPassivate problem for example for
me (and my company) is quite serious, so knowing as soon as possible
something would be very helpfull. I can imagine the stress you are having in
these days, and i want to give you good feedback on your product to make it
become better (and i am quite sure that we'll buy orion once it's finished
:-).
[EMAIL PROTECTED], http://www.net-media.de
NetMedia GmbH
Neugrabenweg 5-7
66123 Saarbruecken
Germany
fon: +49 (0) 681 - 37 98 8 - 0
fax: +49 (0) 681 - 37 98 8 - 99
Hi,
i have a strange benaviour of both orion 0.9.4q and 0.9.4v (but not with
0.9.4). I have a business method in an entity bean, which itself calls
business methods in other entity beans (same type, but different instances).
I have a remote client, that basically does nothing but call this method -
and nothing after this call.
>From my own log files i can see, that the method is executed successfully.
However, after this execution the server initiates first two ejbStore ops
(on each bean touched by the method), and after this (appearantly
unmotivated) an ejbLoad on some bean. However, 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(JAX)
at com.evermind.server.rmi.av.invoke(JAX)
at __Proxy1.setBeanReference(Unknown Source)
at de.netmedia.ejb.test.clienttest.main(clienttest.java:77)
What does this mean ? My ejbPassivate function does only set some variables
in the bean to null / 0. I could not figure out any information on "Werent
current caller" at javasoft.com. Is it an exception generated by orion ? By
the JVM (I'm using Linux, Sun JDK 1.2.2 on the server and windows NT Sun JDK
1.2.2 on the client) ? And why the client recieves an exception for a
function, that only the server executes on its will (and not on client
requests) ?
Does anyone know, what happens ?
Jen
Error in ejbPassivate: java.lang.InternalError: Werent current caller
Hi, i have a strange benaviour of both orion 0.9.4q and 0.9.4v (but not with 0.9.4). I have a business method in an entity bean, which itself calls business methods in other entity beans (same type, but different instances). I have a remote client, that basically does nothing but call this method - and nothing after this call. >From my own log files i can see, that the method is executed successfully. However, after this execution the server initiates first two ejbStore ops (on each bean touched by the method), and after this (appearantly unmotivated) an ejbLoad on some bean. However, 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(JAX) at com.evermind.server.rmi.av.invoke(JAX) at __Proxy1.setBeanReference(Unknown Source) at de.netmedia.ejb.test.clienttest.main(clienttest.java:77) What does this mean ? My ejbPassivate function does only set some variables in the bean to null / 0. I could not figure out any information on "Werent current caller" at javasoft.com. Is it an exception generated by orion ? By the JVM (I'm using Linux, Sun JDK 1.2.2 on the server and windows NT Sun JDK 1.2.2 on the client) ? And why the client recieves an exception for a function, that only the server executes on its will (and not on client requests) ? Does anyone know, what happens ? Jens Stutte [EMAIL PROTECTED], http://www.net-media.de NetMedia GmbH Schubertstr. 8 66111 Saarbruecken Germany fon: +49 (0) 681 - 37 98 80 fax: +49 (0) 681 - 33 89 3
