Problem in accessing an ejb deployed in WLS

Hi,
I deployed my EJB in WL 8.1, when I use weblogic.jar I can able to access. But when I use the wlclient.jar and wl-j2ee-client.jar I am getting following exception:
- javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:50)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:499)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:465)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.dnaO2.infra.serviceadaptor.util.ServiceAdaptorUtility.getInitialContext(ServiceAdaptorUtility.java:141)
at com.dnaO2.infra.serviceadaptor.ejb.EJBHomeServiceLocator.getHome(EJBHomeServiceLocator.java:59)
at com.dnaO2.infra.serviceadaptor.ejb.EJBSrvEndPoint.callEJBService(EJBSrvEndPoint.java:88)
at com.dnaO2.infra.serviceadaptor.ejb.EJBService.callSrvEndPointMethod(EJBService.java:76)
at com.dnaO2.infra.serviceadaptor.ejb.EJBService.invokeService(EJBService.java:58)
at com.dnaO2.login.bo.LoginBO.invokeServiceAdaptor(LoginBO.java:305)
at com.dnaO2.login.bo.LoginBO.createOrUpdateUser(LoginBO.java:58)
at com.dnaO2.login.bizsrv.LoginAppSrv.createOrUpdateUser(LoginAppSrv.java:85)
at com.dnaO2.login.bizsrv.LoginFacade.createUser(LoginFacade.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:214)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:130)
at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor.java:51)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:335)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:139)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
at org.jboss.ejb.Container.invoke(Container.java:873)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:155)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104)
at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
at $Proxy75.createUser(Unknown Source)
at com.dnaO2.login.common.LoginBD.createUser(LoginBD.java:90)
at com.dnaO2.login.test.LoginTestClient.createUser(LoginTestClient.java:50)
at org.apache.jsp.loginTest_jsp._jspService(org.apache.jsp.loginTest_jsp:48)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.ORBPackage.InvalidName
at org.jacorb.orb.ORB.resolve_initial_references(Unknown Source)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:488)
... 81 more
Waiting for reply,
RK

Similar Messages

Problem in accessing the ejbs

HI ,
I am New to EJB. Here i am getting a problem n accessing the resoucess which are deployed in weblogic. Here i want to access the resoucess from a jsp. So i declared a web.xml. In that what i need to write. can anybody help me what i can specify in web.xml
Thank you.

Stop asking the same question again and again. It will decrease your chances of actually getting some help, because your rudeness will make people angry and less inclined to help.
Your whole approach sounds wrong, but that's your problem. I'm betting that you don't need EJBs. You shouldn't write JSPs without JSTL. Totally, utterly wrong.
But if you insist, I would recommend that you actually get a book or some documentation that shows you how to call an EJB from a web app. Since you're using WebLogic, maybe reading their documentation will help:
http://edocs.bea.com/wls/docs70/webapp/components.html
%

Problem in Accessing the EJB

I want to access remote EJB from my Portal Service.
the EJB and the portal Service run on a separated machines.
here is what i wrote:
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sap.engine.services.jndi.InitialContextFactoryImpl");
properties.put(Context.PROVIDER_URL, "p030633:50004");
InitialContext context = new InitialContext(properties);
String name = "sap.com/GDS/GtinManager";
GtinManagerHome home = (GtinManagerHome)
javax.rmi.PortableRemoteObject.narrow.narrow(
context.lookup(name), GtinManagerHome.class);
gm = (GtinManager)home.create();
i run this code from java application and it works.
but in portal i get this error:
"com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at GDS, the whole lookup name is sap.com/GDS/GtinManager."
Thanks
Raja

Hello,
if you NW 04 SP7 or higher, please look this document
https://www.sdn.sap.com/sdn/index.sdn?contenttype=url&content=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to access an ejb from a portal component.mht
else in EP6 SP2, it is more difficult to access to an EJB because the portal have an other classloader sysem and other JNDI context
Best Regards,
Fabrice

Problem with database access in EJB deployment to SJSAS on remote deploy

