You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Wesley Acheson <we...@gmail.com> on 2010/08/31 00:05:45 UTC
Re: Deploying ROOT application errors.
Hi,
I assumed that this would be fixed by now still having a problem with
the same application. Setup the same. Except trying with tomcat 6.0.29
which I downloaded today.
I was unable to get to the bottom of it. I think I can probably reduce
the test case however.
Setup is tomat 6.0.29
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
Windows Vista 32 bit
Running as administrator.
On Thu, Jul 16, 2009 at 11:54 PM, Mark Thomas <ma...@apache.org> wrote:
> Wesley Acheson wrote:
>> Theres only two jars and their not used.
>
> The flippant reply would be "Well delete them then and the problem will
> go away"
>
>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>
> As soon as I saw that, I suspected it would be the one causing grief and...
>
>> However the webapp isn't deployed correctly it still only contains
>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>
> The problem is that if you put a jdbc driver jar in the lib directory,
> it gets registered with DriverManager automatically.
I don't know if this is off topic but how is a jar file which isn't
referenced yet registered? Is it Reflected to see if its a JDBC jar?
> Try de-registering it with a context listener (which you'll need to do
> anyway to avoid a permgen leak on reload).
>
> As an aside, Tomcat tries (and fails) to fix this for you automatically.
> That should be fixed in the next 6.0.x release.
>
> If you still see the problem when the driver is de-registered, I can
> take a look with a profiler.
>
> Mark
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Deploying ROOT application errors.
Posted by Wesley Acheson <we...@gmail.com>.
I reinstalled tomcat to another directory and it all works fine now :(
Now I'm confused. Its the same zip file I used for tomcat yesterday.
Anyway issues closed for the moment.
Wes
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Deploying ROOT application errors.
Posted by Wesley Acheson <we...@gmail.com>.
Sorry for the double/treble post earlier I started one reply saved as
a draft. Then found out more details posted them and accidently sent
the draft also. details below.
>
> Looks like you have a locked JAR file. That is indicative of a memory leak.
>
> You need to figure out a) which JAR can't be deleted and b) what is
> holding the reference to it.
>
> Mark
On Thu, Jul 16, 2009 at 11:54 PM, Mark Thomas <ma...@apache.org> wrote:
> Wesley Acheson wrote:
>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>
> As soon as I saw that, I suspected it would be the one causing grief and...
>
>> However the webapp isn't deployed correctly it still only contains
>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>
> The problem is that if you put a jdbc driver jar in the lib directory,
> it gets registered with DriverManager automatically.
Still that jar file. I haven't even declared a resource in web.xml.
At the moment its only sitting in libs because I intend to use it. And
as per your instructions last year I'm trying to deregister with
DriverManager via a context listener.
> As an aside, Tomcat tries (and fails) to fix this for you automatically.
> That should be fixed in the next 6.0.x release.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Deploying ROOT application errors.
Posted by Mark Thomas <ma...@apache.org>.
On 30/08/2010 23:21, Wesley Acheson wrote:
> More Info it seems to work correctly if the war file is deployed after
> tomcat has started. However if the war file is there when I start
> tomcat it is undeployable.
>
> SEVERE: [C:\icarus\tomcat\webapps\ROOT\WEB-INF\lib] could not be completely dele
> ted. The presence of the remaining files may cause problems
> 31-Aug-2010 00:18:29 org.apache.catalina.startup.ExpandWar deleteDir
Looks like you have a locked JAR file. That is indicative of a memory leak.
You need to figure out a) which JAR can't be deleted and b) what is
holding the reference to it.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Deploying ROOT application errors.
Posted by Wesley Acheson <we...@gmail.com>.
On Tue, Aug 31, 2010 at 12:05 AM, Wesley Acheson
<we...@gmail.com> wrote:
> Hi,
>
> I assumed that this would be fixed by now still having a problem with
> the same application. Setup the same. Except trying with tomcat 6.0.29
> which I downloaded today.
>
> I was unable to get to the bottom of it. I think I can probably reduce
> the test case however.
>
> Setup is tomat 6.0.29
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
> Windows Vista 32 bit
> Running as administrator.
>
More Info it seems to work correctly if the war file is deployed after
tomcat has started. However if the war file is there when I start
tomcat it is undeployable.
SEVERE: [C:\icarus\tomcat\webapps\ROOT\WEB-INF\lib] could not be completely dele
ted. The presence of the remaining files may cause problems
31-Aug-2010 00:18:29 org.apache.catalina.startup.ExpandWar deleteDir
SEVERE: [C:\icarus\tomcat\webapps\ROOT\WEB-INF] could not be completely deleted.
The presence of the remaining files may cause problems
31-Aug-2010 00:18:29 org.apache.catalina.startup.ExpandWar deleteDir
SEVERE: [C:\icarus\tomcat\webapps\ROOT] could not be completely deleted. The pre
sence of the remaining files may cause problems
31-Aug-2010 00:18:29 org.apache.catalina.startup.ExpandWar delete
SEVERE: [C:\icarus\tomcat\webapps\ROOT] could not be completely deleted. The pre
sence of the remaining files may cause problems
31-Aug-2010 00:18:29 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Deploying ROOT application errors.
Posted by Wesley Acheson <we...@gmail.com>.
Sorry I don't understand what's happening. It is working now but It
didn't work the first time I deployed to the new Tomcat instance.
I got a bunch of warnings saying not able to remove from filesystem
and checked the offending jar was in the filesystem too. However
after shutting down tomcat deleting the offending war and exploded
webapp restarting. I can deploy / undeploy to my hearts content.
However shutting down tomcat and stating up again brings back my
original problem.
On Tue, Aug 31, 2010 at 12:05 AM, Wesley Acheson
<we...@gmail.com> wrote:
> Hi,
>
> I assumed that this would be fixed by now still having a problem with
> the same application. Setup the same. Except trying with tomcat 6.0.29
> which I downloaded today.
>
> I was unable to get to the bottom of it. I think I can probably reduce
> the test case however.
>
> Setup is tomat 6.0.29
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
> Windows Vista 32 bit
> Running as administrator.
>
>
> On Thu, Jul 16, 2009 at 11:54 PM, Mark Thomas <ma...@apache.org> wrote:
>> Wesley Acheson wrote:
>>> Theres only two jars and their not used.
>>
>> The flippant reply would be "Well delete them then and the problem will
>> go away"
>>
>>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>>
>> As soon as I saw that, I suspected it would be the one causing grief and...
>>
>>> However the webapp isn't deployed correctly it still only contains
>>> WEB-INF/lib/mysql-connector-java-5.1.6.jar
>>
>> The problem is that if you put a jdbc driver jar in the lib directory,
>> it gets registered with DriverManager automatically.
>
> I don't know if this is off topic but how is a jar file which isn't
> referenced yet registered? Is it Reflected to see if its a JDBC jar?
>
>> Try de-registering it with a context listener (which you'll need to do
>> anyway to avoid a permgen leak on reload).
>>
>> As an aside, Tomcat tries (and fails) to fix this for you automatically.
>> That should be fixed in the next 6.0.x release.
>>
>> If you still see the problem when the driver is de-registered, I can
>> take a look with a profiler.
>>
>> Mark
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org