10 EJB Client problem

Using JDev 10g I create an EJB and a test client for it. Everything is fine.
However when I try to run the client outside of JDeveloper (deployed to a jar file) I get
java -jar client.jar
java.lang.NoClassDefFoundError: javax/management/MBeanRegistrationException
at com.evermind.server.ThreadState.getCurrentState(ThreadState.java:206)
at com.evermind.server.rmi.RMIConnection.checkServletCaller(RMIConnection.java:3336)
at com.evermind.server.rmi.RMIConnection.<init>(RMIConnection.java:181)
at com.evermind.server.rmi.RMIServer.addNode(RMIServer.java:858)
at com.evermind.server.rmi.RMIServer.getConnection(RMIServer.java:923)
at com.evermind.server.rmi.RMIInitialContextFactory.getInitialContext(RMIInitialContextFactory.java:30
9)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at buslogic.MemberSearchEJBClient.getInitialContext(MemberSearchEJBClient.java:60)
at buslogic.MemberSearchEJBClient.main(MemberSearchEJBClient.java:22)

Looks like the classpath doesn't have the jar which contains MBeanRegistrationException class.
Make sure the jar file (looks like jmxri.jar has it) containing is part of the classpath used by the client application.
raghu
JDev Team

Similar Messages

[Jeveloper + EJB client - EJB on OAS] Problem connecting