Hi,
I have deployed an Enterprise application containing an EJB3.0 module to a remote sun application server (Edition 9.0_01 (build b02-p01))
using a mysql ver 5 DB with connector
mysql-connector-java-5.0.0-beta-bin.
It is being used by a swing application client deployed as a module of a separate Enterprise application.
The client can access the session beans but when the EJB tries to create a query with the entity manager the client fails and the following exception appears in the log.
Timestamp:
Aug 20, 2007 09:36:38.910
Log Level:
INFO
Logger:
javax.enterprise.system.container.ejb
Name-Value Pairs:
_ThreadID=21;_ThreadName=p: thread-pool-1; w: 7;
Record Number:
2239
Message ID:
javax.ejb.EJBTransactionRolledbackException at com.sun.ejb.containers.BaseContainer.mapBusinessInterfaceException(BaseContainer.java
Complete Message
1373)
     at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1290)
     at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:192)
     at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:71)
     at $Proxy329.findAll(Unknown Source)
     at test.TestGuyBean.getTheWordGreat(TestGuyBean.java:36)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1050)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:165)
     at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2766)
     at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3847)
     at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:190)
     at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:67)
     at $Proxy323.getTheWordGreat(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:121)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:650)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:193)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1705)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1565)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:947)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:178)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:717)
     at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:473)
     at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1270)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:479)
Caused by: javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is:
java.lang.IllegalArgumentException:
An exception occured while creating a query in EntityManager
     at com.sun.ejb.containers.BaseContainer.checkExceptionClientTx(BaseContainer.java:3588)
     at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3436)
     at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1247)
     ... 30 moreThis is a result of a test portion of the application, but similar results occur when the actual application is run.
