Issues in looking up a ejb deployed on glassfish from tomcat.

Hi all,
I have followed the steps mentioned in the EJB FAQ in the glassfish site and was able to lookup a remote ejb deployed in glassfish from a standalone client.
In case of standalone client, i set the appropriate jndi properties in the initial context as mentioned in the FAQ and added the 4 jars specified to the classpath of the application.
It all worked perfectly well.
But I attempted to do the same from a servlet running under tomcat.
I set the appropriate jndi properties in the intial context and added 4 jars specified in the lib directory of the war file.
But this did not turn out well and tomcat complained me with some servlet init errors.
Then i searched through the web and found this posting from you:
http://www.archivesat.com/GlassFish_Enterprise_JavaBeans_Developers/thread1399339.htm
Then i created a folder called "shared/lib" under TOMCAT_HOME directory in my machine and ran the same example. Wow.....miraculously the application ran well.
But i found that the "index.jsp" which i configured in the welcome file list does not appear now. But i was able to access the servlet without any problem. And the servlet was able to successfully lookup the ejb deployed in glassfish.
Then i thought, let me try to access the ejb from a jsf application.
Then i created a jsf application in netbeans 5.5.1 and tried to access the bean deployed in glassfish.
(Note: the jsf application runs in tomcat 5.5.17 which is bundled with netbeans)
OOPSS....
Tomcat now complains me that it cannot compile the jsp page..
This is the error i got...
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:7: org.apache.jsp.index_jsp is not abstract and does not override abstract method getDependants() in org.apache.jasper.runtime.JspSourceDependent
public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
^
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:12: getDependants() in org.apache.jsp.index_jsp cannot implement getDependants() in org.apache.jasper.runtime.JspSourceDependent; attempting to use incompatible return type
found : java.lang.Object
required: java.util.List
public Object getDependants() {
^
2 errors
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
Any ideas...
Can you please help me.
I've noticed that you were eagerly answering questions related to ejb lookup in many places.
I feel there is some potential compatability issue between tomcat and glassfish...
I request you to investigate on this and clarify the community with your response.
Thanks in advance,
James Selvakumar

Thank you guys!
I've found the answer myself.

Similar Messages

Calling an EJB deployed in OC4J from Java Stored Proc in Oracle

Hello!
Trying to make a call to an EJB deployed in OCJ4 from a oracle java stored proc. After loaded orion.jar and crimson.jar lib into SCOTT schema, I can't get the JNDI Context working because of this error:
============================================
javax.naming.NoInitialContextException: Cannot instantiate class:
com.evermind.server.ApplicationClientInitialContextFactory. Root exception is
java.lang.ClassNotFoundException:
com/evermind/server/ApplicationClientInitialContextFactory
at java.lang.Class.forName0(Class.java)
at java.lang.Class.forName(Class.java)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:45)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java)
at javax.naming.InitialContext.init(InitialContext.java)
at javax.naming.InitialContext.<init>(InitialContext.java)
===============================
I did load the java with "loadjava" with on time with the "resolve" option and time time no option and still no working.
Here is the EJB client code:
=======================================
import java.sql.*;
import java.util.*;
import javax.naming.*;
import com.evermind.server.ApplicationClientInitialContextFactory;
class EmpRemoteCall {
public static void main(String[] args) {
System.out.println(getEmpName());
public static String getEmpName() {
String ejbUrl = "java:comp/env/ejb/Emp";
String username = "admin";
String password = "admin";
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
environment.put(Context.PROVIDER_URL, "ormi://127.0.0.1/testemp");
environment.put(Context.SECURITY_PRINCIPAL, username);
environment.put(Context.SECURITY_CREDENTIALS, password);
//environment.put(Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
//environment.put(javax.naming.Context.URL_PKG_PREFIXES, "oracle.aurora.jndi");
com.kboum.sertir.essais.EmpHome homeInterface = null;
try {
Class.forName("com.evermind.server.ApplicationClientInitialContextFactory", true, ClassLoader.getSystemClassLoader());
System.out.println("Creating an initial context");
Context ic = new InitialContext(environment);
System.out.println("Looking for the EJB published as 'java:comp/env/ejb/Emp'");
homeInterface = (com.kboum.sertir.essais.EmpHome) ic.lookup(ejbUrl);
catch (CommunicationException e) {
System.out.println("Unable to connect: " + ejbUrl);
e.printStackTrace();
//System.exit(1);
catch (NamingException e) {
System.out.println("Exception occurred!");
System.out.println("Cause: This may be an unknown URL, or some" +
" classes required by the EJB are missing from your classpath.");
System.out.println("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.");
e.printStackTrace();
//System.exit(1);
catch (ClassNotFoundException e) {
System.out.println("Unable to connect: " + ejbUrl);
e.printStackTrace();
//System.exit(1);
try {
System.out.println("Creating a new EJB instance");
com.kboum.sertir.essais.Emp remoteInterface = homeInterface.findByPrimaryKey(Integer.valueOf("7369"));
System.out.println(remoteInterface.getENAME());
System.out.println(remoteInterface.getSAL());
remoteInterface.setSAL(2);
System.out.println(remoteInterface.getSAL());
return remoteInterface.getENAME();
catch (Exception e) {
System.out.println(e.getMessage());
e.printStackTrace();
return "error";
null

What I did to solve this problem was to
create a simple RMI remote object that
resides outside the database JVM and that
serves as a proxy EJB client for your java
stored procedure. The stored procedure can
invoke a method on the remote RMI object
which then looks up the EJBean's home
interface and invokes the relevant method on
the bean's remote interface, and relays any
return values back to the java stored
procedure.
Hope this helps,
Avi.
null

Calling an EJB deployed in OC4J from a Java Stored Procedure

Hi all,
Well, I've been trying to figure this out for a bit now and haven't come up with a solution.
I have a Java Stored Procedure in a 9i database and would like to call an EJB deployed in the OC4J Container but DO NOT want to load the various Orion JAR files into the database.
I get hung up on the JNDI piece.
Has anyone figured out how to do this?
Got some code?
Thanks!

Doug,
This is not possible in Oracle9i Release1. in the upcoming Oracle9i DB R2, we will support loading a client-side jars of oc4j (oc4jclient.jar) in the database and call-out EJBs in 9iAS
Please look at this thread Re: Compile procedures for a detailed dicussion on this topic.
regards
Debu Panda
Oracle

How to lookup EJBs deployed in OC4J from a standalone client application

Hello all,
I am trying to lookup an EJB deployed in OC4J 10.1.3 from a standalone client application using the following code:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://localhost:23791");
env.put(Context.SECURITY_PRINCIPAL, "jazn.com/test");
env.put(Context.SECURITY_CREDENTIALS, "test");
Context context = new InitialContext(env);
Object ref = context.lookup("ejb/Dispatch");
I get the following error:
javax.naming.NameNotFoundException: ejb/Dispatch not found
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
For the lookup string I've also tried:
"java:comp/env/ejb/Dispatch" and "Dispatch"
For the Context.PROVIDER_URL property I've also tried:
opmn:ormi://localhost:6003:instance
The result is always the same.
I appreciate if someone could help me with this?
Thanks,
Georgi

Georgi,
Your question has been discussed many times on this forum. Search the forum archives for "RMIInitialContextFactory".
The PROVIDER_URL needs to include the name of the deployed application that your EJB is part of, for example:
env.put(Context.PROVIDER_URL, "ormi://localhost:23791/MyApp");The lookup name has to be the value of the "ejb-name" element in your "ejb-jar.xml" descriptor file.
Your SECURITY_PRINCIPAL value looks strange to me. Personally, I use "principals" (and not JAZN), so I modified the "application.xml" file (in the "j2ee/home/config" subdirectory) to use "principals". Look for the following comment in that file:
Good Luck,
Avi.
Message was edited by:
Avi Abrami

How to connect to remote EJB 3.0 deployed on Glassfish from ADF application

Hello, as we haven't managed to deploy ADF app with EJB 3.0 on Glassfish AS, nor on tomcat 6 with openEJB, nor on JBOSS 5GA, we're trying to deploy our app with remote interface on tomcat 6. We're using ADF, JSF and EJB 3.0 (Eclipselink as JPA).
When the model project is deployed on WLS 10.3, everything works fine. Here is a part from DataControls.cpx
<Source>
<ejb-definition ejb-version="3.0" ejb-name="MySession"
ejb-type="Session"
ejb-business-interface="model.MySession"
ejb-interface-type="remote"
jndi-name="MySessionBean#model.MySession"
provider-url="t3://localhost:7001"
initial-context-factory="weblogic.jndi.WLInitialContextFactory"
xmlns="http://xmlns.oracle.com/adfm/adapter/ejb"
DataControlHandler="oracle.adf.model.adapter.bean.jpa.JPQLDataFilterHandler"/>
</Source>Now the model project is deployed on Glassfish 2. I had to change DataControls.cpx
<Source>
<ejb-definition ejb-version="3.0" ejb-name="MySession"
ejb-type="Session"
ejb-business-interface="model.MySession"
ejb-interface-type="remote"
jndi-name="MySessionBean#model.MySession"
provider-url="iiop://localhost:3700"
initial-context-factory="com.sun.enterprise.naming.SerialInitContextFactory"
xmlns="http://xmlns.oracle.com/adfm/adapter/ejb"
DataControlHandler="oracle.adf.model.adapter.bean.jpa.JPQLDataFilterHandler"/>
</Source>But I get the following error:
SEVERE: Exception:
oracle.jbo.JboException: JBO-29000: Выявлено непредвиденное исключение: javax.naming.NameNotFoundException, сообщ.=Exception in lookup.: `DocJournalService' could not be found.
     at oracle.adfinternal.model.adapter.ejb.EjbDataControl.<init>(EjbDataControl.java:171)
     at oracle.adfinternal.model.adapter.ejb.EjbDefinition.createDataControl(EjbDefinition.java:142)
     at oracle.adf.model.adapter.DataControlFactoryImpl.createSession(DataControlFactoryImpl.java:173)
     at oracle.adf.model.binding.DCDataControlReference.getDataControl(DCDataControlReference.java:166)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `DocJournalService' could not be found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
     at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:58)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:252)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:230)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.adfinternal.model.adapter.ejb.EjbDataControl.<init>(EjbDataControl.java:148)
     ... 60 more
Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72)
     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:241)
     ... 63 more
## Detail 0 ##
javax.naming.NameNotFoundException: Exception in lookup.: `DocJournalService' could not be found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
     at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:58)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:252)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:230)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at oracle.adfinternal.model.adapter.ejb.EjbDataControl.<init>(EjbDataControl.java:148)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)
Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72)
     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:241)
     ... 63 more
Could you tell me where is my mistake?

http://www.alexnet.fr/doc/oracle/oas10132/web.1013/b28221/undejdev003.htm

Doing a jndi lookup() for an EJB deployed on Glassfish v3

Hello.
I have deployed a Stateful Sesion EJB on a Glassfish v3 AppServer.
It is running under 'localhost' on my laptop pc.
I am also running a stand-alone java application on the same pc... it attempts to get a remote connection from the client-app to the Glassfish Server and then do a jndi lookup() to get a reference to my EJB.
here is the client source code:
public class LookupTest {
static Properties props = null;
public static void main(String[] args) {
try {
props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
     props.put(Context.PROVIDER_URL, "iiop://localhost:3700");
     Context ctx = new InitialContext(props);
     System.out.println( "the context is: " + ctx);
     System.out.println( "the environment contains: " + ctx.getEnvironment() );
     System.out.println( " ");
     // do a lookup.
     Object elementObj = ctx.lookup("SerialContextProvider");
     System.out.println(elementObj);
} catch (NamingException e) {
e.printStackTrace();
When I run this app, there are no Errors or Exceptions. It appears that the connection succeeds. But there are no EJB references in the context that is created. The only item that seems to be present in the context is an item named "SerialContextProvider", as noted in the return value from a list("") method invocation. Why can i not see the EJB within the context? Is my code wrong ??
Thanks,
Andy Jerpe
Edited by: user1169567 on Nov 28, 2010 12:12 PM

Ok, but the communication seems to be OK over the wire because if I use netstat -a I can see the ESTABLISHED connection with the server in the right RMI port.
TCP PORTAL35:1581 caapiranga:12405 ESTABLISHED
and then when I stop the instance in the OAS, the client shows an exception telling that the connection was lost.
An curious thing is that the ons.log doesn't log this connection ;/

How to call EJB deployed on websphere from JSP running on Tomcat?

I am trying to establish communication between two app servers. I have a sample EJB deployed on Websphere and wish to call its business methods from a JSP page which is running on Apache Tomcat server. (ie) Tomcat is client to websphere. Is it possible to do? If so, what are the client Jar files of websphere that I should make available to JSP page on Tomcat? Do I need to set any Jars in Tomcat environment variables? Lood forward for your immediate help. Thanks in advance

Please see the thread
http://forum.java.sun.com/thread.jspa?threadID=514536.
Hope that helps..

How to call EJB deployed on OC4J from java stored procedure?

Hello,
I'd like to call EJB from java stored procedure. My example works fine from command line, but the problem seems to be with deployment of this code into database. Especialy I'm wondering how to reference jars like oc4jclient.jar, ejb.jar, ... from java stored procedure.
Is there some example how to do that ?
Can You help me please ?
Many thanks,
Radim Kolek,
Eurotel Prague.

Hi,
You may want to check up this thread
Calling JBoss EJBs from Java stored procedure
Hope this helps,
Sujatha.
OTN Group.

Looking for BC4J EJB deployment example

Hi,
I am looking for an very simple example project for BC4J deployed as EJB, including table definition, BC4J source files, and EJB client source files. I have previously successfully deployed the BC4J to Oracle8i JVM and OC4J, but currently struck at how to write the client application. I would like to know how to call my own remote methods other than working with ViewObjects directly.
Help needed.
Regards,
Patrick.

Maybe this will help:
In JServer, ejb inactivity timeout is controlled by property jbo.ejb.txntimeout which value is 60 (secs) by default.
JServer properties file is deployed as oracle/jbo/server/jboserver.properties, you can get it from jbomt.zip (you should create the same directory structure and a project, say jServerProps.jpr, containing the file).
Edit the file:
jbo.ejb.txntimeout=28800
jbo.ejb.txntype=local
, then deploy it as Classes and Java Stored Procedures to Oracle 8i.
To see effective values of jServer properties you have to set jbo.debugoutput=console in file oracle/jbo/common/Diagnostic.properties - from the same jbomt.zip.
It's better to include the file in the above jServerProps project and deploy at once with jboserver.properties.
null

Lookup ejb deployed in wls8.1 from wls9.2 env

hi guys
i was wondering if anyone had encountered problem when looking up home interface of ejb deployed in weblogic814 from weblogic9.2? basically i have an ejb build with weblogic.appc task and deployed in wls814. this also generated a client jar to use. so, from wls9.2, i had a simple webservice implemented with a POJO. when it tried to lookup the home interface of the ejb in 8, it failed with
<WSEE>java.lang.IncompatibleClassChangeError: class FacadeEJB_g5wccg_HomeImpl_814_WLStub has
interface weblogic.rmi.extensions.server.Stub as super class<ComponentHandler.h
andleRequest:115>i think this must have something to do with compatibility between 8 and 9. i was wondering if anyone knows about this and had a solution for it. ur help is much appreciated.

Hi..
Even we are also facing the same pbm..Any one with a solution ?

Access EJB 3.0 (deployed on Glassfish v3) from Tomcat 6.0.20 (Netbeans 6.8)

Hi all,
I'm a newbie (of java EE and Sun forum).
I have a problem.
I followed this tutorial: http://technology.amis.nl/blog/1368/connecting-to-an-ejb-30-remote-sessionbean-from-tomcat
using Netbeans 6.8, Tomcat 6.0.20, Glassfish v3.
The deploy of EJB on Glassfish is OK.
The deploy of WebApp on Tomcat is OK.
But when I access to the servlet using the browser I receive this exception.
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.enterprise.naming.SerialInitContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.enterprise.naming.SerialInitContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at web.MyServlet.processRequest(MyServlet.java:51)
at web.MyServlet.doGet(MyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
at java.lang.Thread.run(Thread.java:619)
I know that I must copy *.jar files in Tomcat dir and App libraries (https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#Step_3._Include_appserv-rt.jar_and), but it doesn't work.
What are my mistakes?
Thank you for your help.
Servlet code:
package web;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.util.Properties;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import testbean.MySessionBeanRemote;
* @author Stefano
public class MyServlet extends HttpServlet {
* Processes requests for both HTTP <code>GET</code> and <code>POST</code> methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
Properties props = new Properties();
props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
try {
out.println("<html>");
out.println("<head>");
out.println("<title>Servlet MyServlet</title>");
out.println("</head>");
out.println("<body>");
out.println(MySessionBeanRemote.class.getName());
try {
InitialContext ic = new InitialContext(props);
MySessionBeanRemote mySessionRemote = (MySessionBeanRemote) ic.lookup("pippo");
out.println(mySessionRemote.getOK());
} catch (NamingException ex) {
ex.printStackTrace();
out.println("</body>");
out.println("</html>");
} finally {
out.close();

Yes, I did.
I'm not sure about the right actions to do.
For example: the Glassfish FAQ told me to add gf-client*.jar to the Tomcat folder, not appserv-rt.jar , with v3.
I tried with both files. I restarted Tomcat, but nothing work :-(

EJB deployment issue in websphere

EJB deployment issue in websphere
I have created an EJB project in eclipse and created a stateless session bean successfully.
I created Enterprise application project and added the EJB project.
I tried to check it using Universal test client.
When I click the JNDI explorer>>sample.HelloWorldEJBHome
I get error IWAD0401E Unknown type of JNDI object
But when I install an EJB jar using administrator console after exporting the jar file for the EJB project
It is working file
I like to reduce the number of steps by right clicking the server publish and test.
Do any one have come across the same issue please help me
Thanks in advance.

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

ZipFile closed: EJB Deployment Issue

Hi all,
I am facing problems in the Ejb deployment. Please read the following
V r using Weblogic 7.0 with jdk1.4
Just take a luk at steps performed
1. V compiled all the source code, the ejbc compilation and the .ear generation thru ant(v 1.5) build scripts with JDK1.4.1
2. When v tried deployin the .ear file, it gave the error in the particular EJB jar file stating
"unable to deply Ejb bean, Error: ZipFile Closed"
however, if the 1st step is performed using JDK1.4.0_02-b02 version of JDK1.4, the deployment goes on pretty fine. I just wonna know if u or any of your colleague have faced similar problems, the cause of it and the workarounds.
Cheers,
Manjunath Rane

Don't scratch ur head guys....i found the solution. Just apply Weblogic 7.0 sp1. Couldn't find the cause though. There is one potential possiblity.
I was using <ZipFileSet> task of Ant 1.5 to build the EJb Jar File. The Ant documents clearly says that using the above task would cause the generation of .java file thur <javac> would lock up the .class files. I presume that these locked file were being jarred. The deployment thus would have failed due to unability to open the closed files. hence the error.....
Cheers,
Manja

EJB-deployment: RuntimeOperationsException

I'm having trouble deploying an ejb that has been packaged five levels deep(com/something/something2/something3/channel/MyEjb.class)
the ejb-jar.xml is done accordingly. When I try to deploy I get the following
message:
javax.management.RuntimeOperationsException: RuntimeException thrown by the invoke
method of the Dynamic MBean
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:866)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:853)
at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:566)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy70.addTarget(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:486)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:557)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy2.update(Unknown Source)
at weblogic.management.console.pages._domain._upload_app._jspService(_upload_app.java:172)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
If I deploy the same ejb packaged as: channel/MyEjb.class
It deploys fine. Why is this?

Problem solved, it was an utility class that could not be found, so it should have
been a ClassNotFoundException.
"PeterB" <[email protected]> wrote:
>
Yes, it would indeed be strange if it had such an effect. But what does
the exception
tell you? Thank you anyway for your reply.
Peter
"Chuck Nelson" <[email protected]> wrote:
Peter,
I don't think the package 'depth' should be an issue - -
we package sample ejbs under <beahome>/samples/examples/ejb many levels
'deep'.
I would look at the sample deployment descriptors and package names
for one
of examples as a reference
(e.g., <beahome>/samples/examples/ejb/basic/statelessSession)
Chuck Nelson
Developer Relations Engineer
BEA Technical Support

Can't lookup an EJB deployed in Orion AS rom JDeveloper 10.1.3

Everything was OK when the EJB has been looked up from a standalone application. But when it hang up when the lookup was done from a web application .
Please help me,
          Hashtable environment = new Hashtable();
          // Specify the emd-rmi SPI
          environment.put("java.naming.factory.initial", "com.evermind.server.rmi.RMIInitialContextFactory");
          // Specify the host
          environment.put("java.naming.provider.url", "ormi://localhost:23791/appname");
          // Specify username - this must be an admin account on the remote server
          environment.put("java.naming.security.principal", "admin");
          // Password
          environment.put("java.naming.security.credentials", "admin");
          InitialContext context = new InitialContext(environment);
//Context ctx = new InitialContext();
Object obj = context.lookup("ejbname");
Error message.
2006-02-07 15:46:48.541 NOTIFICATION Industrial Telnet Server version: Version 10.1.3.0.0 started-up successfully.
06/02/07 15:49:21 INFO: RMIProtocol.readConnectionHeader Local ORMI version = 1.3 different from remote version 1.0 will use 1.0
07.feb.2006 15:49:20 com.evermind.server.rmi.RMIProtocol readConnectionHeader
INFO: Local ORMI version = 1.3 different from remote version 1.0 will use 1.0

I guess you are facing the same problem as I am:
ADF-EJB deployment issue (urgent)
Too new ormi protocol for older Application Servers.

Issues in looking up a ejb deployed on glassfish from tomcat.

Similar Messages

Maybe you are looking for