|
Replies:
3
-
Last Post:
Oct 10, 2008 11:53 PM
by: ai109478
|
|
|
|
|
|
|
Cannot Undeploy problem - SJSAS 9.1
Posted:
Oct 7, 2008 5:21 PM
|
|
|
Hi there
Wondering if anybody has any clues into a problem we're having undeploying apps from a cluster.
If I go into the DAS and try to undeploy an EAR file I'm being told that I cannot undeploy it:
"Trying to undeploy application from domain failed; Application blah is referenced by appserv910,appserv911 and must be referenced by no server instances or clusters. Application blah is referenced by appserv910,appserv911 and must be referenced by no server instances or clusters."
I'm not sure what this means. This error has only started to appear once I upgraded from 9.1 U2 to 9.1U2 patch 3 - which is 9.1U2 build-08_p03.
It seems to be complaining that the app cannot be undeployed until all references of it on the node agents are removed. But that never used to be the case - and that is what an undeploy is attempting to do - to stop the app on the appserver nodeagents and then undeploy it.
What am I missing?
|
|
|
|
|
|
|
Re: Cannot Undeploy problem - SJSAS 9.1
Posted:
Oct 7, 2008 6:26 PM
in response to: coreyjohnston
|
|
|
Your app is probably deployed to more than one target (maybe another cluster or a standalone server). Here's what you can do:
First remove the reference by using "delete-application-ref". Once the reference is removed, then you can do undeploy command.
To find out if there are any references, use the "get * | grep application-ref.<name-of-application>". You'll see a list in dotted-notation. The target is the first value in the dotted-notation.
(e.g. server.application-ref.hello1.* where server is one of the target)
|
|
|
|
|
|
|
|
|
Re: Cannot Undeploy problem - SJSAS 9.1
Posted:
Oct 7, 2008 9:13 PM
in response to: janey
|
|
|
I think I've found the problem but don't know how to fix it.
Using asadmin get *, I've been able to find an anomality.
The applications are being listed as being deployed on the individual nodeagents (of the cluster), as opposed to the cluster itself.
ie:
In SJSAS 9.1, the get command reveals my app deployed to "appserv910" and "appserv911" which are instances in the cluster "clientTest":
appserv910.application-ref.blah.disable-timeout-in-minutes = 30
appserv910.application-ref.blah.enabled = true
appserv910.application-ref.blah.lb-enabled = false
appserv910.application-ref.blah.ref = blah
appserv910.application-ref.blah.virtual-servers =
appserv910.applications.j2ee-application.blah.availability-enabled = true
appserv910.applications.j2ee-application.blah.description =
appserv910.applications.j2ee-application.blah.directory-deployed = false
appserv910.applications.j2ee-application.blah.enabled = true
appserv910.applications.j2ee-application.blah.java-web-start-enabled = true
appserv910.applications.j2ee-application.blah.libraries =
appserv910.applications.j2ee-application.blah.location = ${com.sun.aas.instanceRoot}/applications/j2ee-apps/blah
appserv910.applications.j2ee-application.blah.name = blah
appserv910.applications.j2ee-application.blah.object-type = user
appserv911.application-ref.blah.disable-timeout-in-minutes = 30
appserv911.application-ref.blah.enabled = true
appserv911.application-ref.blah.lb-enabled = false
appserv911.application-ref.blah.ref = blah
appserv911.application-ref.blah.virtual-servers =
appserv911.applications.j2ee-application.blah.availability-enabled = true
appserv911.applications.j2ee-application.blah.description =
appserv911.applications.j2ee-application.blah.directory-deployed = false
appserv911.applications.j2ee-application.blah.enabled = true
appserv911.applications.j2ee-application.blah.java-web-start-enabled = true
appserv911.applications.j2ee-application.blah.libraries =
appserv911.applications.j2ee-application.blah.location = ${com.sun.aas.instanceRoot}/applications/j2ee-apps/blah
appserv911.applications.j2ee-application.blah.name = blah
appserv911.applications.j2ee-application.blah.object-type = user
whereas in version 8.2EE (and I thought 9.1 prior to U2 patch 3) they list as belong to the cluster "clientTest":
clientTest.applications.web-module.blah.availability-enabled = true
clientTest.applications.web-module.blah.context-root = /apps-blah/agweb/v54e/clientTest/blah
clientTest.applications.web-module.blah.description =
clientTest.applications.web-module.blah.directory-deployed = false
clientTest.applications.web-module.blah.enabled = true
clientTest.applications.web-module.blah.location = ${com.sun.aas.instanceRoot}/applications/j2ee-modules/blah
clientTest.applications.web-module.blah.name = blah
clientTest.applications.web-module.blah.object-type = user
So it kinda makes sense that the appserver can't undeploy it if its listed on the instances appsser910 and appserv911 - however the application was never deployed there directly - it was deployed to the cluster "clientTest" - to which these instances belong.
So I'm a bit stumped as to how to fix this - because it looks like a bug.
|
|
|
|
|
|
|
|
|
Re: Cannot Undeploy problem - SJSAS 9.1
Posted:
Oct 10, 2008 11:53 PM
in response to: coreyjohnston
|
|
|
|
|
If you log on to the administration console (port 4848 - default user/password is admin/adminadmin), you will be able to manage the target for your deployed application. See attached image.
|
|
|
|
|
java.net RSS