I having problems getting a simple client from within JDeveloper 3.0(Code snippet - OAS/EJB Client) talking to a simple EJB on OAS 4.0.8.
I have deployed OK (red flag against status?) but when I run the client using port - 5512(ORB port)I get the message below
Anybody any ideas?
Creating an initial context
Looking for the EJB published as 'MyOASApp/MyEJB'
Naming exception occurred!
Cause: This may be an unknown URL, or some classes required by the EJB are missing from your classpath, or your OAS host is short of resources
Suggestion: Check the components of the URL, and make sure your project includes a library containing the EJB .jar files generated by the deployment utility.
[Root exception is java.net.UnknownServiceException: no content-type]javax.naming.NamingException: Failure to access http://hfxcap4:5512/ows-bin/rmproxy.ior; listener inaccessible or configured wrongly
at oracle.oas.jndi.oas.SiteResolver.getIOR(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveListenerURL(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteObject(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at package1.MyOASAppClient.main(Compiled Code)
**************

HI, I have the same problem that you had, maybe did you manage through ?? Thanks for all the help you could bring me.
Nico
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pFrooney:
Back Again ...
I have tried all ao the above
now using this code below but it fails on the lookup with the error message below:
..created library with client stub, using 1.1.8, moved OASRuntime to top of included libraries
Any suggestions
String oasUrl = "oas://hfxcap4:80";
String oasEJB = "MyOASApp/MyEJB" ;
// Setup the environment
Hashtable environment = new Hashtable();
// Turn JNDI on to OAS
environment.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "oracle.oas.naming.jndi.RemoteInitCtxFactory");
// Lookup the URL
conv_package.MyEJBHome homeInterface = null;
try {
System.out.println("Creating an initial context");
// Get initial JNDI context
Context site = (Context) ((new InitialContext(environment)).lookup(oasUrl));
org.omg.CORBA.COMM_FAILURE:
at oracle.oas.orb.CORBA.Request._invoke(Compiled Code)
at oracle.oas.orb.CORBA.Delegate._invoke(Compiled Code)
at org.omg.CORBA.portable.ObjectImpl._invoke(Compiled Code)
at oracle.oas.orb.CORBA.Delegate.is_a(Compiled Code)
at org.omg.CORBA.portable.ObjectImpl._is_a(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at CClient_package.MyOASAppClient.main(Compiled Code)<HR></BLOCKQUOTE>
null

Help: Problem in running a simple EJB client

Hi All,
I have just started learning EJB and I am facing an issue in running a client for the EJB I developed (a "Hello World" EJB)
I have deployed my application in Sun's reference implementation of j2ee server. I have the following client code through which I intend to access EJB methods
// EJB client code in main()
Context ctx = new InitialContext();
Object hwobj = ctx.lookup("HelloWorldApp");
HelloWorldHome hworldHome = (HelloWorldHome)
PortableRemoteObject.narrow(hwobj,HelloWorldHome.class); // exception here
HelloWorld hworld = hworldHome.create();
String msg = hworld.sayHelloWorld();
System.out.println(msg);
When I am running my client I am getting the following exception. Can anyone tell me why ?
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:296)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at HelloWorldClient.main(HelloWorldClient.java:13)
Thanks
Ratheesh

* I found the solution for this . Add j2ee.jar and Client jar returned by deploytool [ if we check return client jar ] to classpath when running client .
* Then I got CORBA_NO_PERMISSION error . After searching in forum , I found the solution. Posting
Forum Home > Enterprise JavaBeans
Topic: [ J2EE RI Server ] CORBA NO_PERMISSION 0
Welcome ratheeshpai!
Search Forum
Not watching this topic.
This topic has 4 replies on 1 page (Most recent message: Nov 19, 2002 7:59 AM)
[ J2EE RI Server ] CORBA NO_PERMISSION 0
Author: NicholasHsiao Oct 28, 2001 5:51 AM
Hi,
I was trying to deploy one simple session bean into J2EE RI Server. It works fine. And I wrote one client to access this session bean, it show me
java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No
Context ic = null;
try
ic = new InitialContext();
catch(Exception e)
System.out.println("1: "+e.toString());
This exception is happend when I try to lookup the jndi name
This error message is happend only on J2EE 1.3 (1.3_01) . If I downgrade to J2EE 1.3Beta or even 1.2, everything would be okay. Any one know how to solve such problem ??
Re: [ J2EE RI Server ] CORBA NO_PERMISSION 0
Author: cdunn5
In Reply To: [ J2EE RI Server ] CORBA NO_PERMISSION 0 Oct 31, 2001 10:04 PM
Reply 1 of 4
hi,
I don't know the solution but I have the exact same problem. I see your message was posted in October, have you found any solutions yet?
Re: [ J2EE RI Server ] CORBA NO_PERMISSION 0
Author: scottiep
In Reply To: [ J2EE RI Server ] CORBA NO_PERMISSION 0 Nov 22, 2001 11:21 AM
Reply 2 of 4
Da:Frederik Hansen ([email protected])
Message 2 in thread
Soggetto:Re: J2EE - NO_PERMISSION
Newsgroups:dk.edb.programmering.java
View this article only
Data:2001-11-10 03:32:12 PST
For at svare p� mit eget sp�rgsm�l: Access and Security Issues Q1: Some applications that ran under J2EE SDK 1.3
beta 2 stop running under the 1.3 FCS release with the
following message: java.rmi.AccessException: CORBA
NO_PERMISSION 0 No. Why does this happen and what
can be done about it? When your application ran under the 1.3 beta 2
version of the reference implementation (RI), security permissions may
not have
been checked. For example, the beta 2 RI allowed
calls to enterprise beans that required username-password permission,
even
when the client provided no username-password
information. With 1.3 FCS release, the J2EE SDK became strict
about checking adherence to the security policies of J2EE components. How can you make your application run under the
FCS release? 1.If you don't want security checks, do the
following: Use the deploytool to build a deployment
descriptor that does not require a strict security policy: Under the Security screen of the EJB wizard
or the Security tab of the EJB inspector in deploytool, click
"Deployment
Settings..". Under the box "Client
Authentication", make sure "Support Client Choice" is checked instead of
"Certificate"
or "Password". 2.To require the application pass security
checks to run, do the following: When an enterprise bean specifies
"Certificate" or "Password" as the method of Client Authentication, use
a J2EE
application client, instead of a stand-alone
Java application, to access the bean. You will need to login as a valid
J2EE
user.
By : scottiep
Thanks
Ratheesh

Problems by creating EJB Client

Hello,
I tried to create a EJB Client for OC4J in IDE Eclipse.
but I got the exception
javax.naming.NoInitialContextException: Cannot instantiate class: com.evermind.server.rmi.RMIInitialContextFactory. Root exception is java.lang.ClassNotFoundException: com.evermind.server.rmi.RMIInitialContextFactory
I don't know which classes or packages or jars i need to get my application started. I tried to find class
com.evermind.server.rmi.RMIInitialContextFactory
manually but I didn't find it.
Best regards
George

Hi,
you will find the class in ${ora9ias_install}/j2ee/home/oc4jclient.jar
Greetings,
Frank

I am getting this problem when running ejb client

Hi,
Any one help me , i am getting this error when i run my ejb Client
D:\sample\Client>
java -Djava.naming.factory.initial=com.sun.jndi.cosnamin
g.CNCtxFactory -Djava.naming.provider.url=iiop://localhost:1050 com.net.ejbexamples.slsb.EJBClient
Exception in thread "main" org.omg.CORBA.COMM_FAILURE: minor code: 1398079490
completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnectio
n.java:956)
at com.sun.corba.se.internal.iiop.IIOPConnection.send(IIOPConnection.jav
a:1017)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStre
am.java:71)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequest
Impl.java:82)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.
java:153)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNa
mingClient.java:195)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialRefe
rences(InitialNamingClient.java:260)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_r
eferences(InitialNamingClient.java:183)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.ja
va:1465)
at weblogic.iiop.IORManager.createInitialReference(IORManager.java:113)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContex
t(InitialContextFactoryImpl.java:96)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContex
t(InitialContextFactoryImpl.java:86)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
60)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at com.net.ejbexamples.slsb.EJBClient.main(EJBClient.java:15)
Thanks

