-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
>The above shows the problem (along with several other classes loaded
from that location).
>Looks like you have some hard-coded links to the local file system
buried inside the webapp's META-INF entries -
-Original Message-
From: Mark Eggers [mailto:its_toas...@yahoo.com]
Sent: Monday, 13 August 2012 5:46 p.m.
To: users@tomcat.apache.org
>Dale,
>
>Are you running this under Eclipse (looks like it)? If so, what happens
when you run the same test outside of Eclipse?
>
>/mde/
Well, the Clas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My,
On 8/12/12 12:52 PM, my koseli wrote:
> I changed the build.xml to below but I still get the error. Any
> idea?
>
> username="${tomcat.manager.username}"
> password="${tomcat.manager.password}" path="/${name}"
> war="${name}.war"/>
>
> Not
2012/8/13 Koray Duman :
> I think It is anything sending to server. Because I close the browser.
Well, I'm not an expert , so don't trust so much on my reply :-)
But, I guess that your browser doesn't notify anything to finish a
session, because session tracking is managed by server.
So, I think,
my,
On 12.8.2012 18:52, my koseli wrote:
I just tested some more with 6.0.26, and indeed InstallTask seems to be
problematic, so just use DeployTask as recommended by Tomcat docs:
Again, what exact Tomcat version do you use?
I changed the build.xml to below but I still get the error. Any ide
On Sat, 11 Aug 2012 09:07:11 +0100
Mark Thomas wrote:
>
> You are already in an error page so sendError will not trigger the
> error page matching process again. If it did there is a strong
> possibility that you could end up in an infinite loop.
>
> Mark
>
This makes sense, thanks!
I think It is anything sending to server. Because I close the browser.
first I open manager page of tomcat. After closed that browser. I am waitin 30
minute. I open manager page again on different computer. And I see that first
session cannot be closed. There are 2 sessions of tomcat manager.
2012/8/13 Koray Duman :
> Hi;
>
> We have used Tomcat 7.0.28 for 2 weeks. Our applicaiton is working normally
> until yesterday. Yesterday I realized that When I closed our application
> browser, Session cannot be closed by tomcat. It is waiting a lot of time. And
> I realized that manager serv
2012/8/13 Koray Duman :
> Hi;
>
> We have used Tomcat 7.0.28 for 2 weeks. Our applicaiton is working normally
> until yesterday. Yesterday I realized that When I closed our application
> browser, Session cannot be closed by tomcat. It is waiting a lot of time. And
> I realized that manager serv
Hi;
We have used Tomcat 7.0.28 for 2 weeks. Our applicaiton is working normally
until yesterday. Yesterday I realized that When I closed our application
browser, Session cannot be closed by tomcat. It is waiting a lot of time. And I
realized that manager servlet(tomcat manager application) beh
10 matches
Mail list logo
