Errors reported in eaijava.GUID.log file(s) due to incorrect .jar file loading sequence.

Errors reported in eaijava.GUID.log file(s) due to incorrect .jar file loading sequence.

book

Article ID: KB0090955

calendar_today

Updated On:

Products Versions
TIBCO iProcess BusinessWorks Connector -
Not Applicable -

Description

Description:
Type of errors reported:

[ERROR] SWEAIJavaClassLoader - Unable to initialise JMX
[FATAL] SWEAIJavaClassLoader - Failed to initialise class loader

Caused by:
java.lang.NoSuchMethodError: mx4j.remote.ProviderFactory.newJMXConnectorServer

    This is due to the mx4j-tools.jar loading before mx4j-remote.jar.
    By moving the jar to the user directory the loading order is
    changed.
       
======================================================================
Solution to error:

1) Ensure the iProcess Engine is shut down.

2) Move the mx4j-tools.jar from $SWDIR/eaijava/libs/repository/system/
to $SWDIR/eaijava/libs/repository/user/

3) Restart the iProcess Engine.

======================================================================
TIBCO Product Support

  - For an overview of TIBCO Support Services, and information about
     getting started with TIBCO Product Support, visit this site:
    http://www.tibco.com/services/support

  - If you already have a valid maintenance or support contract,
    visit the TIBCO Product Support site: http://support.tibco.com
    Entry to this site requires a username and password. If you do
    not have a username, you can request one.

  - Check the TIBCO Product Support site "Late Breaking News" page
    for product information that was not available at release time.

======================================================================

Copyright (C) 2001-2006 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
Symptoms:

Cause:

Issue/Introduction

Errors reported in eaijava.GUID.log file(s) due to incorrect .jar file loading sequence.