iProcess Engine background processes in suspended state after upgrade to iPE 11.6.0
Article ID: KB0083184
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Technology Plug-ins | 11.6.0 |
Description
Upgrade completed without errors, however the iProcess Engine BG processes do not start:
---------------------------------------------------------------------------------------------- Machine ID Process Name Process Inst Enabled Persistent Last Status Status Comment ---------------------------------------------------------------------------------------------- 1 BG 1 Y Y SUSPENDED Process restart suspended by process manager 1 BG 2 Y Y SUSPENDED Process restart suspended by process manager 1 BG 3 Y Y SUSPENDED Process restart suspended by process manager 1 BG 4 Y Y SUSPENDED Process restart suspended by process manager 1 BG 5 Y Y SUSPENDED Process restart suspended by process manager 1 BG 6 Y Y SUSPENDED Process restart suspended by process manager 1 BG 7 Y Y SUSPENDED Process restart suspended by process manager 1 BG 8 Y Y SUSPENDED Process restart suspended by process manager 1 BG 9 Y Y SUSPENDED Process restart suspended by process manager 1 BG 10 Y Y SUSPENDED Process restart suspended by process manager 1 DLMGR 1 Y Y RUNNING DLMGR process started 1 IAPJMS 1 N Y NOT RUNNING 1 RPCBG 1 Y Y SUSPENDED Process restart suspended by process manager 1 RPC_TCP_LI 1 Y Y RUNNING RPC listener process started 1 RPC_UDP_LI 1 Y Y RUNNING RPC listener process started 1 SPO 1 Y Y RUNNING SPO Server process started 1 WIS 1 Y Y RUNNING WIS process started 1 WIS 2 Y Y RUNNING WIS process started 1 WIS 3 Y Y RUNNING WIS process started 1 WIS 4 Y Y RUNNING WIS process started 1 WIS 5 Y Y RUNNING WIS process started 1 WIS 6 Y Y RUNNING WIS process started 1 WIS 7 Y Y RUNNING WIS process started 1 WIS 8 Y Y RUNNING WIS process started 1 WISMBD 1 Y Y RUNNING WISMBD process started 1 WISMBD 2 Y Y RUNNING WISMBD process started 1 WISMBD 3 Y Y RUNNING WISMBD process started 1 WISMBD 4 Y Y RUNNING WISMBD process started 1 WQS 1 Y Y RUNNING WQS process started |
Environment
TIBCO iProcess Engine (Oracle) 11.6.0.2
TIBCO iProcess Technology Plug-in 11.6.0
RedHat 7.2 64-bit
Resolution
Debug was applied to one of the BG processes. The EAIJAVA plugin fails to initlialize and the background processes are in a SUSPENDED state.
Lines in BG debug log:
[T=225277440]171010104550.059191:c002: lproEAI_LoadLib(): ==> Calling EAIJAVA->EAIRun_Init()...
[T=225277440]171010104550.059208:c064: proEAI_GetCallBack (): Get call-back function: 1
[T=225277440]171010104550.059224:x004: EAI_JAVA: EAIRun_Init() - Entering function
[T=225277440]171010104550.059240:c064: proEAI_GetCallBack (): Get call-back function: 5
[T=225277440]171010104550.059256:c064: proEAI_GetCallBack (): Get call-back function: 2
[T=225277440]171010104550.059273:c064: proEAI_GetCallBack (): Get call-back function: 6
[T=225277440]171010104550.059290:c064: proEAI_GetCallBack (): Get call-back function: 3
[T=225277440]171010104550.059307:c064: proEAI_GetCallBack (): Get call-back function: 4
[T=225277440]171010104550.059323:x004: EAI_JAVA: EAIRun_Init() - Base directory name = /apps/cirrus/swserver/prodcirrus/eaijava
[T=225277440]171010104550.059345:x004: EAI_JAVA: EAIRun_Init() - Class path string = -Djava.class.path=/apps/cirrus/swserver/prodcirrus/eaijava/libs/bootstrap/log4j-1.2.13.jar:/apps/cirrus/swserver/prodcirrus/eaijava/libs/bootstrap/bootstrap.jar:
[T=225277440]171010104550.059370:x004: EAI_JAVA: EAIRun_Init() - LD_LIBRARY_PATH set to /apps/cirrus/swserver/prodcirrus/java/lib/amd64/native_threads:/apps/cirrus/swserver/prodcirrus/java/lib/amd64/server:/apps/cirrus/swserver/prodcirrus/java/lib/amd64:/apps/cirrus/swserver/prodcirrus/libs:/apps/cirrus/swserver/prodcirrus/lib:/apps/cirrus/swserver/prodcirrus/libs
[T=225277440]171010104550.059392:x004: EAI_JAVA: EAIRun_Init() - Found 0 existing JVM's
[T=225277440]171010104550.059410:x004: EAI_JAVA: EAIRun_Init() - Creating Java VM
[T=225277440]171010104550.104576:x004: EAI_JAVA: EAIRun_Init() - Created VM
[T=225277440]171010104550.111076:x004: EAI_JAVA: Error reported: EAI_JAVA: EAIRun_Init() - Can't find java Loader class
[T=225277440]171010104550.111129:c002: lproEAI_LoadLib(): <== Back from EAIJAVA->EAIRun_Init(): FuncRet=-1
[T=225277440]171010104550.111161:c001: lproEAI_LoadLib(): EAIJAVA->EAIRun_Init() Failed: FuncRet=-1
The environment variable SW_SYSCLASSPATH is set correctly. The iProcess Engine process attribute SWLIB_PATH is set correctly for all the background processes.
The "ls -l $SWDIR/eaijava/libs/bootstrap" listed the following:
-r-xr-x--- 1 root root 17336 Jan 19 2016 bootstrap.jar
-r-xr-x--- 1 swpro staffwar 358180 Jan 19 2016 log4j-1.2.13.jar
The bootstrap.jar was owned by root. The iProcess Engine Background user could not access the file - the BG was unable to initialize the plug-in on start-up and became SUSPENDED.
The following commands were run by the UNIX root user to correct the ownership:
$ chown swpro:staffwar $SWDIR/eaijava/libs/bootstrap/bootstrap.jar
$ chmod 550 $SWDIR/eaijava/libs/bootstrap/bootstrap.jar
(Replace swpro with the system iProcess Engine Background user account and staffwar with the system iProcess Engine User group).
The iProcess Engine started normally with all background processes in a RUNNING state.
Lines in BG debug log:
[T=225277440]171010104550.059191:c002: lproEAI_LoadLib(): ==> Calling EAIJAVA->EAIRun_Init()...
[T=225277440]171010104550.059208:c064: proEAI_GetCallBack (): Get call-back function: 1
[T=225277440]171010104550.059224:x004: EAI_JAVA: EAIRun_Init() - Entering function
[T=225277440]171010104550.059240:c064: proEAI_GetCallBack (): Get call-back function: 5
[T=225277440]171010104550.059256:c064: proEAI_GetCallBack (): Get call-back function: 2
[T=225277440]171010104550.059273:c064: proEAI_GetCallBack (): Get call-back function: 6
[T=225277440]171010104550.059290:c064: proEAI_GetCallBack (): Get call-back function: 3
[T=225277440]171010104550.059307:c064: proEAI_GetCallBack (): Get call-back function: 4
[T=225277440]171010104550.059323:x004: EAI_JAVA: EAIRun_Init() - Base directory name = /apps/cirrus/swserver/prodcirrus/eaijava
[T=225277440]171010104550.059345:x004: EAI_JAVA: EAIRun_Init() - Class path string = -Djava.class.path=/apps/cirrus/swserver/prodcirrus/eaijava/libs/bootstrap/log4j-1.2.13.jar:/apps/cirrus/swserver/prodcirrus/eaijava/libs/bootstrap/bootstrap.jar:
[T=225277440]171010104550.059370:x004: EAI_JAVA: EAIRun_Init() - LD_LIBRARY_PATH set to /apps/cirrus/swserver/prodcirrus/java/lib/amd64/native_threads:/apps/cirrus/swserver/prodcirrus/java/lib/amd64/server:/apps/cirrus/swserver/prodcirrus/java/lib/amd64:/apps/cirrus/swserver/prodcirrus/libs:/apps/cirrus/swserver/prodcirrus/lib:/apps/cirrus/swserver/prodcirrus/libs
[T=225277440]171010104550.059392:x004: EAI_JAVA: EAIRun_Init() - Found 0 existing JVM's
[T=225277440]171010104550.059410:x004: EAI_JAVA: EAIRun_Init() - Creating Java VM
[T=225277440]171010104550.104576:x004: EAI_JAVA: EAIRun_Init() - Created VM
[T=225277440]171010104550.111076:x004: EAI_JAVA: Error reported: EAI_JAVA: EAIRun_Init() - Can't find java Loader class
[T=225277440]171010104550.111129:c002: lproEAI_LoadLib(): <== Back from EAIJAVA->EAIRun_Init(): FuncRet=-1
[T=225277440]171010104550.111161:c001: lproEAI_LoadLib(): EAIJAVA->EAIRun_Init() Failed: FuncRet=-1
The environment variable SW_SYSCLASSPATH is set correctly. The iProcess Engine process attribute SWLIB_PATH is set correctly for all the background processes.
The "ls -l $SWDIR/eaijava/libs/bootstrap" listed the following:
-r-xr-x--- 1 root root 17336 Jan 19 2016 bootstrap.jar
-r-xr-x--- 1 swpro staffwar 358180 Jan 19 2016 log4j-1.2.13.jar
The bootstrap.jar was owned by root. The iProcess Engine Background user could not access the file - the BG was unable to initialize the plug-in on start-up and became SUSPENDED.
The following commands were run by the UNIX root user to correct the ownership:
$ chown swpro:staffwar $SWDIR/eaijava/libs/bootstrap/bootstrap.jar
$ chmod 550 $SWDIR/eaijava/libs/bootstrap/bootstrap.jar
(Replace swpro with the system iProcess Engine Background user account and staffwar with the system iProcess Engine User group).
The iProcess Engine started normally with all background processes in a RUNNING state.
Issue/Introduction
iProcess Engine upgraded from 11.4.1.12 to 11.6.0.2
After the upgrade all background processes are SUSPENDED on startup.
Feedback
Yes
No
Powered by
