IJServer Cluster debugging fails to start.
[Symptom]
IJServer Cluster debugging fails to start and the following error dialog box is displayed:
Title: A problem occurred.
Content: A problem occurred in 'During server start - {0}'.
The server failed to start.
Details: The server failed to start.
OM2014: All server instances in cluster {1} were not started.OM1051: Server Instance unable to start: NAME={2}
[Variable information]
{0}: Server name displayed in the Server View
{1}: IJServer Cluster name
{2}: Instance name specified when the IJServer Cluster was created.
[Cause]
The cause is that the [Debug Port] port specified when the IJServer Cluster was registered in the Server View is already being used.
[Action]
Take one of the following actions:
Terminate the other application that is using the port specified at [Debug Port], and then repeat the operation.
Temporarily delete the IJServer Cluster from the Server View and use the [New Server] wizard again. Specify a [Debug Port] that does not duplicate that of other applications, and then repeat the operation.
An Interstage Java EE DAS service project operation failed.
[Symptom]
An addition, deletion, or other project operation for the Interstage Java EE DAS service was performed, but the operation failed and the following error dialog box is displayed:
Title: "A problem occurred." or "Problems occurred."
Content: Publication failed.
Details: Publication failed.
Module publication cancellation failed: {0}
OM2997: Unable to connect to admin-server at given host: [{1}] and port: [{2}]. Please check if this server is up and running and that the host and port provided are correct.
[Variable information]
{0}: Operation target project name
{1}: Host name
{2}: Interstage JMX service port number specified during server registration
[Cause]
The cause is one of the following:
The project was used when the Interstage Java EE DAS service was in a stopped state.
The [Interstage JMX Service Port Number] specified when the Interstage Java EE DAS was registered in the Server View is incorrect.
[Action]
Check that the Interstage JMX service port number is correct. From the Server View, repeat [Connect/Login] or [Connect(Debug Launch)/Login], and then perform the operation again.
The [New Server] wizard displays "Unexpected end of file from server" and login fails.
[Symptom]
When the [Login] button is clicked on the [New Interstage Application Server] page of the [New Server] wizard, the following error message is displayed and login fails:
Content: Login failed for the following reason: Unexpected end of file from server
[Cause]
HTTP connections are not permitted by the Interstage Application Server installed at the host specified at [Server's host name] on the [Define a New Server] page of the [New Server] wizard, but [Use HTTPS communication to connect to target] is not selected on the [New Interstage Application Server] page.
[Action]
Check the communication settings of the connection destination Interstage Application Server and, if necessary, change them. Alternatively, select [Use HTTPS communication to connect to target] on the [New Interstage Application Server] page and click the [Login] button.
