08 Jun

WAS, How to fix: Application already exists in the configuration repository

Application already exists in the configuration repository

If you are getting this error it means that you have screwed you Websphere Application Server application to a very good extend that now you cannot deploy or un-deploy that particular application.

In order to fix this issue we need to do a manual process of deleting the application

Steps:

  1. Stop the Websphere Application Server
  2. Do a search for your ear file in the file system and delete all the occurrences of the XXX.ear folder
  3. Once we deleted these entire XXX.ear folders, delete all the contents of temp and wstemp folder.
  4. Now go to WAS_INSTALL_DIRprofiles<profileName>defaultconfigcells<cellName>nodes<nodeName>
  5. Edit the file serverindex.xml for an entry for our application within the tag
    <deployedApplications>xxx.ear</deployedApplications>
  6. Restart the Websphere Application Server
  7. Redeploy the application to the Websphere Application Server
16 May

Messages: WebSphere Application Server, Version 5.1.x

Here are some of the common messages that you may get while working with Websphere Application Server 5.1.x. I found this list at IBM publib:

WSVR0001I: Server {0} open for e-business
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0002I: Server {0} open for e-business, problems occurred during startup
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0003E: Server {0} failed to start {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0004E: The server name, {0}, is not a valid name.
Explanation: There is a mismatch between the name of the server speicified and the server name in the corresponding server.xml.
User Response: Make sure that the server name specified matches both the directory name for the server and the server name in the corresponding server.xml.

WSVR0007E: Could not find the {0} object in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0008E: Error encountered reading {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0009E: Error occurred during startup {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation: A variable used in the classpath definition of the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2} {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0018W: Unable to create CustomService, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0019W: CustomService, {0}, failed to initialize. {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0020W: CustomService, {0}, failed to shutdown. {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0021W: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation: A variable used in the native path definition of the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid variable
Explanation: A variable used in the resource is not defined or does not contain a valid value.
User Response: Define the missing variable or provide a valid value for the missing variable.

WSVR0024I: Server {0} stopped
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0025I: Creating temporary product license
Explanation: None
User Response: None

WSVR0026I: Error occurred while validating product license
Explanation: None
User Response: None

WSVR0027I: The product will expire in {0} days.
Explanation: None
User Response: None

WSVR0028I: The product has expired. Please re-install or purchase the product.
Explanation: None
User Response: None

WSVR0030E: ORB not initialized
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0031E: Unable to load container {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0032E: Object Adapter created already
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0033E: Unable to load security collaborator, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0034W: Invalid passivation directory specified: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0035E: Failure to initialized the container: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0036E: Failure to obtain initial naming context: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0037I: Starting EJB jar: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0038I: No JNDI name found for {0}, binding home name as {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0039E: Unable to start EJB jar, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0040E: addEjbModule failed for {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0041I: Stopping EJB jar: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0042E: Unable to stop {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0043E: Unbind failed for {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0044E: Unable to stop EJB jar, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0045E: Unable to create sub-context {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0046E: Unable to bind, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0047E: Batch naming operation failed : {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0048W: Binding {0} failed, no JNDI name found
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0049I: Binding {0} as {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0055W: Unexpected objectToKey method callback for object {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0056W: Tie class of {0} can not be found.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0062E: Unable to start EJB, {0}: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0100W: An error occurred initializing, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0101W: An error occurred starting, {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0102E: An error occurred stopping, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0103E: An error occurred destroying, {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0104E: No type or class defined in {0} at line {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0105E: Both type, {0}, or class, {1}, are defined in {2} at line {3}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0106E: Invalid startup value {0} at line {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0107W: Duplicate component, {0}, in file {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0120E: An error occurred processing {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0150E: Missing entry for {0} in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0200I: Starting application: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0201E: Application, {0}, failed to initialize {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0202E: Application, {0}, failed to start {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0205E: Module, {0}, of application, {1}, failed to initialize
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0206E: Module, {0}, of application, {1}, failed to start
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0207I: Preparing to start EJB jar: {0}
Explanation: Preparation includes reading deployment descriptors and loading classes.
User Response: No action is required for this status message.

WSVR0208E: Unable to prepare EJB jar: {0} {1}
Explanation: An EJB jar can fail preparation due to incorrect deployment descriptors.
User Response: Look for messages that appear between this message and the preceeding WSVR0207I message. If you find one, it may be related to the cause of this message. If none is found, use the exception that appears as part of this message as a possible cause of this message.

WSVR0209E: Unable to prepare EJB jar {0}, enterprise bean {1} {2}
Explanation: An EJB can fail preparation if the container required classes have not been generated for the EJB.
User Response: Verify the EJB jar that contains the failed EJB {1} has been deployed.

WSVR0210W: No modules defined for application, {0}, on server, {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0211W: Duplicate library, {0}, defined in {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0212W: Library, {0}, defined in {1} does not exist
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0213W: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0214W: Application, {0}, already installed
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0215W: Starting application, {0}, failed. The application is not installed.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0216W: Stopping application, {0}, failed. The application is not started.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0217I: Stopping application: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0219I: Application, {0}, is disabled
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0220I: Application stopped: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0221I: Application started: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0230E: Invalid uri format encountered while processing cross document link: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0231E: Unrecognized resource type encountered during Application startup: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0232E: Unable to resolve cross document link identified by the uri: {0}, and referenced by document {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0300I: Problems found in {0}
Explanation: Parse errors or warnings were found.
User Response: Fix the errors and warnings.

WSVR0301W: Invalid value type, {0}, expecting {1} at line {2}
Explanation: The type specified in the XML file was not expected.
User Response: Fix the XML file such that the appropriate type is used.

WSVR0302W: Invalid value, {0}, at line {1}
Explanation: The value specified was not valid.
User Response: Change the value to valid value.

WSVR0303W: Invalid element tagname, {0}, at line {1}
Explanation: There is no implementation class for the tag.
User Response: Contact IBM Support

WSVR0304E: Unsupported encoding, {0}
Explanation: The file encoding is not supported
User Response: Using an encoding that is supported by Java.

WSVR0305W: Invalid attribute, {0}, at line {1}
Explanation: The attribute is not valid.
User Response: Remove the attribute.

WSVR0306E: Unsupported XMI version
Explanation: The XMI version is not supported
User Response: Update the file to XMI 2.0

WSVR0307W: Invalid namespace, {0}, at line {1}
Explanation: The namespace is not valid.
User Response: Contact IBM Support

WSVR0308W: Unknown package, {0}, at line {1}
Explanation: The package is not valid.
User Response: Contact IBM Support

WSVR0309E: No packages have been registered
Explanation: No packages are registered
User Response: Contact IBM Support

WSVR0310W: Unable to resolve reference for, {0}, at line {1}
Explanation: The reference could not be resolved.
User Response: Contact IBM Support

WSVR0311W: Unknown exception {0}
Explanation: An unexpected problem occurred.
User Response: Contact IBM Support

WSVR0312E: Unknown exception {0}
Explanation: An unexpected problem occurred.
User Response: Contact IBM Support

WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation: The message listener service may be disabled.
User Response: Verify the message listener service is enabled.

WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation: The message listener service may be disabled.
User Response: Verify the message listener service is enabled.

WSVR0314E: Failed to parse {0} at line {1}, column {2} {3}
Explanation: The XML file does not have a valid XML structure
User Response: Correct the XML file.

WSVR0400W: Unable to register the {0} MBean {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0401W: Unable to deregister the {0} MBean {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0402W: Invalid MBean name {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0500E: Unable to parse {0} at line {1}, column {3} {4}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0501E: Error creating component {0} {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0600W: No thread context
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
Explanation: Only Web-Components and EJB-Components support access to the javaNameSpace.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0604I: Attempt to register EJBContainer MBean: caught exception {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0605W: Thread “{0}” ({1}) has been active for {2} milliseconds and may be hung. There are {3} threads in total in the server that may be hung.
Explanation: A thread has been active for an extended period. This may indicate that the thread is hung, including deadlock and infinite loop situations.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0606W: Thread “{0}” ({1}) was previously reported to be hung but has completed. It was active for approximately {2} milliseconds. There are {3} threads in total in the server that still may be hung.
Explanation: A thread that was previously reported as hung has now completed.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0607W: Too many thread hangs have been falsely reported. The hang threshold is now being set to {0} seconds.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

WSVR0608I: WebSphere process class preloading is enabled using {0}.
Explanation: This is an informational message.
User Response: This is an informational message.

WSVR0609I: WebSphere process class preloading is disabled.
Explanation: This is an informational message.
User Response: This is an informational message.

WSVR0610I: WebSphere process class preloading is generating a preload file.
Explanation: WebSphere process class preloading is generating a preload file. The process startup time may take longer than normal. This will happen the first time a process is started or if a change is detected that requires the file to be regenerated.
User Response: This is an informational message.

WSVR0611E: WebSphere process class preloading could not find or create a preload file.
Explanation: The WebSphere class preloader could not find an existing preload file or was unable to create a new preload file. Class preloading is disabled for this process.
User Response: Verify that the WebSphere process has write authority to the was.install.root/logs/preload or the user.install.root/logs/preload directories and try again.

WSVR0612E: WebSphere process class preloading could not find or create {0}.
Explanation: The WebSphere class preloader could not find or create the specified preload file. Class preloading is disabled for this process.
User Response: Verify that the WebSphere process has write authority to create the specified file and try again.

WSVR0613E: WebSphere process class preloading could not write to the preload file.
Explanation: The WebSphere class preloader could not write to the preload file.
User Response: Verify that the WebSphere process has write authority to the preload file and try again.

WSVR0621E: CMP Bean “{0}” is configured to use a CMP Connection Factory JNDI name of “{1}” resource. This resource does not exist.
Explanation: This error indicates that a CMP which is configured to use a Connection Factory resource is not available. The CMP bean will not function because the resource is not defined by the administrator.
User Response: Create this Connection Factory by ensuring this data source is selected for CMP use in the administrative console.

Reblog this post [with Zemanta]
26 Feb

How to Use WAS profiles to create multiple independent user configurations: IBM Websphere

How to Use WAS profiles to create multiple independent user configurations sharing the same install binaries. This is almost like having multiple servers.

Server: IBM Websphere Application Server 6.1

Tool Used: Use the Profile Management Tool

Note: WAS instances in version 5 are Profiles in v 6

In WAS 6 files are divided into 2 parts Product files and User Data. Hence in order to have multiple instances for different purposed we can have separate User Data sets and these are called as profiles in WAS 6.

By doing this you escape the need of installing multiple servers on the same machine and especially in development environment you can easily control which profile to start (saves lot of resources)

The command is in the following directory:

<was_root>/bin/pmt.sh on UNIX/LINUX

<was_root>binpmt.bat for WINDOIWS


Select “Application Server”

Click “Next”


Select “Advanced Profile Creation”


Don’t Deploy Default Application


Provide an appropriate Name and the default location of the profile

Select the option ” Create the server using development template” if you are not deploying this to a production server and for dev purpose else keep this unchecked.


Give a node name or keep it as it is

Change the Host name to the network name of the server if required


Don’t Select “Enable Administrative Security”


Change the port values as required. (Don’t forget to keep a copy of the port number assigned)


Unselect the “Run the application server process as window service” if you want to have a manual control on the server. As I am using this in development environment I don’t want my server to eat all resources on startup.


Skip this screen


Press “Create”


Select “Launch the first steps console” and verify the profile.

Recommended Reading*