Bo's blog

Friday, March 12, 2010

Websphere: javax.management.InstanceNotFoundException

 

When install the second node in cell, got the following exception wrong port number:

ADMU0001I: Begin federation of node second_NODE with Deployment Manager at

deploymentMgr:8880.

ADMU0027E: An error occurred during federation

WebSphere:process=server1,type=ConfigService,*; rolling back to

original configuration.

ADMU0211I: Error details may be seen in the file:

/…/Profile/logs/addNode.log

ADMU0113E: Program exiting with error:

com.ibm.websphere.management.exception.AdminException:

javax.management.InstanceNotFoundException:

WebSphere:process=server1,type=ConfigService,*, resulting from:

javax.management.InstanceNotFoundException:

WebSphere:process=server1,type=ConfigService,*

Solution:

1. make sure the port number is correct by checking from /……/DeploymentMGRProfile/properties/wsadmin.properties

you should see the following:

com.ibm.ws.scripting.connectionType=SOAP
#com.ibm.ws.scripting.connectionType=RMI

#-------------------------------------------------------------------------
# The port property determines what port is used when attempting
# a connection.
# The default SOAP port for a dmgr or custom profile is 8879
#-------------------------------------------------------------------------
com.ibm.ws.scripting.port=8879

2. make sure both machines (new node and the one has deploymentMgr installed) can be reached, if not add entry to /etc/hosts for both to make sure they can reach each other.

2 Comments:

At 8:03 PM, Blogger Venkat said...

Thanks this really helped me to solve the problem. admin console SOAP address is showing something else. but actual port number is present in the wsadmin.properties.

Thanks one again. Keep posting the issues.

 
At 11:57 AM, Blogger Unknown said...

Thanks

 

Post a Comment

<< Home