1 Reply Latest reply: Sep 6, 2010 3:25 PM by 719173 RSS

    Error at login to Workspace in 11g

    691475
      Greetings

      When trying to login to BPM Workspace to run the Salesquote example y get an empty reply (no html in the response) and an error in the server's console.

      Made a new installation of OBPM 11g (with SOA in the Admin server and a managed instance with OSB using the developer mode for BPM and SOA), installation, creation of schemas and domains went well.
      Both domains rise ok, but in the AdminServer i see the following errors/warnings:

      <Aug 25, 2010 3:11:46 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
      <Aug 25, 2010 3:11:46 PM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
      INFO: SSLSocketFactoryManagerImpl.getKeystoreLocation SOA Keystore location: /oracle/Oracle/Middleware/user_projects/domains/obpm6D/config/fmwconfig/default-keystore.jks
      INFO: SSLSocketFactoryManagerImpl.getKeystorePassword Obtained null or empty keystore password
      INFO: SSLSocketFactoryManagerImpl.getKeyPassword Obtained null or empty key password
      INFO: SSLSocketFactoryManagerImpl.getSSLSocketFactory Could not obtain keystore location or password
      Building cube maps ...
      BPMNFlowElementRegistry.registerVisitor:SEQUENCE_FLOW
      BPMNFlowElementRegistry.registerVisitor:MEASUREMENT

      And latter on:
      <Aug 25, 2010 3:12:56 PM CDT> <Error> <oracle.webservices.runtime> <OWS-00532> <Failed to retrieve policy
      oracle.wsm.policyaccess.PolicyAccessException: WSM-06132 : Error creating a connection to Oracle WSM Policy Manager.
      at oracle.wsm.policyaccess.impl.PMPolicyResolverBase.init(PMPolicyResolverBase.java:113)
      ...
      Caused By: java.security.PrivilegedActionException: oracle.wsm.policymanager.PolicyManagerException: WSM-02120 : Unable to connect to the policy access service.
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)


      Following the labs for Salesquote implementation the creation of users worked fine, the one with ant, and the deployment showed no errors in JDeveloper including the mapping of the process roles to the server's users.

      When trying to login to the workspace i get the following exception on theAdminServer Console:
      <Aug 25, 2010 3:30:11 PM CDT> <Error> <HTTP> <BEA-101020> <[ServletContext@14157918[app:OracleBPMWorkspace module:/bpm/workspace path:/bpm/workspace spec-version:2.5]] Servlet failed with Exception
      fuego.papi.OperationRuntimeException: Runtime operation error.
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:48)
      at oracle.bpm.papi.ora.ProcessServiceSessionAdapter.participantCurrent(ProcessServiceSessionAdapter.java:1235)
      at oracle.bpm.workspace.model.common.PapiBean.getLayouts(PapiBean.java:3338)
      at oracle.bpm.workspace.model.container.ContainerBean.buildStoredPaginatedLayout(ContainerBean.java:612)
      at oracle.bpm.workspace.model.container.ContainerBean.initPreferences(ContainerBean.java:73)
      Truncated. see log file for complete stacktrace

      Caused By: fuego.papi.OperationException: Operation exception.
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:68)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:44)
      at oracle.bpm.papi.ora.ProcessServiceSessionAdapter.participantCurrent(ProcessServiceSessionAdapter.java:1235)
      at oracle.bpm.workspace.model.common.PapiBean.getLayouts(PapiBean.java:3338)
      at oracle.bpm.workspace.model.container.ContainerBean.buildStoredPaginatedLayout(ContainerBean.java:612)
      Truncated. see log file for complete stacktrace

      Caused By: ORABPEL-10585

      Service error.
      Internal Error; Service error occurs in IdentityService in method lookupUser.
      Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services

      at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.lookupUser(AbstractIdentityServiceClient.java:195)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:58)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:44)
      at oracle.bpm.papi.ora.ProcessServiceSessionAdapter.participantCurrent(ProcessServiceSessionAdapter.java:1235)
      at oracle.bpm.workspace.model.common.PapiBean.getLayouts(PapiBean.java:3338)
      Truncated. see log file for complete stacktrace

      Caused By: java.lang.RuntimeException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused
      at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.invoke(IdentityServiceSOAPClient.java:285)
      at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.lookupUser(IdentityServiceSOAPClient.java:323)
      at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.lookupUser(AbstractIdentityServiceClient.java:182)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:58)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:44)
      Truncated. see log file for complete stacktrace

      ...

      <Aug 25, 2010 3:30:11 PM CDT> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'AdminServer' has triggered at Aug 25, 2010 3:30:11 PM CDT. Notification details:
      WatchRuleType: Log
      WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
      WatchData: DATE = Aug 25, 2010 3:30:11 PM CDT SERVER = AdminServer MESSAGE = [ServletContext@14157918[app:OracleBPMWorkspace module:/bpm/workspace path:/bpm/workspace spec-version:2.5]] Servlet failed with Exception
      fuego.papi.OperationRuntimeException: Runtime operation error.
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:48)
      at oracle.bpm.papi.ora.ProcessServiceSessionAdapter.participantCurrent(ProcessServiceSessionAdapter.java:1235)
      at oracle.bpm.workspace.model.common.PapiBean.getLayouts(PapiBean.java:3338)

      ...

      Caused By: ORABPEL-10585

      Service error.
      Internal Error; Service error occurs in IdentityService in method lookupUser.
      Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services

      at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.lookupUser(AbstractIdentityServiceClient.java:195)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:58)
      at oracle.bpm.papi.ora.mgr.OrganizationManager.lookupParticipant(OrganizationManager.java:44)

      ...

      Caused By: java.lang.RuntimeException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused
      at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.invoke(IdentityServiceSOAPClient.java:285)
      at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.lookupUser(IdentityServiceSOAPClient.java:323)
      at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.lookupUser(AbstractIdentityServiceClient.java:182)


      I think something needs fixing with my installation but need help in finding it and knowing how to fix it, or if I need to make the installation in a different fashion.
        • 1. Re: Error at login to Workspace in 11g
          719173
          Google to the rescue
          The problem was related to the IP configuration in the hosts file for the machine's alias.
          It was set to 127.0.1.1 instead of 127.0.0.1 (the usual for localhost) and that made the problem arise.

          Changing /etc/hosts to point the intended server name to 127.0.0.1 successfully solved the problem.

          Thanks to Rudi Acikgoz for blogging on this very issue.
          http://blogs.eteration.com/blog/?p=365