S Eggleston 2700002CDU Visits (325)
Failed to connect to the JMX port on server
When you first connect from MDM Workbench to WebSphere Application Server (AppServer) where MDM Server is installed, for example to deploy a configuration project or to run a virtual job, you might see this error:
Job Manager Error - Failed to connect to the JMX port on server
When you installed MDM server, the install deployed a JMX MBean which should be listening on the AppServer ports for incoming JMX requests. The workbench acts as a JMX client, and this error means it can't make the connection.
There can be several reasons why it might not be able to connect, here are some configuration aspects you should check:
Port / host configuration
Confirm that you have the correct configuration in the Workbench server settings
WebSphere ND configuration
The Workbench does not support integration with WebSphere Application Server ND for administration and for deploying CBAs, due to restrictions in the underlying products.
Workbench does support integration for deploying virtual configuration and running virtual jobs, but the default settings do not work: for WebSphere ND you need to disable the IPC port as shown in the screen capture.
Make sure that the RMI and SOAP ports are correct for the target server: they must be for an application server, and not the deployment manager (dmgr) or node agent.
You can only run virtual jobs on one server at a time, that target server can be a member of a cluster, but it will not provide cluster capabilities such as failover or workload balancing.
Doug Cowie 270005CYF0 Visits (319)
Have you ever tried to start a BPM server on linux only to be greeted by the following incomprehensible error?