Problem
| Potential solution / explanation
|
The connector shuts down unexpectedly during initialization and the
following message is reported:
java.lang.NoSuchMethodError at
com.ibm.workflow.api.Agent$OsaLocator.
locateController(Agent.java:219) at
com.ibm.workflow.api.Agent$OrbLocator.
locate(Agent.java:173) at
com.ibm.workflow.api.Agent.
setName(Agent.java:401).
| This error may indicate that the default IBM Java ORB libraries are
incompatible with those required by the WebSphere MQ Workflow API for
communication to a remote Workflow server via an IBM Java ORB agent.
Per IBM requirements, these libraries need to be boot-strapped so that they
take precedence over the default IBM Java ORB libraries. To do this,
open start_connector.bat or
start_connector.sh), scroll down to the section that begins
STEP 3 and ensure that you have specified the correct IBM Java ORB libraries
as required by IBM.
- Note:
- The WebSphere MQ Workflow API may require different IBM Java ORB libraries
than are shipped. See IBM WebSphere MQ Workflow: Programming
Guide for more information.
|
The connector terminates while processing a message and reports an error
similar to the following: Exception thrown:
com.crossworlds.connectors.mqworkflow.exceptions.
FatalProcessingException: [Type: Fatal Error] [MsgID:
40007] [Mesg: Failed to read message content. An IO error
occurred: java.io.UnsupportedEncodingException
Cp437.]]
| The JVM version you are using does not have the libraries necessary to
support the message character set. The easiest solution to this problem
is to download a more recent version of the JDK from Sun Microsystems and run
the connector in this new JVM. Open the
start_connector.bat (or
start_connector.sh) file and replace all instances of
%CROSSWORLDS%\bin\java with the path of your new JVM.
|
The connector shuts down unexpectedly during initialization and the
following exception is reported:
java.lang.UnsatisfiedLinkError: no mqjbnd01 in shared
library path
| Connector cannot find a required runtime library
(mqjbnd01.dll [Windows] or libmqjbnd01.so
[UNIX]) from the IBM WebSphere MQ Java client libraries. Ensure that
your path includes the library folder.
|
The connector shuts down unexpectedly during initialization, and the
following message is reported: Exception in thread "main"
java.lang.NoClassDefFoundError:
com/ibm/workflow/api/FmcException
| Verify that you specified the correct path of your MQWorkflow client
libraries in start_WebSphereMQWorkflow.bat (Windows) or
start_WebSphereMQWorkflow.sh (UNIX). See "Startup file configuration" for further instructions.
|
The connector shuts down unexpectedly during initialization and the
following exception is reported:
java.lang.UnsatisfiedLinkError: no fmcojprf
(libfmcojpfr.a or .so) in java.library.path
| The connector cannot find a required runtime library. Search for
the library specified (for example, libfmcojprf.a) on your
system and ensure that the parent directory for this file is included in your
path. If the library cannot be found, ensure that you've installed
all necessary prerequisite software (WebSphere MQ Workflow application and
WebSphere MQ client libraries). Once the library is located and added
to your path, you may need to modify the start_connector script and
then add this path to the java.library.path option
that is passed in the command line to start the adapter. To do this,
scroll to the bottom of the start script and locate the command that starts
the adapter (this may begin with
ProductDir\bin\java). The command line specifies
options. Locate the option that begins
_Djava.library.path=. Append the parent
directory for the library in question to the list of other directories
specified for the _Djava.library.path option.
For example, if c:program\files\webspheremq workflow\bin
contained libfmcojprf.a.,after modification, your
command line might include
_Djava.library.path=ProductDir\bin;
%CONNDIR%;c:\program files\webspheremqworkflow\bin.
|