Restarting Portal generates a warning exception, "Application may already have been started."

Technote (troubleshooting)


Problem

During restart of Portal, a warning can be seen in the logs which state that an attempt to start the application was made, but that the application appeared to have already been started.


[12/23/10 13:58:05:757 EST] 00000000 ContainerHelp E WSVR0501E: Error
creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl
@394a394a com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.
ConfigurationWarning: Duplicate application, ibmasyncrsp. Application
may already have been started.



Cause

The cause of the warning exception is that the application is mapped to the same server twice in the deployment.xml. When the server attempts to start the application the second time we get a warning as the application is already deployed and running.

Diagnosing the problem

Reviewing the systemOut logs we observe the following exception:

[12/23/10 13:58:05:757 EST] 00000000 ContainerHelp E WSVR0501E: Error
creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl
@394a394a com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.
ConfigurationWarning: Duplicate application, ibmasyncrsp. Application
may already have been started.

Resolving the problem

This could happen to any application so determining which application is having the issue and then view the specific deployment.xml.

In this technote we will focus on the application that is mentioned in the exception above, 'ibmasyncrsp'.

If you review the deployment.xml for this application was70\profiles\<profile_name>\config\cells\<cell_name>\applications\ibmasyncrs
p.ear\deployments\ibmasyncrsp\

you will see multiple deploymentTargets entries:

<deploymentTargets xmi:type="appdeployment:ClusteredTarget"
xmi:id="ClusteredTarget_1282493265846" name="WebSphere_Portal_Cluster"
/>
<deploymentTargets xmi:type="appdeployment:ServerTarget"
xmi:id="ServerTarget_1287169305776" name="WebSphere_Portal3"
nodeName="node70mlpd122" />

This shows the application being loaded twice, once as a cluster target and once as a server target.

Note: If you have a cluster setup, then you will need to use the ClusteredTarget.

To resolve this warning, go to the DMGR admin console:

Applications->Application Types->WebSphere enterprise Applications

Select your application

Select Manage Modules

Note: if the application is not listed here, it may be a hidden application. Manually editing the deployment.xml will be required.

Under the Server column, there should be two entries. One to the WebSphere_Portal_Cluster and the other to WebSphere_Portal.

Select the check box and then up in the 'Clusters and servers' section.

Select the cluster=WebSphere_Portal_Cluster and hit Apply.

Save and synchronize cluster.

Under Manage Modules, the Server column should now only have one entry. WebSphere_Portal_Cluster


Related information

Portal Support Site
Portal 7.0 Wiki


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal

Software version:

7.0

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows, i5/OS, z/OS

Reference #:

1460331

Modified date:

2011-01-20

Translate my page

Machine Translation

Content navigation