Found in negative cache.... very strange.
RFC found in negative cache
What is the negative cache?

How can I run EJB Client in other computer ?

Hello,
I'm trying to run converter examples.
if ejb client pgm resides on a same machine with j2ee server , it works fine.
But when I put client pgm on a different maching
below message show.
No application client descriptors defined for: ConverterClinet
I put ConverterApp.ear, ConverterAppClient.jar and ConverterClient.class on the machine and
set APPCPATH=ConverterAppClient.jar
set VMARGS=-Dorg.omg.CORBA.ORBInitialHost=xxx.xxx.xx.xx
What should I do to run ejb client on different machine?

Hi SangHPark,
I had the same problem but have solved it and it works.
I ran the client remotely from a win98 box.
Keep two things in mind
1> Deploy the applications to an ip address and not to the local host using the deploy too. Use the deploy tool Gui to add a new server and then deploy the application to this ip address.
2> I am running j2ee version 1.3 and jsdk 1.3
Use the following code but instead of using "java:comp/env/ejb/SimpleConverter" use the jndi name of the object: "MyConverter" as specified in the tutorial.
Properties prop = new Properties();
prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
prop.setProperty(Context.PROVIDER_URL,"IIOP://xxx.xx.x.xxx:1050");
System.out.println("Attempting to create context...");
Context initial = new InitialContext(prop);
// Instead of this use the below line of code
//Object objref = initial.lookup("java:comp/env/ejb/SimpleConverter");
Object objref = initial.lookup("MyConverter");
// MyConverter is the Jndi name of the ConverterBean as per the tutorial
You need to do the following things.
1> After making changes to the code recompile using Ant and redeploy it.
2> Copy the j2ee.jar, ConverterAppClient.jar and ConverterClient.class file to the machine that u want to run the client from.
3> create a directory called "config" on the remote machine where you copied the files in step two.
4> Copy to this directory the files ejb.properties and security.properties from your j2ee_home\config\ directory.
For example you copied the files in step 2 on the remote machine in the c:\test directory. Create c:\test\config directory and copy the files from step 4 into this directory.
5> Run the following command from the directory where u copied the client files
java -Dorg.omg.CORBA.ORBInitialHost="host name" -classpath .\j2ee.jar;.;.\ConverterAppClient.jar ConverterClient
Monal

How to get remote ejb client working with Weblogic 8.1?

