unable to connect to grid registry

 1 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Gary Padgett
Veteran Member
Posts: 90
Veteran Member
    I am having issues in my production system with programs such as RQ10 trying to trigger workunits after converting from PFI to LPA.  I see log file entries containing the message I will include below.  There is a little more verbiage in the LPSforLSF_7034.log file in $GENDIR/bpm.  Here is an example - apparently at the point where the program is checking to see if Processflow is enabled, service is enabled, etc.

    [2013-12-18 21:17:01] [LPSJNIUtil] Exception encountered while calling Java, stack trace follows:
    com.lawson.bpm.eprocessserver.interfaces.LPSConnectionException: Unable to connect to Grid Registry at LAWN4PAPROD.hlm.ad.moffitt.usf.edu:52005
        at com.lawson.bpm.eprocessserver.interfaces.LPSGridSession.connectToRegistry(LPSGridSession.java:49)
        at com.lawson.bpm.eprocessserver.interfaces.LPSGridSessionForLSF.(LPSGridSessionForLSF.java:57)
        at com.lawson.bpm.eprocessserver.interfaces.LPSGridSessionForLSF.(LPSGridSessionForLSF.java:35)
    [2013-12-18 21:17:01] [LPSDatabaseBridge] createLPSDatabaseBridge: unable to instantiate LPSGridSessionForLSF

    We are not encountering an issue like this in our non-production system - any ideas?  We had to revert to PFI and really need to get this fixed.
    Thanks
    Gary Padgett
    Veteran Member
    Posts: 90
    Veteran Member
      RESOLVED - I was referencing an old version of Java in my production environment.  I changed /etc/lawson.env file to make LAW_JAVA_HOME and JAVA_HOME both point to the Java within WebSphere and it is now working.  Also changed PATH and LIBPATH