NAM Messages

NAM0002

Problem with serializing or deserializing of the object

Solution:

Check the class hierarchy to see if all the classes are Serializable.

NAM0003

Problem in creating a remote object for SerialContextProvider.

Cause:

Problem during publishing SerialContextProvider in CosNaming Service.

Solution:

Check if ORB CosNaming Service initialized. Check if ORB CosNaming Service initialized.

NAM0004

Application Server may not be running at port intended.

Cause:

Possible Network Error.

Solution:

Check to see if the Application Server is up and running on the port intended. The problem could be because of incorrect port. Check to see if you can access the host on which the Application Server is running.

NAM0005

The JMS Connection Factory may not be bound to a JNDI name.

Solution:

Check the list of JNDI bindings by clicking on the JNDI tree on the Administrator’s console. Check the JMS resource references bindings.

NAM0006

The JMS destination may not be bound to a JNDI name.

Solution:

Check the list of JNDI bindings by clicking on the JNDI tree on the Administrator’s console. Check the JMS resource references bindings.

NAM0007

Unresolved Message Destination Reference

Solution:

Check if the Message Destination has been linked to a Message Destination

NAM0008

Invalid Destination Name

Solution:

Check Destination Name

NAM1000

No endpoints selected.

Solution:

Check system property com.sun.appserv.iiop.endpoints.

NAM1001

No endpoints selected.

Solution:

Check system property com.sun.appserv.iiop.endpoints.

NAM1002

Bad JNDI provider URL

Solution:

Check system property java.naming.provider.url.

NAM1003

Bad host:port entry

Solution:

Check system property com.sun.appserv.iiop.endpoints.

NAM1004

Unknown host

Solution:

Check the host entry.

NAM1005

No endpoints selected.

Solution:

Check system property com.sun.appserv.iiop.endpoints.