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 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 10:24 --- Since I also had problems with relogin and the session data getting lost, and with JNLP files having no-cache settings under IE, I decided to leave the Tomcat authentication and write a security filter (doing both BASIC and FORM login). During development I noticed that even though Java Web Start can mimick a session (using ;jsessionid=), the load-the-jar routines work outside this connection and the downloads cause the authentication popup. So there indeed is no error in Tomcat and the solution should be searched in fine tuning the secured domain or convincing JWS to use the established session. -- 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 53 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-06032005/build/libtool --silent --mode=compile gcc -I/usr/local/gump/public/workspace/apache-httpd/dest-06032005/include -g -O2 -g -O2 -pthread -DHAVE_APR -I/usr/local/gump/public/workspace/apr/dest-06032005/include/apr-1 -g -O2 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/home/gump/workspaces2/public/workspace/apache-httpd/srclib/pcre -I /opt/jdk1.4/include -I /opt/jdk1.4/include/ -c jk_ajp12_worker.c /usr/local/gump/public/workspace/apache-httpd/dest-06032005/build/libtool: /usr/local/gump/public/workspace/apache-httpd/dest-06032005/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 2406032005, brutus:brutus-public:2406032005 Gump E-mail Identifier (unique within run) #9. -- 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 33869] New: - tomcat5 has classloading problems
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=33869. 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=33869 Summary: tomcat5 has classloading problems Product: Tomcat 5 Version: 5.0.28 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] when I try to deploy blojsom, or jetspeed, on tomcat-5.0.28, I get a strange error about not being able to find some log4j classes. It amounts to a classloader problem: http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/bin/catalina.sh?rev=1.19view=markup catalina.sh uses CLASSPATH=$CLASSPATH:$CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/commons-logging-api.jar which means that, due to classloaders, webapps using log4j won't be able to see it from the commons-logging-api classes. It happens to me with blojsom or jetspeed-2, tomcat-5.0.28 and IBM jdk 1.4.2 see: http://bugs.gentoo.org/show_bug.cgi?id=84206 It can be worked around by either adding log4j.jar to the classpath or removing commons-logging-api (I imagine that the second workaround would limit logging until the bootstrap process is completed. -- 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]
JDBC Realm exception
Hi, I was able to get my JDBC basic authentication realm working fine. I left my server running overnight (session would have timed out) and when I tried to access my resource this morning I was getting this. I'm still looking into it, but I can reproduce it and will post details soon. This is a major show stopper for me. Any thoughts guys? Thank you!! Darren PS. Uses MD5 password hashing. Like I said, it works but at some point starts throwing this exception (I think after session expire). Mar 6, 2005 10:04:33 AM org.apache.catalina.realm.JDBCRealm getPassword SEVERE: Exception retrieving password for architect java.sql.SQLException: Connection.close() has already been called. Invalid operation in this state. at com.mysql.jdbc.Connection.getMutex(Connection.java:2086) at com.mysql.jdbc.PreparedStatement.executeQuery PreparedStatement.java:1508) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10948] - JNDI lookup in servlet init fails
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=10948. 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=10948 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 20:00 --- As the comments above suggest and a quick test confirms, this does work as expected. -- 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 29777] - HttpServletRequest#getParameterNames problem
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=29777. 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=29777 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 22:08 --- Created an attachment (id=14418) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14418action=view) I had exact same code and same problem. But I got around by using for loop as displayed -- 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 29777] - HttpServletRequest#getParameterNames problem
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=29777. 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=29777 --- Additional Comments From [EMAIL PROTECTED] 2005-03-06 22:14 --- Created an attachment (id=14419) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14419action=view) But meanwhile I have same problem with loop of enumeration.hasMoreElements() from request.getAllAttributes() and I can see that enumeration.hasMoreElements() still true when there is no more. -- 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: JDBC Realm exception
Yep. It definitely hoses up when the session times out. In fact, the JDBC realm adaptor is blown for all valid user accounts in the RDBMS server, not just the session that timed out. Here is a slightly different but easily repeated exception. It may be within the MySQL driver, but I somehow doubt it. My 5.025 tomcat did not have this problem I believe. Only restarting Tomcat corrects this, but only until the session times out. Mar 6, 2005 5:48:25 PM org.apache.catalina.realm.JDBCRealm getPassword WARNING: Exception retrieving password for guest Mar 6, 2005 5:48:25 PM org.apache.catalina.connector.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.NullPointerException at com.mysql.jdbc.PreparedStatement.setString (PreparedStatement.java:1254) at org.apache.catalina.realm.JDBCRealm.credentials (JDBCRealm.java:497) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:525) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) On Sun, 2005-03-06 at 10:19 -0500, Darren Govoni wrote: Hi, I was able to get my JDBC basic authentication realm working fine. I left my server running overnight (session would have timed out) and when I tried to access my resource this morning I was getting this. I'm still looking into it, but I can reproduce it and will post details soon. This is a major show stopper for me. Any thoughts guys? Thank you!! Darren PS. Uses MD5 password hashing. Like I said, it works but at some point starts throwing this exception (I think after session expire). Mar 6, 2005 10:04:33 AM org.apache.catalina.realm.JDBCRealm getPassword SEVERE: Exception retrieving password for architect java.sql.SQLException: Connection.close() has already been called. Invalid operation in this state. at com.mysql.jdbc.Connection.getMutex(Connection.java:2086) at com.mysql.jdbc.PreparedStatement.executeQuery PreparedStatement.java:1508) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) - 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]