I have Weblogic 8.1 running on a WinXP box behind my firewall. Port 7001 is open to WL and remote browsers can access the console.
I have a client machine running WinXP on a different network that is remote to the WL server. It can ping the WL server machine.
I use JVM 1.4.2_08 on all machines.
If I put my client machine on the LAN with the WL server, then my EJB test client works fine. If I put the client machine on the remote network then the test client fails with a ClassCastException when trying to do a PortableRemoteObject.narrow on the bean home.
I had this running fine on JBoss 3.22 using RMI over HTTP. I added an HTTP invoker service to my jboss.xml file. I don't know if something similar is needed on the Weblogic side - any ideas on that? All I've done on the WL side is turn on Tunneling - which obviously works because the remote client gets a correct home object when doing a lookup on the bean - based on the IOR string of the home obj.
Below I include my client code, exception, ejb-jar.xml and my weblogic-ejb-jar.xml.
Any ideas on what else needs to be done so that a remote client can do a PortableRemoteObject.narrow? My client.jar has all of the EJB classes, and runs fine when run from LAN.
Thanks,
--BobC
Client Code
Properties p = new Properties();
p.put("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
p.put("java.naming.provider.url", "http://66.114.140.213:7001");
InitialContext ic = new InitialContext(p);
// Test register bean
Object homeObj = ic.lookup("tacplanner/register");
RegisterHome home = (RegisterHome) PortableRemoteObject.narrow(homeObj, RegisterHome.class); // <<< ClassCastException here
Exception
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at com.nimblus.tacplanner.test.TestUtils.<init>(TestUtils.java:60)
at com.nimblus.tacplanner.test.TestUtils.main(TestUtils.java:196)
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>register</ejb-name>
<home> com.nimblus.tacplanner.server.ejb.stateless.RegisterHome</home>
<remote> com.nimblus.tacplanner.server.ejb.stateless.Register</remote>
<ejb-class>com.nimblus.tacplanner.server.ejb.stateless.RegisterSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<resource-ref>
<description>The Oracle Datasource</description>
<res-ref-name>java:/OracleDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>register</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>register</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
</stateless-session-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<jndi-name>OracleDS</jndi-name>
</resource-description>
</reference-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>tacplanner/register</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
--------------------

Problem solved.
For remote clients you need to generate and use the stub classes for EJB interfaces using Weblogic's appc utility.
See: "http://e-docs.bea.com/wls/docs81/ejb/appc_ejbc.html#1151900"
--BobC

Error in running EJB Client on a remote machine

I delploy my beans and can run the EJB Client locally. However when I try to run the Client on another machine, there are errors.
Here is the errors
Syntax error
Out of environment space
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/enterprise/appclient/Main
I have follow the step in the j2ee tutorial and set the env variables according. Here is the bat file I write
set APPCPATH=CBSAppClient.jar
set VMARGS=-Dj2eelogin.name=guest -Dj2eelogin.password=guest123 -Dorg.omg.CORBA.ORBInitialHost=192.168.0.2
runclient -client CBSApp.ear -name CBSClient -textauth
Do anyone facing the same problem with me?
And how can I solve the problems?
This is really URGENT, please help

You are running on Windows 9x or Me, right? The darn OS has 300 or so bytes allocated for environment by default.
Try setting the Initial environment to 4096 in the Properties|Memory tab for the batch file. That will get rid of "Out of environment space". The syntax error is another matter; Windows (except NT and derivatives) shells do not allow '=' in an environment variables value. You cannot overcome that. Some software (Sybase for instance) interprets # as = just because of that. Unfortunately, the JVM doesn't take such an approach.
Better, grab copies of Unix utilities for Windows (www.gnu.org) including the wonderful shell 'bash' and write .sh scripts, which are inherently more powerful.

EJB Client Access From JDeveloper9iR2

I seem to be running into a lot of problems when trying to get a simple EJB client to talk to an EJB on our 9IAS platform. I have developed a simple session bean (just to test) which simply returns a string. When I create the default client code this works fine using the embedded OC4J server in Jdeveloper but I can't run a similar client against 9IAS when I deploy the code. When I go through the client wizard it seems to produce the same code as the standalone EJB OC4J client. I simply changed the name of the server (Context.PROVIDER_URL, "ormi://pe2500/). This is the parameter code I use:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
env.put(Context.PROVIDER_URL, "ormi://pe2500:23891/MyEJBs");
This is the output I receive:
D:\jdeveloper9ir2\jdk\bin\javaw.exe -ojvm -classpath D:\javadev\ejbservlet\ejbservlet\WEB-INF\classes;D:\jdeveloper9ir2\jdev\lib\jdev-rt.jar;D:\jdeveloper9ir2\j2ee\home\lib\ojsp.jar;D:\jdeveloper9ir2\j2ee\home\jsp\lib\taglib\ojsputil.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar;D:\jdeveloper9ir2\jdev\lib\ojc.jar;D:\jdeveloper9ir2\j2ee\home\lib\activation.jar;D:\jdeveloper9ir2\j2ee\home\lib\ejb.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaas.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaxp.jar;D:\jdeveloper9ir2\j2ee\home\lib\jcert.jar;D:\jdeveloper9ir2\j2ee\home\lib\jdbc.jar;D:\jdeveloper9ir2\j2ee\home\lib\jms.jar;D:\jdeveloper9ir2\j2ee\home\lib\jndi.jar;D:\jdeveloper9ir2\j2ee\home\lib\jnet.jar;D:\jdeveloper9ir2\j2ee\home\lib\jsse.jar;D:\jdeveloper9ir2\j2ee\home\lib\jta.jar;D:\jdeveloper9ir2\j2ee\home\lib\mail.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\lib\xmlparserv2.jar;D:\jdeveloper9ir2\lib\xmlcomp.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar Samplemypackage6.ctejb1Client3
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
     java.net.ConnectException: Connection refused: connect
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage6.ctejb1Client3.main(java.lang.String[])
          ctejb1Client3.java:18
Process exited with exit code 0.
Can anyone tell me if this is the correct communication method for client EJB's talking to the 9IAS server?
Any help really appreciated.
Chris Taylor

hi Chris Taylor, did you find the solution for this error. i too get this error and i am looking for the answer. if you find any answer please share with me too. if i get any answer for this i will reply you too.

Ejb client error

Hi, I use jdev 10g. I created a session bean with wizards and after that I created I Ejb client for that bean. When I start the embedded server and run the client java file I get the following error :
com.evermind.server.rmi.OrionRemoteException: jazn.com/admin is not allowed to call this EJB method, check your security settings (method-permission in ejb-jar.xml and security-role-mapping in orion-application.xml).
     at denemeSessionHome_StatelessSessionHomeWrapper1.create(denemeSessionHome_StatelessSessionHomeWrapper1.java:41)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
at connection to localhost/127.0.0.1 as admin
     at com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1527)
     at com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1480)
     at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
     at __Proxy0.create(Unknown Source)
     at ejbpackage.denemeSessionClient.main(denemeSessionClient.java:21)
