PSWATCHSRV does not auto-restart causing app server domain instability

Current environment:
- Solaris 10
- Oracle 10.2.0.4
- PS HRCS 9.0
- PTools 8.49.19
- Weblogic 9.2
- Tuxedo 9.1
We have two PIA web sites that reside on the same PIA web domain. They each interact with a different app server domain residing on csapp81. One is assigned a jolt listening port of 9060 (CS90SBX) and the other uses 9030 (CS90UNT). Recently, after patching the PTools to 8.49.19, we discovered that occasionally the PSWATCHSRV in one of the app server domains will shut down and not restart. The domain continues to run without the WATCHSRV but then erratic behavior in the PIA is observed:
- Users attempting to access worklists are logged off
- Reports stop posting from PSNT and PSUNX
- Users attempting to navigate to reports already posted are logged off with "An Error Has Occurred" message
- Some users are unable to log in and see a message in red on the signon page: bea.jolt.ServiceException
Re-booting the app server domain will solve the problem temporarily until the PSWATCHSRV shuts down again. We have noticed that in the app server that is not affected, the PSWATCHSRV restarts one second after shutting down whereas in the affected domain it never auto-restarts. We have tried re-building the web server and app server domains but this does not affect the problem. There appears to be no difference between the two domains. In fact a couple of weeks earlier SBX was working fine and UNT was affected. Now it's the exact opposite and we have another environment (CFG) showing the same behavior.
The proof the problem exists:
Verified the issue by the application server log file <APPSRV_0602_SBX.LOG>, which displays that PSWATCHSRV has been shutdown and never restarted:
PSAPPSRV.11610 (3) [06/02/09 12:48:40 GetCertificate](3) Returning context. ID=PS, Lang=ENG, UStreamId=124840_11610.3, Token=PSFT_HR/2009-06-02-05.48.40.000003/PS/ENG AAAAmwECAwQAAQAAAAACvAAAAAAAAAAsAARTaGRyAgBOZQgAOAAuADEAMBTG0ddiK9wa09fTauVpwsrNvqJDmwAAAFsABVNkYXRhT3icPcZNDkAwFEXh02oM7YS8VAkL8DMSwdzILi3O6xu4J/lygcf5IuDQ+Tcb2DlLJjaWKn9mLm5WjkREtJFa7c1odjQkBlNU+Wv5APmFCio=
PSWATCHSRV.11609 (0) [06/02/09 12:52:38] Shutting down
PSAPPSRV.11612 (29) [06/02/09 12:55:45 [email protected] (NETSCAPE 7.0; WINXP) ICPanel](3) (PublishSubscribe): PublicationManager::Publish(): publication a18e2838-4f31-11de-9268-83dc49eeb5cf.USER_PROFILE published in 0.0900 seconds
My question is: Has anyone else ever seen this behavior in an 8.49.19 environment? If so, how was it resolved?
We are now conducting UAT and the occasional disruption of having to restart the app server just so people can login to the system is not making a good impression on the customer.
We have an open SR ticket with Support but as yet they have not been able to help us...

Looks like Tuxedo is not doing he's job. You should double check the Tuxedo version and rolling patch installed.
And also the configuration of AppServer, section "PSWATCHSRV", if the interval is set to 0, then it is disabled.
Moreover, from your output it is difficult to understand what's going wrong.
Nicolas.

