Error saving connection factory

I was trying to create a JCA connection factory so that I can use the user module to convert IDOCs to flat file. But I was encountering this problem when saving
Saving JCA Connection Factory: CF_ID1_800 failed due to: Can not add connection factory
I use NWA_SUPERADMIN role.. But seems like even that can't save it correctly.
THanks

Hi Brian,
I am also facing the same issue in SAP PI NWA  for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file.            we are on SAP PI 7.11  sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r

Similar Messages

  • Error saving connection - jdev

    Hi ,
    I am strying to create a Webservice Data control from a wsdl generated from a SOA process deployed in the server and when I click on the finish button during the configuration in Jdev - It gives null pointer exception - Error saving connection.
    The Connections.xml is empty. Is this a bug in Jdev.
    Can some one guide a what needs to be done.
    Thanks,
    Robin

    Hi,
    What is your JDev Version?

  • Error saving JCA Connection factory in PI NWA

    Hi All,
    I am facing an  issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
    error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
    i posted this  in SAP PI forum also...
    Error saving connection factory
    Regards
    ashutosh r

    Hello Carme,
    From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
    This beautiful blog by William will surely help you rectify the problem.
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    Kindly check if you have done the following in your configuration:
    1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15" 
    2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
    3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
    I hope this should solve your problem.
    Regards, Gaurav.

  • Error in connection to SEM, changes will not be saved

    Hi All,
    When i am creating an opportunity i am getting an error
    "Error in connection to SEM, changes will not be saved", and it does not allow me to save the opportunity.
    Regards,
    Radhika

    Dear Mangesh,
    Thank you for your post. It's really helpful.
    Best Regards,
    Duc Lam.

  • Application Deployment in Managed Node Failed with the error - ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.ne

    2013-06-24 21:16:28,551 [bxapp2.healthnet.com] [  STANDARD] [                    ] (l.access.RuleCandidateIterator) INFO    - Single candidate rule resolution optimization is enabled
    Error retrieving JNDI initial context:
    2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [  STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
    at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
    at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
    at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
    at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
    at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 94 more
    2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [  STANDARD] [                    ] (tener.ListenerStateManagerImpl) ERROR   - Unexpected exception.
    java.lang.NullPointerException
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
    at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [  STANDARD] [                    ] (          internal.async.Agent) INFO    - Agents will be executed via the enterprise tier.
    2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [  STANDARD] [                    ] (          internal.async.Agent) INFO    - Passivation will be done on a per-page basis.
    2013-06-24 21:16:30,023 [bxapp2.healthnet.com] [  STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
    at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
    at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
    at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
    at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
    at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
    at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
    at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 84 more
    2013-06-24 21:16:30,038 [bxapp2.healthnet.com] [  STANDARD] [                    ] (      etier.impl.EngineStartup) ERROR   - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
    com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    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.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1045)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    ... 60 more
    Caused by: java.lang.reflect.InvocationTargetException
    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.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    ... 62 more
    Caused by: java.lang.NullPointerException
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
    at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
    at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
    at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
    ... 67 more
    2013-06-24 21:16:30,051 [bxapp2.healthnet.com] [  STANDARD] [                    ] (      etier.impl.EngineStartup) INFO    - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
    2013-06-24 21:16:30,164 [bxapp2.healthnet.com] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) ERROR   - Enterprise tier failed to initialize properly, PegaRULES not available
    2013-06-24 21:16:30,190 [bxapp2.healthnet.com] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) INFO    - Web Tier initialization is complete.
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 167.238.162.41:8008 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "pegamanaged2" for domain "sbxdomain8" running in Production Mode>
    <Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    Greetings,
    javax.naming.NameNotFoundException. Root exception is
    org.omg.CosNaming.NamingContextPackage.NotFound
    =================
    Below is the line of my LoginServlet class which is
    referred to in the stack trace - Object object =
    context.lookup
                        ( "java:comp/env/ejb/WarehouseClerk" );The root of the naming context is 'java:comp/env' and this is where lookup automatically begins for EJBs and resources. IOW, by specifying "java:comp/env/ejb/WarehouseClerk" as the EJB lookup name the server is actually treating this as "java:comp/env/java:comp/env/ejb/WarehouseClerk". Specify only the ejb context ("ejb/WarehouseClerk") in your lookup and you should be fine.
    Any help would be most appreciated.
    SeanRegards,
    Tony "Vee Schade" Cook

  • Error when creating a new JMS connection factory in GlassFish V3 b57

    When I use the admin console and try to create a new JMS connection factory in GlassFish V3 b57, the operation fails with the error message
    An error has occurred: Can't find ConfigModel.Property for attr -connection-validation-required on interface com.sun.enterprise.config.serverbeans.ConnectorConnectionPool
    Should I better report this in the GlassFish news forum (http://forums.java.net/jive/forum.jspa?forumID=56&start=0)?
    p.s. I launch the admin console from within NetBeans 6.7.1 (the server started before the IDE). WIth version b 56, creating a JMS connection factory worked fine.
    Best regards,
    Michael Justin

    This bug does not apear in the nightly build (b58) now so everything looks fine again.
    Greetings,
    Michael

  • Error : Connection factory has been stopped

    Hi ,
    i Have a JPA/Toplink application to be depolyed on OAS 10.1.3.3 , i defined a DataSource on the Application Server , but iam getting this error when iam trying to run my application :
    Caused by: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection
    factory has been stopped.
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:259)
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
    at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:130)
    Thanks
    Message was edited by:
    mr_jaber

    well as always...nothing works like restart of the server. Issue resolved.

  • OJMS Connection Factory Error

    Hi,
    (Platforms: OC4J developer preview 4, JDev 10.1.3 EA, Database :Oracle 10.1.0 )
    I have tried to implement the JMS provider (OJMS) according to the following document :
    http://www.oracle.com/technology/sample_code/tech/java/codesnippet/jms/datasources/ResourceProvider.html
    In my client code while I try to get the queue by :
    queue = (Queue)jndiContext.lookup("java:comp/resource/TestRP/Queues/RPQueue");
    there is no problem. But when I try to get connection factory by :
    queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/resource/TestRP/QueueConnectionFactories/RPTable");
    it fails and gives the following exception:
    05/11/28 11:40:19 javax.naming.NamingException: Lookup error: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910; nested exception is:
         java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910 [Root exception is java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910]
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:68)
    05/11/28 11:40:19      at javax.naming.InitialContext.lookup(InitialContext.java:351)
    05/11/28 11:40:19      at BServlet.insertToQueue(BServlet.java:224)
    05/11/28 11:40:19      at BServlet.doPost(BServlet.java:199)
    05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:846)
    05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:397)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
    05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:245)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:231)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.access$1000(ServerSocketAcceptHandler.java:33)
    05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:820)
    05/11/28 11:40:19      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    05/11/28 11:40:19      at java.lang.Thread.run(Thread.java:595)
    05/11/28 11:40:19 Caused by: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910
    05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:100)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:83)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:341)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:158)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:235)
    05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:55)
    05/11/28 11:40:19      ... 18 more
    Any idea?
    Thanks,

    Hi Brian,
    I am also facing the same issue in SAP PI NWA  for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file.            we are on SAP PI 7.11  sp06....
    error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
    could you share info, how your issue got solved..
    Regards
    ashutosh r

  • Error creating JCA connection factory in NWA

    Hi,
    I need to load an file with idoc content into a XML.
    So parameter IDOCXmlToFlatConvertor is required  and it's necessary to create a JCA Connection Factory in NWA.
    I'm trying to do it using :
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm
    But, when i try to create a JCA Connection Factory in NWA, systems returns next error:
    com.sap.engine.services.connector.exceptions.BaseDeploymentException: Can not set authentication user store "null" in security context "MRD_300" for connector "MRD_300" in application "sap.com/tc~sapjra".
    at com.sap.engine.services.connector.deploy.util.security.SecurityUtils.deploySecurity(SecurityUtils.java:507)
    However, creating JCA connection as indicated in this blog, security tab doesn't allow any change  and field user store can't be modified.
    How to do it?
    Carme

    Hello Carme,
    From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
    This beautiful blog by William will surely help you rectify the problem.
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    Kindly check if you have done the following in your configuration:
    1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15" 
    2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
    3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
    I hope this should solve your problem.
    Regards, Gaurav.

  • Error in looking up the JMS Connection Factory

              Hi,
              I am using weblogic6.1. I created a JMS Connection factory from administrator
              console with the name QueueConnectionFactory..But when i restart the server and
              try to look up that factory its giving an NameNotFoundException...This is the
              entry of the factory in config.xml
              <JMSConnectionFactory JNDIName="QueueConnectionFactory"
              Name="QueueConnectionFactory" Targets="myserver"/>
              But if i change reapply the target server to myserver from admin console whenever
              restart the server it works fine..
              I dont know where is the problem..Can u please update me on the problem if u people
              have any idea.
              The trace of the exceptions i got is as below:
              java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
              resolve QueueConnectionFactory. Resolved
              : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
              java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
              QueueConnectionFactory. Resolved: '' Unr
              esolved:'QueueConnectionFactory' ; remaining name ''
              Thanx
              Regards,
              Narayan
              

              Hi Zach,
              No, I dont think ur interpretation is right..Once the entry corresponding
              to JMS Connection Factory is there in config.xml, the server should automatically
              bind it at the time of booting.. right. Why should this administrator server come
              into the picture.
              Thanx
              "Zach" <[email protected]> wrote:
              >Don't know. Sounds like the admin server is not notifying JMS of the
              >changes under certain situations. You might post in the management.console
              >newsgroup.
              >
              >_sjz.
              >
              >"Narayan" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Hi,
              >> I am using weblogic6.1. I created a JMS Connection factory from
              >administrator
              >> console with the name QueueConnectionFactory..But when i restart the
              >server and
              >> try to look up that factory its giving an NameNotFoundException...This
              >is
              >the
              >> entry of the factory in config.xml
              >>
              >> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
              >> Name="QueueConnectionFactory" Targets="myserver"/>
              >> But if i change reapply the target server to myserver from admin console
              >whenever
              >> restart the server it works fine..
              >> I dont know where is the problem..Can u please update me on the problem
              >if
              >u people
              >> have any idea.
              >> The trace of the exceptions i got is as below:
              >> ****************
              >> java.rmi.RemoteException: javax.naming.NameNotFoundException:
              >Unable to
              >> resolve QueueConnectionFactory. Resolved
              >> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
              >> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
              >to
              >resolve
              >> QueueConnectionFactory. Resolved: '' Unr
              >> esolved:'QueueConnectionFactory' ; remaining name ''
              >>
              >> **********************
              >>
              >> Thanx
              >> Regards,
              >> Narayan
              >>
              >>
              >
              >
              

  • Error in looking up JMS connection factory in cluster

              Hi,
              We have setup a JMS connection factory targeted to clustered servers. We currently
              have two physical servers defined in the cluster.
              When the clustered servers first comes up, we can't see the JMS connection factory
              in the JNDI tree of any of the clustered servers. We can see in the server log
              that factory is actually being started. Binding to the JNDI tree is not happening.
              Through Management console when we move the target of connection factory back
              and forth, then the problem is gone.
              Any pointers to the problem are welcome.
              P.S. We are using WL 7.0.1
              Thanks
              Nishchit
              

              Hi,
              We have setup a JMS connection factory targeted to clustered servers. We currently
              have two physical servers defined in the cluster.
              When the clustered servers first comes up, we can't see the JMS connection factory
              in the JNDI tree of any of the clustered servers. We can see in the server log
              that factory is actually being started. Binding to the JNDI tree is not happening.
              Through Management console when we move the target of connection factory back
              and forth, then the problem is gone.
              Any pointers to the problem are welcome.
              P.S. We are using WL 7.0.1
              Thanks
              Nishchit
              

  • Error saving job  to database for standard jobs scheduling

    Hi,
        In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
    Error saving job  to database
    Message no. BT117
    Diagnosis
    The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
    System Response
    Job not saved and not scheduled.
    Procedure
    To analyze this problem, start by checking the system log for messages about network or database problems.  You can also use the computing center management system to check your system for problems.
    Guide me for the same.
    Thanku

    HI,
    Sometimes this error will come.
    Try to schedule jobs manually using SM36 instead of using standard job button.
    Also you can check this thread
    Re: Error saving job SAP_REORG_JOBS to database
    Which seems to report same problem.
    Its nothing to take with database conenctivity as SAP is up and running .
    Try this and revert.
    Regards,

  • JMS proxy and XA connection factory

    Hi all,
    I would like to ask you what is the best practice to adopt about the scenario described below.
    A JMS proxy retrieves a message and processes it.
    Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
    (later another app will check failed messages for fixing & republishing them into ALSB).
    In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
    Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
    Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
    Or XA connection factory is not needed and could I use
    Routing Options with exactly once or both are needed ?
    Thanks
    ferp

    Hi all,
    I did some tests and follow what I've achieved.
    Scenario 1.
    - Precondition
    -- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
    -- A business service BS with XA factory that publishes into MyOutboundQueue
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2.
    - Precondition
    -- As 1. but no error is forced in the pipeline
    -- the MyOutboundQueue destination queue is paused
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2A.
    - Precondition
    -- As 2. with MyOutboundQueue paused and resumed
    - Flow:
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- before all the retries failed the queue is resumed
    --- BS succeeds to publish the message
    Scenario 3.
    - Precondition
    -- A JMS proxy with NO XA factory + Error Destination
    -- A business service BS with NO XA factory
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is NOT rolled back, message NOT redelivered to proxy
    -- so
    --- no message delivered to MyOutboundQueue2 destination
    --- no message delivered to MyRecoveryQueue2 destination
    --- message consumed from MyQueue2 and now is lost!
    To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
    But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
    So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
    So both my proxy service and business service use an XA factory.
    Regards
    ferp

  • Repository error while connecting OracleB2B to WLS

    I am trying to connect OracleB2B 11g to weblogic server 8.1 using Generic JMS-1.0 protocol. I have given the below details while configuring channels
    destination name: CI_to_WLI
    Connection Factory: weblogic.jws.jms.QueueConnectionFactory
    Destination Provider: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://172.24.230.16:7001
    tried using credentilas of weblogic server too
    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://172.24.230.16:7001;java.naming.security.principal=admin;java.naming.security.credentials=admin
    But as soon as i post a request i am able to see the below errors:
    Informational -: B2B-50025: Repository error: java.lang.NullPointerException
    at oracle.tip.b2b.msgproc.ToplinkHelper.findBusinessMessagesByWireMessag
    eId(ToplinkHelper.java:1289)
    at oracle.tip.b2b.msgproc.DbAccess.updateProcessingTime(DbAccess.java:57
    48)
    at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1427)
    at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecu
    tor.java:540)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:
    200)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:77)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused By: java.lang.NullPointerException
    at oracle.tip.b2b.data.RTPContext.executeQuery(RTPContext.java:144)
    at oracle.tip.b2b.msgproc.ToplinkHelper.findBusinessMessagesByWireMessag
    eId(ToplinkHelper.java:1282)
    at oracle.tip.b2b.msgproc.DbAccess.updateProcessingTime(DbAccess.java:57
    48)
    at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1427)
    at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216
    at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
    at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecu
    tor.java:540)
    at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:
    200)
    at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
    (WorkManagerExecutor.java:77)
    at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
    er.java:183)
    at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Regards,
    Deepthi
    Edited by: user12396907 on Dec 29, 2009 8:50 PM

    Hi Deepthi,
    I still have doubt on port as by default, BAM server listens on port 9001. Please cross-check your servers configuration again.
    Please let me know what details must be given in destination provider other than URLDestination provider box should hold host name/ip address of server, port number, naming factory, user name and password in below format -
    java.naming.provider.url=t3://<host>:<port>;java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.security.principal=<username>;java.naming.security.credentials=<password>
    Regards,
    Anuj

  • Can't Create Saved Connection in 11g (Discoverer Plus).

    We're getting ready to go live with a new installation of Discoverer Weblogic 11g, but we have run into a problem. We are getting errors when we have any user try to create a saved login connection from their login screen. We hit "Create Connection" and enter all the required login info (as we always did with our 10g version), but when we hit 'Apply' or 'Apply and Connect' we get the following errors.......
    A connection error.
    - Oracle BI Discoverer Viewer cannot save the connection. Check for other errors.
    - ORA-04063: package body "PROD_DISCOVERER_PS.WWSSO_API_PRIVATE" has errors ORA-06508: PL/SQL: could not find program unit being called: "PROD_DISCOVERER_PS.WWSSO_API_PRIVATE" ORA-06512: at line 1
    Users can login just fine when they enter all their info on the login screen, this is only happening when we try to create the saved connection. Is anyone else running into this on 11g? Is there a setting we are missing or something? Maybe something in the pref.txt file? Any help would be appreciated, especially since we are being asked to go live soon. Thanks!
    Here is our system setup:
    Oracle BI Discoverer 11g (11.1.1.4.0)
    Oracle Business Intelligence Discoverer Plus 11g (11.1.1.4.0)
    Discoverer Model - 11.1.1.4.0
    Discoverer Server - 11.1.1.4.0
    End User Layer - 5.1.1.0.0.0
    End User Layer Library - 11.1.1.4.0
    Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
    Java Virtual Machine:     Sun Microsystems Inc. 1.6.0_29
    JVM Memory Available:     9046KB out of 37372KB
    Operating System:     x86 Windows XP 5.1
    Using protocol: RMI protocol over JRMP transport

    Additional info:
    Based on the error messages, we can see something is wrong with the package being called. We had a long running help ticket with Oracle opened, but in our opinion, it was not really resolved. We provided the following info after a request from Oracle....
    The package does exist. The package is valid but the package body is invalid due to missing dependant objects
    It is owned by PROD_DISCOVERER_PS.
    The database version is 11.2.0.1.0 (64 bit)
    SQL> select OWNER, OBJECT_TYPE
    +2 from all_objects+
    +3 where object_name = 'WWSSO_API_PRIVATE';+
    OWNER OBJECT_TYPE
    PROD_DISCOVERER_PS PACKAGE
    PROD_DISCOVERER_PS PACKAGE BODY
    We have tried to recomplie the package, still invalid.
    After some further questions we were asked to provide info on the app_registry.......We got an error when trying that.......
    The app_registry object does not exist ...
    SQL> connect sys as sysdba
    Enter password:
    Connected.
    SQL> select comp_id,version,status from app_registry;
    ERROR at line 1:
    ORA-00942: table or view does not exist
    In the end (after a lot of back and forth), Oracle could not reproduce our problem on their test system. Because their test system uses Enterprise Edition and we installed Standard Edition, their solution was that the issue is caused because we are using Standard Oracle DB and we should be using Enterprise Edition. Creating a saved connection doesn't sound at all like something that would be affected by Standard or Enterprise edition. That's not an easy "solution" for us right now, and we can use a real fix. That's like taking your car into the shop because your blinkers don't work on your 2010 model car and the dealer's solution is "Oh, your 2010 car blinkers don't work? We have a 2011 model and they work just fine. You'll need to buy a 2011 car so the turn signals function."

Maybe you are looking for