After installing TIBCO iProcess Technology plugins, and trying to start iProcess Engine, an error is reported, 1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!

After installing TIBCO iProcess Technology plugins, and trying to start iProcess Engine, an error is reported, 1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!

book

Article ID: KB0079986

calendar_today

Updated On:

Products Versions
TIBCO iProcess Technology Plug-ins -

Description

After installing the TIBCO iProcess Technology plugins, and trying to start iProcess engine, the following error is reported in the sw_warn.log file:
2010/02/25 13:51:01(BG:1:15200:2:pro:/proeai.c:80297:2522): 1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!


And in the eaijava*.log, there is the following:

2010-02-25 13:51:01,304 [ERROR] SWJMXUtils - Unable to start RMI connector
java.rmi.server.ExportException: Port already in use: 15033; nested exception is:
        java.net.BindException: Address already in use
        at sun.rmi.transport.tcp.TCPTransport.listen(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport.exportObject(Unknown Source)
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(Unknown Source)
        at sun.rmi.transport.LiveRef.exportObject(Unknown Source)
        at sun.rmi.server.UnicastServerRef.exportObject(Unknown Source)
        at java.rmi.server.UnicastRemoteObject.exportObject(Unknown Source)
        at java.rmi.server.UnicastRemoteObject.exportObject(Unknown Source)
        at javax.management.remote.rmi.RMIJRMPServerImpl.export(Unknown Source)
        at javax.management.remote.rmi.RMIJRMPServerImpl.export(Unknown Source)
        at javax.management.remote.rmi.RMIConnectorServer.start(Unknown Source)
        at com.staffware.core.swjmx.library.util.SWJMXUtils.initialiseListenerSystem(SWJMXUtils.java:388)
        at com.staffware.core.swjmx.library.util.SWJMXUtils.initialise(SWJMXUtils.java:315)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.staffware.core.swjmx.library.IProcessSwjmx.initialiseJMX(IProcessSwjmx.java:127)
        at com.staffware.core.swjmx.library.IProcessSwjmx.init(IProcessSwjmx.java:215)
        at com.staffware.core.swprocess.library.SWProcessControl.&ltinit>(SWProcessControl.java:141)
Caused by: java.net.BindException: Address already in use

 

Issue/Introduction

After installing TIBCO iProcess Technology plugins, and trying to start the iProcess Engine, the following message is reported in the sw_warn log file: 1867-'EAIJAVA' EAI Run-Time Plug-In failed to initialize, error EAI_JAVA: EAIRun_Init() - Initialise method failed in Loader!

Environment

Product: TIBCO iProcess Technology Plug-In All supported versions and operating systems

Resolution

There are 2 areas that need checking:

1). Check the following 3 files:
$SWDIR/jmsadmin/jmsdb.properties
$SWDIR/eaijava/jmxconfig.properties
$SWDIR/etc/swjmx.properties
The first 2 files define the JMX server port for BW client connections (default 10021) and the last file defines the JMX server port for Business Studio to deploy process to iProcess Engine (default 10025). Ensure these 2 ports are different.

2). Even if these 2 ports are different, make sure the port for Business Studio is not next to the port that BW clients use for connection. This is because TIBCO reserves the subsequent port next to the JMX server port that BW clients use for RMI server port (default is 10021 + 1 which is 10022).

This means iProcess BW plug-ins will use 2 ports (the one defined in jmsdb.properties/jmxconfig.properties and the subsequent port). JMX server used by Business Studio will have a different port (defined in swjmx.properties) and these 3 ports should not be used by other applications.  


If the problem is not resolved, open a ticket with TIBCO support supplying the following information:
1). Detail version of iProcess Technology plug-in
2). Detail version of iProcess Engine
3). sw_warn.log/sw_error.log file(s)
4). eaijava*.log files(s)
5). swadm show_all_attributes output
6). $SWDIR/eaijava/jmxconfig.properties
7). $SWDIR/etc/swjmx.properties