Process exited with exit code 0.
all settings are the default ones.
Anyone has any idea???

hi
There was no problem with that... the AdviceClient is not in the package... I needed j2ee.jar and AdviceAppClient.jar to run the client and hte AdviceClient is in C\java\Projects\Advice directory.... can anyone help me with what is wrong with my first command which didnt work ...
java -classpath c:\Sun\AppServer\lib\j2ee.jar;c:\java\Projects\Advice;c:\java\Projects\AdviceAppClient.jar AdviceClient
This one worked though....
java -cp {$CLASSPATH}:"C:\java\Projects\Advice";AdviceAppClient.jar;c:\Sun\AppServer\lib\j2ee.jar; AdviceClient
I dont know what makes the difference...
vidhya

EJB client spawning threads

We've got problems with respect to the number of EJB client threads (ExecuteThread) spawned by WebLogic in a client JVM. As the number of threads increase (~1700 in a JVM with 512Mb of memory and 2 hours of uptime), the JVM performance degrades substantially - although almost all these threads are waiting for requests, as one can see in the thread dump attached bellow.
This problem happens in an integration scenario involving both WebLogic (8.1 and 6.1 as service providers) and webMethods Integration Server (version 6.0.1); the webMethods EJB adapter (version 1.2) acts like EJB client from the WebLogic instances, and the "EJB client spawning threads" can be detected by thread dumps extracted from the Integration Server JVM. The URL property from the wm EJB adapter has been setup as t3://server:port. The Integration Server runs with Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP), mixed mode) JRE in HP-UX (11.11) environment.
Although we couldn't reproduce this problem in a prod like environemnt, we'd identified that initially, WebLogic (weblogic.jar from WebLogic 6.1) spawns 5 ExecuteThreads plus 3 additional threads (TimeEventGenerator, SpinnerRandomSource and HighPriority TimeEventGenerator) in the first access of an EJB not matter the instance used, as well as two new threads (ExecuteThread) for each access to new WebLogic instances (different from previously accessed WebLogic instances). With weblogic.jar from the WebLogic 8.1 SP4 the behavior is slightly different: from the second instance access toward, only two new Threads (ExecuteThread in weblogic.JavaSocketReaders queue) are created.
We have also noticed that this problem should not be reflect of context classloaders because the counter of the ExecuteThread for the default pool only increases; in case of a pool cached in separate context classloaders, we should see "duplicate" threads with the same counter (starting with 0), which is not the case.
The questions are 1) why weblogic is spawning so much threads; 2) is there any setup/config to limit the number of WebLogic threads in the client context ?
Excerpt from the thread dump:
Full thread dump Java HotSpot(TM) Server VM (1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP) mixed mode):
"ExecuteThread: '1749' for queue: 'default'" daemon prio=10 tid=05734140 nid=4813 lwp_id=583942 in Object.wait() [0x0dfbe000..0x0dfbe4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
     at weblogic.common.internal.DynaQueue.getW(DynaQueue.java:228)
     - locked <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
     at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:252)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1742' for queue: 'default'" daemon prio=10 tid=04c263f0 nid=4812 lwp_id=583845 runnable [0x06449000..0x064494f0]
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:281)
     - locked <4a5ee690> (a java.net.Socket)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1735' for queue: 'default'" daemon prio=10 tid=05733fd8 nid=4811 lwp_id=583784 in Object.wait() [0x064ca000..0x064ca4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a6b8> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a6b8> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1734' for queue: 'default'" daemon prio=10 tid=01ecd940 nid=4810 lwp_id=583783 in Object.wait() [0x0654b000..0x0654b4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a728> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a728> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1733' for queue: 'default'" daemon prio=10 tid=05733e70 nid=4806 lwp_id=583777 in Object.wait() [0x066ce000..0x066ce4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a798> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a798> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1732' for queue: 'default'" daemon prio=10 tid=01ecd7d8 nid=4801 lwp_id=583771 in Object.wait() [0x065cc000..0x065cc4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a808> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a808> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1731' for queue: 'default'" daemon prio=10 tid=05733d08 nid=4798 lwp_id=583766 in Object.wait() [0x067d0000..0x067d04f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a878> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a878> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
... (cut for brevity)
"ExecuteThread: '2' for queue: 'default'" daemon prio=10 tid=009251b8 nid=172 lwp_id=569500 in Object.wait() [0x3d61f000..0x3d61f4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b4498> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b4498> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1' for queue: 'default'" daemon prio=10 tid=00924ee8 nid=171 lwp_id=569499 in Object.wait() [0x3d6a0000..0x3d6a04f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b40f0> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b40f0> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: 'default'" daemon prio=10 tid=00925050 nid=170 lwp_id=569498 in Object.wait() [0x3d7a2000..0x3d7a24f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b3d48> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b3d48> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"Thread-2" daemon prio=10 tid=00bec5f0 nid=18 lwp_id=569246 in Object.wait() [0x41e2e000..0x41e2e4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
     at com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr.run(RepoServer.java:1533)
     - locked <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
"Thread-1" daemon prio=10 tid=00bec488 nid=17 lwp_id=569244 in Object.wait() [0x41eaf000..0x41eaf4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.driver.queue.data.DataQueue.dequeue(DataQueue.java:310)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:260)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:254)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.app.repov4.server.RepoServerBase$RepoEventManager.run(RepoServerBase.java:224)
"Log Thread" prio=10 tid=00bec320 nid=16 lwp_id=569243 in Object.wait() [0x41f30000..0x41f304f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:171)
     - locked <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:126)
     - locked <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.app.b2b.server.ServerLogHandler$LogThread.run(ServerLogHandler.java:268)
