dumpList(">Non-Serializable<",
> nonSerializable);
> }
> }
> }
> }
>
> private void dumpList(String header, Collection list)
> {
> if (list.size() >
erator iterator = list.iterator();
while (iterator.hasNext()) {
logger.debug(iterator.next());
}
}
}
}
-Original Message-
From: Reinhard Moosauer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2006 3:58 AM
To: Tomcat Users List
Subject: Re: manag
erator iterator = list.iterator();
while (iterator.hasNext()) {
logger.debug(iterator.next());
}
}
}
}
-Original Message-----
From: Reinhard Moosauer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2006 3:58 AM
To: Tomcat
Peter,
you saved me. Thanks a lot!
I also upgraded to using the deploy-task with update="true" and got even
better behavior than before.
Application-update works with a sub-second downtime now.
BTW I use in META-INF/context.xml:
as the path. This it is working out of the box without creati
]
> Sent: Tuesday, March 14, 2006 9:04 AM
> To: Tomcat Users List
> Subject: Re: manager-remove/undeploy without losing sessions
>
> Hi List,
>
> I found something, that looked promising, but did not work.
> Developers, please look, this could be a bug:
>
> The deploy-task
: Tuesday, March 14, 2006 9:04 AM
To: Tomcat Users List
Subject: Re: manager-remove/undeploy without losing sessions
Hi List,
I found something, that looked promising, but did not work.
Developers, please look, this could be a bug:
The deploy-task has an attribute "update", removes the cont
Please open a bug report,
then we can better discuss the issue.
Peter
Am 14.03.2006 um 16:21 schrieb Reinhard Moosauer:
Hi Peter,
thanks for making it clear.
I would appreciate your opinon in how we could enhance this:
- I think, even on production systems, there should be a
possibility
Hi Peter,
thanks for making it clear.
I would appreciate your opinon in how we could enhance this:
- I think, even on production systems, there should be a possibility to
do a 'soft' application update without interrupting all users.
When only minor changes in the application are made, the
Hmm,
I thing you are right.
ContextConfig.destroy() remove the working dir after undeploy the app.
/**
* Process a "destroy" event for this Context.
*/
protected synchronized void destroy() {
// Called from StandardContext.destroy()
if (log.isDebugEnabled())
Hi List,
I found something, that looked promising, but did not work.
Developers, please look, this could be a bug:
The deploy-task has an attribute "update", removes the context before
re-installing it. I hoped that this one would do what I want.
But unfortunately, it is equivalent to undeploy/
Sorry, other question over yours
How works that smooth behavior ? I'm tomcat 5.0.x and each time that we
need update the call center version, everybody has to stop working for a
few minutes.
Any clue ?
thanks
-Original Message-
From: Reinhard Moosauer [mailto:[EMAIL PROTECTED]
Sent: Tu
11 matches
Mail list logo