Similar Messages

  • When in landscape mode page does not scroll up causing the keyboard to cover typing are.

    When in landscape mode page does not scroll up causing the keyboard to cover typing area.

    No, but try terminating and restarting Safari:
    1. Press the Home button
    2. Double click the Home button to bring up the "Recent Apps" tray.
    3. Touch and hold on the Safari icon in the "Recent Apps" tray until a "-" appears.
    4. Touch the "-" to terminate Safari.
    5. Restart Safari and see if your Bookmarks are back.

  • Reporting Services Webpart - web part does not auto render consistantly

    We are on SharePoint 2010 (integrated with Reporting Services)- on several sites we have added the Reporting Services Web Part and with a saved parameter.  The behavior of this web part is not consistent.  There are times when I open up a site
    and the web part will auto render the report.  5 minutes later I can go into the same site, and the web part does not auto render the report.  I have to do edit page, or close and re-open the web site.  Has anyone experienced this type of behavior. 
    I've looked for assistance with this issue on-line cannot find anything that specifically addresses this issue.   

    Hi Karen,
    If the parameters have default values in the report, then the report can be rendered automatically.
    For this issue, I recommend to verify the things below:
    Does this issue occur when you open the page with the web part in a new tab in the browser or go back to the previous opened tab?
    Does this issue occur in the server side or client side?
    Please add the site to trusted sites in Internet Explorer to see how it works.
    Please change another browser to see how it works.
    For narrowing down the issue scope, please test with another report and compare the results.
    Thanks,
    Victoria
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • Requested query does not exist on the current server.

    Hi All,
    I am facing a problem in BI 7.0 related to query view.I am able to create a view on a query and can successfully save it .But when I am trying to open it using Bex Analyzer, it throws an error that query does not exist on the current server.
    Please find the steps below which I did to create a query view in BI 7.0.
    1.Executed query and then clicked on save from the tool bar.It asks me to save as workbook or save as view.I clicked on save as view and gave some name to view.It saved successfully.
    2.Now when in Bex I am trying to open the view , it gives the message 'The requested query does not exist on the current server'.
    Please help me in solving the issue.
    Regards,
    Phani.

    Hi,
    I am facing the same problem, though some others of my views can be opened.
    We had an upgrade of the system to Support Package stack 13. Maybe this caused problems.
    My BEx Analyzer Version is:
    Support Package 14, Patch 3, Revision 811
    Philipp

  • Netscape cert type does not permit use for SSL server on Weblogic

    We have WLS 11g (11.1.1.5 SOA) on UNIX and we are trying to connect secured service (Using client certificate along with UserName and Password for Authentication ). I was able to test it using SOAP UI.
    But when I am testing the webservice I am facing listed error
    java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): https://abcd:1111/JWSs/V1/TermsWS at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at
    and domain log shows that
    Caused By: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: Netscape cert type does not permit use for SSL server
    Please help me to resolve listed issue.
    Can I use Netscape client certificate on WLS?
    Do I need to take any extra care while working with client cert?
    I appreciate your help.

    Netscape cert type does not permit use for SSL clientTry using another certificate. Your certificate can't be used as a web browser client certificate.

  • Mac Pro does not auto-sleep (manual sleeping if fine!)

    I have a small annoyance with my 2009 (Nehalem) Mac Pro I am wondering if someone can help with, or suggest something, please:
    The Mac Pro does not auto-sleep; ever. I have played around with the sleep time settings, and enabled or disabled the 'sleep drives' option, but to no avail. Mac Pro will stay on, no matter if I am logged on OR even on the 'log on users' screen.
    That said, I can sleep the Mac Pro manually at any time, and without any problems; it stays asleep without a hitch, and wake-up is flawless.
    There is nothing in the console log that would tell me why the auto sleep doesn't function. I deleted the sleep plist and re-set, but again, no change.
    Any ideas? Not sure what could signal the system to not do auto-sleep?
    It's running 10.6.3.
    Cheers,
    Dan

    Exactly the same problems as those described above: forced sleep works (by using the power button or closing the lid) but automatic sleep doesn't (using 'Energy Saving' preferences).
    Tried every single piece of advice here and on other posts: reset PRAM/ SMC, verified disc, repaired permissions, deleted the power saving preference files, cleared caches & history, restarted in every conceivable mode... The only things that worked were safe boot and creating a new user account which means it must be a software issue.
    Disabled/ removed/ paused/ reinstalled every piece of software I could but to no avail. The most frustrating thing? Having to wait for 5 mins every time I tried something to check whether the damned thing was going to go to sleep.
    In the end, and in desperation, I took the advice of Dino X and downloaded PleaseSleep. Success! A genius piece of software. It forces sleep when the Energy Saver preferences cut in but, even if I don't set exceptions, it won't force sleep if there's a DVD playing (for example).
    Only had the Mac for a few months and I'll never go back to that other, unmentionable operating system; the Mac's just too good but I'm vexed that I'm having to use third party software to get it to work as it should (and was) - feels like a bit of a Win*s solution to me.

  • HT5772 How do I delete voice memos from my phone?  It does not show on the app or in iTunes.  Thanks!

    How do I delete voice memos from my phone?  It does not show in the app or in iTunes.  Thanks

    Welcome to the Apple Community.
    Settings > Music > Show all music > Off

  • SAP PI Message Cancellation Alert - Message does not have restartable error status

    Hello SCNers
    Version: 7.1
    Scenario: File --> PI -->SOAP
    We have a situation where a PI message  in Integration Engine shows error status.We want to cancel the message in IE but are unable to do so.
    On clicking Cancel for this message in SXMB_MONI, we are receiving an alert "Message does not have restartable error status".
    In SXMSPMAST table, value for ITFACTION is DEL.
    We do not want to run report RSXMB_DEL_TO_ARCH, that would change status of all messages with DEL status to ARCH.
    Is there a way to Cancel or Change the Status of this single message?
    Regards
    Sudheer

    Hi Hareesh,
    Tried that too, but to no avail.
    Strangely, the log shows NO_ERROR_STATE for the cancelation of this message thru RSXMB_CANCEL_MESSAGES.
    But in SXMSPMAST table the status of this message is 14 (System Error - Manual Restart Possible).
    Regards
    Sudheer

  • Problem in WAD (The requested query / does not exist on the current server)

    Dear Guru's
    When i execute a Web Application in WAD in the selection screen suppose if i give Key product  as 86000 then check and execute i get correct data. Then if i come to  backpage (Selection screen again using backspace) and change Key product  as 86022  then check and execute then i get following error
    The requested query / does not exist on the current server
    System error in program CL_RSR_OLAP_VAR and form BAD STATE (see long text)
    Can any one please provide me some good solution...
    We are using BI 7.0 sp 16, But i am executing this Wed Application in 3.1WAD.
    Thanks and Regards,
    kalyan

    Dear Jai,
    Issue is in WAD selection screen for first product valuse every thing if fine, when i go back and change product value and then CHECK and EXECUTE the following error comes.
    The requested query / does not exist on the current server
    System error in program CL_RSR_OLAP_VAR and form BAD STATE (see long text)
    Any one have any idea plssssssssssssssssssssssssssssssssssss..........
    dude's some soln.....
    Thanks and Regards,
    Dev
    Edited by: Srinivas dev on Jul 4, 2008 2:45 PM

  • E2E RCA - The requested query / does not exist on the current server

    Hi All,
    The RCA for managed system is configured successfully and we are getting EWA for JAVA also.
    But when i try to look at the statistics through Workload Analysis it gives error "The requested query / does not exist on the current server" and "unknown or deleted query".
    I again tried to run CCMSBI_SETUP_E2E report but the problem STILL persists.
    Please let me know what are the other methods i shall try.
    Thanks,
    Rohan

    Hi,
    Our solution manager is in EHP1 SP23 and BI content is on 704 SP05.
    Firstly the BI was configured in 001 client, we changed it to production client and activated the source system as mentioned in SOLMAN_SETP -> Basic configuration.
    Later i found out the there are no queries.  I already told to update the BI content and SAP BW patch to SP06.
    Do you think it will work?
    Thanks and regards,
    Rohan

  • The requested query does not exist on the current server

    Hy, i created an workbook an QAs with a query that i have trasported from DEV.
    The query exist on QAs system but when open the workbook i receive this error message:<i>'The requested query does not exist on the current server'</i>.
    When i select ok, the workbokk is opened correctly because the query exist in system QAs.
    How can i remove the initial error message .
    Thank's
    Andrea
    System: BI 7.0
    tool BEx version  7.0

    Hi
    When you create a workbook in DEV, you will be assigning a query for that workbook
    When you transport workbook from DEV to QA,the assigned workbook comes along with it
    When you transport only query from DEV to QA, there are certain technical elements called query elements which may not have transported properly
    To avoid this inconsistency between DEV and QA,it is advisable you transport the workbook again....Create new workbook in DEV, assign a query, transport the workbook to QA
    Regards
    N Ganesh

  • Error - The requested query does not exist on the current server

    Hi all,
    We've started to get an error when exeucting queries on our BW system.  The erorr is "The requested query does not exist on the current server".  Even though I can go in an change the query on the server, I get this message when I try to execute it.  I also get the same message when I try to run the query in RSRT.
    Has anyone else run into this problem?
    Thanks!
    ~Matt

    The problem that we had was due to a pre-query not transported up.  We transported up the missing pre-query and everything worked fine.  If you go into change mode on the query and press the check button.  It should tell you which query is missing.

  • Mdm:iOS terminal does not communicate to a MDM server

    How do you do?
    It is Matsuzaki SHinji.
    I want you to teach about Apple MDM.
    I am MDM Vendor.
    The MDM server is using Apache 2.2.3.
    WavDAV is used.
    The PUT method is supported.
    The contract of an enterprise is completed.
    The application of MDM is also completed.
    I am using the following URL by webdav.
    It has also checked that it was in the state which can be used.
    https://www.anetm.com/dav/
    It is a thing of APNs.
    nj_dev_apns-dev.pem
    The "user ID" of subject contained in a nj_dev_apns-dev-key-noenc.pem certificate is "jp.co.nishitele."
    APNs is used using the following ruby script.
    In the following codes, a device token is ending exchangeably.
    "[ -device torkn string 32 length set- ]"
    Start Script
    #!/usr/bin/ruby -Ku
    require 'openssl'
    require 'socket' 
        (msg = []) << "[ -device torkn string 32 length set- ]"
        device  = msg.pack("H*")
        socket = TCPSocket.new('gateway.sandbox.push.apple.com',2195)
        context = OpenSSL::SSL::SSLContext.new('SSLv3')
        context.cert = OpenSSL::X509::Certificate.new(File.read('nj_dev_apns-dev.pem'))
        context.key  = OpenSSL::PKey::RSA.new(File.read('nj_dev_apns-dev-key-noenc.pem'))
        ssl = OpenSSL::SSL::SSLSocket.new(socket, context)
        ssl.connect
        payload = <<-EOS
      "mdm":{"<PushMagic>"
    EOS
        (message = []) << ['0'].pack('H') << [32].pack('n') << device << [payload.size].pack('n') << payload
        ssl.write(message.join(''))
        ssl.close
        socket.close
    End Script
    It performs.
    The next warning has occurred at the iPhone terminal.
    Apr 30 11:04:35 Evangerion-iPhone4S apsd[60] <Warning>: <APSCourier: 0x131e80>: Failed to parse JSON message payload for topic 'jp.co.nishitele': The operation couldn’t be completed. (Cocoa error 3840.)
    An iOS terminal does not communicate to a MDM server.
    I would like to solve this.
    And thank you.
    Thank you for your consideration.
    He is waiting for the reply.

    Is this iPad used? 
    iTunes should be version 11
    It should be reset to wipe all content from the device and set up as a new device with iTunes.    It should update to IOS 7.0.4

  • TS1702 My app store does not load the featured apps, also in charts. Everytime i open the app store, the screen remains blank. Im using ipad3, ios6.

    My app store does not load the featured apps. The screen remains empty everytime I open it.

    Saw this on another post.
    Applecare Senior Advisor Txx Bxxx (I have his contact info in an email he just sent) just confirmed with me that the problem people are having with the App Store not loading is an apple issue with there servers, ITS NOT YOUR IPAD so don't go restoring it!   It's not happening to everyone however but they are looking into it, its really hit or miss.
    In the meantime ...........
    The Complete Guide to Using the iTunes Store
    http://www.ilounge.com/index.php/articles/comments/the-complete-guide-to-using-t he-itunes-store/
    Can't connect to the iTunes Store
    http://support.apple.com/kb/TS1368
    iTunes: Advanced iTunes Store troubleshooting
    http://support.apple.com/kb/TS3297
    Best Fixes for ‘Cannot Connect to iTunes Store’ Errors
    http://ipadinsight.com/ipad-tips-tricks/best-fixes-for-cannot-connect-to-itunes- store-errors/
    Try this first - Reset the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.
    This works for some users. Not sure why.
    Go to Settings>General>Date and Time> Set Automatically>Off. Set the date ahead by about a year.Then see if you can connect to the store.
     Cheers, Tom

Maybe you are looking for

  • IPhone & iPad won´t show up in iTunes?

    Hi! I have a problem with my iTunes; non of my iDevices shows up -.- anyone having any idea what I should do, please?

  • Why is my Photoshop CS4 crashing? (Vista OS)

    I've been trying to work on my art in photoshop after getting a tablet for my birthday, but for some reason, Photoshop keeps crashing after about an hour or so of being in it. I suspect it's the driver, but I'm not entirely sure. I'm downloading the

  • Creating BusinessPartner with both mail to and bill to address

    Hi, I am having problem creating a business partner with both mail to and bill to address. I want to create two instances (lines) in BPAddresses; one with mial to address and another with bioll to address. But I still get the error code -5002 with th

  • Cisco 5508 Memory Usage

    What is the average memory usage for a Cisco 5508 with 500 APs (mostly 3502s) running 7.0.116.0 code? I am currently at 450 access points and have 80% memory usage should I be concerned?

  • The airport on my Time Capsule will now only allow one device to connect at a time.

    When I first installed my new time capsule, everything worked beautifully. I had multiple devices connected to the AirPort and life was good. A few weeks ago, I swapped my cable modem and everything went bad from there. Now I can only connect one dev