Prev
Next
Forums S3 Systems Administration

pfserv test testGroupIOS -- Failure

Sort:
You are not authorized to post a reply.
Author
Messages
jdever
Advanced Member
Posts: 29
Advanced Member
6/11/2010 1:15 AM
    The last smoke test of a LDF 9.0.1.4 install is failing with this message:
    /opt/lawson/gen/bin]$ pfserv test testGroupIOS
    Running component tests.
    Finished running component tests.
    Output from file /opt/lawson/law/system/pfcomponenttest.log:
    Thu Jun 10 14:58:14 EDT 2010 Starting component test flow testGroupIOS.
    FAILURE running test flow "pftestQuery01".
    ErrorCode=2 (ProcessFlow engine error)
    InformationCode=0
    ReturnMessage="Error calling pfEngine: java.lang.NoClassDefFoundError: javax.e
    jb.EJBObject"
    ErrorActivityName=""
    See ProcessFlow Server logs for details.
    Thu Jun 10 14:58:15 EDT 2010 Leaving component test flow testGroupIOS.

    pflow.out:
    Caused by: java.lang.ClassNotFoundException: javax.ejb.EJBObject
    [Jun 10, 2010 12:20:54 PM] at java.net.URLClassLoader.findClass(URLClassLoader.java:496)
    [Jun 10, 2010 12:20:54 PM] at java.lang.ClassLoader.loadClass(ClassLoader.java:631)
    [Jun 10, 2010 12:20:54 PM] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
    [Jun 10, 2010 12:20:54 PM] at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
    [Jun 10, 2010 12:20:54 PM] ... 23 more

    _____
    It appears that the test is looking for the javax.ejb.EJBObject... that I believe is located in the j2ee.jar in the $WAS_HOME/lib.

    Has anyone ever seen this error when executing the " pfserv test testGroupIOS" smoke test?
    Thanks for the help.

    Tags: pfserv
    Roger French
    Veteran Member
    Posts: 545
    Veteran Member
    6/11/2010 2:32 PM
      Try getting an update to the pfserv.cfg file located in %LAWDIR%/system. I know we had to get an updated one because our pflow queries weren't working and the cause was becasue of the pfserv.cfg. There was a problem with one of the lines in the file. That may or may not be the solution to your problem.
      Tags: pfserv
      jdever
      Advanced Member
      Posts: 29
      Advanced Member
      6/11/2010 4:47 PM
        This isssue was a direct result of a bad "pfserv" program ( script). Patches applied after the original 9.0.1.4 ESP have a corrected pfserv.
        This bad pfserv script produced a hard coded location for the j2ee.jar that was incorrect:
        The bad location = /opt/lawson/gen/java/thirdParty/:j2ee:j2ee.jar::
        The correct location = /opt/lawson/gen/java/thirdParty/j2ee/j2ee.jar::
        This was a result of using the ${path_seperator} variable instead of the ${file_seperator} variable (as well as having it in the script 1 to many times).
        --
        Correcting the script to have the correct location will correct the problem. Later "pfserv" versions drop the hard coding of the j2ee.jar altogether.
        --
        Most people apply the existing Env patches prior to doing the smoke tests, this is why no one has raised this issue in the past. The patches contain the corrected pfserv.
        Tags: pfserv
        jdever
        Advanced Member
        Posts: 29
        Advanced Member
        6/11/2010 4:50 PM
          This issue is now resolved.
          Thanks.
          Tags: pfserv
          You are not authorized to post a reply.