java.lang.SecurityException in tomcat 5.5.4
Hi I installed tomcat5.5.4 and jdk1.5 in the windows xp machine. Iam using beanfactory 0.99 framework. I get this error , can anybody help on this... HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.SecurityException gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:117) gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:97) gnu.beanfactory.servlet.Dispatcher.process(Dispatcher.java:80) gnu.beanfactory.servlet.Dispatcher.dispatch(Dispatcher.java:40) org.apache.jsp.nummi.SupplierMinMaxSettings_jsp._jspService(org.apache.jsp.nummi.SupplierMinMaxSettings_jsp:107) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.4 logs. Apache Tomcat/5.5.4 - Do you Yahoo!? All your favorites on one personal page Try My Yahoo!
DO NOT REPLY [Bug 32837] - double login when using ;jsessionid=
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32837. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32837 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: Project jakarta-tomcat-jk-native (in module jakarta-tomcat-connectors) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-tomcat-jk-native has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-tomcat-jk-native : Connectors to various web servers Full details are available at: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/gump_work/build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native.html Work Name: build_jakarta-tomcat-connectors_jakarta-tomcat-jk-native (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: make [Working Directory: /usr/local/gump/public/workspace/jakarta-tomcat-connectors/jk/native] - Making all in common make[1]: Entering directory `/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common' /bin/sh /usr/local/gump/public/workspace/apache-httpd/dest-28122004/build/libtool --silent --mode=compile gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-28122004/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/usr/local/gump/public/workspace/apr/dest-28122004/include/apr-1 -g -O2 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I /opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c /usr/local/gump/public/workspace/apache-httpd/dest-28122004/build/libtool: /usr/local/gump/public/workspace/apache-httpd/dest-28122004/build/libtool: No such file or directory make[1]: *** [jk_ajp12_worker.lo] Error 127 make[1]: Leaving directory `/home/gump/workspaces2/public/workspace/jakarta-tomcat-connectors/jk/native/common' make: *** [all-recursive] Error 1 - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/rss.xml - Atom: http://brutus.apache.org/gump/public/jakarta-tomcat-connectors/jakarta-tomcat-jk-native/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2928122004, brutus:brutus-public:2928122004 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32856] New: - java.lang.securityException in tomcat 5.5.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32856. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32856 Summary: java.lang.securityException in tomcat 5.5.4 Product: Tomcat 5 Version: 5.5.4 Platform: PC OS/Version: Windows XP Status: NEW Severity: critical Priority: P1 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I installed tomcat5.5.4 and jdk1.5 in the windows xp machine. Iam using beanfactory 0.99 framework. I get this error , can anybody help on this... HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.SecurityException gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:117) gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:97) gnu.beanfactory.servlet.Dispatcher.process(Dispatcher.java:80) gnu.beanfactory.servlet.Dispatcher.dispatch(Dispatcher.java:40) org.apache.jsp.nummi.SupplierMinMaxSettings_jsp._jspService (org.apache.jsp.nummi.SupplierMinMaxSettings_jsp:107) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.4 logs. Apache Tomcat/5.5.4 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32850] - Release Notes and Docs should mention that ResourceParams support has been dropped since 5.0.x
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32850. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32850 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 10:28 --- It's a little bit late for this addition. If you want to contribute a changes document, post it on tomcat-dev. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32856] - java.lang.securityException in tomcat 5.5.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32856. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32856 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 10:29 --- BZ is not a support forum. Please post on tomcat-user about this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.lang.SecurityException in tomcat 5.5.4
This is a question for the tomcat-user mailing list, not tomcat-dev. ssk 2001 wrote: Hi I installed tomcat5.5.4 and jdk1.5 in the windows xp machine. Iam using beanfactory 0.99 framework. I get this error , can anybody help on this... HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.SecurityException gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:117) gnu.beanfactory.servlet.DigestSecurity.verify(DigestSecurity.java:97) gnu.beanfactory.servlet.Dispatcher.process(Dispatcher.java:80) gnu.beanfactory.servlet.Dispatcher.dispatch(Dispatcher.java:40) org.apache.jsp.nummi.SupplierMinMaxSettings_jsp._jspService(org.apache.jsp.nummi.SupplierMinMaxSettings_jsp:107) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.4 logs. Apache Tomcat/5.5.4 - Do you Yahoo!? All your favorites on one personal page Try My Yahoo! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32858] New: - Error on load TagLibraryValidator
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32858. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32858 Summary: Error on load TagLibraryValidator Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Servlet JSP API AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I'm trying to use JSTL 1.1 with this version of tomcat with j2sdk1.4.2_05. On load jsp page get the exception exception javax.servlet.ServletException: javax/servlet/jsp/tagext/TagLibraryValidator org.apache.jasper.servlet.JspServlet.service(JspServlet.java:244) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagLibraryValidator java.lang.ClassLoader.defineClass0(Native Method) java.lang.ClassLoader.defineClass(ClassLoader.java:539) I'm using the example in: http://ftp.pucpr.br/apache/jakarta/taglibs/standard/jakarta-taglibs-standard-current.zip -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Postcard
Best wishes, your friend. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32858] - Error on load TagLibraryValidator
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32858. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32858 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 16:18 --- Bugzilla is not a support forum. Please ask questions like this on the tomcat-user mailing list (and have a read of the FAQ before you do) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32854] - CGIServlet waits for child process to be finished. (using fork in perl cgi)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32854. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32854 --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 17:04 --- -1 for your patch as currently written. It breaks the fix for bug 12041. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32850] - Release Notes and Docs should mention that ResourceParams support has been dropped since 5.0.x
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32850. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32850 [EMAIL PROTECTED] changed: What|Removed |Added Version|5.5.6 |Nightly Build --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 18:28 --- (In reply to comment #1) It's a little bit late for this addition. If you want to contribute a changes document, post it on tomcat-dev. I'm not well-versed in how this all works, so I apologize in advance for any misunderstanding, but I don't see why it is too late to include this for 5.5.x for all x 6. I'll contribute proposed diffs for the release notes and docs to the tomcat-dev list as suggested. I would have expected it to be cleaner to track it here, target it for 5.5.7 or later and attach my suggestions here. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] JK 1.2.8 Stability
Hi, JK 1.2.8 has been available for about a week now. There has been no bugs reported against this release, but we need a vote to make it official. So following the usual criteria, JK 1.2.8 is: [ ] Alpha [ ] Beta [ X ] Stable Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
Has anyone else encountered this problem? I have heard several replies like
well it only happens on windows so we are not going to worry about it well a
lot of people use windows. As soon as I can I will no longer be using
windows but for now I'm stuck.
Case to reproduce
1) Deploy a jar through the tomcat manager console
2) Access that web context.
3) Un-Deploy through the tomcat manager console (notice it does not
disappear in the list only gets stopped).
4) Try to redeploy - Message: FAIL - Application already exists at path
/mss-portal
5) Try to undeploy again. - Message: FAIL - Encountered exception
LifecycleException: Manager has not yet been started
I need help if there is a work around please let me know...
As I have said below I have tried the locking flags on context.
ACARBONE
-Original Message-
From: Carbone, Adam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 9:11 AM
To: 'Tomcat Developers List'
Subject: RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
Hi!
I remember one time my friend has same problem in windows. It was
because windows file system has lock directory, so it cannot be removed
until JVM process was shutdown.
I don't know any solution, i haven use windows in software development
in years now.. =))
Artsi
ti, 2004-12-28 kello 14:04 -0500, Carbone, Adam kirjoitti:
Has anyone else encountered this problem? I have heard several replies like
well it only happens on windows so we are not going to worry about it well a
lot of people use windows. As soon as I can I will no longer be using
windows but for now I'm stuck.
Case to reproduce
1) Deploy a jar through the tomcat manager console
2) Access that web context.
3) Un-Deploy through the tomcat manager console (notice it does not
disappear in the list only gets stopped).
4) Try to redeploy - Message: FAIL - Application already exists at path
/mss-portal
5) Try to undeploy again. - Message: FAIL - Encountered exception
LifecycleException: Manager has not yet been started
I need help if there is a work around please let me know...
As I have said below I have tried the locking flags on context.
ACARBONE
-Original Message-
From: Carbone, Adam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 9:11 AM
To: 'Tomcat Developers List'
Subject: RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
Yes,
It is a windows issue with locking... :'( but it was not something
that existed in 5.0.28 it wasn't until I upgraded to 5.5.4 that I had it!
(regretting that now) I know that a lot was changed with the deployer in
between those versions, I believe it was re written completely. And
supposedly there were flags added to give the old behavior but I think there
is a bug with those flags! Because they don't do anything.
~adam
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:46 PM
To: Tomcat Developers List
Subject: RE: Bug??
Hi!
I remember one time my friend has same problem in windows. It was
because windows file system has lock directory, so it cannot be removed
until JVM process was shutdown.
I don't know any solution, i haven use windows in software development
in years now.. =))
Artsi
ti, 2004-12-28 kello 14:04 -0500, Carbone, Adam kirjoitti:
Has anyone else encountered this problem? I have heard several replies
like
well it only happens on windows so we are not going to worry about it well
a
lot of people use windows. As soon as I can I will no longer be using
windows but for now I'm stuck.
Case to reproduce
1) Deploy a jar through the tomcat manager console
2) Access that web context.
3) Un-Deploy through the tomcat manager console (notice it does not
disappear in the list only gets stopped).
4) Try to redeploy - Message: FAIL - Application already exists at path
/mss-portal
5) Try to undeploy again. - Message: FAIL - Encountered exception
LifecycleException: Manager has not yet been started
I need help if there is a work around please let me know...
As I have said below I have tried the locking flags on context.
ACARBONE
-Original Message-
From: Carbone, Adam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 9:11 AM
To: 'Tomcat Developers List'
Subject: RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do
it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they
need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made
that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application
with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException:
Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe,
DO NOT REPLY [Bug 32865] New: - Host does not respect deployOnStartup setting when starting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32865. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32865 Summary: Host does not respect deployOnStartup setting when starting Product: Tomcat 5 Version: 5.5.6 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Apps are deployed on host start up whether deployOnStartup is set to true or false. Patch: Index: HostConfig.java === RCS file: /home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/HostConfig.java,v retrieving revision 1.51 diff -u -r1.51 HostConfig.java --- HostConfig.java 1 Dec 2004 11:06:22 - 1.51 +++ HostConfig.java 28 Dec 2004 19:59:17 - @@ -1101,7 +1101,8 @@ log.error(sm.getString(hostConfig.jmx.register, oname), e); } -deployApps(); +if (host.getDeployOnStartup()) +deployApps(); } -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32865] - Host does not respect deployOnStartup setting when starting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32865. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32865 --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 21:44 --- Created an attachment (id=13846) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13846action=view) patch to HostConfig -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32866] New: - Manager does not inherite the webapp distributable/ property
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32866. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32866 Summary: Manager does not inherite the webapp distributable/ property Product: Tomcat 5 Version: 5.0.30 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] There seems to be a slight inconsistency on the distributable/ implementation as it will throw a ISE only if the manager is set to distributable=true. The manager will NOT inherit the webapp distributable property. The documentation looks fairly consistent with my interpretation of the Servlet 2.4 specification (7.7.2), the Tomcat documentation states about the Manager distributable property that: --- Set to true to ask the session manager to enforce the restrictions described in the Servlet Specification on distributable applications (primarily, this would mean that all session attributes must implement java.io.Serializable). Set to false (the default) to not enforce these restrictions. NOTE - The value for this property is inherited automatically based on the presence or absence of the distributable element in the web application deployment descriptor (/WEB-INF/web.xml). --- Looking at the source code, it is clear to me that this is not the case as the Manager setDistributable property is only set when parsing the server.xml (or context that is) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32867] New: - context distributable property is not modified during reloading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32867. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32867 Summary: context distributable property is not modified during reloading Product: Tomcat 5 Version: 5.0.30 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The digester rule only set the distributable property to true when the distributable/ element exists in the application. This is not a big problem but unfortunately, as the context instance is recycled, if you remove the distributable/ property, the context will still hold the previous value (ie the context set as distributable) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] Host does not respect deployOnStartup setting when starting up
Index: HostConfig.java === RCS file: /home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catali na/startup/HostConfig.java,v retrieving revision 1.51 diff -u -r1.51 HostConfig.java --- HostConfig.java 1 Dec 2004 11:06:22 - 1.51 +++ HostConfig.java 28 Dec 2004 19:59:17 - @@ -1101,7 +1101,8 @@ log.error(sm.getString(hostConfig.jmx.register, oname), e); } -deployApps(); +if (host.getDeployOnStartup()) +deployApps(); } Regards Tony BenBrahim
DO NOT REPLY [Bug 32865] - Host does not respect deployOnStartup setting when starting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32865. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32865 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 22:31 --- I removed this flag on purpose (obviously, it is useless). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32865] - Host does not respect deployOnStartup setting when starting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32865. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32865 --- Additional Comments From [EMAIL PROTECTED] 2004-12-28 22:59 --- I urge you to reconsider: 1) the flag is not removed, there is still a property deployOnStartup, settable in server.xml (sure in this case it may be useless) or settable on the MBean (in which case it is very useful, for fine grained control of which apps get deployed, and to configure the Contexts through JMX prior to deployment). It is also documented, and worked in 5.0.x, 4.x.x and prior. 2) the patch causes no harm, if someone does not set deployOnStartup, it is true by default. The patch just restores the previous documented functionality. 3) is there any reason for removing the flag, and why do you feel it is useless? I am trying to embed Tomcat using JMX, and the ignoring of the deployOnStartup flag is causing all kinds of problems. I need to set useNaming to false on the contexts, and since DefaultContext is gone, the only way I can see to do this is on the context themselves. I want to do this programmatically (through JMX), not trhough yet another xml file. Regards Tony BenBrahim -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32869] New: - DTD version in deployment descriptor ignored
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32869. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32869 Summary: DTD version in deployment descriptor ignored Product: Tomcat 5 Version: 5.0.30 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] In the deployment descriptor file webapps/app/WEB-INF/web.xml, the XML statement of DTD to be used is ignored without error or warning. Using this: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; ...is no different from using this: !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; The former has DTD tags listed for resource-env-ref, while the latter does not. Tomcat will always blindly accept the resource-env-ref tag, even when the DTD does not allow it (the 2.2 DTD does not allow this tag, but uses the tag without complaint). If a DTD version used is not supported, I would expect an error to be generated when trying to deploy the app. If a deprecated DTD is both listed and supported, I would perhaps expect a warning while still following the DTD. In all cases where a tag is not allowed according to the DTD, I would expect errors and not following of some other DTD without error or warning. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Removing Tomcat files in jakarta.apache.org/site
Anyone mind if I nuke: http://jakarta.apache.org/site/idedev-rdeclipse.html http://jakarta.apache.org/site/idedev-rdtomcat.html http://jakarta.apache.org/site/idedev-rdnetbeans.html They look like they're either dead, or long since have become a part of Tomcat's site. If they are still live, could they be migrated into Tomcat? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
