EJB- HRS and Client Error

This is the error i get when i do the 1st part of the Human resource reservation in Jdeveloper tutorial:
what could cause the error:
C:\jdeveloper\jdk\bin\javaw.exe -ojvm -XXdebug,quiet,port1033 -classpath C:\jdeveloper\jdev\mywork\MyHRApplication\EJB-Tier\classes;C:\jdeveloper\jdev\lib\jdev-rt.jar;C:\jdeveloper\j2ee\home\lib\activation.jar;C:\jdeveloper\j2ee\home\lib\ejb.jar;C:\jdeveloper\j2ee\home\lib\jaas.jar;C:\jdeveloper\j2ee\home\lib\jaxp.jar;C:\jdeveloper\j2ee\home\lib\jcert.jar;C:\jdeveloper\j2ee\home\lib\jdbc.jar;C:\jdeveloper\j2ee\home\lib\jms.jar;C:\jdeveloper\j2ee\home\lib\jndi.jar;C:\jdeveloper\j2ee\home\lib\jnet.jar;C:\jdeveloper\j2ee\home\lib\jsse.jar;C:\jdeveloper\j2ee\home\lib\jta.jar;C:\jdeveloper\j2ee\home\lib\mail.jar;C:\jdeveloper\j2ee\home\oc4j.jar;C:\jdeveloper\lib\xmlparserv2.jar;C:\jdeveloper\lib\xmlcomp.jar Samplehr.hrAppClient
Debugger connected to local process.
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 Samplehr.hrAppClient.main(java.lang.String[])
          hrAppClient.java:18
Debugger disconnected from local process.
Process exited with exit code 0.

Try below solution :
1. Take a copy of HReports.jar (Updated file) from the FR Report Server instance.
2. Bring the copied file to the User's Local Workstation and replace it with the one located under %HYPERION_HOME%\products\biplus\lib
3. Re-launch the FR Studio.
4. Open any of the FR Reports and now it can successfully print preview the FR Reports from the FR Studio.
above error happens if any FR patch is installed on FR server but not on client. So try above and if it does not resolve then make sure server and client has same patch level.

Similar Messages

[b]EJB Hotel RA Client Error - HELP[/b]

1. Travel schema installed fine
2. Web Client can successfully be run and all the buttons
work fine
3. The only file I modified was in config properties.
Provider_Url = ormi://localhost:8888/OneEJBHotel
4. in oc4j directory: principals file:
user id is "admin", and password was given as
"admin"
4. deployment from jdeveloper is fine as follows:
---- Deployment started. ---- Jan 24, 2003 6:24:08 PM
Wrote EJB JAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel.jar
Wrote WAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.war
Wrote EAR file to C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.ear
Invoking OC4J admin tool...
C:\jdeveloper\jdk\jre\bin\javaw.exe -jar C:\jdeveloper\j2ee\home\admin.jar ormi://DLEE/ admin **** -deploy -file C:\oc4j\samples\ejb\OneEJBHotel\src\oracle\otnsamples\OneEJBHotel\OneEJBHotel-Web.ear -deploymentName OneEJBHotel
Auto-unpacking C:\oc4j\j2ee\home\applications\OneEJBHotel-Web.ear... done.
Auto-unpacking C:\oc4j\j2ee\home\applications\OneEJBHotel-Web\OneEJBHotel-Web.war... done.
Copying default deployment descriptor from archive at C:\oc4j\j2ee\home\applications\OneEJBHotel-Web/META-INF/orion-application.xml to deployment directory C:\oc4j\j2ee\home\application-deployments\OneEJBHotel...
Auto-deploying OneEJBHotel (New server version detected)...
Exit status of OC4J admin tool (-deploy): 0
C:\jdeveloper\jdk\jre\bin\javaw.exe -jar C:\jdeveloper\j2ee\home\admin.jar ormi://DLEE/ admin **** -bindWebApp OneEJBHotel OneEJBHotel-Web http-web-site /OneEJBHotel
Exit status of OC4J admin tool (-bindWebApp): 0
Use the following context root(s) to test your web application(s):
http://DLEE:8888/OneEJBHotel
Elapsed time for deployment: 14 seconds
---- Deployment finished. ---- Jan 24, 2003 6:24:22 PM
5. System Configuation
jdeveloper: 9.0.3.1035
DB: oracle 92010
oc4j: 9.0.3.0.0
6. When run from jdeveloper client: run Client.jpr
the following errors were generated:
Process exited with exit code 0.
C:\jdeveloper\jdk\bin\javaw.exe -ojvm -classpath C:\oc4j\samples\ejb\OneEJBHotel\src\classes;C:\oc4j\samples\ejb\OneEJBHotel\config;C:\oc4j\samples\ejb\OneEJBHotel;C:\oc4j\samples\ejb\OneEJBHotel\src\web;C:\jdeveloper\jdev\lib\jdev-rt.jar;C:\jdeveloper\j2ee\home\lib\activation.jar;C:\jdeveloper\j2ee\home\lib\ejb.jar;C:\jdeveloper\j2ee\home\lib\jaas.jar;C:\jdeveloper\j2ee\home\lib\jaxp.jar;C:\jdeveloper\j2ee\home\lib\jcert.jar;C:\jdeveloper\j2ee\home\lib\jdbc.jar;C:\jdeveloper\j2ee\home\lib\jms.jar;C:\jdeveloper\j2ee\home\lib\jndi.jar;C:\jdeveloper\j2ee\home\lib\jnet.jar;C:\jdeveloper\j2ee\home\lib\jsse.jar;C:\jdeveloper\j2ee\home\lib\jta.jar;C:\jdeveloper\j2ee\home\lib\mail.jar;C:\jdeveloper\j2ee\home\oc4j.jar oracle.otnsamples.OneEJBHotel.client.EJBHotelSample
javax.naming.NamingException: Lookup error: java.io.IOException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791; nested exception is:
     java.io.IOException: Server protocol was not ORMI, if uncertain about the port your server uses for ORMI then use the default, 23791
     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 oracle.otnsamples.OneEJBHotel.client.EJBHotelSample.getHotelSystemBean()
          EJBHotelSample.java:132
     void oracle.otnsamples.OneEJBHotel.client.EJBHotelSample.main(java.lang.String[])
          EJBHotelSample.java:147
