The Service Registry application fails to start when using a generated server startup script

Technote (troubleshooting)


Problem(Abstract)

If you use a WebSphere Application Server generated startup script to start a server, then the Service Registry application may fail to start with a com.ibm.serviceregistry.ServiceRegistryStartupBeanBean setSchemaNames java.io.FileNotFoundException

Symptom

The Service Registry application fails to start and the following exception is seen in the SystemOut.log:

E com.ibm.serviceregistry.ServiceRegistryStartupBeanBean setSchemaNames GSR5000I: Captured exception [#]: java.io.FileNotFoundException: <script_location>/config/cells/<cell_name>/nodes/<node_name>/servers/<server_name>/server.xml (No such file or directory)


Cause

The Service Registry application startup uses the user.dir system property to load configuration. If a generated script is used to start a server (startServer.sh -script) then the user.dir is the script directory not the <WAS_PROFILE_HOME>.


Resolving the problem

Add the following line to the generated server startup script:

cd <WAS_PROFILE_HOME>

Related information

WebSphere Application Server startServer command

Product Alias/Synonym

WSRR

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Service Registry and Repository
Startup

Software version:

7.5, 8.0, 8.5

Operating system(s):

AIX, HP Itanium, HP-UX, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:

1610070

Modified date:

2014-08-04

Translate my page

Machine Translation

Content navigation