>As I said, after doing the trick with the all-lower case undeployment,
>the deployment worked and so I cannot reproduce the problem anymore. But
>yes, we checked the domain_dir/generated folder before and found that
>not everything was cleared.
>
Did you happen to check the domain.xml entries at the time? The entries
in domain.xml are the key information that tell the server the
application is still deployed.
>I suspect that there might be a case where
>this stuff is not getting cleared completely but asadmin says
>undeployment was successful, so the question is, how to reproduce that?
>
>
Right, we will not be able to do much if we cannot reproduce it now...
>
>
>>-----Original Message-----
>>From: Hong.Zhang_at_Sun.COM [mailto:Hong.Zhang_at_Sun.COM]
>>Sent: Donnerstag, 7. Januar 2010 19:35
>>To: users_at_glassfish.dev.java.net
>>Cc: Daniel Seyfried
>>Subject: Re: The context root [...] in application [...] is already in
>>use by another application on this instance [server]
>>
>>Hi, Mark
>> Thanks for the additional information. If it's a single instance
>>set up, the undeployment should've wiped out the previous information
>>completely and the server should not complain about the context root
>>
>>
>in
>
>
>>use the next time (especially after a restart!). Most likely the
>>undeployment was not completed successfully and left some information
>>hanging around.
>> A successful undeployment should stop/unload the application from
>>container, remove the application entries from domain registry (the
>>domain.xml), and remove the bits from application repository
>>(domain_dir/applications/) and generated directories
>>(domain_dir/generated).
>> If you can still reproduce the problem, can you check after the
>>undeployment, if the above are all cleaned as expected and if there is
>>anything in the server.log?
>>
>> Thanks,
>>
>>- Hong
>>
>>
>>
>>>thank you for your kind response. More inlined.
>>>
>>>
>>>
>>>
>>>>Hi, Markus
>>>>Not sure why the cases would do the magic, but could you provide a
>>>>little bit more information on the machine set up? :-)
>>>>Is this a cluster set up or a single instance set up? You mentioned
>>>>there is a second server which is in the same LAN which works ok,
>>>>what's
>>>>the relationship of that second server to this instance you were
>>>>
>>>>
>>>>
>>>trying
>>>
>>>
>>>
>>>>to undeploy the application from?
>>>>What's the exact command you used to undeploy the application from
>>>>
>>>>
>>the
>>
>>
>>>>instance? If the instance is part of the cluster set up, you can
>>>>
>>>>
>>only
>>
>>
>>>>remove the application reference from that instance and not
>>>>
>>>>
>undeploy
>
>
>>>>(the undeploy command is to remove the application from the whole
>>>>domain).
>>>>
>>>>Thanks,
>>>>
>>>>- Hong
>>>>
>>>>
>>>>
>>>There is no relation between the machines but just that they are
>>>
>>>
>>running
>>
>>
>>>the same software, but attached to different databases (separated
>>>
>>>
>>data
>>
>>
>>>pools). It is not a cluster, but both machines are set up using
>>>GFv2ur2-ML in default installation mode.
>>>
>>>The exact command to undeploy is:
>>>
>>>asadmin undeploy MyApp.ear
>>>
>>>Regards
>>>Markus
>>>
>>>
>>>
>>>
>---------------------------------------------------------------------
>
>
>>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>