Improper values in admin.config file directives
Improperly used directives in the Install_Root /bin/admin.config
file can cause V4.0 administrative server initialization to fail when used
with a remote administrative repository database.
The nany.trace file contains the following messages:
[5/30/03 20:54:45:177 CDT] 77966861 WsnInitCtxFac W NMSV0602E: Naming
Service unavailable. A communications error occurred.
[5/30/03 20:54:45:178 CDT] 77966861 Nanny W Waiting for initial context,
retries in progress!
[5/30/03 20:54:47:186 CDT] 77966861 Nanny E Failed to get nodeHome for :
ejsadmin/homes/NodeHome :
java.lang.NullPointerException
at com.ibm.ejs.sm.util.process.Nanny.GetAdminNode(Nanny.java:506)
at com.ibm.ejs.sm.util.process.Nanny.AdminServerStartup(Nanny.java:587)
at com.ibm.ejs.sm.util.process.Nanny.main(Nanny.java:681)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
The administrative server tracefile gets to this point and stops:
[5/30/03 20:52:28:741 CDT] 77426701 Server U Version : 4.0.5
[5/30/03 20:52:29:743 CDT] 77426701 Server U Edition: Advanced Edition for
Multiplatforms
[5/30/03 20:52:30:246 CDT] 77426701 Server U Build date: Fri Nov 22
00:00:00 CST 2002
[5/30/03 20:52:30:247 CDT] 77426701 Server U Build number: ptf50246.04
[5/30/03 20:52:31:682 CDT] 77426701 SystemOut U trace and message are set
to true
[5/30/03 20:52:32:207 CDT] 77426701 ORBRas W com.ibm.CORBA.iiop.Util Util
P=950444:O=0:CT JORB0012: Pass by reference has been set to: true
(NoLocalCopies = true)
Root Cause
This can be caused by using a remote database with the following
parameters in the admin.config file:
com.ibm.ejs.sm.adminServer.dbserverName=dbsystem
com.ibm.ejs.sm.adminServer.dbportNumber=50006
To fix this problem, check the values and correct any errors. Verify that
the database serverName is the correct DNS name of the server. Also,
confirm that the DB server is using the specified port.
Security settings are misconfigured for the Administrative
Server
Another possible cause is a security error. First, try disabling Global
Security and restarting the administrative server.
On a Unix® system, you can do this from a DB2® command prompt:
- su to your db2 instance user ID.
- Make sure all WebSphere processes are stopped.
- Run the following commands:
- db2 connect to WebSphere Application Server (assumes your database is
named WAS)
- Update EJSADMIN.SECURITYCFG_TABLE set SECURITYENABLED = 0;
- disconnect was
- Before starting WebSphere, update the Install_Root
/properties/sas.server.props file by changing
com.ibm.CORBA.securityEnabled=true to
com.ibm.CORBA.securityEnabled=false. Remove the
sas.server.props.future file.
- Start the administrative server, check the security values and make
the necessary corrections.
Naming service port is not configured properly
This error message can also occur if the wrong ORB port is configured for
an application. In this case, it is not due to a misconfiguration for the
repository database.
Run the command dumpNameSpace; check in the output to determine what orb
port is being used. If NMSV0602E is logged with the error msg, no
providerURL or initialContextFactory was specified in the application;
Content: JndiLookupInfo: jndiName="ejb/ContactEmailBMPHome";
providerURL=""; initialContextFactory=""
If the naming service is running on an ORB port other than the default and
the application is not configured to use the correct naming service port,
this error will occur. This is commonly referred to as the Bootstrap port.
The default port used by the ORB is 900.
Check the port number and correct.
|