Process exited with exit code 0.
Thanks for help!
David

David,
config.properties is used only by the client.jpr. Not by the Web.jpr
config.properties file has been provided for looking up resources[EJB, Datasources] from JNDI tree of OC4J.
Since servlet and other resources are in the same container[Single JVM] there is no need to specify the username, password, Provdier_URL at the time of lookup.
Look at the init method of EJBHotelServlet.java :
Context ctx = new InitialContext();
// Acquire the home interface handle and call the create
//method on it
homeInterface = (HotelSystemHome)ctx.lookup("OneEJBHotel");
Here servlet looks up EJB without any authentication information, as servlet and EJB are in the same container.
Whereas Stand alone client is running outside the OC4J.
So the stand alone client need to authentcate itself for looking up the resources from JNDI tree.
Look at the getHotelSystemBean method of EJBHotelSample.java :
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, prop.getProperty("Initial_Context_Factory"));
env.put(Context.SECURITY_PRINCIPAL, prop.getProperty("Principal"));
env.put(Context.SECURITY_CREDENTIALS, prop.getProperty("Credential"));
env.put(Context.PROVIDER_URL, prop.getProperty("Provider_Url") );
// Associate the properties with the context
Context ctx = new InitialContext(env);
// Acquire the home interface handle and call the create
//method on it
homeInterface = (HotelSystemHome)ctx.lookup("OneEJBHotel");
Here stand alone client looks up EJB by specifying the authentication information, as stand alone client and EJB are running in different JVM's.
Hope this helps...
Cheers
--Venky

Question on EJB, JNDI and client jars

Hi,
This is a very fundamental question on EJBs and their clients - what
all should go into the client jar of an ejb?
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?
Any help would be greatly appreciated. Pointers to material on the
internet which explain this/related things in detail would be a great
help.
Thank you,
Anoushka

"Anoushka" <[email protected]> writes:
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?Most protocols (IIOP, T3, JRMP) provide a slot for encoding a codebase
in RMI requests. The codebase is usually an http URL that specifies
where to get classes that are not currently available to the
client. This URL is used to construct a java.net.URLClassLoader which
then downloads classes on demand. These classes can include stubs,
object arguments - pretty much anything you like. There are certain
security restrictions on the URLClassLoader which is why you sometimes
have to specifiy a security manager in a client. T3 will for
preference generate stubs in the client rather than download them,
however this is not allowed in an applet - and so in this case T3 will
also download stubs from the server.
The net of this is that you don't have to put very much at all in a
client jar UNLESS you can't use the URLClassLoader. In that instance
you have to put EVERYTHING you need in the client jar.
HTH
andy

Fundamental question on EJB, JNDI and client jars

Hi,
This is a very fundamental question on EJBs and their clients - what
all should go into the client jar of an ejb?
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?
Any help would be greatly appreciated. Pointers to material on the
internet which explain this/related things in detail would be a great
help.
Thank you,
Anoushka

hello,
well, the process is fairly simple actually.. The client needn't necessarily have
the container generated stub. as a client u could contact what is known as a boot-strap
service to download the stub over the wire.. infact one of the advantages of RMI
is precisely that. and since RMI is the underlying architecture of EJBs, it all
becomes rather simple. when u 'lookup' a bean, what u are in essence doing is
asking the server to send down the stub to your JVM. well.. right now this is
what i got time for..i will try to post a lengthier explanation in a couple of
days at leisure..
Vijay
"Anoushka" <[email protected]> wrote:
>
Hi,
This is a very fundamental question on EJBs and their clients - what
all should go into the client jar of an ejb?
I know for sure that just the remote and home interface classes of the
ejb are sufficient on the client's classpath to work with an EJB on a
totally different server, but I dont understand the logic behind it.
If the client has to pass its object parameters over the network to
the server where the ejb bean is located, should the container
generated stub not be present on the client's classpath? After the
client does the JNDI lookup of the ejb home on the server, how does it
serialize and pass the parameters over the network if the container
generated stub is not present?
Any help would be greatly appreciated. Pointers to material on the
internet which explain this/related things in detail would be a great
help.
Thank you,
Anoushka

