IBM E02HRLL-G - WebSphere Partner Gateway Express, Administration Manual

Page: 190 / 268

java.lang.NoClassDefFoundError with reprocessDbLoggingErrors.bat
About this task
You might encounter java.lang.NoClassDefFoundError for the following reason.
The reprocessDbLoggingErrors.bat file has the path to ws_runtime.jar, which is
present in the directory:
<WAS_HOME>\deploytool\itp\plugins\com.ibm.websphere.v61_6.1.0.
But, after every fixpack release, the folder name com.ibm.websphere.v61_6.1.0 gets
changed to the corresponding fixpack version. Hence, the batch file fails to find the
ws_runtime.jar. To fix this issue, you have to set the ws_runtime.jar path, as
described below:
1.
Navigate to the directory:
<WAS_HOME>\deploytool\itp\plugins
2. Check the path for ws_runtime.jar.
3. Navigate to the directory:
<WAS_HOME>\bin
4. Edit the reprocessDbLoggingErrors.bat file directory.
5. Set the correct path for ws_runtime.jar and rerun the script.
Recovery process when queue and disk is full or unavailable
About this task
When messaging system and common file system are full or not available during
processing, the Business Document Object (BDO) will be persisted temporarily
under Receiver machine temp folder:
WPG_HUB_INSTALL_HOME\Receiver\temp
. In this
case, the Hub will trigger an event 103205 with the following description:
Receiver Processing halted, due to following reason failed to process target:
With Queue and File system unavailable/Full.
Please make sure queue and disk system are available
for processing and start the receiver.
If you get a message with the above description, do the following:
1.
Make sure queue and common file system disk are available for processing.
2. Restart the receiver server.
3.
Move the Business Document Object (BDO) persisted under receiver temp
folder to (Hub’s) common file system
router_in folder.
Workflow Handler Runtime Error
While document processing, a failure error may occur and the document viewer
displays ’Workflow handler runtime error’. In such a scenario, check if the
WebSphere SystemErr.log file contains the following errors:
v
java.net.ConnectException error:
Possible solution: If you are using the WebSphere Transformation Extender RMI
Server, ensure that the server is running and is able to access the hostname and
port mentioned in the exception.
v
com.ibm.websphere.dtx.dtxpi.rmi.MRmiApiException: Unknown error - Loading
map failed - Native function: CMpiMapSet::CMpiMapSet:
Possible solutions:
184
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide