Troubleshooting
Problem
This document lists some of the reported JText error messages, along with explanations and tips for resolving them.
Resolving The Problem
|
MsgID: 101002 | Type: Error *** ERROR :: Exception while initialization of ConnectorAgent :: Reason :: Exception 'java.lang.NullPointerException' |
| Explanation | The error is caused by not setting the supported BO. |
| Tips | Please specify the supported BO in JTextConnector.cfg to solve the problem. |
| MsgID: 102005 | **** Warning :: Unable to update recovery log. Encountered Exception ‘java.io.EOFException’ Reason: null |
| Explanation | The problem was found due to the recovery log being shared by multiple instances of the JText agent. The problem was found ONLY with the following conditions - 1. On UNIX platforms, where the multiple instances are all started from the Adapters' bin directory 2. Multiple connector instance configuration and the event log's default value not being modified on any of the connector configuration files |
| Tips | Separate the event logs for different adapter instances should fix the problem. |
| MsgID: 106005 | **** Warning :: Internal error. Exception :: java.io.IOException at com.crossworlds.connectors.jtext.FileParser.run(FileParser.java:456) at java.lang.Thread.run(Thread.java:567) |
| Explanation | This is due to an error with the datahandler. The problem occurs when the first character of the EndBODelim is present within the content of the event file. |
| Tips | Fixed in the data handler 2.6.1 IF with Jtext 5.6 |
| MsgID:107029 | Mesg: ****ERROR :: For the MO 'MO_JTextConnector_Default', 'StagingDir' has some value, FileSeqEnabled' is set to 'false' and 'OutFileName' is not 'Native'. This combination is not allowed. Please change the configuration and try again. Terminating Connector. |
| Explanation | The above combination has been avoided in JText due to several technical design considerations, the most significant of them being the output file content integrity |
| Tips | JText does not support the configuration where StagingDir is set and FileSeqEnabled=false and OutputFileName is not Native |
| MsgID: 110007 | **** WARNING :: Invalid filename ''SEC1.YOPB1SAM.S1'' . Specify a valid value. |
| Explanation | JText is multi-threaded but the FTP Package is not. Due to non-synchronization of multiple JText threads with one FTP client, we face the problem of the output stream being null, which leads to the error - "[MsgID: 110007] [Mesg: **** WARNING :: Invalid filename ''SEC1.YOPB1SAM.S1'' . Specify a valid value.]" |
| Tips |
|
| MsgID: 105002/110016 | [Type: Error] [MsgID: 105002] [Mesg: **** WARNING :: JTextBOHandler.doVerbFor FAILED for BO 'ASBOJTextWrapper'. Reason :: **** ERROR : [Type: Error] [MsgID: 110016] [Mesg: **** ERROR :: Unable to access the directory 'ftp://trgedi:t rgedi@9.27.45.6:21/IBM.EDI.UNPACKED.DATA'. Please Check its access privileges.] |
| Explanation | Configuration error with JText/FTP to/from Mainframe |
| Tips | Assume that the MVS user name is 'mvsuser' and the password is 'pwd4ftp' and an SDS system is used.(The event/output directory should contain the full path from the root.) For Polling Operations: If the file AAADYN.SAND needs to be polled from "MVSUSER" then refer to the below sample configuration. Sample Configuration: FTPOSPlatform MVS EventDir ftp://mvsuser:pwd4ftp@mainframe.us.ibm.com/MVSUSER EventExt sand FTPEventFileMask AAA* |
| JText Adapter can not start and getting FileParser: run() error | |
| Explanation | The NullPointerException error in log file is caused by wrong MO naming. |
| Tips | While the JText connector instance name is SCNCJTextConnector, its MO name should be MO_SCNCJTextConnector_default. |
| Mesg: **** WARNING :: Formatting failed. Reason ::Already reached end of BO while expecting more token Mesg: **** WARNING :: Formatting failed. Reason :: Unable to find version "*.*.*" of business object definition "Customer | |
| Explanation | It means that the format of input file is not what the JText adapter expects. |
| Tips |
|
[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Adapter for JText","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.6;2.5;2.4","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21207961