EJB lookup problem in EAServer 6.0
I'm migrating EAserver 4.1 to 6.0. EAserver 4.1 of Web
component and ejb component is successfully deployed in 6.0.
Web component is working fine but in ejb component is
throwing NamingException while lookup. if i verified
deployed package in "deploy" folder of EAserver 6.0
installation this is already existed. Please see below for
more information on exception.
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] -------------New GET Request--------------
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Time received= Wed Aug 29 18:38:44 IST 2007
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] General info:
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] RemoteHost= 10.100.106.112
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] RemoteAddr= 10.100.106.112
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] RemoteUser= null
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] RequestURL=
http://hdchctdann6311:8080/ent/Coordinator
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Request headers:Accept= image/gif,
image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-shockwave-flash, application/vnd.ms-excel,
application/vnd.ms-powerpoint, application/msword, */*
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Accept-Language= en-us
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Accept-Encoding= gzip, deflate
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] User-Agent= Mozilla/4.0 (compatible; MSIE
6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322)
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Host= hdchctdann6311:8080
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Connection= keep-alive
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Authorization= Basic
cnNodWdhbjphYWFhYWEzMg==
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] Login Credentials from Authorization Header:
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] coordID=rshugan
2007-08-29 18:38:44.327 INFO HttpListener0-2
[ConsoleOutput] coordPwd=aaaaaa32
2007-08-29 18:38:44.514 INFO HttpListener0-2 [JavaCompiler]
D:\Sybase6.0\Shared\jdk1.4.2_10\bin\javac.exe -target 1.4
-source 1.4 -d D:\Sybase6.0\EAServer6\genfiles\java\classes
-classpath
D:\Sybase6.0\EAServer6\bin\..\lib\eas-server-14.jar;D:\Sybase6.0\EAServer6\bin\..\lib;
D:\Sybase6.0\EAServer6\bin\..\ant\lib\ant.jar;D:\Sybase6.0\Shared\jdk1.4.2_10\lib\tools.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\sslplus_nio.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\sslplus.jar;D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\EccpressoFIPSJca.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\EccpressoFIPS.jar;
D:\j2sdk1.4\lib;D:\Sybase6.0\EAServer6\bin\..\genfiles\java\classes;
D:\Sybase6.0\EAServer6\bin\..\lib\ext\jconn3.jar;D:\Sybase6.0\EAServer6\bin\..\lib\ext\jTDS3.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\ext\pbejbclient100.jar;D:\Sybase6.0\EAServer6\bin\..\lib\ext\pbjdbc12100.jar;
D:\Sybase6.0\EAServer6\deploy\webapps\ent\WEB-INF\classes;D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\11\web.components.ent162660.jar;
D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\11\web.components.ent162671.jar;
D:\Sybase6.0\EAServer6\lib\eas-server-14.jar;D:\Sybase6.0\EAServer6\lib;
D:\Sybase6.0\EAServer6\ant\lib\ant.jar;D:\Sybase6.0\Shared\jdk1.4.2_10\lib\tools.jar;
D:\Sybase6.0\EAServer6\lib\fips\jdk14\sslplus_nio.jar;D:\Sybase6.0\EAServer6\lib\fips\jdk14\sslplus.jar;
D:\Sybase6.0\EAServer6\lib\fips\jdk14\EccpressoFIPSJca.jar;D:\Sybase6.0\EAServer6\lib\fips\jdk14\EccpressoFIPS.jar;
D:\j2sdk1.4\lib;D:\Sybase6.0\EAServer6\genfiles\java\classes;
D:\Sybase6.0\EAServer6\lib\ext\jconn3.jar;D:\Sybase6.0\EAServer6\lib\ext\jTDS3.jar;
D:\Sybase6.0\EAServer6\lib\ext\pbejbclient100.jar;D:\Sybase6.0\EAServer6\lib\ext\pbjdbc12100.jar;
D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\3\lib.default-ext162090.jar
-sourcepath D:\Sybase6.0\EAServer6\genfiles\java\src
D:\Sybase6.0\EAServer6\genfiles\java\src\com\sybase\djc\org\omg\CosNaming\iiop_stubs\NamingContext.java
2007-08-29 18:38:59.634 INFO HttpListener0-2 [JavaCompiler]
2007-08-29 18:38:59.697 INFO HttpListener0-2 [JavaCompiler]
D:\Sybase6.0\Shared\jdk1.4.2_10\bin\javac.exe -target 1.4
-source 1.4 -d D:\Sybase6.0\EAServer6\genfiles\java\classes
-classpath
D:\Sybase6.0\EAServer6\bin\..\lib\eas-server-14.jar;D:\Sybase6.0\EAServer6\bin\..\lib;
D:\Sybase6.0\EAServer6\bin\..\ant\lib\ant.jar;D:\Sybase6.0\Shared\jdk1.4.2_10\lib\tools.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\sslplus_nio.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\sslplus.jar;D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\EccpressoFIPSJca.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\fips\jdk14\EccpressoFIPS.jar;
D:\j2sdk1.4\lib;D:\Sybase6.0\EAServer6\bin\..\genfiles\java\classes;
D:\Sybase6.0\EAServer6\bin\..\lib\ext\jconn3.jar;D:\Sybase6.0\EAServer6\bin\..\lib\ext\jTDS3.jar;
D:\Sybase6.0\EAServer6\bin\..\lib\ext\pbejbclient100.jar;D:\Sybase6.0\EAServer6\bin\..\lib\ext\pbjdbc12100.jar;
D:\Sybase6.0\EAServer6\deploy\webapps\ent\WEB-INF\classes;D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\11\web.components.ent162660.jar;
D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\11\web.components.ent162671.jar;
D:\Sybase6.0\EAServer6\lib\eas-server-14.jar;D:\Sybase6.0\EAServer6\lib;
D:\Sybase6.0\EAServer6\ant\lib\ant.jar;D:\Sybase6.0\Shared\jdk1.4.2_10\lib\tools.jar;
D:\Sybase6.0\EAServer6\lib\fips\jdk14\sslplus_nio.jar;D:\Sybase6.0\EAServer6\lib\fips\jdk14\sslplus.jar;
D:\Sybase6.0\EAServer6\lib\fips\jdk14\EccpressoFIPSJca.jar;D:\Sybase6.0\EAServer6\lib\fips\jdk14\EccpressoFIPS.jar;
D:\j2sdk1.4\lib;D:\Sybase6.0\EAServer6\genfiles\java\classes;
D:\Sybase6.0\EAServer6\lib\ext\jconn3.jar;D:\Sybase6.0\EAServer6\lib\ext\jTDS3.jar;
D:\Sybase6.0\EAServer6\lib\ext\pbejbclient100.jar;D:\Sybase6.0\EAServer6\lib\ext\pbjdbc12100.jar;
D:\Sybase6.0\EAServer6\temp\HDCHCTDANN6311\3\lib.default-ext162090.jar
-sourcepath D:\Sybase6.0\EAServer6\genfiles\java\src
D:\Sybase6.0\EAServer6\genfiles\java\src\com\sybase\djc\rmi\iiop\iiop_stubs\NameService.java
2007-08-29 18:39:21.611 INFO HttpListener0-2 [JavaCompiler]
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] javax.naming.NamingException:
com.sybase.djc.SystemException
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.ThreadContext.loadClass(ThreadContext.java:157)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.CdrInputStream.read_Object(CdrInputStream.java:1180)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.CdrInputStream_DJC.read_Object(CdrInputStream_DJC.java:952)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.ObjectRefHelper.read(ObjectRefHelper.java:25)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.SimpleObjectInputStream.readObject(SimpleObjectInputStream.java:102)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.SimpleObjectInputStream_DJC.readObject(SimpleObjectInputStream_DJC.java:940)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.SimpleObjectInputStream.readObject(SimpleObjectInputStream.java:91)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.SimpleObjectInputStream_DJC.readObject(SimpleObjectInputStream_DJC.java:903)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.iiop_stubs.NameService.resolve(NameService.java:468)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.resolve(ClientNamingContext.java:673)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.lookup1(ClientNamingContext.java:294)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.lookup(ClientNamingContext.java:251)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.naming.InitialContext.lookup(InitialContext.java:347)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.xml.util.EJBUtils.getInquiryHome(EJBUtils.java:27)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.xml.CoordinatorInquiriesProcessor.<init>(CoordinatorInquiriesProcessor.java:34)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.CoordinatorHttpRequestProcessor.<init>(CoordinatorHttpRequestProcessor.java:34)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.DispatcherSM.getGetRequestProcessor(DispatcherSM.java:86)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.EntServlet.doGet(EntServlet.java:103)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet.service(EntServlet.java:28)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC.access$201(EntServlet_DJC.java:4)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC$3.invoke(EntServlet_DJC.java:310)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:654)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:589)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC.service(EntServlet_DJC.java:339)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet$WC.service(EntServlet$WC.java:24)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.WebApplicationHandler.dispatch(WebApplicationHandler.java:157)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.WebApplicationHandler.handle(WebApplicationHandler.java:115)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpServer.service(HttpServer.java:909)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.HttpListener.handleConnection(HttpListener.java:107)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] Caused by: java.lang.ClassNotFoundException:
class loader: web.components.ent, class name:
com.ilx.mis.entIA.ejb.InquiryHome
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader.load(NamedClassLoader.java:616)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader_DJC.load(NamedClassLoader_DJC.java:916)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader.loadClass(NamedClassLoader.java:135)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader_DJC.loadClass(NamedClassLoader_DJC.java:1042)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader.loadClass(NamedClassLoader.java:111)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader_DJC.loadClass(NamedClassLoader_DJC.java:1000)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader.loadClass(NamedClassLoader.java:94)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.NamedClassLoader_DJC.loadClass(NamedClassLoader_DJC.java:958)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.util.ThreadContext.loadClass(ThreadContext.java:148)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] ... 46 more
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.resolve(ClientNamingContext.java:685)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.lookup1(ClientNamingContext.java:294)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.lookup(ClientNamingContext.java:251)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.naming.InitialContext.lookup(InitialContext.java:347)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.xml.util.EJBUtils.getInquiryHome(EJBUtils.java:27)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.xml.CoordinatorInquiriesProcessor.<init>(CoordinatorInquiriesProcessor.java:34)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.CoordinatorHttpRequestProcessor.<init>(CoordinatorHttpRequestProcessor.java:34)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.DispatcherSM.getGetRequestProcessor(DispatcherSM.java:86)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.ilx.mis.entIA.web.EntServlet.doGet(EntServlet.java:103)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet.service(EntServlet.java:28)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC.access$201(EntServlet_DJC.java:4)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC$3.invoke(EntServlet_DJC.java:310)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:654)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:589)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet_DJC.service(EntServlet_DJC.java:339)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
web.components.ent.EntServlet$WC.service(EntServlet$WC.java:24)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.WebApplicationHandler.dispatch(WebApplicationHandler.java:157)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.WebApplicationHandler.handle(WebApplicationHandler.java:115)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpServer.service(HttpServer.java:909)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
com.sybase.djc.server.jetty.HttpListener.handleConnection(HttpListener.java:107)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
2007-08-29 18:39:21.658 INFO HttpListener0-2
[ConsoleOutput] at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
2007-08-29 18:39:21.673 INFO HttpListener0-2
[ConsoleOutput] Response Status= 503
2007-08-29 18:39:21.689 INFO HttpListener0-2
[SystemException] java.lang.NoClassDefFoundError was thrown
by method
web.components.ent.EntServlet.service(javax.servlet.http.HttpServletRequest
, javax.servlet.http.HttpServletResponse)
2007-08-29 18:39:21.689 INFO HttpListener0-2
java.lang.NoClassDefFoundError:
org/apache/turbine/util/StringUtils
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.ilx.mis.entIA.web.EntServlet.doGet(EntServlet.java:136)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
web.components.ent.EntServlet.service(EntServlet.java:28)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
web.components.ent.EntServlet_DJC.access$201(EntServlet_DJC.java:4)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
web.components.ent.EntServlet_DJC$3.invoke(EntServlet_DJC.java:310)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:654)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:589)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
web.components.ent.EntServlet_DJC.service(EntServlet_DJC.java:339)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
web.components.ent.EntServlet$WC.service(EntServlet$WC.java:24)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.sybase.djc.server.jetty.WebApplicationHandler.dispatch(WebApplicationHandler.java:157)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.sybase.djc.server.jetty.WebApplicationHandler.handle(WebApplicationHandler.java:115)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpServer.service(HttpServer.java:909)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
com.sybase.djc.server.jetty.HttpListener.handleConnection(HttpListener.java:107)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
2007-08-29 18:39:21.689 INFO HttpListener0-2 at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
2007-08-29 18:39:21.689 WARN HttpListener0-2
[ServletHandler] Error for /ent/Coordinator
2007-08-29 18:39:21.689 WARN HttpListener0-2 Caused by:
java.lang.NoClassDefFoundError:
org/apache/turbine/util/StringUtils
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.ilx.mis.entIA.web.EntServlet.doGet(EntServlet.java:136)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
web.components.ent.EntServlet.service(EntServlet.java:28)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
web.components.ent.EntServlet_DJC.access$201(EntServlet_DJC.java:4)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
web.components.ent.EntServlet_DJC$3.invoke(EntServlet_DJC.java:310)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:654)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.sybase.djc.transaction.TransactionManager.invokeBeanManaged(TransactionManager.java:589)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
web.components.ent.EntServlet_DJC.service(EntServlet_DJC.java:339)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
web.components.ent.EntServlet$WC.service(EntServlet$WC.java:24)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.sybase.djc.server.jetty.WebApplicationHandler.dispatch(WebApplicationHandler.java:157)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.sybase.djc.server.jetty.WebApplicationHandler.handle(WebApplicationHandler.java:115)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpServer.service(HttpServer.java:909)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
com.sybase.djc.server.jetty.HttpListener.handleConnection(HttpListener.java:107)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
2007-08-29 18:39:21.689 WARN HttpListener0-2 | at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
2007-08-29 18:39:38.136 INFO HttpListener0-0
[TilesRequestProcessor] Tiles definition factory found for
request processor '/easmgmplugin'.
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: default
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: ejb.components.management
2007-08-29 18:44:10.886 INFO HttpListener0-2
[TransactionBatch:default] init: maximum batch size = 1,
maximum batch wait = 1 ms
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: lib.default-ext
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: application.console
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing:
ejb.components.console.managementejb
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: ejb.components.datawindow
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: ejb.components.entia
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing:
web.components.console.console
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: web.components.ent
2007-08-29 18:44:10.886 INFO HttpListener0-2
[NamedClassLoader] Refreshing: web.components.entia_xsl
2007-08-29 18:44:10.886 INFO HttpListener0-2
[N
Note that WebLogic 12c endorses JavaEE6.
Look ups and how JNDI works is explained in the JavaEE6 tutorial: http://docs.oracle.com/javaee/6/tutorial/doc/gipjf.html
Similar Messages
-
EJB lookup returned stub from a different classloader.
I've written an EJB for doing authenitcation. This EJB is accessed by an security-mbean (BEA's login module).
- The EJB is deployed in an EAR.
- The EJB-stubs are extracted and is included as part of the MBEAN Jar.
When I hit a webapp causing the EJB lookup to occur, the stub object returned is created by the webapp's classloader. This cause a ClassCastException when trying to cast the returned home interface into the home interface of the MBEAN's classloader.
Note that all this is happening on the same BEA server running WLS8.1.
I don't want to put the EJB jar on the system classpath so I can redeploy the EJB, the Application's EAR and the MBEAN to a cluster.
-alexRobert Greig <[email protected]> wrote:
Thanks for responding to my question, which newsgroup is more appropriate for
my line of question?
But before I move this thread, I would like to add:
I've already handled the recursion problem on top of the ejb-lookup before JNDI
becomes avaliable (while doing server startup) problem.
The advantage with the EJB model is this. By changing the host/port configuration,
I can switch between a local-authentication server or a remote provide authentication
server network configuration.
If I were to include the necessary classes in the mbean JAR from our application,
there maybe resources issues since I now have 2 classloaders loading my server-portion
of classes. Not sure how that will workout with resources and all. This model
has the disadvantage of any classes I have in the mbean JAR will require updates
outside my EAR. This wroks against the EAR deployment model.
-alex
Alex Cheung wrote:
I've written an EJB for doing authenitcation. This EJB is accessedby an security-mbean (BEA's login module).
- The EJB is deployed in an EAR.
- The EJB-stubs are extracted and is included as part of the MBEANJar.
This isn't a good approach. You are pretty much stuffed mainly for the
reasons you outline.
Also note that if you continue to go down this road you will have to
handle the potential recursion (i.e accessing an EJB will invoke a
security call to your provider!).
Why do you need to implement this as an EJB? The main advantages of EJBs
are security and container managed transactions neither of which is
relevant here surely?
Robert -
EJB lookup from another EJB server
Hi people,
I have two application servers on two different computers. One
of them contains an EJB, which I need to access from another EJB
server. I know that I can achieve this using RMI, but will then
security and transaction contexts be propagated to the called
EJB?
Sincerely,
Sergei Batiuk.Here is the solution posted on another forum:
[email protected] Dec 8, 6:03 am show options
Newsgroups: ibm.software.websphere.studio
From: [email protected]
Date: 8 Dec 2004 06:03:04 -0800
Local: Wed, Dec 8 2004 6:03 am
Subject: Re: EJB lookup on from one server to another does not work
Eric,
I dealt with this same problem trying to run 2 local servers (websphere
test servers), using 2 separate WSAD 5.1.2 workspaces. Running on 1
server I have an application that contains an EJB, and running on the
other server is an application that uses an access bean to make a
remote call to my EJB, running on my other server. I too repeately
received the "NameNotFoundException" when trying to lookup my EJB home
reference.
What you have to do to get around this is to modify the server
configuration of the application that contains the EJB that you are
attempting to call remotely. You must open the the server.wsi file for
the server that is running the EJB and go to the "Configuration" tab.
You must check the "Enable administrative console". Once this is
complete, start your server. When it is started, right click on the
server, and select "run administrative console". In the admin console,
select
servers -> application servers -> <your server> -> end points ->
bootstrap address. For "host" you must change "localhost" to either
your ip address or computer name (ive only tried my ip, but your
computer name should work too). When building your properties to get
the initial context, make sure you use
"env.put(Context.PROVIDER_URL, "corbaloc:iiop:<the ip or computer name
listed as the bootstrap host of server running ejb>:<the port listed as
the bootstrap port of server running ejb, which is 2809 in your case>
Restart your server and things should work. -
EJB lookup works in embedded OC4J but not stand-alone
I use JDeveloper 9.0.3.1 to develop a combined web & EJB application. The EJBs are deployed on a 9.0.3 iAS server on a different machine.
The EJB lookup is in a helper class that's called by the servlet. For EJB lookup, I use the class "com.evermind.server.rmi.RMIInitialContextFactory" as described by the OC4J servlet guide (http://download-uk.oracle.com/docs/cd/A97688_10/generic.903/a97680/develop.htm#1003973). So my code looks like this:
Hashtable map = new Hashtable();
map.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
map.put(Context.PROVIDER_URL, "ormi://server:port/app-business");
map.put(Context.SECURITY_PRINCIPAL, "admin");
map.put(Context.SECURITY_CREDENTIALS, "password");
map.put("dedicated.rmicontext", "true");
InitialContext context = new InitialContext(map);
Object thing = context.lookup("MyEjb");
EJBHome feedback = (EJBHome)PortableRemoteObject.narrow(thing, "com.company.ejb.MyEjbHome");
The last insert into the map (map.put("dedicated.rmicontext", "true");) wasn't mentioned neither in the servlet guide nor the EJB one. But without it, I'd always get some "domain is null" error.
Now this code above works flawlessly in the embedded OC4J of JDeveloper. But it always hangs in the "Object thing = context.lookup("MyEjb");" line when executed either in a stand-alone OC4J (the one from JDeveloper launched through the batch file in [JDeveloper directory]\jdev\bin\start_oc4j.bat) or in the OC4J in iAS.
Does anybody know why this happens or how to fix it? I know that there are other ways of EJB lookup in servlets but since we also have plain Java classes for testing purposes that access EJBs, this seemed like the simplest thing to do for both Java classes and servlets.I was referring to the java client case where this optoin is not required. In general for web clients one doesn't use the rmi initial context to find the bean. This is because the bean and the webclient are both packaged in the same application. One defines the ejb-ref in the web.xml for the bean and then looks it using the default initial context. Something like
Context ctx = new InitialCOntext();
ctx.lookup("bean ejb-ref-name");
However if you must use rmi for accessing the bean from the web client then the dedicated connection property is required.
For java clients you would setup the rmi context environment.
Since you are trying to use a common utility class for both java and webclient I would recommend that you look into packaging the java client as a j2ee application client. Basically in that case you would be able to define a ejb-ref in the aplication-client.xml and use the default initial context in code for both the cases.
Hope that helps
Dhiraj -
EJB lookup on Remote Server or different domain fails
Hi,
I am having two different domain (domain1,domain2) respectvely. My ABC.ear j2eee application is deployed on domain2 and its iiop port is 33703.In domain1 i have xyz.war (web application) and it's IIOP port is 3700 .In xyz.war i am having CallEJB.jsp file.In this Jsp file i want to lookup an EJB Service called PaymentEJB(JNDI Name is ejb/PaymentEJB).
The code is below
InitialContext context=new InitialContext();
Object objRef=context.lookup("corbaname:iiop:andaman:33703#ejb/PaymentEJB");
I am getting the following error.
[#|2005-12-14T16:42:03.422+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.corba._DEFAULT_.rpc.transport|_ThreadID=11;|"IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: all interfaces/3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2661)
My doubt is
1.While starting domain1 and domain2 iiop listeners are started on the port 3700 and 33703.in that case why EJB lookup tries to create listener on one more time.
2.I am looking the 33703 port only.but it tries to create port on 3700 why?
3.It was working till JES2005Q1.Is there any patch i need to install? or i need to change anything in my code.
I am frustrated with this error for past one week.I will be happy if some body will give me the peace of mind(thru some solution).Hi
I found the solution for this issue.
To lookup the EJB applications in web component,we should not set any thing in the Initial Context.i.e the lookup should be
InitialContext initContext=new InitialContext();
Object objref = initContext.lookup("java:comp/env/ejb/"+ejbName_);
This will get you the Home object of the EJB you are looking.
In your web.xml you should have the entry like below.(Just replace the ejbname which you are looking for)
<ejb-ref>
<ejb-ref-name>ejb/GetAssertionEJB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ssertion.GetAssertionHome</home>
<remote>com.assertion.GetAssertionRemote</remote>
</ejb-ref>
In your sun-wb.xml,you should have the entry like below(Just replace the ejbname which you are looking for)
<ejb-ref>
<ejb-ref-name>ejb/GetAssertionEJB</ejb-ref-name>
<jndi-name>corbaname:iiop:<hostname>:<iiopport>#ejb/GetAssertionEJB</jndi-name>
</ejb-ref>
Hope this works. -
JNDI EJB Lookup fails on Remote Server
Hi,
I am having two different domain (domain1,domain2) respectvely. My ABC.ear j2eee application is deployed on domain2 and its iiop port is 33703.In domain1 i have xyz.war (web application) and it's IIOP port is 3700 .In xyz.war i am having CallEJB.jsp file.In this Jsp file i want to lookup an EJB Service called PaymentEJB(JNDI Name is ejb/PaymentEJB).
The code is below
InitialContext context=new InitialContext();
Object objRef=context.lookup("corbaname:iiop:andaman:33703#ejb/PaymentEJB");
I am getting the following error.
[#|2005-12-14T16:42:03.422+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.corba._DEFAULT_.rpc.transport|_ThreadID=11;|"IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: all interfaces/3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:2661)
My doubt is
1.While starting domain1 and domain2 iiop listeners are started on the port 3700 and 33703.in that case why EJB lookup tries to create listener on one more time.
2.I am looking the 33703 port only.but it tries to create port on 3700 why?
3.It was working till JES2005Q1.Is there any patch i need to install? or i need to change anything in my code.
I am frustrated with this error for past one week.I will be happy if some body will give me the peace of mind(thru some solution).http://docs.sun.com/source/819-0079/dgjndi.html
This might help. -
CSS one-armed-config and SMTP reverse lookup problems?
I was wondering if there would be potential reverse lookup problems from other company's when we try to send mail to their mail Domains.
If I configure failover for our mail server, I am thinking if we are sending mail, there could be a reverse-lookup issue, because our mail server would be configured with public IP Addresses other than what the MX record points to in DNS.
If we originate mail from our inside users, it will originate from the service IP address and not the VIP address.
Is this a valid concern?The main advantage of this configuration is that the web servers will receive the IP address of the client that made the request. This is often required by web servers' administrators for accounting purposes.
In a one-armed configuration only, the network port ( Enet0) is used on the SCA. Only this specific port can be used for this setup. Encrypted and decrypted traffic will go through the same link
http://www.cisco.com/en/US/products/hw/contnetw/ps2083/products_configuration_example09186a00801bbf4e.shtml -
Hi, experts
I have a question with the EJB lookup in weblogic, this is a question which has been asked many times when I google that. But likely there is not a clearly answer, so maybe I can get the answer from the experts?
If we lookup an EJB, we need to use the "mappedName#interface_name" as the query name used in lookup method, Is this the only way that we query the EJB? Or is there any other ways we can simply the query name?
Thanks for your time.Try posting in the forum dedicated to WLS EJB - WebLogic Server - EJB
Also, why don't you explain what you're looking for exactly, how would you like to look up the EJB's, or are you asking for a best practice? Describing your use case will help get the best answer, right now your question is extremely generic. -
Hi,
I am new to J2EE and JDeveloper. I am trying to manually migrate one Oracle Form to J2EE. I have created two jsps. First JSP creates UI, does all the validation and then calls second jsp for processing. In second jsp I am trying to get homeinterface for ejb on which I will call database operations method. The problem I am facing is I am not getting what exactly should be entry for lookup(calling lookup on initail context). I tried to locate it in orion-ejb-jar.xml and also in ejb-jar.xml but didn't get it. Pls help me regarding the same.
Regds,
SampadaWell this is possible only in JDeveloper.
In the web.xml, specify the details as
<ejb-ref>
<ejb-ref-name>ejb/EmployeeHome</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>EmployeeHome</home>
<remote>Employee</remote>
<ejb-link>Employee</ejb-link>
</ejb-ref>
</web-app>
In the orion-ejb-jar.xml, specify the following
<orion-ejb-jar>
<enterprise-beans>
<session-deployment max-instances="-1" name="Employee" location="ejb/EmployeeHome"/>
<entity-deployment max-instances="-1" name="EmpEB" copy-by-value="false" data-source="jdbc/EmpDS" exclusive-write-access="false"/>
</enterprise-beans>
In the snippet above, i access a session bean, you change this according to ur settings.
The client code has been already posted above.
regards,
Sachin -
EJB from stored procedure lookup problem
We are running a test case with in an EJB deployed to Oracle 8.1.6, accessing it from a Java stored procedure. It works okay if the stored procedure is called a limited number of times from a single client (client is non-Java). However, for performance testing, we are trying to run it several hundred times in sequence to better simulate the eventual production environment. Consistently on the 216th call, it fails with a NamingException from the InitialContext lookup. We can restart the client again and it will fail on the same call.
Sounds like something memory related to me. Does anyone have any ideas? I'm using standard EJB client code in my stored procedure, instantiating an InitialContext, performing a lookup on the EJB, performing a home interface create, then accessing an EJB method.
Thinking it might be that my test was too fast for whatever garbage collection is being done on the server, I tried a 2 second delay between invocations--same problem occurs, however. Should I be making a call to remove my EJBs when my stored procedure ends? If so, how would I do that?
I did try making the handle to my EJB a static variable within the stored procedure and only "creating" the EJB once. That works okay with a single client, but if I run 2 clients simultaneously, 1 will work for awhile and then eventually die trying to call the EJB method--while the other client continues to run successfully.
I'm stumped. Any insight or guidance will be greatly appreciated. Thanks.My DBA bumped up the large_pool_size and java_pool_size settings and the problem went away. I couldn't convince him to bump the settings one at a time, so am not sure which one was at the root of the problem.
As I looked at the trace logs on the server, I also noticed that we were getting intermittent "peer disconnected socket" messages during the testing. That appears to have gone away with the pool size increases, also--in case that helps out anyone else. -
Ejb-ref and JNDI lookup problem
Hi,
I use WLS6.1sp2. I created one EntityBean and SessionBean jar files. I tried to
use session bean to refer entity bean, I failed. The details are as following:
In EntityBean's weblogic-ejb-jar.xml, I set:
<jndi-name>cabin.CabinHome</jndi-name>
In sessionbean's ejb-jar.xml
<ejb-ref>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.titan.cabin.CabinHome</home>
<remote>com.titan.cabin.Cabin</remote>
</ejb-ref>
In sessionbean's weblogic-ejb-jar.xml
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<jndi-name>ejb/CabinHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
At sessionbean's client, I use
javax.naming.Context jndiContext = getInitialContext();
Object obj = jndiContext.lookup("java:comp/env/ejb/CabinHome");
When I run client file, I get the following error message:
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome']; Link Remaining Name: 'ejb/CabinHome']>
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome'
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining name
'CabinHome']; Link Remaining Name: 'ejb/CabinHome']
at com.titan.travelagent.TravelAgentBean.listCabins(TravelAgentBean.java:45)
at com.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl.listCabins(TravelAgentBean_a4c3ph_EOImpl.java:37)
at com.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 1, 2002 11:32:40 PM PST> <Info> <Management> <dj> <travelServer> <ExecuteThread:
'14' for queue: 'default'> <system> <> <140009> <Configuration changes for domain
saved to the repository.>
Do you know what's wrong? how to fix this problem?
Thanks in advance.
DJSlava,
I took "cabin." out from weblogic-ejb-jar.xml, I got the same error.
DJ
"Slava Imeshev" <[email protected]> wrote:
Hi DJ,
I think you don't need "cabin." in weblogic-ejb-jar.xml :
<jndi-name>cabin.CabinHome</jndi-name>
Regards,
Slava Imeshev
"DJ" <[email protected]> wrote in message
news:[email protected]...
Hi,
I use WLS6.1sp2. I created one EntityBean and SessionBean jar files.I
tried to
use session bean to refer entity bean, I failed. The details are asfollowing:
In EntityBean's weblogic-ejb-jar.xml, I set:
<jndi-name>cabin.CabinHome</jndi-name>
In sessionbean's ejb-jar.xml
<ejb-ref>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.titan.cabin.CabinHome</home>
<remote>com.titan.cabin.Cabin</remote>
</ejb-ref>
In sessionbean's weblogic-ejb-jar.xml
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/CabinHome</ejb-ref-name>
<jndi-name>ejb/CabinHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
At sessionbean's client, I use
javax.naming.Context jndiContext = getInitialContext();
Object obj = jndiContext.lookup("java:comp/env/ejb/CabinHome");
When I run client file, I get the following error message:
- with nested exception:
[javax.naming.LinkException: [Root exception is
javax.naming.NameNotFoundException:>> Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining>name>> 'CabinHome'; Link Remaining Name: 'ejb/CabinHome']>
javax.naming.LinkException: . Root exception isjavax.naming.NameNotFoundException:
Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remainingname
'CabinHome'
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[javax.naming.LinkException: [Root exception is
javax.naming.NameNotFoundException:>> Unable to resolve ejb.CabinHome Resolved: '' Unresolved:'ejb' ; remaining>name>> 'CabinHome'; Link Remaining Name: 'ejb/CabinHome']
atcom.titan.travelagent.TravelAgentBean.listCabins(TravelAgentBean.java:45)
atcom.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl.listCabins(TravelAgentBe
an_a4c3ph_EOImpl.java:37)
atcom.titan.travelagent.TravelAgentBean_a4c3ph_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 1, 2002 11:32:40 PM PST> <Info> <Management> <dj> <travelServer><ExecuteThread:
'14' for queue: 'default'> <system> <> <140009> <Configuration changesfor
domain
saved to the repository.>
Do you know what's wrong? how to fix this problem?
Thanks in advance.
DJ -
Hi,
I have a client Java application accessing a session EJB in a remote JBoss J2EE server. I'm using JWS 1.2 to deploy my application but when I do a JNDI lookup to get access the the remote's object home interface I get this error:
"Need to specify class name in environment or system property, or as an applet parameter, or in an application resorce file: java.naming.factory.initial"
All the jar files are signed and the JNPL file contains <all-permissions/>. This is the code that triggers the exception
jndiContext = new InitialContext();
homeRMIReference = jndiContext.lookup(C_SERVICE_NAME);
Any help would be appreciated.
Thanks in advance,
RafaelHi,
I've finally found the origin of the problem.
1. JNDI uses a minimum set of properties during initialization phase:
java.naming.factory.initial
java.naming.factory.url.pkgs
java.naming.provider.url
Therefore these properties must be set in the <resource> topic of the JNLP file. The value of these properties is defined in the jndi.properties file that you can find in jbossjmx.ant.jar (within the jboss/client directory)
2. You have to add the JBoss files to your bundle. For doing so I've unjared all the .jar files within the jboss/client directory; afterwards I have jared them in a single file "jboss.jar" and I've signed the file. I've added jboss.jar to the <resource> tag within the JNLP file (Note that I've added all the jboss files just to do quick check but usually you will have to add only those files you need (it doesn't make sense to deploy all JBoss files in each client application)
I hope this helps,
Rafael -
JNDI lookup problem in WAS 5.1
Hello all,
I have generated an EAR using XDoclet and MyEclipse. When I deploy this EAR on WAS 5.1, I get the following exception:
javax.naming.NameNotFoundException: Context: WarHog/nodes/WarHog/servers/server1, name: ejb/TEDIObjectManagerLocal: First component in name TEDIObjectManagerLocal not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.rmi.iiop.CDRInputStream.readBoxedIDLEntity(CDRInputStream.java:2112)
at com.ibm.rmi.iiop.CDRInputStream.readIDLValue(CDRInputStream.java:2177)
at com.ibm.rmi.iiop.CDRInputStream.fast_read_value(CDRInputStream.java:1734)
at com.ibm.rmi.io.IIOPInputStream.readValueType(IIOPInputStream.java:2085)
at com.ibm.rmi.io.IIOPInputStream.readObjectField(IIOPInputStream.java:2057)
at com.ibm.rmi.io.IIOPInputStream.inputClassFields(IIOPInputStream.java:1765)
at com.ibm.rmi.io.IIOPInputStream.inputObjectUsingClassDesc(IIOPInputStream.java:1348)
at com.ibm.rmi.io.IIOPInputStream.continueSimpleReadObject(IIOPInputStream.java:420)
at com.ibm.rmi.io.IIOPInputStream.simpleReadObjectLoop(IIOPInputStream.java:404)
at com.ibm.rmi.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:347)
at com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:200)
at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1367)
at com.ibm.rmi.util.ProxyUtil.copyObject(ProxyUtil.java:450)
at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObject(UtilDelegateImpl.java:789)
at javax.rmi.CORBA.Util.copyObject(Util.java:333)
at com.wdc.tedi.interfaces._TransformationEngine_Stub.transform(_TransformationEngine_Stub.java:268)
at com.wdc.tedi.web.TestHarnessBean.translate(TestHarnessBean.java:42)
at com.wdc.tedi.web.TestHarnessBean.setDataBlob(TestHarnessBean.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)First of all, I don't really understand what the error means. Is it that the JNDI lookup failed when one of my beans tried to do a lookup on 'ejb/TEDIObjectManagerLocal'? I believe there's some configuration that went wrong (EJB reference binding or something) when I deployed the EAR. The reason I don't think it's a faulty code is because the EAR runs like a charm when I deploy it on Oracle 10g and Weblogic.
I am really stuck on this problem and shall appreciate any help that I can get. I can send the code, xdoclet tags and configuration if that might assist someone.
Thanks
-ybh6336Hello all,
I'm still stuck on this issue. Following are the entries related to my
application when I do a 'dumpNameSpace':
28 (top)/nodes/WarHog/servers/server1/ejb/tedi/TEDIObjectManager
28
com.wdc.tedi.interfaces._TEDIObjectManagerHome_Stub
29 (top)/nodes/WarHog/servers/server1/ejb/tedi/DSValueLookup
29
com.wdc.tedi.interfaces._DSValueLookupHome_Stub
30 (top)/nodes/WarHog/servers/server1/ejb/tedi/TransformationEngine
30
com.wdc.tedi.interfaces._TransformationEngineHome_StubObservations:
- I only see the namespace entries for my Session beans. There's one
entity bean also which does not show up.
- I don't see anything for the Local Home interfaces, it shows only the
Home interfaces.
As additional information, I'm looking up 'TEDIObjectManagerLocal'
using 'ejb/TEDIObjectManagerLocal'. I also tried using 'local:ejb/ejb/TEDIObjectManagerLocal' (as Karthyk suggested) and
'java:comp/env/ejb/TEDIObjectManagerLocal', but that does not work
either.
Also, the XDoclet tags that I use to generate the interfaces for
TEDIObjectManager bean are as follows:
/* @ejb.bean name="TEDIObjectManager"
* display-name="TEDIObjectManager"
* description="TEDIObjectManager"
* jndi-name="ejb/tedi/TEDIObjectManager"
* local-jndi-name="ejb/TEDIObjectManagerLocal"
* type="Stateless"
* view-type="both"
* @ejb.util generate="physical"
* @ejb.ejb-ref ejb-name="TEDIObject"
* view-type = "local"
* ref-name = "ejb/TEDIObjectLocal"
* @oc4j.bean jndi-name="ejb/tedi/TEDIObjectManager"
*/My ejb-jar.xml looks like following for that bean:
<session >
<description><![CDATA[TEDIObjectManager]]></description>
<display-name>TEDIObjectManager</display-name>
<ejb-name>TEDIObjectManager</ejb-name>
<home>com.wdc.tedi.interfaces.TEDIObjectManagerHome</home>
<remote>com.wdc.tedi.interfaces.TEDIObjectManager</remote>
<local-home>com.wdc.tedi.interfaces.TEDIObjectManagerLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TEDIObjectManagerLocal</local>
<ejb-class>com.wdc.tedi.ejb.TEDIObjectManagerSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-local-ref >
<ejb-ref-name>ejb/TEDIObjectLocal</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.wdc.tedi.interfaces.TEDIObjectLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TEDIObjectLocal</local>
<ejb-link>TEDIObject</ejb-link>
</ejb-local-ref>
</session>AND following for the bean that is referencing it:
<session >
<description><![CDATA[TransformationEngine]]></description>
<display-name>TransformationEngine</display-name>
<ejb-name>TransformationEngine</ejb-name>
<home>com.wdc.tedi.interfaces.TransformationEngineHome</home>
<remote>com.wdc.tedi.interfaces.TransformationEngine</remote>
<local-home>com.wdc.tedi.interfaces.TransformationEngineLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TransformationEngineLocal</local>
<ejb-class>com.wdc.tedi.ejb.TransformationEngineSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-local-ref >
<ejb-ref-name>ejb/TEDIObjectManagerLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.wdc.tedi.interfaces.TEDIObjectManagerLocalHome</local-home>
<local>com.wdc.tedi.interfaces.TEDIObjectManagerLocal</local>
<ejb-link>TEDIObjectManager</ejb-link>
</ejb-local-ref>
</session>The entries in ibm-ejb-jar-bnd.xmi (generated using MyEclipse) are as
follows for the two beans:
<ejbBindings
xmi:id="Session_bnd_1"
jndiName="ejb/tedi/TransformationEngine">
<ejbRefBindings xmi:id="EJBRefBnd_1"
jndiName="ejb/TEDIObjectManagerLocal">
<bindingEjbRef href="META-INF/ejb-jar.xml#EJBLocalRef_1"/>
</ejbRefBindings>
<enterpriseBean
xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_TransformationEngine" />
</ejbBindings>
<ejbBindings
xmi:id="Session_bnd_3"
jndiName="ejb/tedi/TEDIObjectManager">
<ejbRefBindings xmi:id="EJBRefBnd_2"
jndiName="ejb/TEDIObjectLocal">
<bindingEjbRef href="META-INF/ejb-jar.xml#EJBLocalRef_2"/>
</ejbRefBindings>
<enterpriseBean
xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_TEDIObjectManager" />
</ejbBindings>I know I'm swamping the post with code, but please let me know if anyone finds something unusual.
NOTE: When deploying on WAS, in the 'Map EJB references to beans' step, I'm giving the following values for 'TransformationEngine' bean:
Reference binding: ejb/TEDIObjectManagerLocal
JNDI Name: ejb/tedi/TEDIObjectManager
There's one other similar binding that works for 'TEDIObjectManager'
bean:
Reference binding: ejb/TEDIObjectLocal
JNDI Name: ejb/TEDIObject
Everything in ejb-jar and ibm-ejb-jar-bnd.xmi look similar for this working bean, there is one difference though, I do the lookup on this one using 'java:comp/env/ejb/TEDIObjectLocal', but I've already tried that for the other one.
Really appreciate your time.
Thanks
-yogesh -
Ejb lookup and oc4j container startup
I have a servlet that is set to auto start on container startup that does a lookup on a ejb in another container. jndi locates the ejbhome but fails to load the class for the ejb home. It knows the name of the class but the classloader cannot find it. This same servlet works fine after the container has started up.
It feel the problem is a classloader problem or a restriction by oracle. Any help is appreciated.
Why can't the OC4J default application that auto starts servlets at container startup not find the ejbhome class?
David JacobsWe have previously done it, but it only worked when we are using in 10g AS R1. But now, we are porting to R2, but it doesn't work. We didn't do any other things, just a simple lookup using the url, context factory. In R1 it worked fine, in R2, we are encountering the same, NameNotFoundException. Hope someone could help us also with this. Another thing, when we are using ormi://<rest of url>, it doesn't return any exception and our application hangs, but if we use opmn:ormi://<rest of URL>, that's the time it throws the NameNotFoundException. In R1, we didn't have any problems.
-
EJB lookup failing in DCM managed Oracle AS clustering
Hi
My purpose is to test DCM managed Oracle AS clustering:
For that I have two Oracle Application servers installed in two different machines with
Version: 10.1.2.0.2 and Installation Type as J2EE and Web Cache
I created an OracleAS File-based Farm and associated both the instances of AS to the cluster. Then I created One OC4J instance called InstanceOne on the cluster and deployed my Application ear onto the cluster.I also configued web Application and EJB Application State Replication the with OracleAS Cluster (OC4J).
My Application has one Ejb module and a web module. My stateless Session bean is Spring framework implemented and I am trying to load the Spring Context lookup from the Struts Action Class by using WebApplicationContext.
My spring context looks like this
<bean id="jndiTemplate"
class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">com.evermind.server.rmi.RMIInitialContextFactory</prop>
<prop key="java.naming.provider.url">opmn:ormi://<server host>:InstanceOne/<Application Name></prop>
<prop key="java.naming.security.principal">oc4jadmin</prop>
<prop key="java.naming.security.credentials">admin</prop>
<prop key="oracle.j2ee.naming.cache.timeout">30</prop>
<prop key="Dedicated.Connection">yes</prop>
<prop key="Dedicated.RMIcontext">false</prop>
<prop key="LoadBalanceOnLookup">true</prop>
</props>
</property>
</bean>
<bean id="service"
class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean">
<property name="jndiTemplate">
<ref bean="jndiTemplate"/>
</property>
<property name="jndiName">
<value>MyServiceEJB</value>
</property>
<property name="cacheHome">
<value>false</value>
</property>
<property name="refreshHomeOnConnectFailure">
<value>true</value>
</property>
<property name="businessInterface">
<value>com.my.springejb.MyBusinessInterface</value>
</property>
</bean>
When I give only one server lookup like
opmn:ormi://<server host1>:InstanceOne/<Application Name>
then lookup is working, But by giving two servers in cluster, like opmn:ormi://<server host1>:InstanceOne/<Application Name>, opmn:ormi://<server host2>:InstanceOne/<Application Name>
I am getting error like this
06/12/01 19:27:41 java.lang.NumberFormatException: For input string: "InstanceOne"
06/12/01 19:27:41 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
06/12/01 19:27:41 at java.lang.Integer.parseInt(Integer.java:468)
06/12/01 19:27:41 at java.lang.Integer.parseInt(Integer.java:518)
06/12/01 19:27:41 at com.evermind.server.rmi.RMIInitialContextFactory.getInitialContext(RMIInitialContextFactory.java:237)
06/12/01 19:27:41 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
06/12/01 19:27:41 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
06/12/01 19:27:41 at javax.naming.InitialContext.init(InitialContext.java:219)
06/12/01 19:27:41 at javax.naming.InitialContext.<init>(InitialContext.java:195)
06/12/01 19:27:41 at org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:105)
06/12/01 19:27:41 at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)
06/12/01 19:27:41 at org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.create(SimpleRemoteStatelessSessionProxyFactoryBean.java:19)
My intension of testing is, if I make one server instance (InstanceOne) down then my lookup should divert all ejb calls to the other server in the cluster, which is not happening at all, and I am getting Server SHUT DOWN exception in the server.
Can anybody please let me know, whether the approach is correct and is there any problem with Spring lookup which does not support multiple host lookup or anything I am missing in my steps, as I am following the Oracle Application Server High Availability Guide 10g Release 2 (10.1.2)you can find an running sample from :
http://javahowto.blogspot.com/2007/12/calling-weblogic-ejb-3-from-jruby-and.html
In weblogic, local ejb don't appear in the jndi tree, but , it can be founded ...
It works into 10.0 and 10.3
Cheers !
Maybe you are looking for
-
How do I recover lost files off my external WD Passport hard drive with Time Machine?
I have been backing up my Macbook Pro with Time Machine and my Western Digital Passport since May 2010. I accidentally deleted my music in February of 2011, but had backed it up with Time Machine. Now when I try to go back and recover the files in Ti
-
Hi gurus the misc account at the end of the period only show one leg of the journal when we run the account analysis report,the journal is Cash 01.00.00.000.60628.000.000 45.00(cr)asset Miscellaneous Cash 01.00.00.000.60627.000.000 45.00(dr)liability
-
I wrote an applet who connects to a database on a network where WebServer and Oracle Server were in the same host. Now I have to migrate the applet to a network where the Webserver and the database server are in diferent hosts. Because of security is
-
Hello there, Does somebody know how I can make dashboards in 2004s or where I can get some information about dashboards??Ik would like to build one
-
JPG files copied to Philips Picopix 3410 are currupted with a prefix of ._ and will not display on the PicoPix. Help please?