Skip to main content

The context root [...] in application [...] is already in use by another application on this instance [server]

12 replies [Last post]
Anonymous

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so
far, but recently he wanted to replace the EAR and now the server
instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was
rebootet. Subsequent "asadmin deploy" with the new EAR is not working,
it says: "The context root [...] in application [...] is already in use
by another application on this instance [server]". This is rather weird,
as there actually is *nothing* deployed currently in that instance (but
a second server is running in the same LAN with *the same* EAR, having
no problems at all).

We would be rather glad if somebody could tell us what the cause of this
message could be (again, *nothing* is currently deployed on that
machne)!

Thanks in advance

Markus

[att1.html]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Markus Karg

Strange but true, Daniel got it to work:

original ear was written in camel case, and deployment did not work
anymore in original case

then he deployed and undeployed in all-lower case (what is working only
on Windows due to NTFS's case insensitivity)

THEN the deployment of the camel case worked!

REALLY WEIRD! It looks like the deployment of the wrong-cased EAR
cleaned up the temporary trash that was left over after the undeploy. If
that would be true, Daniel should get awarded a "worst trick ever award
in gold". ;-)

Daniel, good Job!

Regards

Markus

From: Eve Pokua [mailto:gorgeous65@msn.com]
Sent: Donnerstag, 7. Januar 2010 10:54
To: glassfish users GFusers
Subject: RE: The context root [...] in application [...] is already in
use by another application on this instance [server]

Hi,

Have you tried undeploying from the admin console and restarting the
server?

eve

________________________________

Date: Thu, 7 Jan 2010 09:55:40 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
Subject: The context root [...] in application [...] is already in use
by another application on this instance [server]

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so
far, but recently he wanted to replace the EAR and now the server
instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was
rebootet. Subsequent "asadmin deploy" with the new EAR is not working,
it says: "The context root [...] in application [...] is already in use
by another application on this instance [server]". This is rather weird,
as there actually is *nothing* deployed currently in that instance (but
a second server is running in the same LAN with *the same* EAR, having
no problems at all).

We would be rather glad if somebody could tell us what the cause of this
message could be (again, *nothing* is currently deployed on that
machne)!

Thanks in advance

Markus

________________________________

Add other email accounts to Hotmail in 3 easy steps. Find out how.

[att1.html]

Hong Zhang

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

Markus Karg wrote:
>
> Strange but true, Daniel got it to work:
>
> original ear was written in camel case, and deployment did not work
> anymore in original case
>
> then he deployed and undeployed in all-lower case (what is working
> only on Windows due to NTFS's case insensitivity)
>
> THEN the deployment of the camel case worked!
>
> REALLY WEIRD! It looks like the deployment of the wrong-cased EAR
> cleaned up the temporary trash that was left over after the undeploy.
> If that would be true, Daniel should get awarded a "worst trick ever
> award in gold". ;-)
>
> Daniel, good Job!
>
> Regards
>
> Markus
>
> *From:* Eve Pokua [mailto:gorgeous65@msn.com]
> *Sent:* Donnerstag, 7. Januar 2010 10:54
> *To:* glassfish users GFusers
> *Subject:* RE: The context root [...] in application [...] is already
> in use by another application on this instance [server]
>
> Hi,
>
> Have you tried undeploying from the admin console and restarting the
> server?
>
> eve
>
> ------------------------------------------------------------------------
>
> Date: Thu, 7 Jan 2010 09:55:40 +0100
> From: karg@quipsy.de
> To: users@glassfish.dev.java.net
> Subject: The context root [...] in application [...] is already in use
> by another application on this instance [server]
>
> Dear GlassFish Community,
>
> our customer is using GlassFish v2ur2 with our EAR without problems so
> far, but recently he wanted to replace the EAR and now the server
> instance seems to be broken:
>
> "asadmin undeploy" removed the EAR from the instance, then the host
> was rebootet. Subsequent "asadmin deploy" with the new EAR is not
> working, it says: "The context root […] in application […] is already
> in use by another application on this instance [server]". This is
> rather weird, as there actually is *nothing* deployed currently in
> that instance (but a second server is running in the same LAN with
> *the same* EAR, having no problems at all).
>
> We would be rather glad if somebody could tell us what the cause of
> this message could be (again, *nothing* is currently deployed on that
> machne)!
>
> Thanks in advance
>
> Markus
>
> ------------------------------------------------------------------------
>
> Add other email accounts to Hotmail in 3 easy steps. Find out how.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Markus Karg

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@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Hong Zhang

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@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Markus Karg

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. 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?

> -----Original Message-----
> From: Hong.Zhang@Sun.COM [mailto:Hong.Zhang@Sun.COM]
> Sent: Donnerstag, 7. Januar 2010 19:35
> To: users@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@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Hong Zhang

>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@Sun.COM [mailto:Hong.Zhang@Sun.COM]
>>Sent: Donnerstag, 7. Januar 2010 19:35
>>To: users@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@glassfish.dev.java.net
>>>For additional commands, e-mail: users-help@glassfish.dev.java.net
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
>

[att1.html]

Markus Karg

Hong,

thank you for your kind help.

Since the problem was worked around I think we will no more be able to
find out what caused the problem. As our customers are always in a
hurry, we just cannot wait for hours to do investigations, but must
apply the first workaround that will make the host run again. Sad, but
true.

So no, we did not check the domain.xml, but as GlassFish did not reject
deployment obviously it must have been clean.

Regards

Markus

From: Hong.Zhang@Sun.COM [mailto:Hong.Zhang@Sun.COM]
Sent: Freitag, 8. Januar 2010 02:05
To: users@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]

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@Sun.COM [mailto:Hong.Zhang@Sun.COM]
Sent: Donnerstag, 7. Januar 2010 19:35
To: users@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@glassfish.dev.java.net
For additional commands, e-mail:
users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail:
users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

[att1.html]

Eve Pokua

Hi,

Have you tried undeploying from the admin console and restarting the server?

eve

Date: Thu, 7 Jan 2010 09:55:40 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
Subject: The context root [...] in application [...] is already in use by another application on this instance [server]

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so far, but recently he wanted to replace the EAR and now the server instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was rebootet. Subsequent "asadmin deploy" with the new EAR is not working, it says: "The context root […] in application […] is already in use by another application on this instance [server]". This is rather weird, as there actually is *nothing* deployed currently in that instance (but a second server is running in the same LAN with *the same* EAR, having no problems at all).

We would be rather glad if somebody could tell us what the cause of this message could be (again, *nothing* is currently deployed on that machne)!

Thanks in advance
Markus
_________________________________________________________________
Have more than one Hotmail account? Link them together to easily access both
http://clk.atdmt.com/UKM/go/186394591/direct/01/
[att1.html]

Markus Karg

Eve,

thank you for your kind response.

As I wrote below, the EAR was undeployed and the complete host was
restarted already.

Shall we try this a second time?

Daniel, do you think it is worth an attempt? Like to do that remotely on
the customer's host?

Regards

Markus

From: Eve Pokua [mailto:gorgeous65@msn.com]
Sent: Donnerstag, 7. Januar 2010 10:54
To: glassfish users GFusers
Subject: RE: The context root [...] in application [...] is already in
use by another application on this instance [server]

Hi,

Have you tried undeploying from the admin console and restarting the
server?

eve

________________________________

Date: Thu, 7 Jan 2010 09:55:40 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
Subject: The context root [...] in application [...] is already in use
by another application on this instance [server]

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so
far, but recently he wanted to replace the EAR and now the server
instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was
rebootet. Subsequent "asadmin deploy" with the new EAR is not working,
it says: "The context root [...] in application [...] is already in use
by another application on this instance [server]". This is rather weird,
as there actually is *nothing* deployed currently in that instance (but
a second server is running in the same LAN with *the same* EAR, having
no problems at all).

We would be rather glad if somebody could tell us what the cause of this
message could be (again, *nothing* is currently deployed on that
machne)!

Thanks in advance

Markus

________________________________

Add other email accounts to Hotmail in 3 easy steps. Find out how.

[att1.html]

Eve Pokua

Hi,

I have had issues like this before. The only way I got around this

was created a whole new application and then copied the files from

the old application into it. Is this just a war application? How about

changing the sun-web.xml context Root. I'm sure there's some place

where you can change the context Root of the application. How

about the domain.xml? Check the domain.xml. The server is holding

details of the old application somewhere even though you've uninstall

it. Also, are you using lookups to access data in the app client/web clients?

I use to have issues a lot when I was using lookups till I change my

clients using @EJB or annotations.

Thanks

eve

Date: Thu, 7 Jan 2010 12:01:29 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
CC: seyfried@quipsy.de
Subject: RE: RE: The context root [...] in application [...] is already in use by another application on this instance [server]

Eve,

thank you for your kind response.

As I wrote below, the EAR was undeployed and the complete host was restarted already.

Shall we try this a second time?

Daniel, do you think it is worth an attempt? Like to do that remotely on the customer's host?

Regards
Markus

From: Eve Pokua [mailto:gorgeous65@msn.com]
Sent: Donnerstag, 7. Januar 2010 10:54
To: glassfish users GFusers
Subject: RE: The context root [...] in application [...] is already in use by another application on this instance [server]

Hi,

Have you tried undeploying from the admin console and restarting the server?

eve

Date: Thu, 7 Jan 2010 09:55:40 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
Subject: The context root [...] in application [...] is already in use by another application on this instance [server]

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so far, but recently he wanted to replace the EAR and now the server instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was rebootet. Subsequent "asadmin deploy" with the new EAR is not working, it says: "The context root […] in application […] is already in use by another application on this instance [server]". This is rather weird, as there actually is *nothing* deployed currently in that instance (but a second server is running in the same LAN with *the same* EAR, having no problems at all).

We would be rather glad if somebody could tell us what the cause of this message could be (again, *nothing* is currently deployed on that machne)!

Thanks in advance
Markus

Add other email accounts to Hotmail in 3 easy steps. Find out how.
_________________________________________________________________
Have more than one Hotmail account? Link them together to easily access both
http://clk.atdmt.com/UKM/go/186394591/direct/01/
[att1.html]

Markus Karg

No, this is an EAR combining WAR and EJB-JAR.

The context root must not get modified due to external dependencies. :-(

Yes we are using lookups but the same EAR works well in lots of other
installations, so this shouldn't be the cause.

Do you know *where* the information is stored in the server after the
uninstallation? I mean, if that gets removed, it should work again.
Shouldn't it?

Thanks

Markus

From: Eve Pokua [mailto:gorgeous65@msn.com]
Sent: Donnerstag, 7. Januar 2010 12:46
To: glassfish users GFusers
Subject: RE: The context root [...] in application [...] is already in
use by another application on this instance [server]

Hi,

I have had issues like this before. The only way I got around this
was created a whole new application and then copied the files from
the old application into it. Is this just a war application? How about
changing the sun-web.xml context Root. I'm sure there's some place
where you can change the context Root of the application. How
about the domain.xml? Check the domain.xml. The server is holding
details of the old application somewhere even though you've uninstall
it. Also, are you using lookups to access data in the app client/web
clients?
I use to have issues a lot when I was using lookups till I change my
clients using @EJB or annotations.

Thanks

eve

________________________________

Date: Thu, 7 Jan 2010 12:01:29 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
CC: seyfried@quipsy.de
Subject: RE: RE: The context root [...] in application [...] is already
in use by another application on this instance [server]

Eve,

thank you for your kind response.

As I wrote below, the EAR was undeployed and the complete host was
restarted already.

Shall we try this a second time?

Daniel, do you think it is worth an attempt? Like to do that remotely on
the customer's host?

Regards

Markus

From: Eve Pokua [mailto:gorgeous65@msn.com]
Sent: Donnerstag, 7. Januar 2010 10:54
To: glassfish users GFusers
Subject: RE: The context root [...] in application [...] is already in
use by another application on this instance [server]

Hi,

Have you tried undeploying from the admin console and restarting the
server?

eve

________________________________

Date: Thu, 7 Jan 2010 09:55:40 +0100
From: karg@quipsy.de
To: users@glassfish.dev.java.net
Subject: The context root [...] in application [...] is already in use
by another application on this instance [server]

Dear GlassFish Community,

our customer is using GlassFish v2ur2 with our EAR without problems so
far, but recently he wanted to replace the EAR and now the server
instance seems to be broken:

"asadmin undeploy" removed the EAR from the instance, then the host was
rebootet. Subsequent "asadmin deploy" with the new EAR is not working,
it says: "The context root [...] in application [...] is already in use
by another application on this instance [server]". This is rather weird,
as there actually is *nothing* deployed currently in that instance (but
a second server is running in the same LAN with *the same* EAR, having
no problems at all).

We would be rather glad if somebody could tell us what the cause of this
message could be (again, *nothing* is currently deployed on that
machne)!

Thanks in advance

Markus

________________________________

Add other email accounts to Hotmail in 3 easy steps. Find out how.

________________________________

Add other email accounts to Hotmail in 3 easy steps. Find out how.

[att1.html]

Hendrawan

Dear GlassFish Community,

I'm new in here, I want to build a load balance and clustering for my
glassfish, how to setup there.
Is the cluster and load balance work in 1 machine, or different machine.

config a
---------
Public --- load balance --- cluster
| |
node1 node2

so for the config a, i must setup 4 machine, 1 for load balance, 1 for
cluster and 2 for each node.

config b
----------
Public --- loadbalance/cluster
| |
node1 node2

config b, i must setup 3 machine, 1 for the load balance and cluster, 2 for
each node.

so what is the best suggest
your feedback are welcome, thanks
[att1.html]