You will see the following error messages in the logs:
BBOO0221W ADMC0051W: Failed to do a multicast-based processdiscovery,
trying discovery mbean
BBOO0222I SECJ0305I: Role based authorization check failed for security
name <null>, accessId NO_CRED_NO_ACCESS_ID while invoking method:
query:
com.ibm.ws.management.discovery.ServerInfo on resource Discovery and
module Discovery. ADMC0051W: Failed to do a multicast-based process
discovery, trying
discovery mbean instead followed by....
BBOO0222I ADMD0023I: Process discovered (name: dmgr, type: Deployment
Manager
ADMD0003E: Can not open the multicast socket to join mulicast group
BBOO0221W ADMD0015W: Unable to join the multicast group: 232.133.104.73/
232.133.104.73
The logs also detected a security problem in the NodeAgent:
2004/03/25 18:09:13.440 on: unknown certificate; targetException=java.la
ng.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHand
LHandshakeException: unknown certificate.
To resolve this problem, apply APAR PQ84695, which is on PTF UQ86037.
If the problem persists with the error messages below and the
applications do not show as started, you might have to follow these steps
in the administrative console:
- Select Servers > Application Servers > servername >
Administration Services > JMX Connectors > SOAPConnector > Custom
Properties
- Change:
sslConfig from node1/DefaultSOAPSSLSettings
to:
node1/RACFJSSESettings
- Recycle Application Server.
All applications show as started with a green check mark in the
administrative console. |