Skip navigation
Buddiga
Currently Being Moderated

Upgrade ES2 | Stuck at JNDI Information

Feb 1, 2012 4:40 PM

Tags: #livecycle #installation #es2

Hi, This is my first post!

 

I am upgrading Adobe LC 8.2 to ES2 on AIX, WAS7.x and Oracle 11gR2. I am stuck at an exception, this I did search in forum and found no solid answer. Will try to redeploy, meanwhile if someone know the answer will be helpful.

 

ationServer=websphere) defaultIfNotFound: null

[2012-02-01 19:05:41,818], FINE, Thread-49, com.adobe.livecycle.lcm.core.LCMDataManager, getting variable (applicationServer=websphere) defaultIfNotFound: null

[2012-02-01 19:05:41,833], SEVERE, Thread-49, com.adobe.livecycle.upgrade.gui.upgrade8.UpgradeJNDIPortDialog$TestCo nnectionTask, Task failed

javax.naming.NamingException: Error getting WsnNameService properties [Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible  vmcid: IBM  minor code: E07  completed: No]

        at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInit CtxFactory.java:1475)

        at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(Wsn InitCtxFactory.java:982)

        at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCt xFactory.java:902)

        at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(Ws nInitCtxFactory.java:574)

        at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)

        at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:79 8)

        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)

        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)

        at javax.naming.InitialContext.lookup(InitialContext.java:436)

        at com.adobe.livecycle.upgrade.UpgradeUtils.validateJNDIPort(UpgradeUtil s.java:899)

        at com.adobe.livecycle.upgrade.gui.upgrade8.UpgradeJNDIPortDialog$TestCo nnectionTask$ActualTask.<init>(UpgradeJNDIPortDialog.java:599)

        at com.adobe.livecycle.upgrade.gui.upgrade8.UpgradeJNDIPortDialog$TestCo nnectionTask$1.construct(UpgradeJNDIPortDialog.java:564)

        at com.adobe.livecycle.lcm.core.tasks.SwingWorker$2.run(SwingWorker.java :114)

        at java.lang.Thread.run(Thread.java:736)

Caused by: org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible  vmcid: IBM  minor code: E07  completed: No

        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:12 70)

        at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1 330)

        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:11 58)

        at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1 296)

        at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1877)

        at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1252)

        at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:458)

        at com.ibm.WsnBootstrap._WsnNameServiceStub.getProperties(_WsnNameServic eStub.java:38)

        at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInit CtxFactory.java:1472)

        ... 13 more

Caused by: java.net.NoRouteToHostException: Can't assign requested address

        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383)

        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:245)

        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232)

        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)

        at java.net.Socket.connect(Socket.java:539)

        at java.net.Socket.connect(Socket.java:488)

        at java.net.Socket.<init>(Socket.java:385)

        at java.net.Socket.<init>(Socket.java:199)

        at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WS TCPTransportConnection.java:270)

        at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConn ectionBase.java:354)

        at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.ja va:436)

        at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.jav a:187)

        at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)

        at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)

        at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)

        at com.ibm.rmi.corba.ClientDelegate.locate(ClientDelegate.java:1974)

        at com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.java:1 999)

        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:11 80)

        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:12 66)

        ... 21 more

[2012-02-01 19:06:04,628], FINE, AWT-EventQueue-0, com.adobe.livecycle.lcm.gui.dialogs.TestProgressDialog, stopping task and timer

[2012-02-01 19:06:04,628], INFO, AWT-EventQueue-0, com.adobe.livecycle.upgrade.gui.upgrade8.UpgradeJNDIPortDialog$TestCo nnectionTask, Stopping task: com.adobe.livecycle.upgrade.gui.upgrade8.UpgradeJNDIPortDialog$TestCon nectionTask@68306830

 
Replies
  • Currently Being Moderated
    Feb 1, 2012 9:40 PM   in reply to Buddiga

    Hi Buddiga,

     

    There could be two reasons for this issue:

     

    1)      You have launched LiveCycle Configuration Manager (LCM) from a JDK other than IBM’s. This is least likely since it is an AIX box.

     

    2)      You are using version 7.0.0.9 or 7.0.0.11 of WebSphere.

     

    If at all it is the first case, kindly make sure that you are launching you LCM from IBM JDK.

    In case it is second, please apply the IBM patch as mentioned in http://help.adobe.com/en_US/LiveCycle/9.5/supported_platforms.html  (the text to look for is ‘Version 7.0.0.9 and 7.0.0.11 requires the following patch installed’)

     

    Let me know if that solves the issue.

     

    Thanks and Regards,

    Hina Rastogi

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 1, 2012 10:59 PM   in reply to Buddiga

    Hi Buddiga,

     

    Please verify that you are using the correct JNDI port.

    By default the value is 2809. However, this can be any other value too and can be confirmed from WebSphere admin console.

    Look for value of SOAP_CONNECTOR_ADDRESS under Ports section of your WebSphere Application Server instance.

     

    Thanks and Regards,

    Hina Rastogi

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 1, 2012 11:41 PM   in reply to Buddiga

    Hi Buddiga,

     

    Yes you are correct, it is BOOTSTRAP_ADDRESS.

    So, is your BOOTSTRAP_ADDRESS default i.e. 2809 or is it other than that?

     

    Thanks and Regards,

    Hina Rastogi

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points