Re: asp file and session creation
Gunay, On 4/24/12 2:50 AM, gunay arslan wrote: > As a web application developer, I needed to stop creation vast amount > of "dummy" sessions, that is why I proposed this. I understand what you want. > I understand that specs are important and there are vast amount of > software that requires these spec to be applied to run. Good. > What I am proposing is , we can add a non-distructive variable with > default value working as the spec dictates. If anyone want to optimize > session creation they can change the value. There are many such > variables across the tomcat, that you can tweak. The only way I can think of to do this would be to add yet another wrapper around the HttpSession that may or may not be connected to a real session. But then, checks like this in a JSP: if(null == session) ...would suggest that the session actually exists while "session.getAttribute" may fail because the session isn't real. I suppose you could lazily-create the session at that point if you wanted, but I think most people would argue that this should be the responsibility of the web application. By the way, you can certainly build what I've described above as a fairly simple Filter. > My business is running on top of Tomcat, it is important for me to > have a better Tomcat, more reliable, more high-performance. Is Tomcat not reliable for you? It seems to work quite well for many of us. > BTW. send-replace method does not solve the problem > > a very common pattern in a jsp/jstl is > > created. No, a session should only be created for each client that arrives, not for every request (unless you have poorly-behaved clients that don't send HTTP cookies back to the server, or if you have a poorly-written webapp that does not properly rewrite URLs to include session identifiers). The basic idea here is that your page either does or does not require a session. If it doesn't require a session, then don't use a session, and set your JSP to session="false". If it does use a session, then state session="true" and go ahead and use the session. You can't really have it both ways unless you want to code your way around it. Note that anyone who reads your code will probably be surprised by this kind of customization, because it is certainly non-standard. > If I say session="false" then eve if there is a session available , > it is not transferred to the jsp You can always do this: HttpSession mySession = request.getSession(false); That will not create a session if it doesn't exist (and return null) or it will give you the existing session. > maybe a lighter solution will be putting > a session to page even when session="false" , in case there is an > existing session ? Again, your page either does or does not use sessions. You can't have it both ways. If you want to write a Filter to change that, you can do it quite easily. -chris signature.asc Description: OpenPGP digital signature
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) 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 gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 2 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-26042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-26042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-26042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-26042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-26042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-26042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-dae
Re: asp file and session creation
HI Christopher, The problem is not that the "poorly" configured browser or web application. When you have a web application open to the internet you can not guarantee that all of your clients will behave as you wish. Right now it is very easy to write a simple script and create too much sessions. one article on the subject: http://www.tomcatexpert.com/blog/2011/05/18/crawler-session-manager-valve for the last 12 years I am writing web applications. I know how to manage the session in the servlet or jsp . The point is that even in the very big projects there are people/developers that do not now exactly how the session lifecycle is working on the running web container. It would be nice if there are flags to helps the minimize the risks. The main point was that , if you did not specify the session attribute on the jsp , even if you do not use a session, every time for every request ( assuming the client does not send session cookie - as bots do in the article above ) a new session is created . Here I am not telling that we need to change the standards, I am suggesting to add a variable so for this session behavior, with default value running as it is right now, you need to check other lazy session creation change to value, restart the application. We will not dictate any thing, will not change anything. best regards. Gunay Arslan On Apr 26, 2012, at 5:07 PM, Christopher Schultz wrote: > Gunay, > > On 4/24/12 2:50 AM, gunay arslan wrote: >> As a web application developer, I needed to stop creation vast amount >> of "dummy" sessions, that is why I proposed this. > > I understand what you want. > >> I understand that specs are important and there are vast amount of >> software that requires these spec to be applied to run. > > Good. > >> What I am proposing is , we can add a non-distructive variable with >> default value working as the spec dictates. If anyone want to optimize >> session creation they can change the value. There are many such >> variables across the tomcat, that you can tweak. > > The only way I can think of to do this would be to add yet another > wrapper around the HttpSession that may or may not be connected to a > real session. But then, checks like this in a JSP: > > if(null == session) > > ...would suggest that the session actually exists while > "session.getAttribute" may fail because the session isn't real. I > suppose you could lazily-create the session at that point if you wanted, > but I think most people would argue that this should be the > responsibility of the web application. > > By the way, you can certainly build what I've described above as a > fairly simple Filter. > >> My business is running on top of Tomcat, it is important for me to >> have a better Tomcat, more reliable, more high-performance. > > Is Tomcat not reliable for you? It seems to work quite well for many of us. > >> BTW. send-replace method does not solve the problem >> >> a very common pattern in a jsp/jstl is >> >> > created. > > No, a session should only be created for each client that arrives, not > for every request (unless you have poorly-behaved clients that don't > send HTTP cookies back to the server, or if you have a poorly-written > webapp that does not properly rewrite URLs to include session identifiers). > > The basic idea here is that your page either does or does not require a > session. If it doesn't require a session, then don't use a session, and > set your JSP to session="false". If it does use a session, then state > session="true" and go ahead and use the session. You can't really have > it both ways unless you want to code your way around it. Note that > anyone who reads your code will probably be surprised by this kind of > customization, because it is certainly non-standard. > >> If I say session="false" then eve if there is a session available , >> it is not transferred to the jsp > > You can always do this: > > HttpSession mySession = request.getSession(false); > > That will not create a session if it doesn't exist (and return null) or > it will give you the existing session. > >> maybe a lighter solution will be putting >> a session to page even when session="false" , in case there is an >> existing session ? > > Again, your page either does or does not use sessions. You can't have it > both ways. If you want to write a Filter to change that, you can do it > quite easily. > > -chris >
Re: asp file and session creation
On 26/04/2012 19:54, gunay arslan wrote: > Here I am not telling that we need to change the standards, I am > suggesting to add a variable so for this session behavior, with > default value running as it is right now, you need to check other > lazy session creation change to value, restart the application. We > will not dictate any thing, will not change anything. Actually the problem here is folks that ask user questions on the dev list and then ignore the instruction to move the issue to the users list where they would find that they have already been given the answer as to how avoiding large numbers of sessions is already supported within the current specifications and several previous versions. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: asp file and session creation
Sorry Mark, I did not ignored moving the issue to the user list, I tried to reply on user list email, but because I am not subscribed to there my email failed (naturally), I do not want to subscribe to the list, as the volume of email is pretty high. I did not ask just question, I also send a code to solve a problem, maybe only me treated this as a problem. I just wanted to contribute back, right now my tomcat instances are running with modification code. Anyway if you think this as a garbage, just throw away. Sorry for taking your time, and sorry from the whole group for disturbing best regards. Gunay Arslan On Apr 26, 2012, at 10:00 PM, Mark Thomas wrote: > On 26/04/2012 19:54, gunay arslan wrote: >> Here I am not telling that we need to change the standards, I am >> suggesting to add a variable so for this session behavior, with >> default value running as it is right now, you need to check other >> lazy session creation change to value, restart the application. We >> will not dictate any thing, will not change anything. > > Actually the problem here is folks that ask user questions on the dev > list and then ignore the instruction to move the issue to the users list > where they would find that they have already been given the answer as to > how avoiding large numbers of sessions is already supported within the > current specifications and several previous versions. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Duplicate String values
All, I've been doing some memory profiling on my webapp to see where I can reduce our memory footprint a bit by combining equivalent objects. YourKit has some nice utilities to look for duplicate objects -- especially Strings. I can see that the string "java.lang.String" has lots of duplicates. Many of the ones I've inspected so far can be traced-back to catalina.mbeans.MBeanUtils and the registry of MBeans that it contains. Would anyone object to using String-interning to share copies of class names for MBeans? I could even restrict such interning to Strings that start with "java.lang" since those are probably the most-used ones, and those strings are probably already interned by all the RTTI infrastructure in the JVM anyway. -chris signature.asc Description: OpenPGP digital signature
Re: How to configure maxParameterCount
thank you. no further question. 在 2012年4月25日 下午6:37，Konstantin Kolinko 写道： > 2012/4/25 Zhi Xie : > > -- 已转发邮件 -- > > 发件人： Zhi Xie > > 日期： 2012年4月25日 下午5:58 > > 主题： How to configure maxParameterCount > > 收件人： users-h...@tomcat.apache.org > > > > > > > > Hi, is there anybody know how to customize the tomcat connecter's > > maxParameterCount. The default value is 1, too large for me. I need > to > > set it to 1000. > > How to configure it? > > > > That is a question for the users@ list. > > 1. read "Configuration reference" part of Documentation > 2. edit Connector attributes in server.xml > 3. restart Tomcat > > What is the problem? > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Best Regards Gary Apache Geronimo
DO NOT REPLY [Bug 53151] Tomcat 7 SimpleTCPCluster.java does not send payload on Start & Stop
https://issues.apache.org/bugzilla/show_bug.cgi?id=53151 Keiichi Fujino changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #2 from Keiichi Fujino 2012-04-27 04:20:25 UTC --- Life-cycle implementation was refactored in Tomcat7 . As the result, SimpleTcpCluster in Tomcat7 has inherited LifecycleBase and LifecycleBase notifies a life cycle event. Therefore, the upper code is unnecessary to the SimpleTcpCluster in Tomcat7. However, as the side effects of this refactoring, In Tomcat7.0, instance of SimpleTcpCluster is no longer set to the data field of LifecycleEvent. In Tomcat6, it was set as the second argument. Therefore, if your LifecycleListener used getData() method in order to get instance of SimpleTcpCluster, you must use getLifecycle() method instead of getData() method. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) 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 gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 20 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 28 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-27042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-27042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-27042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-27042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-27042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-27042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-27042012.jar:/srv/gump/ public/workspace/junit/dist/junit-27042012.jar - [junit] Apr 27, 2012 4:48:
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) 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 gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 23 mins 14 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-27042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-27042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-27042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-27042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-27042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-27042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-da
DO NOT REPLY [Bug 53151] Tomcat 7 SimpleTCPCluster.java does not send payload on Start & Stop
https://issues.apache.org/bugzilla/show_bug.cgi?id=53151 --- Comment #3 from Nilesh 2012-04-27 06:01:48 UTC --- Thanks Keiichi for the detailed reply. Appreciated! Thanks Nilesh -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-taglibs-standard (in module tomcat-taglibs) 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 gene...@gump.apache.org.
Project tomcat-taglibs-standard has an issue affecting its community
integration.
This issue affects 2 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:
- tomcat-taglibs-standard : Standard Taglib
- tomcat-taglibs-standard-install : JSP Taglibs
Full details are available at:
http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-INFO- Optional dependency httpunit failed with reason build failed
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/tomcat-taglibs/standard/pom.xml
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/gump_work/build_tomcat-taglibs_tomcat-taglibs-standard.html
Work Name: build_tomcat-taglibs_tomcat-taglibs-standard (Type: Build)
Work ended in a state of : Failed
Elapsed: 33 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
install
[Working Directory: /srv/gump/public/workspace/tomcat-taglibs/standard]
M2_HOME: /opt/maven2
-
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/srv/gump/public/workspace/tomcat-taglibs/standard/spec/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/srv/gump/public/workspace/tomcat-taglibs/standard/spec/target/taglibs-standard-spec-1.2-SNAPSHOT.jar
to
/srv/gump/public/workspace/mvnlocalrepo/shared/org/apache/taglibs/taglibs-standard-spec/1.2-SNAPSHOT/taglibs-standard-spec-1.2-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing
file:/srv/gump/public/workspace/mvnlocalrepo/shared/repository.xml
[INFO] Installing
org/apache/taglibs/taglibs-standard-spec/1.2-SNAPSHOT/taglibs-standard-spec-1.2-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building JSTL Implementation
[INFO]task-segment: [install]
[INFO]
[INFO] [remote-resources:process {execution: default}]
[INFO] snapshot org.apache.taglibs:taglibs-standard-spec:1.2-SNAPSHOT: checking
for updates from apache.snapshots
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'7407cf06385c8bc046b133abce041b9d396176be'; remote = '
' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'7407cf06385c8bc046b133abce041b9d396176be'; remote = '
' - IGNORING
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve dependencies for one or more projects in the reactor.
Reason: Unable to read local copy of metadata: Cannot read metadata from
'/srv/gump/public/workspace/mvnlocalrepo/shared/org/apache/taglibs/taglibs-standard-spec/1.2-SNAPSHOT/maven-metadata-apache.snapshots.xml':
end tag name must match start tag name from line 6 (position: TEXT
seen ...home page.\n... @8:5)
org.apache.taglibs:taglibs-standard-spec:jar:1.2-SNAPSHOT
Path to dependency:
1) org.apache.taglibs:taglibs-standard-impl:bundle:1.2-SNAPSHOT
2) org.apache.taglibs:taglibs-standard-spec:jar:1.2-SNAPSHOT
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 32 seconds
[INFO] Finished at: Fri Apr 27 06:56:10 UTC 2012
[INFO] Final Memory: 40M/97M
[INFO]
-
