×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Exception creating CMP bean using JDeveloper: "Werent current caller"

Exception creating CMP bean using JDeveloper: "Werent current caller"

Exception creating CMP bean using JDeveloper: "Werent current caller"

(OP)
Hi there,

I am trying to run a CMP entity bean on an oc4j server using JDeveloper to create and deploy the bean and a sample application. The bean is created using an existing DB table.

The reading part is all working, I can find a bean using its primary key. But when it comes to creating a new bean I get the following exception:

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 Person_EntityBeanWrapper4.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)
de.fiscus.sfs.cmp.Person PersonHome_EntityHomeWrapper6.create(long)
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()

void com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(java.lang.Throwable)
java.lang.Object com.evermind.server.rmi.RMIConnection.invokeMethod(com.evermind.server.rmi.RMIContext, long, long, java.lang.reflect.Method,
java.lang.Object[])
java.lang.Object com.evermind.server.rmi.RemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
java.lang.Object com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[])
de.fiscus.sfs.cmp.Person __Proxy0.create(long)
void SamplePersonClient2.main(java.lang.String[])

Any idea?

Thank you!
Chris
Replies continue below

Recommended for you

RE: Exception creating CMP bean using JDeveloper: "Werent current caller"

I have the same problem. Have you solved it?

RE: Exception creating CMP bean using JDeveloper: "Werent current caller"

(OP)
Yes, I did solve the problem.

This happened when I generated an Container Managed Persistence Bean with JDeveloper, and deployed it. I could use that bean with a client and retrieve a specific instance using the home interface's findByPrimaryKey() method. I could not create a new bean using the home interface's create( primaryKey) method. The following Exception occurred:
java.lang.InternalError: Werent current caller

The problem was an SQL Exception that occurred in the CMP area I could not see. To make such SQL Exceptions visible (in my case it was a database constraint violation), set the system variable ejb.assert to false for the OC4J server at startup by modifying the startup command:
java -Dejb.assert=false -jar %OC4J_HOME%\oc4j.jar

This feature is undocumented but working.

Hey, if this works for you let me know.

CU, Chris

RE: Exception creating CMP bean using JDeveloper: "Werent current caller"

Hi Chris
I was having a similar problem in using the OC4j as applied to CMP bean.I'm using OC4J on Windows 2000 and was not able to make out as in which file should i change the value of the variable.I shall be highly obliged if u can send me the solution to this problem ASAP.
Thanx and Cheers!!!
Rahul

RE: Exception creating CMP bean using JDeveloper: "Werent current caller"

(OP)
Hi Rahul,

you can't find this variable in a configuration file but you can set it in the environment of the OC4J process. Just add the variable when you start OC4J with the -D option of Java (refer to my last message).

CU, Chris

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close