"Cron Daemon" prio=10 tid=00bec1b8 nid=15 lwp_id=569241 in Object.wait() [0x41fb1000..0x41fb14f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15190> (a java.util.Vector)
     at com.wm.util.Cron.run(Cron.java:424)
     - locked <46c15190> (a java.util.Vector)
     at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool2" prio=10 tid=00bec050 nid=14 lwp_id=569240 in Object.wait() [0x42032000..0x420324f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15268> (a com.wm.util.pool.PooledThread)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
     - locked <46c15268> (a com.wm.util.pool.PooledThread)
     at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool1" prio=10 tid=00bebee8 nid=13 lwp_id=569239 in Object.wait() [0x420b3000..0x420b34f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152d0> (a com.wm.util.pool.PooledThread)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
     - locked <46c152d0> (a com.wm.util.pool.PooledThread)
     at java.lang.Thread.run(Thread.java:534)
"webMethods Integration Server" prio=10 tid=000870e0 nid=12 lwp_id=569238 in Object.wait() [0x42134000..0x421344f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.app.b2b.server.Server.run(Server.java:353)
     - locked <46c152f0> (a com.wm.app.b2b.server.Server)
"Signal Dispatcher" daemon prio=10 tid=00086f78 nid=7 lwp_id=569231 waiting on condition [0x00000000..0xffffffff]
"Finalizer" daemon prio=10 tid=00086e10 nid=5 lwp_id=569229 in Object.wait() [0x4293b000..0x4293b4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
     - locked <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
     at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:188)
"Reference Handler" daemon prio=10 tid=00086ca8 nid=4 lwp_id=569228 in Object.wait() [0x429bc000..0x429bc4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15340> (a java.lang.ref.Reference$Lock)
     at java.lang.Object.wait(Object.java:429)
     at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:120)
     - locked <46c15340> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=00086b40 nid=1 lwp_id=569222 in Object.wait() [0x68ff3000..0x68ff24f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Thread.join(Thread.java:1001)
     - locked <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Thread.join(Thread.java:1054)
     at com.wm.app.b2b.server.Server.start(Server.java:141)
     at com.wm.app.b2b.server.Main.main(Main.java:40)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.wm.proxy.Proxy.invokeStaticMethod(Proxy.java:166)
     at com.wm.app.server.ServerProxy.ServerMain_main(ServerProxy.java:77)
     at com.wm.app.server.ServerApp.start(ServerApp.java:105)
     at com.wm.app.Application.launch(Application.java:490)
     at com.wm.app.server.Main.main(Main.java:50)
"VM Thread" prio=7 tid=000167f8 nid=3 lwp_id=569227 runnable
"VM Periodic Task Thread" prio=8 tid=00016908 nid=11 lwp_id=569235 waiting on condition
"Suspend Checker Thread" prio=10 tid=00016880 nid=6 lwp_id=569230 runnable

We already opened a case. Actually, we did reproduce the problem: it happens because there is a hardware load balancing between the client and the WebLogic Server.
As far as I know, EJB load balancing can be done only with WebLogic clusters. Could you confirm that ?

ClassCastException exception while running EJB Client

Folks,
I am getting following exception while running the EJB Client.. I am
using WLS 5.1
Exception in thread "main" java.lang.ClassCastException
at
javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:319)
at FirstStatelessEJBClient.Client.lookupHome(Client.java:149)
at FirstStatelessEJBClient.Client.<init>(Client.java:44)
at FirstStatelessEJBClient.Client.main(Client.java:82)
Can anybody throw a light on this.
Thanks
Ashish

Hi Eduardo,
Below is my classpath. The stubs are in first_statlessSession.jar file.
CLASSPATH=C:\weblogic\myserver\first_statelessSession.jar;
C:\jdk1.2.2\lib\tools.jar;C:\weblogic\license;C:\weblogic\classes;C:\weblogi
c\lib\weblogicaux.jar;
C:\weblogic\myserver\clientclasses;C:\weblogic\myserver\serverclasses
Also, I am just compiling and deploying the
C:\weblogic\examples\ejb\basic\statelessSession myself and testing it. I
am
using the build.cmd files to compile and deploy the above EJB. If I use the
jars provided by weblogic it works fine with same above classpath.
I don't know what to do next. I have invested the whole day to solve this
problem and couldn't.
Please let me know if I am doing anything wrong.
Appreciate your help.
Thanks,
Ashish
Eduardo Ceballos wrote:
Try putting the stubs into the client class path.
"Ashish N. Shah" wrote:
Folks,
I am getting following exception while running the EJB Client.. I am
using WLS 5.1
Exception in thread "main" java.lang.ClassCastException
at
javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:319)
at FirstStatelessEJBClient.Client.lookupHome(Client.java:149)
at FirstStatelessEJBClient.Client.<init>(Client.java:44)
at FirstStatelessEJBClient.Client.main(Client.java:82)
Can anybody throw a light on this.
Thanks
Ashish

Two web apps using the same EJB client jar

I am currently deploying two web apps on a server. Both web apps use an EJB client
jar (the same jar) to access EJB's and both apps work when tested independently.
The problem arises when I log into app A and then log into app B. As soon as
I do app A loses it's references to the EJBHomes, and other classes.
It seems a classloader is unloading the first classes and instances loaded by
the first app and then loading them from app B's client.jar.
If I put the client.jar in the system classpath everything is fine, but that's
just a hack.
Is it not possible to deploy two web apps on a server using the same client.jar's
in their own WEB-INF/lib's?

Joe,
As Pravin mentions, the checking of those boxes in Workbench triggers scheduled jobs within the EAC that kicks off the scripts at the appropriate time/day. But as you've noticed, there's not a ton of flexibility and you don't get cron or Windows Scheduler-type capabilities.
If you need to do something special, you can manually kick off the report generation scripts from your control directory using the runcommand.bat (or sh) script or place the command into a cron/Windows Scheduler job:
For example, to kick off the WeeklyReports job, you would do this:
runcommand.sh WeeklyReports runSo, assuming you go down the route of creating multiple ReportGenerators and scripts, you would create a job to kick off the new script you've created at the appropriate time.
Hope that helps,
Patrick
http://branchbird.com

Java EJB client "Can't connect to ORB" errors...

I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

I finally found the answer to my problem.... in the Ant script I had
copied from another example, the "-iiop" was lacking in the ejbc
arguments - almost all of the examples assume you'll be calling EJBs
from within the container, instead of a stand-alone client, so they
don't use that flag.
Putting that "-iiop" flag into the ejbc arguments fixed everything.
Thanks, Shivani, for pointing out what is now obvious but was
mysterious.
Douglas Bullard
In article <[email protected]>,
[email protected] says...
I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

Deploying an EJB Client into 8iJVM

I have attempted several times without much success to load the client for an EJB in 8.1.7.
The difference between this EJB client and others is that it makes calls to BC4J to retrieve data.
The deployment fails with either mismatches in Aurora classes or referes me to loadjava trace file which I can not find.
Having not much success with including the other libraries in the advanced option of loading related libraries, including the JBO EJB runtime, I attampted to load all the jar and Zip files by hand, in this case I got alot of errors relating to the fact that the classes could not be resolved.
Does nay one have any ideas about the correct procedure in loading EJB code in 8.1.7 JVM, which make BC4J calls.
(Note: The EJB code will them make calls to other EJBs which use BC4J for persistace).
Many thanks.
Omeed.

Have you checked how many invalid java objects you have in the database? It may be the JVM was not correctly installed.
I tried to upgrade to 8.1.7 and had 250 java classes that were invalid because Designer R1 was not compatible with 8.1.7.
You can also try to load the EJB by hand and see if that is the problem.
Linda

10 EJB Client problem

Similar Messages

Maybe you are looking for