The "at test.TestGuyBean.getTheWordGreat(TestGuyBean.java:36)" is
being invoked by the client and "$Proxy329.findAll(Unknown Source)" is where the query is constructed.
The code is as follows
public String getTheWordGreat(String bob){
        String s = "abcdefgh ";
        List<MobileDialingCodes> c = mobileDialingCodesFacade.findAll();
        for (MobileDialingCodes elem : c) {
            s += elem.getNumber() + " ";
//        System.out.println("bob");
        return s;
public ArrayList<MobileDialingCodesHC> getAllDialingCodes(){
        List allCodesEJB = findAll();
        ArrayList<MobileDialingCodesHC> allCodesHC = new OurArrayList();
        for (Object elem : allCodesEJB) {
            allCodesHC.add(convertEJBtoHC((MobileDialingCodes)elem));
        return allCodesHC;
}The default config for the application is used and the application
uses the netbeans defaults. Netbeans 5.5. Toplink persistence manager.
Any suggestions would be appreciated.
null

Did you try after restarting the iAS server?

Error when ejb deployment in WLS 9.1 clustered environment

Hello,
We have a WLS 9.1 cluster consisting of one admin server and two managed servers. we are deploying ejb jar,It is succeed on the first managed server but fail on the second managed server. The admin console and for the second managed server contains the following log(below given). I checked the classpath of two managed servers, It is same in two servers. when i restarted the two managed servers, application is in active state but not running in second managed sever complining for one ejb class that the jndi-name in the weblogic-ejb-jar.xml is not correct. If it is not correct it should not run in first managed server also right.
please help me whether Am I doing something wrong or is this a bug?
below given the log when i deployed the ejb.
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762802> <BEA-149265> <Failure occured in the execution of deployment request with ID '1179481757718' for task '8'. Error is: 'java.lang.AssertionError: Assertion violated'
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762823> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'MyEJB'.
Regards,
mohan
Edited by raj_bea_raj at 05/29/2007 1:35 AM
Edited by raj_bea_raj at 05/29/2007 1:41 AM

If you're using OC4J standalone, use the latest available OC4J, 10.1.3.3.
If you're using a manage OC4J, ie. Application Server, upgrade to the latest available version and upgrade your JDK. The provided JDK might be outdated.
--olaf

Problem in accessing a EJB bean through a servlet

Dear all,
I'm a trying to call a stateless session bean which has its home and component interfaces, which prints the name it receives from the servlet client.
I'm trying to access a remote server EJB beans, which has been registered with JNDI & when deploying the EJB beans onto the Jboss server which operates in localhost: 8081 it has shown
20:19:16,890 INFO [EjbModule] Deploying greetBean
   20:19:17,109 INFO [ProxyFactory] Bound EJB Home 'greetBean' to jndi 'greetJndi'
20:19:17,125 INFO [EJBDeployer] Deployed: file:/C:/jboss-4.0.5.GA/server/default/deploy/greet.jarThis is my servlet which is there in tomcat container which runs in localhost:8082 to access the bean:
import java.net.*;
import javax.ejb.*;
import javax.rmi.*;
import java.rmi.*;
import javax.naming.*;
import java.util.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class greetServlet extends HttpServlet
public void doPost
(HttpServletRequest req, HttpServletResponse res)
throws ServletException,IOException
res.setContentType("text/html");
PrintWriter out=res.getWriter();
try
     out.println("Inside servlet");
Properties props=new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
*props.put(Context.PROVIDER_URL, "localhost:8081");*
props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
System.out.println("Properties ok");
Context ctx=new InitialContext(props);
System.out.println("context ok");
greetHome home = (greetHome)
ctx.lookup("greetJndi");
System.out.println("home ok");
greetRemote remote=home.create();
System.out.println("remote ok");
String a = req.getParameter("text1");
String s = remote.greetme(a);
System.out.println(s);
out.println(s);
catch(Exception e)
{System.out.println(""+e);}
}When i try to access the bean it's throwing a communication exception. The exact stack trace is:
javax.naming.CommunicationException: Could not obtain connection to any of these
      urls: localhost:8081 and discovery failed with error: javax.naming.Communicatio
     nException: Receive timed out [Root exception is java.net.SocketTimeoutException
     : Receive timed out] [Root exception is javax.naming.CommunicationException: Fai
     led to retrieve stub from server localhost:8081 [Root exception is java.io.EOFEx
ception]]Could anyone say why this is occuring and how this can be fixed.
Thanx in advance.

when i change the properties url attribute to jnp://localhost:1099 like
props.put(Context.PROVIDER_URL, "jnp://localhost:1099");It's throwing unmarshall exception:
javax.naming.CommunicationException [Root exception is java.rmi.ServerException:
RemoteException occurred in server thread; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested excep
tion is:
        java.net.MalformedURLException: no protocol: Files/Apache]Could anyone throw light on this?

Problem in accessing Data Source Deployed in JBoss using JNDI

Hi everybody!
I need your help in the next question:
I have created a data source to connect to my MySql data base using the following entry in mysql-ds.xml (JBOSS 3.2.5)
<datasources>
    <local-tx-datasource>
        <jndi-name>MySqlDS</jndi-name>
        <connection-url>jdbc:mysql://localhost:3306/mytest</connection-url>
        <driver-class>com.mysql.jdbc.Driver</driver-class>
        <user-name>root</user-name>
        <password>1</password>
    </local-tx-datasource>
</datasources> in Eclipse SDK 3.1.2 i trying get access to the datasource
InitialContext initialContext = new InitialContext();
DataSource ds = (DataSource)initialContext.lookup("java:/MySqlDS");
if (ds != null) {
    result = ds.getConnection();
                   System.out.println("OK");
    else {
         System.out.println("Failed to lookup datasource.");
    } http://localhost:8080/jmx-console service = JNDI name equal "java:/MySqlDS"
I have error "Cannot get connection: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial"
Error happen in
DataSource ds = (DataSource)initialContext.lookup("java:/MySqlDS");I trying
DataSource ds = (DataSource)initialContext.lookup("MySqlDS");and i had such error.
Can anybody help me?

hi,
please check is your error corrected
public class DBConnection {
     static DataSource dataSource = null;
     * To get the datsource
     public static DataSource getDatasource() {
          InitialContext ctx=null;
     if (dataSource == null){
     try {
          ctx=new InitialContext();
dataSource = (DataSource) ctx.lookup("java:/MySqlDS");
     } catch (Exception e) {
     System.out.println("eror in DataSource class"+e);
     try {
     ctx.close();
     } catch (Exception e) {
          System.out.println("eror in DataSource class context closing"+e);
     return dataSource;
     * To get connection from Database.
     public static Connection getConnection() {
               Connection con = null;
               DataSource dataSource = null;
               try {
                    dataSource =getDatasource();
                    con = dataSource.getConnection();
               } catch (SQLException e) {
                    e.printStackTrace();
               } catch (Exception e) {
                    e.printStackTrace();
               return con;
if you want a connetion then call Connection con=DBConnection .getConnection()
hope this helps you

Access romote EJB using EJBTransport

I'm trying to access an ejb deployed in WLS 8.1 SP6 from ALSB 2.5 using the EJBTransport following the instructions conteined in http://e-docs.bea.com/alsb/docs25/userguide/ejbtransport.html#wp1074283
But... when I tried to register an ejb client jar resourse I got these conflicts:
java.lang.IncompatibleClassChangeError:class services.ClientesSrv_r155q8_HomeImpl_816_WLStub has interface weblogic.rmi.extensions.server.Stub as super class
java.lang.NoClassDefFoundError:weblogic/ejb20/interfaces/BaseEJBObjectIntf
The ejb client jar was generated using weblogic.appc. Any help would be really appreciated.
Thanks in advance, Paulo.

You need to remove the stub classes from the client jar. Those classes are meant for a standalone java client or another 8.1 server.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Problems in accessing EJB from stand-alone client

Hi,
I am trying to access a EJB deployed in RI from a stand-alone client. When I run it, I got this exception:
Exception in thread "main" java.rmi.AccessException: CORBA NO_PERMISSION 9998 Ma
ybe; nested exception is:
org.omg.CORBA.NO_PERMISSION: minor code: 9998 completed: Maybe
org.omg.CORBA.NO_PERMISSION: minor code: 9998 completed: Maybe
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc
eption(ReplyMessage_1_2.java:93)
at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException(
ClientResponseImpl.java:108)
at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli
entSC.java:136)
at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
at TheBeanRemoteStub.test(Unknown Source)
at Client.main(Client.java:19)
The following is the code of the client:
System.setProperty(Context.SECURITY_PRINCIPAL, "achong");
System.setProperty(Context.SECURITY_CREDENTIALS, "achong");
Context context = new InitialContext(System.getProperties());
Object object = PortableRemoteObject.narrow(context.lookup("MyBean"), TheBeanHome.class);
TheBeanHome home = (TheBeanHome) object;
I have set "support client choice" while deploying the bean, and set which roles can access which methods. Any idea? Is my code is incorrect?

I have the same problem like you.
If you solve it, please give me a hint.
Thank you very much!
[email protected]

Can't access EJB deployed on remote OC4J - what am I doing wrong?

I'm unable to access an EJB deployed on a remote OC4J instance (ie, part of a 9iAS installation on another machine vs local in JDeveloper).
I've reverted to a stupid-simple EJB in hopes of getting it going prior to trying my actual code. The EJB works fine in JDev (9.0.3) - I 'run' the EJB to start the local OC4J instance, run my client code (generated via the "New Sample Java Client..." option in the Navigator context popup) and all is well.
I then create an EAR file via the the "Create EJB Jar Deployment Profile..." context popup of the ejb-jar.xml node, followed by "Deploy to EAR file" from the context popup of the resulting ejb1.deploy node. I next "Deploy EAR File" via the "Oracle Enterprise Manager" that comes with 9iAS (the :1810 port). After successfully deploying, I modify my client code in JDeveloper, specifying the new connection information for the remote machine via the Hashtable constructor of InitialContext and attempt to run it. I've tried a number of Context.PROVIDER_URL forms, including: ormi://registered_pingable_host_name:23791/deployed_application_name
ormi://registered_pingable_host_name:23791/session_deployment_name (from the <enterprise-beans><session-deployment name="xxx"/></enterprise-beans> section of my orion-ejb-jar.xml file, as per a tip in this forum)
I've tried prefixing ormi:// with http:, but get no response whatesoever in this case.
I've also tried it without the port number (this port number matches that in my remote OC4J's <oc4j_instance_home>/config/rmi.xml file).
On the Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS settings, I've tried various values, generally using the 'admin' user, with passwords taken from:
<oc4j_instance_home>/principals.xml
<oc4j_instance_home>/application-deployments/application_name/principals.xml
I've also tried matching the password in the jazn-data.xml, to no avail - this password appears encrypted anyway, but thought I'd give it a try on the off-chance that it was just a randomly-generated password - no go.
I've also tried SCOTT/TIGER, anonymous, etc. Incidentally, the 'deactivated' attribute of the <user> tag is set to "false" in my principals.xml files.
No matter what I do, I always get back "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect"
Additionally, I get this same message when I try to establish an Application Server Connection via JDev.
Clearly, I'm missing something critical (and probably simple), but I can't for the life of me figure it out.
Any help would be much appreciated!
Thanks,
Jim Stoll

Ok, well this is a bit strange...
3103 - 3103 also fails, and some experimentation has led me to find that any time that I specify a range smaller than 6 (3101 - 3106 works, 3101 - 3105, 3101-3101, 3103-3103, etc does not), the OC4J instance will not restart. I get "An error occurred while starting. The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes started. Check opmn log files such as ipm.log and ons.log for detailed." in the OEM window (I specify the RMI port range, hit Apply, go to the OC4J instance home page, see that the Status is 'Down', hit Start, and get that message.) <ORACLE_HOME>/product/iasinfra/opmn/logs/ipm.log tells me:
02/12/03 09:41:12 There is no rmi port left for starting an OC4J process. Please check oc4j's port property in OPMN's configuration file.
02/12/03 09:41:12 start_proc: UID 3719788: failed to build args
02/12/03 09:41:12 start_proc_req: failed to start a process in GID OC4JJim2, type: 2
If I bump it up to 3101 - 3106 or higher, it starts right up. Running opmnadmin debug, as suggested by Venky (thanks Venky!), yields:
PROCESS TABLE
UID PID FLAGS TYPE STATUS REF HTTP AJP RMI JMS
3654011 84 00000040 OC4J Alive 1 0 3005 3106 3206
424987 604 00000000 Apache Alive 1 7777 0 0 0
2932088 14849 00000000 OC4J Alive 1 0 3003 3103 3203
3063160 14878 00000000 OC4J Alive 1 0 3001 3101 3201
3194232 14906 00000000 OC4J Alive 1 0 3000 3105 3205
3325304 14936 00000000 OC4J Alive 1 0 3002 3102 3202
3456376 14964 00000000 OC4J Alive 1 0 3004 3104 3204
Which is what I would expect, given the specified range of 3101-3106. Trying each of these ports in turn, I've found that I can hit the EJB successfully on 3106, but 3101 - 3105 all fail with:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: No such domain/application: Project7_2; nested exception is:
     javax.naming.AuthenticationException: No such domain/application: Project7_2
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage9.MySessionEJBClient1.main(java.lang.String[])
          MySessionEJBClient1.java:15
I'm a little concerned about assuming the high-end of the range to be the active port on a regular basis (though thus far, among about 20 - 30 tries spaced over 20 - 30 minutes, it has been...) - I guess I can have my code loop through the range until it finds a good port or exhausts the list, but that seems a bit excessive.
Can you think of a reason that my OC4J instance won't start with a range size of less than 6? I'm on 9iAS 9.0.2, if that makes any difference.
Thanks,
Jim

ViewController to call deployed EJB JAR on WLS

Hi,
I have Model project containing EJB deployed into WLS as EJB JAR file.
I need to create another application for the View and reference the deployed EJB JAR.
The idea is to call remote EJB without having and any project dependencies.
Can you please advice on how it can be done.
Thank you in advance
Emile

Hi Frank,
The Model is only EJB.
The View only contains ADF Faces (no bindings , no page def , no datacontrol).
Please consider it as urgent
Thank you for your reply
Edited by: ebitar on Oct 12, 2011 9:46 AM

Error while accessing EJB deployed in another app

Hi,I have an EJB deployed in another application and was trying to access it from different application (both running on seperate weblogic server 5.1)when i do look-up like this : Hashtable hmRemote = new Hashtable(); hmRemote.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); hmRemote.put(Context.PROVIDER_URL, "http://localhost:7001/doc"); Hashtable hmLocal = new Hashtable(); hmLocal.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); hmLocal.put(Context.PROVIDER_URL, "http://localhost:7004/amit"); hmLocal.put(WLContext.DELEGATE_ENVIRONMENT, hmRemote); Context ctx = new InitialContext(hmLocal);I get following error on console :Wed May 02 12:28:30 CDT 2001:<I> <ConMan> Bootstrap unable to get a http connection to localhost/127.0.0.1Wed May 02 12:28:30 CDT 2001:<I> <ConMan> Bootstrap unable to get a http connection to localhost/127.0.0.1Exception caught in try javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found atHTTP://localhost:7001]Please help me.thanksamit

I solved the problem or I learned the process. I forgot to add two jar files in tomcat shared library. It is working now. Thanks.

How to access an EJB from a web application deployed in the same server

Hey All,
I deployed an EJB named EventServerBean to Sun Application Server 9.0, and put the client side jar file (named eventserver.jar which is generated by Sun Application Server) to C:\Sun\AppServer\lib. Now, I have a web application which is a simple jave file -- lookup EventServer EJB and invoke a remote method in this EJB. However, the web application always throws an exception "java.lang.NoClassDefFoundError: eventserver/EventServerRemoteHome"
Here is my java class that access the ejb:
public class Post_Event {
    public HashMap<String, String> getEventInfo(String event_name, String site) {
        System.out.println("Post_Event, the class path: " + System.getProperty("java.class.path"));
        System.out.println("Post_Event, user.dir: " + System.getProperty("user.dir"));
        System.out.println("Post_Event, java.library.path: " + System.getProperty("java.library.path"));
        HashMap<String, String> result = null;
        EventServerRemote remote = null;
        StringTokenizer st, st2;
        // here get the event information from host
        try {
            String lookupStr = "corbaname:iiop:" + site + ":3700#ejb/EventServerBean";
            InitialContext initialContext = new InitialContext();
            EventServerRemoteHome remoteHome = (EventServerRemoteHome) javax.rmi.PortableRemoteObject.narrow(initialContext.lookup(lookupStr), EventServerRemoteHome.class);
            if (remoteHome != null) {
                remote = remoteHome.create();
        } catch (javax.naming.NamingException ne) {
            ne.printStackTrace();
            return null;
        } catch (javax.ejb.CreateException ce) {
            ce.printStackTrace();
            return null;
        } catch (java.rmi.RemoteException re) {
            re.printStackTrace();
            return null;
        } catch (java.io.IOException ioe) {
            ioe.printStackTrace();
            return null;
        System.out.println("look up remote event server successfully.");
     result = remote.getEvent(event_name);
        return result;
    } I output the class path in this java file, and the class path DOES include the path C:\Sun\AppServer\lib where eventserver\EventServerRemoteHome.class is.
Does anyone know why it happens? Why a java class can't find a class that is in its class path?
appreciate any help!

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Wael Abbas ([email protected]):
Thank you for your great topic.
I think you need to copy the snippet code and past it to every application, applet, servlet or JSP every time you need to use your EJB.
Its better to include this snippet code in a simple JavaBean and use this bean as a bridge to your EJB, you may include a connect method in your JavaBean or but the connection code in the constructor and include a setters, getters and other methods to encapsulate your EJB methods.
You can use your JavaBean in any application, applet, servlet or JSP just create an object form it and call its methods.
Its just an idea
I hope it will be useful.
<HR></BLOCKQUOTE>
null

How to access EJB deployed in JBOSS 4 from Creator

Hello.
I am trying to access EJBs deployed on JBOSS in order to develop a web app client, when I import the EJB set from Creator (sessions and entities packages in a jar file) I got the following error message....."No EJB set found in file....." .
I presume there is an kind of xml file description specific for Sun App Server missing. I would like to know if there is other way to expose EJB in creator?....maybe write a config file by hand.
I already read the tutorials related to EJB but those only use pre build EJB jars for Sun App Sserver.
Also I read all the posted about JBoos and EJB in this forum but those are pretty general.
By the way I have Delegate classes to access the EJB. How do I register my delegates in Creator in order to expose their methods?
I�ll really appreciate some light in this matter.
Thanks in advance!!!

Hi,
The below forum thread may help you :
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51321
Thanks,
Runa.

Access Denied with EJB Deployment to 8i with JDeveloper

Hi,
I'm having a problem deploying an EJB to Oracle 8i with
JDeveloper 2.0.
I am receiving an insufficient privileges error in the
deployment process when it reaches the stage Generating EJBHome
and EJBObject on the server. I am logging in using the system,
sys, scott or internal account and all still receive the same
error. What role/privelege do I need to deploy an ejb to 8i?
Thanks in advance.
Here is a dump of the output JDeveloper produces.
*** Invoking the Oracle JDeveloper deployment utility ***
Scanning project files...done
Generating classpath dependencies...done
Generating archive entries table...done
Writing archive...done
*** Invoking the Oracle8i deployment utility ***
Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Generating Comm Stubs...done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...done
Generating EJBHome and EJBObject on the
server...oracle.aurora.server.tools.sess_iiop.ToolsException: A
SQL exception occured while compiling:
oracle.aurora.ejb.gen.test_MyEJB.EjbObject_MyEJB : ORA-01031:
insufficient privileges
at oracle.aurora.server.tools.sess_iiop.ToolImpl.error
(Compiled Code)
at oracle.aurora.ejb.deployment.GenerateEjb.generateBean
(Compiled Code)
at oracle.aurora.ejb.deployment.GenerateEjb.invoke
(Compiled Code)
at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke
(Compiled Code)
at
oracle.jdeveloper.wizard.deployment.EJBDeployMonitor.run
(Compiled Code)
at oracle.jdeveloper.wizard.common.ProgressDialog.run
(Compiled Code)
at java.lang.Thread.run(Compiled Code)
null

Chris,
Perhaps you should be checking if the user you wish to deploy
EJBs to has at least JAVAUSERPRIV.
As SYSTEM
grant JAVAUSERPRIV to <user>;
Good luck
/Mark
Chris Jones (guest) wrote:
: Hi,
: I'm having a problem deploying an EJB to Oracle 8i with
: JDeveloper 2.0.
: I am receiving an insufficient privileges error in the
: deployment process when it reaches the stage Generating EJBHome
: and EJBObject on the server. I am logging in using the system,
: sys, scott or internal account and all still receive the same
: error. What role/privelege do I need to deploy an ejb to 8i?
: Thanks in advance.
: Here is a dump of the output JDeveloper produces.
: *** Invoking the Oracle JDeveloper deployment utility ***
: Scanning project files...done
: Generating classpath dependencies...done
: Generating archive entries table...done
: Writing archive...done
: *** Invoking the Oracle8i deployment utility ***
: Reading Deployment Descriptor...done
: Verifying Deployment Descriptor...done
: Gathering users...done
: Generating Comm Stubs...done
: Compiling Stubs...done
: Generating Jar File...done
: Loading EJB Jar file and Comm Stubs Jar file...done
: Generating EJBHome and EJBObject on the
: server...oracle.aurora.server.tools.sess_iiop.ToolsException: A
: SQL exception occured while compiling:
: oracle.aurora.ejb.gen.test_MyEJB.EjbObject_MyEJB : ORA-01031:
: insufficient privileges
: at oracle.aurora.server.tools.sess_iiop.ToolImpl.error
: (Compiled Code)
: at oracle.aurora.ejb.deployment.GenerateEjb.generateBean
: (Compiled Code)
: at oracle.aurora.ejb.deployment.GenerateEjb.invoke
: (Compiled Code)
: at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke
: (Compiled Code)
: at
: oracle.jdeveloper.wizard.deployment.EJBDeployMonitor.run
: (Compiled Code)
: at oracle.jdeveloper.wizard.common.ProgressDialog.run
: (Compiled Code)
: at java.lang.Thread.run(Compiled Code)
null

Problem in accessing an ejb deployed in WLS

Similar Messages

Maybe you are looking for