Possible errors with promotion

This topic describes errors that might occur when a promotion operation between two WSRR instances is attempted, and their possible causes.

NamingException error

Example message
A problem occurred while attempting to transition the state of the object. 
Reason: GSR1201E: Promotion failed because of a NamingException while attempting to 
connect to corbaloc:iiop:myServer1.hursley.ibm.com:2809.
Action
Check the WebSphere® Application Server SystemOut.log to see which error has caused the issue. Resolve the configuration issues and promote the original object again.
Note: For promotion of WSRR content from one secure WebSphere Application Server topology to other secure WebSphere Application Server topologies, the client WebSphere Application Server requires the certificate of the target WebSphere Application Server in its trust store. If the promotion fails you must load the client WebSphere Application Server certificate into the target WebSphere Application Server trust store.
Explanation
There are a number of reasons why this error can occur:
  • Promoting to a secure WSRR system when security has not been configured correctly. The error can be caused by one of the following reasons:
    • Naming Exception: incorrect host name or port number. - Check the host name is correct, and that the sever port number is correctly set to the Bootstrap port, as listed in the WebSphere Application Server Console.
    • No trusted SSL Certificate found (or other SSL error). - Swap signer certificates, as detailed in the "Swapping signer certificates" section in Configuring promotion in a secure environment.
    • LTPA token mismatch/error. - Share LTPA encryption keys as detailed in the "Secure to secure promotion" section in Configuring promotion in a secure environment.
  • If you previously had security enabled and disable security, the Application Server might still be attempting to use the SSL transport layer. You can fix this by setting outbound CORBA settings to use TCP/IP. For more information, see the "Using TCP/IP to communicate with the target Application Server" section in Configuring promotion in a secure environment.
  • The remote server that you are promoting to might be doing an internal redirect to the same remote host. This will appear in an FFDC with this form: 
    org.omg.CORBA.TRANSIENT: java.net.UnknownHostException: oraclehost:host=myRemoteHost,port=9100
  vmcid: IBM  minor code: E02  completed: No
    To resolve this problem, add the myRemoteHost server and its ip address to /etc/hosts or c:\windows\system32\drivers\etc\hosts

ORB request timeout

Promotion might fail due to an ORB request timeout. If this occurs, promotion is rolled back before it completes. The following error is written to the WebSphere Application Server SystemOut.log file:
org.omg.CORBA.TRANSACTION_ROLLEDBACK vmcid: 0x49421000 minor code: 44 completed: Maybe
An ORB timeout can occur even if transaction timeout has been set to a suitable value. The default value of the ORB timeout is 180 seconds. In the first instance it should be increased to 360 seconds to see if that is sufficient to allow the operation to complete. After that it should be doubled until it is clear that it is not the limiting factor in any problems. The ORB timeout should never be longer than the total transaction timeout. Set the ORB Service Request timeout in the WAS administration console. Select Application Servers > server-name > Container Settings > Container Services > ORB Service.

AccessException error

The following error might be written to the WebSphere Application Server SystemOut.log file after a promotion operation:
[4/18/11 10:53:02:525 EST] 0000003a SecurityColla A SECJ0053E: Authorization failed
 for esi2ldap1.rt:636/sr1wasconsole while invoking
 (Home)ServiceRegistry#ServiceRegistryAPIEJB.jar#ServiceRegistryAdmin create::2 Subject:
Principal: esi2ldap1.rt:636/sr1wasconsole
Public Credential: com.ibm.ws.security.auth.WSCredentialImpl@3e8a3e8a
 is not granted any of the required roles: Administrator User
[4/18/11 10:53:06:026 EST] 0000003a FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider
 logIncident FFDC1003I: FFDC Incident emitted on
 /var/gov/WebSphere/ffdc/WSRRCluster01Mbr11_208e208e_11.04.18_10.53.02.533682980025370962854.txt
 com.ibm.ejs.container.EJSContainer.preInvokeForStatelessSessionCreate 2139
[4/18/11 10:53:06:263 EST] 0000003a api E com.ibm.sr.governance.api.ServiceRegistryPromotionImpl
 processPromotion GSR5000I: Captured exception [178]: java.rmi.AccessException:
 CORBA NO_PERMISSION 0x0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: java.rmi.AccessException: ; nested exception is:
com.ibm.websphere.csi.CSIAccessException: SECJ0053E: Authorization failed for
 esi2ldap1.rt:636/sr1wasconsole while invoking
 (Home)ServiceRegistry#ServiceRegistryAPIEJB.jar#ServiceRegistryAdmin create::2 Subject:
Principal: esi2ldap1.rt:636/sr1wasconsole
Public Credential: com.ibm.ws.security.auth.WSCredentialImpl@3e8a3e8a
 is not granted any of the required roles: Administrator User vmcid: 0x0 minor code: 0 completed: No
[4/18/11 10:53:06:277 EST] 0000003a api E com.ibm.sr.governance.api.ServiceRegistryPromotionImpl
 processPromotion java.rmi.AccessException: CORBA NO_PERMISSION 0x0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION: java.rmi.AccessException: ; nested exception is:
com.ibm.websphere.csi.CSIAccessException: SECJ0053E: Authorization failed for
 esi2ldap1.rt:636/sr1wasconsole while invoking
 (Home)ServiceRegistry#ServiceRegistryAPIEJB.jar#ServiceRegistryAdmin create::2 Subject:
Principal: esi2ldap1.rt:636/sr1wasconsole
Public Credential: com.ibm.ws.security.auth.WSCredentialImpl@3e8a3e8a
 is not granted any of the required roles: Administrator User vmcid: 0x0 minor code: 0 completed: No
at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java:275)
at com.ibm.CORBA.iiop.UtilDelegateImpl.wrapException(UtilDelegateImpl.java:743)
at javax.rmi.CORBA.Util.wrapException(Util.java:296)
at com.ibm.serviceregistry._ServiceRegistryAdminHome_Stub.create(_ServiceRegistryAdminHome_Stub.java:245)
at com.ibm.sr.governance.api.ServiceRegistryPromotionImpl.invokeImport(ServiceRegistryPromotionImpl.java:373)
at com.ibm.sr.governance.api.ServiceRegistryPromotionImpl.access$0(ServiceRegistryPromotionImpl.java:364)
The following are possible causes of this error:
  • The WSRR user has not been mapped to the J2EE roles; for details, see J2EE role mappings.
  • The promotion operation is between two WSRR instances on the same host, and the custom property com.ibm.websphere.orb.uniqueServerName has not been set; for details, see Configuring promotion on a single host.
Parent topic: Promotion problems