Error while running EJB from java client on JBOSS

Hi
As i am new to EJB i have created a helloworld application in ejb which is working fine when i try to call it from servlet but when i try to invoke the same ejb from java client (i.e from diff jvm) on jboss i got the following error:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]]
     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1399)
     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.gl.TestClient.main(TestClient.java:39)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
     at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
     ... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:228)
     ... 5 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at java.net.Socket.connect(Socket.java:469)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:266)
     at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
     at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
     ... 5 more
Following is my code:
Home Interface:
package com.gl;
import javax.ejb.CreateException;
public interface testHome extends EJBHome {
     String JNDI_NAME = "testBean";
     public     test create()
     throws java.rmi.RemoteException,CreateException;
Remote Interface:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBObject;
public interface test extends EJBObject {
     public String welcomeMessage() throws RemoteException;
Bean:
package com.gl;
import java.rmi.RemoteException;
import javax.ejb.EJBException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
public class testbean implements SessionBean {
     public void ejbActivate() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void ejbPassivate() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void ejbRemove() throws EJBException, RemoteException {
          // TODO Auto-generated method stub
     public void setSessionContext(SessionContext arg0) throws EJBException,
               RemoteException {
          // TODO Auto-generated method stub
     public void ejbCreate(){}
     public String welcomeMessage(){
          return "Welcome to the World of EJB";
ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>testBean</ejb-name>
<home>com.gl.testHome</home>
<remote>com.gl.test</remote>
<ejb-class>com.gl.testbean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
jboss.xml:
<?xml version='1.0' ?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
<jboss>
<enterprise-beans>
<entity>
<ejb-name>testBean</ejb-name>
<jndi-name>testBean</jndi-name>
</entity>
</enterprise-beans>
</jboss>
Client code:
package com.gl;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
public class TestClient {
     public static void main(String[] args) throws Exception{
               try{
               /*     Properties props=new Properties();
                    props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
                    props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
                    props.put(Context.PROVIDER_URL, "jnp://localhost:1099");
               Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL, "localhost:1099");
                    System.out.println("Properties ok");
                    //env.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
                    //env.put(Context.PROVIDER_URL,"http://localhost:8080");
                    //env.put(Context.SECURITY_PRINCIPAL, "");
                    //env.put(Context.SECURITY_CREDENTIALS, "");
                    Context ctx=new InitialContext(props);
                    System.out.println("context ok");
                    //testHome home = (testHome)ctx.lookup("testBean");
                    Object obj = ctx.lookup ("testBean");
                    System.out.println("ojb = " + obj);
                    testHome ejbHome = (testHome)PortableRemoteObject.narrow(obj,testHome.class);
               test ejbObject = ejbHome.create();
               String message = ejbObject.welcomeMessage();
                    System.out.println("home ok");
                    System.out.println("remote ok");
                    System.out.println(message);
                    catch(Exception e){e.printStackTrace();}
I am able to successfully deployed my ejb on JBOSS but i m getting above error when i am trying to invoke ejb from java client.
kindly suggest me something to solve this issue.
Regards
Gagan
Edited by: Gagan2914 on Aug 26, 2008 3:28 AM

Is it a remote lookup? Then maybe this will help:
[http://wiki.jboss.org/wiki/JBoss42FAQ]
- Roy

Steps to deploy an ejb application and running an ejb client in weblogic server6.1

steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet

Hi.
Check out the beanManaged example that ships with WLS and read the accompanying docs. This
is a simple EJB with a servlet that invokes it.
Michael
shekhar sachdev wrote:
steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet--
Michael Young
Developer Relations Engineer
BEA Support

Just installed Mac OS X 10.8.5 on a Mac Pro 2010 platform. The App Store shows there is an upgrade, so I click the download button. After about 2 hrs the process stops and an Error (102) appears on the screen. Any idea what goes wrong? THX

Just installed Mac OS X 10.8.5 on a Mac Pro 2010 platform.
The App Store shows there is an upgrade, so I click the download button.
After about 2 hrs the process stops and an Error (102) appears on the screen.
Any idea what goes wrong?
THX

ahstephen wrote:
Thank you for the response.
The upgrade I'm interested is for OS X v.10.8.5...
...The App Store page shows 2 different upgrades:
Mountain Lion (10.8.5) Software Upgrade, and
Yosemite FREE upgrade
If the App Store is showing 10.8.5 as an update, what do you currently have installed? The final update to Mountain Lion was 10.8.5, and since the basic OS installation of Mountain Lion is no longer offered in the App Store, that would suggest you're currently at an earlier version of Mountain Lion - 10.8.x where x=less than 5. If that's the case, I'd suggest getting the 10.8.5 update. There is also a Supplemental Update for 10.8.5 and that may be what the App Store is offering.

Error trying to deserialize EJB HomeHandle and EJB Handle classes

I get the following exception when I try to deserialize both a javax.ejb.HomeHandle and a javax.ejb.Handle. I serialize and immediately deserialize within the same application using the same classloader so there are not alot of external variables that may cause the problem. Any ideas on why I can't deserialize an ejb handle?
The reason I am doing this is to try and get around the need to reference another application just to call a remote method in that application. I want to serialize the remote home interface handle or the remote component interface handle and deserialize it using my local application classloader. Does anybody know if this would work?
#1#java.lang.ClassNotFoundException: Loader /L_service:ejb could not load class turtle.registry.SBRegistryRemoteHome
     at com.sap.vmc.core.impl.sapjvm.sharing.NativeSharedClassLoaderImpl.loadClass(NativeSharedClassLoaderImpl.java:609)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:265)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:333)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at java.io.ObjectInputStream.resolveProxyClass(ObjectInputStream.java:656)
     at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1499)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1462)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1698)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349)
     at com.sap.engine.services.ejb3.runtime.impl.LocalHandleDelegate.readStub(LocalHandleDelegate.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.ServerHandleDelegate.readStub(ServerHandleDelegate.java:64)
     at com.sap.engine.services.ejb3.runtime.impl.LocalHandleDelegate.readEJBHome(LocalHandleDelegate.java:101)
     at com.sap.engine.services.ejb3.runtime.impl.StatelessHomeHandleImpl.readObject(StatelessHomeHandleImpl.java:73)
     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:585)
     at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1818)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1718)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349)
     at turtle.common.util.SerializationHelper.convertObject(SerializationHelper.java:43)
     at turtle.common.server.connect.RemoteFactory.getRemoteSAPWAS(RemoteFactory.java:206)
     at turtle.common.server.connect.RemoteFactory.getRemote(RemoteFactory.java:46)
     at turtle.common.server.connect.RemoteProxyFactory.getRemote(RemoteProxyFactory.java:99)
     at turtle.common.server.connect.RemoteProxyFactory.create(RemoteProxyFactory.java:91)
     at turtle.common.server.connect.RemoteProxyFactory.createProxy(RemoteProxyFactory.java:52)
     at turtle.server.runtime.registry.RegistryFacade.connectToRegistry(RegistryFacade.java:932)
     at turtle.server.runtime.registry.RegistryFacade.getGenericRegistryBI(RegistryFacade.java:987)
     at turtle.server.runtime.registry.RegistryFacade.unbindObjectsInProject(RegistryFacade.java:857)
     at turtle.registry.ProjectRegistrar$1$1.run(ProjectRegistrar.java:130)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:337)
     at turtle.common.security.auth.AuthenticatorBase.doAs(AuthenticatorBase.java:387)
     at turtle.registry.ProjectRegistrar$1.run(ProjectRegistrar.java:172)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)

Has anyone been able to get this to work? Or can anyone confirm that this is a bug?
As a simpler test, I modified the UserManagementBean of the Car Rental example application. I added some code in the register method that serializes and deserializes the Handle object obtained from the SessionContext.getEJBObject().getHandle() method. The serialization completes without issue. However, I get the same error when trying to deserialize the Handle object:
java.lang.ClassNotFoundException: Loader /L_service:ejb could not load class com.sap.engine.examples.epf.ejb.controller.customer.UserManagementHome
     at com.sap.vmc.core.impl.sapjvm.sharing.NativeSharedClassLoaderImpl.loadClass(NativeSharedClassLoaderImpl.java:609)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:265)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:333)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at java.io.ObjectInputStream.resolveProxyClass(ObjectInputStream.java:656)
     at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1499)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1462)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1698)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349)
     at com.sap.engine.services.ejb3.runtime.impl.LocalHandleDelegate.readStub(LocalHandleDelegate.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.ServerHandleDelegate.readStub(ServerHandleDelegate.java:64)
     at com.sap.engine.services.ejb3.runtime.impl.LocalHandleDelegate.readEJBHome(LocalHandleDelegate.java:101)
     at com.sap.engine.services.ejb3.runtime.impl.StatelessHomeHandleImpl.readObject(StatelessHomeHandleImpl.java:73)
     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:585)
     at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1818)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1718)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1917)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1841)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1718)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349)
     at com.sap.engine.examples.epf.ejb.controller.customer.SerializationUtils.deSerialize(SerializationUtils.java:33)
     at com.sap.engine.examples.epf.ejb.controller.customer.SerializationUtils.deepClone(SerializationUtils.java:59)
     at com.sap.engine.examples.epf.ejb.controller.customer.UserManagementBean.register(UserManagementBean.java:75)

HT202919 I need to update my ARD admin from 3.6 to 3.7 but client is at 3.8 and it errors out. How do I work around this?

I need to update my ARD admin from 3.6 to 3.7 but client is at 3.8 and it errors out. How do I work around this?

This is a concern amoung many corporate users. It's going to take somekind of policy change with apple.
Enterprise support:
Call enterprise support (866) 752-7753 to create a case ID number

Sysid and client of caller for EJB Jco function

Hello,
I'm trying to identify the sender system and client (ABAP) for a processFunction call implemented as ejb (with JCO interface).
Does someone knew a method to access caller information from the processFunction call?
Regards,
Frank

Hi Frank,
I have to admit that my proposal does not work.
There is a thread change in the 7.0x JCo RFC Provider service so that casting the thread this way is illegal.
I am afraid that there is no possibility as you would like to have one.
But I think the switch with release 7.10 to internally use the new JCo would allow a similar cast then.
I think it should be possible with release 7.10 and higher. But that does not help you right now.
I'm sorry.
Best regards,
Stefan

Conntrans u2013 initialization error and Client console show no inbound queue

Hallo,
I installed Communication station and Client application to two computers. Test from Communication station to CRM is OK, test from client to Communication station is OK too. When I run Conntrans it show: u201CError during Conntrans initalizatin; contact system administratoru201D. In log file is:
Exception in CGUIDlg::CreateComObjects_AltThread . Was comerror exception (Neplatný ukazatel hr:80004003); technical hint: Create InitPar NamedCollection</SESS_LOG_TEXT>
</SESSION_ENTRY>
Client console show me, that I have u201CNo unprocessed messages available in the queueu201D. But in transaction smq1 I have 923 entries to send to Mobile Client.
I regenerate metadata, reassign siteID and did transaction table again, but still no messages in inbound queue.
Configuration: CRM 2007, CRM Mobile Client 6.0 SP02.
Can anyone help me please with these problems.
Thank you very much.
Jiri

Hallo Wolfhard,
thank you very much for your help and fast reply. I uninstall .NET 1.1 on client side (I had both .NET 1.1 and 2.0). Now I can run Conntrans. When I try synchronizaiton, it wrote "initializing transfer process" and after few second Conntrans fell down. In log is no error - everything have succeeded. I include ending part of log. In Client console inbound queue is the same.
<SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>43090EC6134E43479082B5043DD7E18F</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:19</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Returning from CGUIDlg::OnInitDialog...</SESS_LOG_TEXT>
</SESSION_ENTRY>
- <SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>A49BAA7D177D463491F635F8A64591E6</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Call to CGUIDlg::OnInitDialog in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
</SESSION_ENTRY>
- <SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>F5AE51A961664408830DDF07DA60C1F5</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Call to GetConfigurationDetails in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
</SESSION_ENTRY>
- <SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>1163EBE1ABB249ECAE0D3B230E6CCBB8</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Call to InitConfiguration in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
</SESSION_ENTRY>
- <SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>BE6FFFFE896D410A80D58C020195B56D</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Call to CreateAndPlaceControls in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
</SESSION_ENTRY>
- <SESSION_ENTRY>
<SESS_LOG_ENTRY_ID>FD53890701BA40AE8DADB1F9701FDCFC</SESS_LOG_ENTRY_ID>
<SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
<SESS_LOG_TYPE>I</SESS_LOG_TYPE>
<SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
<SESS_LOG_TEXT>Call to TaskBarCreateIcon in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
</SESSION_ENTRY>
</SESSION_ENTRIES>
After I applied note 1071267 on Client 6.0 SP02 I could not run Client Console. When I run it, I got "Failed to load control sbtstatus. Your version may be outdated. Make sure you are using the version of the control that was provided with your application". Conntrans after fix I can run, but it is the same as above - it will fell down after few second of synchronization.
My version of librfc32.dll is newer, so I did not applied note 1074669.
I will try to uninstall client side and apply note again to clean installation if it helps.
Thank you very much. With regards
Jirka

@WebService in EJB 3.0 ? Error on deployment

Hi,
I have implemented a stateless Session EJB with a @WebService Annotation. The EJB Modul can be deployed on a Glassfish Server with out errors.
When I try to deploy the EJB Modul on Weblogic 10.0 I got the following Error:
<23.10.2007 15.03 Uhr GMT+01:00> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/ix_workflow/WorkflowModelService".
class: org.imixs.workflow.jee.ejb.jaxws.GetEnvironmentList could not be found
     at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
     at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
     at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
     at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
     Truncated. see log file for complete stacktrace
>
<23.10.2007 15.03 Uhr GMT+01:00> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1193148199315' for task '35'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(BEA_Test1.jar)
Unable to deploy EJB: WorkflowManagerImplementation from BEA_Test1.jar:
My code dose not include a Class
org.imixs.workflow.jee.ejb.jaxws.GetEnvironmentList
nor the package org.imixs.workflow.jee.ejb.jaxws
Can anybody help me or give me a hint what this error message means?
Thanks a lot
Ralph

Hi, Rick
Thanks for your help.
I deleted de application-client.xml file, added the following lines to the web.xml file:
     <ejb-ref>
          <ejb-ref-name>ejb/SessionEJB</ejb-ref-name>
          <ejb-ref-type>Session</ejb-ref-type>
          <remote>ar.com.eds.ejb3.model.SessionEJB</remote>
     </ejb-ref>
and now I´m using oracle.j2ee.rmi.RMIInitialContextFactory
there is no error, and it doesn´t throw any exception but the following line returns null.
SessionEJB sessionEJB = (SessionEJB)context.lookup("java:comp/env/ejb/SessionEJB");
Its seems the lookup method finds the remote ejb because it doesn´t fail, but it returns null.
Any idea what is wrong?
Mauricio.

ClassNotFoundException in EJB's and Threads (Classloader issue)

A very interesting bug has cropped up in WebLogic 6.1. When a J2EE
application packaged appropriately, a client application running in a
user-created Thread will always throw a ClassNotFoundException when
attempting to get back a user-created object from an EJB living on
another cluster. This error does not happen when the call is being made
from outside a Thread.
Sounds strange, I know, so I'll try to give everyone as much detail as
possible so they can avoid this bug, and so that the folks at BEA can
fix it.
* A java class running inside a clustered WL6.1 server is attempting to
reference an EJB on another clustered WL 6.1 server. Accessing the bean
is not a problem, the client class is able to obtain a remote reference
to the bean and make method calls on it. Calling a method causes the
following stack trace:
2002-01-11 10:36:57,331 [Thread-4] ERROR
wpni.app.mywp.display.DisplayJobs$JobsMonitor -
wpni.app.mywp.display.DisplayJobs$JobsMonitor.run: Error checking Jobs
status.
java.rmi.UnmarshalException: failed to unmarshal class
wpni.app.jobs.JobsData; nested exception is:
java.lang.ClassNotFoundException: wpni.app.jobs.JobsData: This
error could indicate that a component was deployed on a cluster member
but not other members of that cluster. Make sure that any component
deployed on a server that is part of a cluster is also deployed on all
other members of that cluster
java.lang.ClassNotFoundException: wpni.app.jobs.JobsData: This error
could indicate that a component was deployed on a cluster member but
not other members of that cluster. Make sure that any component deployed
on a server that is part of a cluster is also deployed on all other
members of that cluster
at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:146)
at
weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:211)
at
weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:290)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:107)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:115)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at
weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:230)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:254)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy140.getJobsData(Unknown Source)
at
wpni.app.mywp.display.DisplayJobs$JobsMonitor.run(DisplayJobs.java:48)
at java.lang.Thread.run(Thread.java:484)
* The class that is not found (JobsData) is definitely in the EAR file
on both the client cluster and the server cluster, and in the
appropriate location.
* When we attempted to run the code outside of a Thread, everything
worked perfectly, so it was definitely the Thread that was causing the
problem.
* Deploying the EJB on the client cluster did not do anything to solve
the problem.
* Adding the JobsData to the System CLASSPATH at the startup of the
WebLogic server DID solve the problem. But of course that defeats the
purpose of packaging everything in the EAR file.
So, the conclusion seems to be that when DisplayJobs$JobsMonitor kicked
off the Thread, the Thread should have been created in either the WAR's
classloader or the JAR's classloader (wouldn't matter, since the
JobsData class is in the JAR's classloader, which is a parent of the
WAR's classloader). But instead, the Thread is being created in the
System classloader, which can't find the JobsData class!
We believe that any Thread created by a class living within an EAR's
classloader should remain within that same classloader, and not migrate
to any other classloader, in order to avoid situations like this. We're
opening a case with BEA to attempt to get this resolved. In the
meantime, we recommend to developers that if they have to make
cross-cluster RMI calls from inside user-created Threads, that they only
attempt to receive primitive types or standard JDK objects. Otherwise,
you'll have to add the classes to the System CLASSPATH at startup of the
WebLogic instance.
Thanks,
Erin
* "[White House spokeperson Ari] Fleischer
* warned Democrats this morning against
* investigations into the Bush administration's
* dealings with Enron. 'The American people
* are tired of partisan witch hunts and endless
* investigations,' he said." [Ed.: Uh... ]
* www.washingtonpost.com/wp-dyn/articles/A25159-2002Jan10.html
* Erin Reid Myers, Chief Architect
* WashingtonPost.Newsweek Interactive
* [email protected]
* Work: (703) 469-3154
* Cell: (703) 725-3050
[att1.html]

Things can go seriously wrong if your application uses user threads (violating
EJB spec programming restrictions and BEA recommendations).
I'm curious, does it work if you enable network classloading on the server
which invokes remote EJB (in config.xml -
<Server NetworkClassLoadingEnabled="true" ...
</Server>
Erin Reid Myers <[email protected]> wrote:
A very interesting bug has cropped up in WebLogic 6.1. When a J2EE
application packaged appropriately, a client application running in a
user-created Thread will always throw a ClassNotFoundException when
attempting to get back a user-created object from an EJB living on
another cluster. This error does not happen when the call is being made
from outside a Thread.
Sounds strange, I know, so I'll try to give everyone as much detail as
possible so they can avoid this bug, and so that the folks at BEA can
fix it.
* A java class running inside a clustered WL6.1 server is attempting to
reference an EJB on another clustered WL 6.1 server. Accessing the bean
is not a problem, the client class is able to obtain a remote reference
to the bean and make method calls on it. Calling a method causes the
following stack trace:
2002-01-11 10:36:57,331 [Thread-4] ERROR
wpni.app.mywp.display.DisplayJobs$JobsMonitor -
wpni.app.mywp.display.DisplayJobs$JobsMonitor.run: Error checking Jobs
status.
java.rmi.UnmarshalException: failed to unmarshal class
wpni.app.jobs.JobsData; nested exception is:
java.lang.ClassNotFoundException: wpni.app.jobs.JobsData: This
error could indicate that a component was deployed on a cluster member
but not other members of that cluster. Make sure that any component
deployed on a server that is part of a cluster is also deployed on all
other members of that cluster
java.lang.ClassNotFoundException: wpni.app.jobs.JobsData: This error
could indicate that a component was deployed on a cluster member but
not other members of that cluster. Make sure that any component deployed
on a server that is part of a cluster is also deployed on all other
members of that cluster
at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:146)
at
weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:211)
at
weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:290)
at
java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:107)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:115)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at
weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:230)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:254)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy140.getJobsData(Unknown Source)
at
wpni.app.mywp.display.DisplayJobs$JobsMonitor.run(DisplayJobs.java:48)
at java.lang.Thread.run(Thread.java:484)
* The class that is not found (JobsData) is definitely in the EAR file
on both the client cluster and the server cluster, and in the
appropriate location.
* When we attempted to run the code outside of a Thread, everything
worked perfectly, so it was definitely the Thread that was causing the
problem.
* Deploying the EJB on the client cluster did not do anything to solve
the problem.
* Adding the JobsData to the System CLASSPATH at the startup of the
WebLogic server DID solve the problem. But of course that defeats the
purpose of packaging everything in the EAR file.
So, the conclusion seems to be that when DisplayJobs$JobsMonitor kicked
off the Thread, the Thread should have been created in either the WAR's
classloader or the JAR's classloader (wouldn't matter, since the
JobsData class is in the JAR's classloader, which is a parent of the
WAR's classloader). But instead, the Thread is being created in the
System classloader, which can't find the JobsData class!
We believe that any Thread created by a class living within an EAR's
classloader should remain within that same classloader, and not migrate
to any other classloader, in order to avoid situations like this. We're
opening a case with BEA to attempt to get this resolved. In the
meantime, we recommend to developers that if they have to make
cross-cluster RMI calls from inside user-created Threads, that they only
attempt to receive primitive types or standard JDK objects. Otherwise,
you'll have to add the classes to the System CLASSPATH at startup of the
WebLogic instance.
Thanks,
Erin
* "[White House spokeperson Ari] Fleischer
* warned Democrats this morning against
* investigations into the Bush administration's
* dealings with Enron. 'The American people
* are tired of partisan witch hunts and endless
* investigations,' he said." [Ed.: Uh... ]
* www.washingtonpost.com/wp-dyn/articles/A25159-2002Jan10.html
* Erin Reid Myers, Chief Architect
* WashingtonPost.Newsweek Interactive
* [email protected]
* Work: (703) 469-3154
* Cell: (703) 725-3050
Dimitri

I unable to run ejb with application client using oc4j j2ee container

Hi,
I have installe oracle9i (1.0.2.2) oc4j j2ee container.
I unable to run the ejbs . please help me how to run ejbs with application client and which files are shall configure.
See the client application is :
public static void main (String []args)
try {
//Hashtable env = new Hashtable();
//env.put("java.naming.provider.url", "ormi://localhost/Demo");
//env.put("java.naming.factory.initial", "com.evermind.server.ApplicationClientInitialContextFactory");
//env.put(Context.SECURITY_PRINCIPAL, "guest");
//env.put(Context.SECURITY_CREDENTIALS, "welcome");
//Context ic = new InitialContext (env);
System.out.println("\nBegin statelesssession DemoClient.\n");
Context context = new InitialContext();
Object homeObject = context.lookup("java:comp/env/DemoApplication");
DemoHome home= (DemoHome)PortableRemoteObject.narrow(homeObject, DemoHome.class);
System.out.println("Creating Demo\n");
Demo demo = home.create();
System.out.println("The result of demoSelect() is.. " +demo.sayHello());
}catch ( Exception e )
System.out.println("::::::Error:::::: ");
e.printStackTrace();
System.out.println("End DemoClient....\n");
When I am running client application I got this type of Exception
java.lang.SecurityException : No such domain/application: sampledemo
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java : 2040)
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java : 1884)
at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java : 1491)
at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java : 323)
at com.evermind.server.rmi.RMIContext.lookup(RMIConext.java : 106)
at com.evermind.server.administration.LazyResourceFinder.lookup(LazyResourceFinder.java : 59)
at com.evermind.server.administration.LazyResourceFinder.getEJBHome(LazyResourceFinder.java : 26)
at com.evermind.server.Application.createContext(Application.java: 653)
at com.evermind.server.ApplicationClientInitialContext.getInitialContext(ApplicationClientInitialContextFactory.java :179 )
at javax.naming.spi.NamingManager.getInitialContext(NamingManger.java : 246)
at javax.naming.InitialContext.getDefaultInitialCtx(InitialContext.java : 246)
at javax.naming.InitialContext.init(InitialContext.java : 222)
at javax.naming.InitialContext.<init>(InitialContext.java : 178)
at DemoClient.main(DemoClient.java : 23)
.ear file is copied into applications directory.
I have configured server.xml file like this
<application name="sampledemo" path="../applications/demos.ear" />
demos.ear file Contains following files
application.xml
demobean.jar
Manifest.mf
demobean.jar file contains following files
application-client.xml
Demo.class
DemoBean.class
DemoHome.class
ejb-jar.xml
jndi.properties
Mainifest.mf
Please give me your valuable suggestions. Which are shall i configure .
Thanks & Regards,
Badri

Hi Badri,
ApplicationClientInitialContextFactory is for clients which got deployed inside OC4J container..
For looking up EJB from a stand alone java client please use RMIInitialContextFactory..So please change ur code....
Also please check ur server.xml
Since you have specified your ejb domain as "sampledemo"
you have to use that domian only for look up..But it seems that you are looking up for "Demo" domain instead of "sampledemo" domain...So change your code to reflect that..
Code snippet for the same is :
Hashtable env = new Hashtable();
env.put("java.naming.provider.url", "ormi://localhost/sampledemo");
env.put("java.naming.factory.initial", "om.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
Context ic = new InitialContext (env);
Hope this helps
--Venky

HELP! Having trouble connecting to EJB with RMI client

I've got a simple stateless session EJB deployed and I'm trying to connect
to it using a standalone
RMI client. I'm getting the following error back when I first do a
context.lookup("ejb/beanname"):
org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: Maybe
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at org.omg.CORBA.SystemException.<init>(SystemException.java:49)
at org.omg.CORBA.COMM_FAILURE.<init>(COMM_FAILURE.java:77)
at org.omg.CORBA.COMM_FAILURE.<init>(COMM_FAILURE.java:63)
at
com.sun.corba.ee.internal.iiop.IIOPConnection.purge_calls(Compiled Code)
at com.sun.corba.ee.internal.iiop.ReaderThread.run(Compiled Code)
Any troubleshooting advice would be greatly appreciated.
BTW: After this error, iPlanet's cxs process seems to die! Until I restart
cxs I get no connection failures
of the form:
javax.naming.CommunicationException:
Cannot connect to ORB. Root exception is org.omg.CORBA.COMM_FAILURE:
minor code: 1398079490 completed: No
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at org.omg.CORBA.SystemException.<init>(SystemException.java:49)
at org.omg.CORBA.COMM_FAILURE.<init>(Compiled Code)
at org.omg.CORBA.COMM_FAILURE.<init>(Compiled Code)
at com.sun.corba.ee.internal.iiop.IIOPConnection.writeLock(Compiled
Code)
at com.sun.corba.ee.internal.iiop.IIOPConnection.send(Compiled Code)
at com.sun.corba.ee.internal.iiop.IIOPOutputStream.invoke(Compiled
Code)
at
com.sun.corba.ee.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.ja
va:74)
at
com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:16
0)
at
com.sun.corba.ee.internal.corba.InitialNamingClient.resolve(InitialNamingCli
ent.java:199)
at
com.sun.corba.ee.internal.corba.InitialNamingClient.cachedInitialReferences(
InitialNamingClient.java:278)
at
com.sun.corba.ee.internal.corba.InitialNamingClient.resolve_initial_referenc
es(InitialNamingClient.java:187)
at
com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.java:1422
at
com.sun.corba.ee.internal.POA.POAORB.resolve_initial_references(POAORB.java:
541)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:252)
at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(Compiled Code)
at
com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:185)
at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:72)
.... stuff deleted....
Is RMI client support in iPlanet 6.0 truly this buggy or am I missing
something?
Jack Profit
[email protected]

Make sure to review the Converter sample and employ all of the workarounds
listed there.
David
Jack Profit wrote:
I've got a simple stateless session EJB deployed and I'm trying to connect
to it using a standalone
RMI client. I'm getting the following error back when I first do a
context.lookup("ejb/beanname"):

EJB- HRS and Client Error

Similar Messages

Maybe you are looking for