Re: SSLv3/TLS man-in-middle vulnerability
Mark,
Since we do not know how to "switch connectors", or install OpenSSL, and do
not have JDK on the server (only JRE 1.6.0_17), then I suppose the best bet
is to wait until Tomcat is fixed ("coming soon").
Steve Johnson (619) 237-8315 P Please consider the environment before
printing this e-mail.
Mark Thomas
To
Tomcat Users List
01/18/2010 09:19
AM cc
Subject
Please respond to Re: SSLv3/TLS man-in-middle
"Tomcat Users vulnerability
List"
Caterpillar: Confidential Green Retain Until: 02/17/2010
On 18/01/2010 11:03, Steve G. Johnson wrote:
>
> We recently installed Tomcat 5.5.23 in Windows server to support the
Infor
> WebUI (webtop) application.
> We installed a cerificate and are using SSl on port 8443. This all works
> fine.
>
> The local IT Security team ran an HP "Web Inspect" and it showed a High
> vulnerability for SSLv3/TLS known as CVE-2009-3555.
> We are running JVM JRE 1.6.0._17 on the server.
> You state on the http://tomcat.apache.org/security-5.html site at end of
> page that this is not a vulnerability depending on a number of factors.
> This is very unclear tor us.
>
> The Web Inspect product sated that this must be fixed as follows:
> "
> Patches must be applied to the underlying web server and ssl library.
> OpenSSL Patch: http://www.openssl.org/source/openssl-0.9.8l.tar.gz
> Apache Mod-SSL Patch:
> http://www.apache.org/dist/httpd/patches/apply_to_2.2.14
> /CVE-2009-3555-2.2.patch
> These patches may cause issues with sites that require renegotiation.
> (Sites requiring public HTTPS access with certain folders
> protected by client-side certificates)
> "
>
> What can we do to make the vulnerability shown in Web Inspect go away?
You have a couple of options, depending on which connector you are using.
BIO & NIO connectors
- use JSSE for SSL
- JSSE is provided by the JDK
- a fix will require a fix the JDK - talk to your JDK vendor
- the next 6.0.x release (coming soon) will contain a workaround
APR/native connector
- uses OpenSSL for SSL
- OpenSSL is provided by the OpenSSL project
- a fix requires a fix in OpenSSL
- APR/native 1.1.19 includes a workaround for this issue
Right now, the quickest way to fix this is to switch to the APR/native
connector and use 1.1.19
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Connector 1.2.28 success and failure
2010/1/19 Michael Hahn : >>isapi_redirect.dll (failing): >>(..) >> log_file=C:\tomcat\isapi_redirect.log The above is different in the working file, log_file=C:\tomcat\logs\isapi_redirect.log > 2010-01-18 23:16:33 W3SVC1804915670 10.10.10.227 GET /servlets-examples/servlet/HelloWorldExample - 80 - 10.10.10.181 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+InfoPath.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 The above looks to me like a zero-length success (code 200) response. Why are you saying about 404? Is servlets-examples webapp deployed on the failing server? Is it running? Try accessing Tomcat directly through the HTTP connector to test that. Try looking at Tomcat Manager webapp (the URL is /manager/html and username with a role "manager" to access it is usually added to conf/tomcat-users.xml). Is the request reaching Tomcat? -- you can configure an AccessLogValve in Tomcat, see http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html The default server.xml file has an example of a configured AccessLogValve. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Connector 1.2.28 success and failure
It should be a mod_jk configuration issue. After compared your two configurations, I found two main differences: - extension_uri=/jakarta/isapi_redirect.dll + extentions_uri=/jakarta/isapi_redirect.dll extension_uri vs extensions_uri, right vs wrong - log_level=info + log_level=ALL The mod_jk document said log_level: A string value for log level (can be debug, info, warn, error or trace). "ALL" is not an acceptable value. So you can correct these and try again, hope it will work for you. Michael Hahn-7 wrote: > > The question, simply put, is we have no idea why we were able to get the > connector to work on one server (and only one server) and every other > server > we've tried has failed with 404 errors and no isapi_redirect.log files > being > generated. Even making the configuration identical to the working server > has > failed. I've triple checked the paths for the files, and several other > team > members have also done so. We've also checked the permissioning of the > file, > and made sure that IIS has access to it. We're not sure where to go from > here. The IIS log files are showing the following for requests: > > 2010-01-18 23:16:33 W3SVC1804915670 10.10.10.227 GET > /servlets-examples/servlet/HelloWorldExample - 80 - 10.10.10.181 > Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+InfoPath.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) > 200 0 0 > > On Mon, Jan 18, 2010 at 3:52 PM, Michael Hahn wrote: > >> Hello, we've been tasked with fowarding some requests to our IIS6 >> sharepoint server to tomcat 5.5 for use with SSO for other Tomcat based >> authentication. The SSO piece of the puzzle is working fine. However, the >> request forwarding we are having major problems with. >> >> We first installed Tomcat 5.5 and the Connecter 1.2.28 on a clean VMWare >> image running WSS 3.0. The connector worked flawlessly here, and the >> requests were forwarded appropriately, and the logs were generated. >> >> After the test run, we moved to our actual Sharepoint dev servers. We >> followed the same process to install the connector, as Tomcat itself was >> already installed, and then tweaked the configuration file to match the >> new >> environment. It came back with a 404 error for the contexts that should >> have >> been fowarded. We then attempted to make the two enviorments the same as >> far >> as Tomcat was concerned, moving the tomcat files from the location they >> were >> at on the working server. We then updated the configuration files to >> match >> the moved location of tomcat, as well as updating the Virtual Directory >> and >> ISAPI directory locations. After restarting both IIS and Tomcat, we were >> still given the same 404 error when accessing the forwarded contexts. We >> also tried a server restart at this point. After that failed, we tried >> making the configuration files identical to the ones from the working >> server, making sure that the contexts fowarded were the same (cutting the >> SSO servlet out of the picture). Still, it failed to work with the same >> symptoms. >> >> At this point, we decided to verify that the tomcat server installed >> could >> be accessed from the working server. We updated the configuration files >> on >> the clean box to forward to the dev server's IP address. Once that was >> done, >> we were able to forward requests to IIS on the clean box to the Tomcat >> instance on dev box. After this, we tried setting up the connector on >> several other dev boxes, and we were successful on none of them, using >> the >> identical configuration as the clean, working server. At this point, we >> started trying some more exotic solutions, including creating simple IIS >> websites without Sharepoint installed on the failing boxes, which >> produced >> the exact same failed result. >> >> We are using the properties file approach for the isapi_redirect.dll, >> rather than the registry. Below is the configuration from the only server >> that is working, as well as the configuration from one of the failing >> servers (as they are all identical). If anyone could give us a new place >> to >> look for the problem, we'd be appreciative, since without the log files, >> we're at a bit of a loss on where to go from here. >> >> isapi_redirect.dll (working): >> extension_uri=/jakarta/isapi_redirect.dll >> log_file=C:\tomcat\logs\isapi_redirect.log >> log_level=info >> worker_file=C:\tomcat\conf\workers.properties >> worker_mount_file=C:\tomcat\conf\uriworkermap.properties >> >> uriworkermap.properties (working): >> /admin/*=wlb >> /manager/*=wlb >> /servlets-examples/*=wlb >> /cas-server/*=wlb >> /jkmanager=jkstatus >> >> workers.properties (working): >> worker.list=wlb,jkstatus >> >> worker.ajp13w.type=ajp13 >> worker.ajp13w.host=localhost >> worker.ajp13w.port=8009 >> >> worker.wlb.type=lb >> worker.wlb.balance_w
Re: The code of method _jspService(...) is exceeding the 65535 byteslimit
2010/1/18 iainmac : > > Hi, > > I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me > this length error. > > I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18. > > I know I can rewrite the code, and over time I probably will, but is there a > way of configuring Tomcat 6 to enable me to compile these jsp's? > If you add the following option mappedfile false to the JspServlet declaration in conf/web.xml, the JSP engine will not generate separate write() command for each line of your JSP. Maybe that will allow you to postpone hitting the limit. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Getting 403 (Access Denied) when running Tomcat "under" Eclipse
Hi, AHH!! I was only looking through the Eclipse GUI settings, and hadn't noticed that under Servers-->Tomcat v5.5 in the Eclipse Project Explorer, there were catalina.policy, etc. files, including tomcat-users.xml :(... So, I added my role and user definitions to that tomcat-users.xml, and it worked!! I'm still a little puzzled though. In Eclipse Servers, there was also a web.xml, but I *did NOT* have to modify that web.xml, and it's picking up the web.xml from my webapp's WEB-INF\web.xml. Is that because the web.xml under Eclipse Servers is server-scoped, and so the web.xml in my webapp is overriding the Eclipse Servers web.xml? Thanks! Jim Ziggy wrote: > Doesnt eclipse use use a $CATALINA_BASE to run tomcat? I think the tomcat > instance on eclipse is not the same as the one on $CATALINA_HOME. Look at > the server project files under eclipse they will have their own > configuration files. > > On Mon, Jan 18, 2010 at 10:43 PM, wrote: > > > Hi, > > > > I have a web application that works when run directly under Tomcat. This > > web app has the following in web.xml: > > > > > > > >testweb > > accessible by authenticated users of the > > tomcat role > >/* > >GET > >POST > >PUT > >DELETE > > > > > >These roles are allowed access > >luceneuser > > > > > > > > > >BASIC > >Search > > > > > > > >Only 'tomcat' role is allowed to access this web > > application > >testuser > > > > > > However, when I run the webapp under Eclipse (i.e., do a "Run on server"), > > and attempt to login as the same user, with the same password, I get a 403 > > (Access denied) error. > > > > If I remove the constraint, it then works under Tomcat and Eclipse > > > > I've checked the Tomcat logs, and I don't see any info there. > > > > Can anyone tell me why this is happening?? > > > > Thanks, > > Jim > > > > P.S. Tomcat version is 5.5.2.8, under Windows. Eclipse is latest Galileo. > > > > - > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Connector 1.2.28 success and failure
The question, simply put, is we have no idea why we were able to get the connector to work on one server (and only one server) and every other server we've tried has failed with 404 errors and no isapi_redirect.log files being generated. Even making the configuration identical to the working server has failed. I've triple checked the paths for the files, and several other team members have also done so. We've also checked the permissioning of the file, and made sure that IIS has access to it. We're not sure where to go from here. The IIS log files are showing the following for requests: 2010-01-18 23:16:33 W3SVC1804915670 10.10.10.227 GET /servlets-examples/servlet/HelloWorldExample - 80 - 10.10.10.181 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Trident/4.0;+InfoPath.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 On Mon, Jan 18, 2010 at 3:52 PM, Michael Hahn wrote: > Hello, we've been tasked with fowarding some requests to our IIS6 > sharepoint server to tomcat 5.5 for use with SSO for other Tomcat based > authentication. The SSO piece of the puzzle is working fine. However, the > request forwarding we are having major problems with. > > We first installed Tomcat 5.5 and the Connecter 1.2.28 on a clean VMWare > image running WSS 3.0. The connector worked flawlessly here, and the > requests were forwarded appropriately, and the logs were generated. > > After the test run, we moved to our actual Sharepoint dev servers. We > followed the same process to install the connector, as Tomcat itself was > already installed, and then tweaked the configuration file to match the new > environment. It came back with a 404 error for the contexts that should have > been fowarded. We then attempted to make the two enviorments the same as far > as Tomcat was concerned, moving the tomcat files from the location they were > at on the working server. We then updated the configuration files to match > the moved location of tomcat, as well as updating the Virtual Directory and > ISAPI directory locations. After restarting both IIS and Tomcat, we were > still given the same 404 error when accessing the forwarded contexts. We > also tried a server restart at this point. After that failed, we tried > making the configuration files identical to the ones from the working > server, making sure that the contexts fowarded were the same (cutting the > SSO servlet out of the picture). Still, it failed to work with the same > symptoms. > > At this point, we decided to verify that the tomcat server installed could > be accessed from the working server. We updated the configuration files on > the clean box to forward to the dev server's IP address. Once that was done, > we were able to forward requests to IIS on the clean box to the Tomcat > instance on dev box. After this, we tried setting up the connector on > several other dev boxes, and we were successful on none of them, using the > identical configuration as the clean, working server. At this point, we > started trying some more exotic solutions, including creating simple IIS > websites without Sharepoint installed on the failing boxes, which produced > the exact same failed result. > > We are using the properties file approach for the isapi_redirect.dll, > rather than the registry. Below is the configuration from the only server > that is working, as well as the configuration from one of the failing > servers (as they are all identical). If anyone could give us a new place to > look for the problem, we'd be appreciative, since without the log files, > we're at a bit of a loss on where to go from here. > > isapi_redirect.dll (working): > extension_uri=/jakarta/isapi_redirect.dll > log_file=C:\tomcat\logs\isapi_redirect.log > log_level=info > worker_file=C:\tomcat\conf\workers.properties > worker_mount_file=C:\tomcat\conf\uriworkermap.properties > > uriworkermap.properties (working): > /admin/*=wlb > /manager/*=wlb > /servlets-examples/*=wlb > /cas-server/*=wlb > /jkmanager=jkstatus > > workers.properties (working): > worker.list=wlb,jkstatus > > worker.ajp13w.type=ajp13 > worker.ajp13w.host=localhost > worker.ajp13w.port=8009 > > worker.wlb.type=lb > worker.wlb.balance_workers=ajp13w > > worker.jkstatus.type=status > > isapi_redirect.dll (failing): > extentions_uri=/jakarta/isapi_redirect.dll > log_file=C:\tomcat\isapi_redirect.log > log_level=ALL > worker_file=C:\tomcat\conf\workers.properties > worker_mount_file=C:\tomcat\conf\uriworkermap.properties > > uriworkermap.properties (failing): > /cas-server=wlb > /cas-server/*=wlb > /mywebapp=wlb > /mywebapp/*=wlb > /servlets-examples/*=wlb > /jkstatus=jkstatus > > workers.properties (failing): > worker.list=wlb,jkstatus > > worker.ajp13w.type=ajp13 > worker.ajp13w.host=localhost > worker.ajp13w.port=8009 > > worker.wlb.type=lb > worker.wlb.balance_
Re: Log files? - [solved]
On Mon, 2010-01-18 at 10:14 -0500, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Rick,
>
> On 1/17/2010 11:16 AM, Rick Bragg wrote:
> > OK, I did
> > #apt-get install --reinstall tomcat6
> > And the log files are back!
> >
> > I'm definitely a newbe at this. The re-install kept my startup scripts
> > (and config files) all in tact. So this is a bit strange.
> >
> > Here are the changes I made in the /etc/init.d/tomcat6 file yesterday
> >
> > JDK_DIRS="/usr/lib/jvm/java-6-sun"
> >
> > if [ -z "$JAVA_OPTS" ]; then
> > JAVA_OPTS="-Djava.awt.headless=true -Xmx256M"
> > fi
>
> I suspect that, before your --reinstall, you had something broken in
> your /etc/init.d/tomcat6 script. Since you re-installed before posting
> back, we can't see what you did at the time.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEUEARECAAYFAktUeuYACgkQ9CaO5/Lv0PDJVQCfW+bYCBef2W4afNl8RdYcUkYE
> fNsAmNRJZ544rPUqyucTSH3FRg0Gx1k=
> =i0Ht
> -END PGP SIGNATURE-
>
I did allot of things really fast. Too fast. One thing I noticed is
that in /etc/default/tomcat6 I had the older openjdk set, At one point,
(before I did a reinstall,) I exported the sunjdk, and then when I did
the reinstall, it went back to the old openjdk and started logging
again... (but then it was using the wrong JDK!)
Ultimately, it was the suggestion from Konstantin that fixed the newer
sun jdk, but I had to be reminded of this by Chuck (on another mailing
list!)
Add the following line
permission java.lang.RuntimePermission "setContextClassLoader";
into the grant codeBase "file:
${catalina.home}/bin/tomcat-juli.jar" { .. }
block of catalina.policy file.
Thanks again everyone!
rick
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Getting 403 (Access Denied) when running Tomcat "under" Eclipse
Doesnt eclipse use use a $CATALINA_BASE to run tomcat? I think the tomcat instance on eclipse is not the same as the one on $CATALINA_HOME. Look at the server project files under eclipse they will have their own configuration files. On Mon, Jan 18, 2010 at 10:43 PM, wrote: > Hi, > > I have a web application that works when run directly under Tomcat. This > web app has the following in web.xml: > > > >testweb > accessible by authenticated users of the > tomcat role >/* >GET >POST >PUT >DELETE > > >These roles are allowed access >luceneuser > > > > >BASIC >Search > > > >Only 'tomcat' role is allowed to access this web > application >testuser > > > However, when I run the webapp under Eclipse (i.e., do a "Run on server"), > and attempt to login as the same user, with the same password, I get a 403 > (Access denied) error. > > If I remove the constraint, it then works under Tomcat and Eclipse > > I've checked the Tomcat logs, and I don't see any info there. > > Can anyone tell me why this is happening?? > > Thanks, > Jim > > P.S. Tomcat version is 5.5.2.8, under Windows. Eclipse is latest Galileo. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Getting 403 (Access Denied) when running Tomcat "under" Eclipse
Hi, I have a web application that works when run directly under Tomcat. This web app has the following in web.xml: testweb accessible by authenticated users of the tomcat role /* GET POST PUT DELETE These roles are allowed access luceneuser BASIC Search Only 'tomcat' role is allowed to access this web application testuser However, when I run the webapp under Eclipse (i.e., do a "Run on server"), and attempt to login as the same user, with the same password, I get a 403 (Access denied) error. If I remove the constraint, it then works under Tomcat and Eclipse I've checked the Tomcat logs, and I don't see any info there. Can anyone tell me why this is happening?? Thanks, Jim P.S. Tomcat version is 5.5.2.8, under Windows. Eclipse is latest Galileo. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Connector 1.2.28 success and failure
Nice letter, but what's the actual question? On 01/18/2010 10:52 PM, Michael Hahn wrote: Hello, we've been tasked with fowarding some requests to our IIS6 sharepoint Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Connector 1.2.28 success and failure
Hello, we've been tasked with fowarding some requests to our IIS6 sharepoint server to tomcat 5.5 for use with SSO for other Tomcat based authentication. The SSO piece of the puzzle is working fine. However, the request forwarding we are having major problems with. We first installed Tomcat 5.5 and the Connecter 1.2.28 on a clean VMWare image running WSS 3.0. The connector worked flawlessly here, and the requests were forwarded appropriately, and the logs were generated. After the test run, we moved to our actual Sharepoint dev servers. We followed the same process to install the connector, as Tomcat itself was already installed, and then tweaked the configuration file to match the new environment. It came back with a 404 error for the contexts that should have been fowarded. We then attempted to make the two enviorments the same as far as Tomcat was concerned, moving the tomcat files from the location they were at on the working server. We then updated the configuration files to match the moved location of tomcat, as well as updating the Virtual Directory and ISAPI directory locations. After restarting both IIS and Tomcat, we were still given the same 404 error when accessing the forwarded contexts. We also tried a server restart at this point. After that failed, we tried making the configuration files identical to the ones from the working server, making sure that the contexts fowarded were the same (cutting the SSO servlet out of the picture). Still, it failed to work with the same symptoms. At this point, we decided to verify that the tomcat server installed could be accessed from the working server. We updated the configuration files on the clean box to forward to the dev server's IP address. Once that was done, we were able to forward requests to IIS on the clean box to the Tomcat instance on dev box. After this, we tried setting up the connector on several other dev boxes, and we were successful on none of them, using the identical configuration as the clean, working server. At this point, we started trying some more exotic solutions, including creating simple IIS websites without Sharepoint installed on the failing boxes, which produced the exact same failed result. We are using the properties file approach for the isapi_redirect.dll, rather than the registry. Below is the configuration from the only server that is working, as well as the configuration from one of the failing servers (as they are all identical). If anyone could give us a new place to look for the problem, we'd be appreciative, since without the log files, we're at a bit of a loss on where to go from here. isapi_redirect.dll (working): extension_uri=/jakarta/isapi_redirect.dll log_file=C:\tomcat\logs\isapi_redirect.log log_level=info worker_file=C:\tomcat\conf\workers.properties worker_mount_file=C:\tomcat\conf\uriworkermap.properties uriworkermap.properties (working): /admin/*=wlb /manager/*=wlb /servlets-examples/*=wlb /cas-server/*=wlb /jkmanager=jkstatus workers.properties (working): worker.list=wlb,jkstatus worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8009 worker.wlb.type=lb worker.wlb.balance_workers=ajp13w worker.jkstatus.type=status isapi_redirect.dll (failing): extentions_uri=/jakarta/isapi_redirect.dll log_file=C:\tomcat\isapi_redirect.log log_level=ALL worker_file=C:\tomcat\conf\workers.properties worker_mount_file=C:\tomcat\conf\uriworkermap.properties uriworkermap.properties (failing): /cas-server=wlb /cas-server/*=wlb /mywebapp=wlb /mywebapp/*=wlb /servlets-examples/*=wlb /jkstatus=jkstatus workers.properties (failing): worker.list=wlb,jkstatus worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8009 worker.wlb.type=lb worker.wlb.balance_workers=ajp13w worker.jkstatus.type=status
RE: Tomcat crash dump on Windows
*** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. --- Begin Message --- Thanks Chris. I was pretty under the gun last week - so was a little lazy. Your link is quite helpful though. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, January 18, 2010 2:53 PM To: Tomcat Users List Subject: Re: Tomcat crash dump on Windows -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 1/18/2010 10:59 AM, Jeffrey Janner wrote: > Thanks Chris. Some useful info I can start looking at. > Yes, it looked like a normal shutdown to me also, all connectors stopped, etc. > The only issue was that I think I should have seen a 3rd servlet announce its > shutdown in the app log, and it wasn't there. I'm having the developers look > into that as the probable cause. > Unfortunately, a test instance starts/stops just fine all day long, so it's > not reproducible. > I'm not a developer myself, so I'm not fully versed on the available tools > for getting thread dumps, etc. > Is there a HowTo page for thread dumps or beginner's debugging guide > somewhere out there? Yep. I'm not sure why there are so many hits on Google for "tomcat thread dump" that aren't on the Tomcat site, but most of them only work in one environment or another. I'm a contributor to this Wiki page, which should help you in almost any case. If you can't get it working in your environment, let us know and we'll add another section to help. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktUyjgACgkQ9CaO5/Lv0PDZgQCeO7zhYhD3KYgFhQrnKlMbN0+S n9kAoL76PP/Y7O6YVnilVETztFqrMn0T =hgAG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --- End Message --- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat crash dump on Windows
*** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. --- Begin Message --- Doh! Why didn't I remember the "thread dump" option on the system tray monitor. Of course, I don't remember now whether it showed Tomcat as running or down. The services MMC showed "Stopping" and the tomcat5.exe was still running, but I can't remember what the status said in the system tray. Will do that next time. -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, January 18, 2010 2:53 PM To: Tomcat Users List Subject: Re: Tomcat crash dump on Windows -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 1/18/2010 10:59 AM, Jeffrey Janner wrote: > Thanks Chris. Some useful info I can start looking at. > Yes, it looked like a normal shutdown to me also, all connectors stopped, etc. > The only issue was that I think I should have seen a 3rd servlet announce its > shutdown in the app log, and it wasn't there. I'm having the developers look > into that as the probable cause. > Unfortunately, a test instance starts/stops just fine all day long, so it's > not reproducible. > I'm not a developer myself, so I'm not fully versed on the available tools > for getting thread dumps, etc. > Is there a HowTo page for thread dumps or beginner's debugging guide > somewhere out there? Yep. I'm not sure why there are so many hits on Google for "tomcat thread dump" that aren't on the Tomcat site, but most of them only work in one environment or another. I'm a contributor to this Wiki page, which should help you in almost any case. If you can't get it working in your environment, let us know and we'll add another section to help. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktUyjgACgkQ9CaO5/Lv0PDZgQCeO7zhYhD3KYgFhQrnKlMbN0+S n9kAoL76PP/Y7O6YVnilVETztFqrMn0T =hgAG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --- End Message --- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The code of method _jspService(...) is exceeding the 65535 byteslimit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain, On 1/18/2010 10:28 AM, iainmac wrote: > I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me > this length error. Unlikely. See below. > I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18. This is going to be the change that matters. > I know I can rewrite the code, and over time I probably will, but is there a > way of configuring Tomcat 6 to enable me to compile these jsp's? No. This is a Java language limit that you are reaching: code may not exceed 64k for a single method. Since JSPs compile into a single method, you must simply limit the amount of code in the whole JSP. This is one of the worst mal-features of JSP that exist IMO. :( Some options: 1. Use includes to split your pages 2. Move some portions of your code into methods declared within the JSP 3. Move some portions of your code into tag libaries 4. Don't put so much logic into JSPs :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktUy6UACgkQ9CaO5/Lv0PAC4ACeMZjuEhMJl25Box4mqbwnrWKX 4C4AoLy/z89rn6VPN+ICsdgKKrpfIS5T =Sqs4 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crash dump on Windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 1/18/2010 10:59 AM, Jeffrey Janner wrote: > Thanks Chris. Some useful info I can start looking at. > Yes, it looked like a normal shutdown to me also, all connectors stopped, etc. > The only issue was that I think I should have seen a 3rd servlet announce its > shutdown in the app log, and it wasn't there. I'm having the developers look > into that as the probable cause. > Unfortunately, a test instance starts/stops just fine all day long, so it's > not reproducible. > I'm not a developer myself, so I'm not fully versed on the available tools > for getting thread dumps, etc. > Is there a HowTo page for thread dumps or beginner's debugging guide > somewhere out there? Yep. I'm not sure why there are so many hits on Google for "tomcat thread dump" that aren't on the Tomcat site, but most of them only work in one environment or another. I'm a contributor to this Wiki page, which should help you in almost any case. If you can't get it working in your environment, let us know and we'll add another section to help. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktUyjgACgkQ9CaO5/Lv0PDZgQCeO7zhYhD3KYgFhQrnKlMbN0+S n9kAoL76PP/Y7O6YVnilVETztFqrMn0T =hgAG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSLv3/TLS man-in-middle vulnerability
On 01/18/2010 10:18 AM, Mark Thomas wrote: On 18/01/2010 11:03, Steve G. Johnson wrote: We recently installed Tomcat 5.5.23 in Windows server to support the Infor WebUI (webtop) application. We installed a cerificate and are using SSl on port 8443. This all works fine. The local IT Security team ran an HP "Web Inspect" and it showed a High vulnerability for SSLv3/TLS known as CVE-2009-3555. We are running JVM JRE 1.6.0._17 on the server. You state on the http://tomcat.apache.org/security-5.html site at end of page that this is not a vulnerability depending on a number of factors. This is very unclear tor us. The Web Inspect product sated that this must be fixed as follows: " Patches must be applied to the underlying web server and ssl library. OpenSSL Patch: http://www.openssl.org/source/openssl-0.9.8l.tar.gz Apache Mod-SSL Patch: http://www.apache.org/dist/httpd/patches/apply_to_2.2.14 /CVE-2009-3555-2.2.patch These patches may cause issues with sites that require renegotiation. (Sites requiring public HTTPS access with certain folders protected by client-side certificates) " What can we do to make the vulnerability shown in Web Inspect go away? You have a couple of options, depending on which connector you are using. BIO& NIO connectors - use JSSE for SSL - JSSE is provided by the JDK - a fix will require a fix the JDK - talk to your JDK vendor - the next 6.0.x release (coming soon) will contain a workaround NIO doesn't allow handshakes and is not vulnerable. Instead it will time out the request So if using Tomcat 6, then NIO is a work around Filip APR/native connector - uses OpenSSL for SSL - OpenSSL is provided by the OpenSSL project - a fix requires a fix in OpenSSL - APR/native 1.1.19 includes a workaround for this issue Right now, the quickest way to fix this is to switch to the APR/native connector and use 1.1.19 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSLv3/TLS man-in-middle vulnerability
On 18/01/2010 11:37, Jens Neu wrote: > Steve, > > it is not a vulnerability of Tomcat, nevertheless it can be fixed by it. > You definitely _should_ fix it, since data integrity can not be assured on > your https connections any more. > > I have little to no Windows experienc; but my understanding is, that while > running Tomcat on Windows Server, it will make use of the SSL/TLS > libraries provided by Windows. Means: the Openssl solution will not work > your your. > You would have to wait until MS provides a patch (some Windows guy should > correct me on this if I'm mistaken). You are mistaken. BIO & NIO use JSSE from the JDK. APR/native does use OpenSSL. > Meanwhile you should investigate if you can fix it by clever choosing the > Tomcat Connector; maybe some Windows- Tomcat Expert jumps on it :) See my other reply on this thread for details. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSLv3/TLS man-in-middle vulnerability
On 18/01/2010 11:03, Steve G. Johnson wrote: > > We recently installed Tomcat 5.5.23 in Windows server to support the Infor > WebUI (webtop) application. > We installed a cerificate and are using SSl on port 8443. This all works > fine. > > The local IT Security team ran an HP "Web Inspect" and it showed a High > vulnerability for SSLv3/TLS known as CVE-2009-3555. > We are running JVM JRE 1.6.0._17 on the server. > You state on the http://tomcat.apache.org/security-5.html site at end of > page that this is not a vulnerability depending on a number of factors. > This is very unclear tor us. > > The Web Inspect product sated that this must be fixed as follows: > " > Patches must be applied to the underlying web server and ssl library. > OpenSSL Patch: http://www.openssl.org/source/openssl-0.9.8l.tar.gz > Apache Mod-SSL Patch: > http://www.apache.org/dist/httpd/patches/apply_to_2.2.14 > /CVE-2009-3555-2.2.patch > These patches may cause issues with sites that require renegotiation. > (Sites requiring public HTTPS access with certain folders > protected by client-side certificates) > " > > What can we do to make the vulnerability shown in Web Inspect go away? You have a couple of options, depending on which connector you are using. BIO & NIO connectors - use JSSE for SSL - JSSE is provided by the JDK - a fix will require a fix the JDK - talk to your JDK vendor - the next 6.0.x release (coming soon) will contain a workaround APR/native connector - uses OpenSSL for SSL - OpenSSL is provided by the OpenSSL project - a fix requires a fix in OpenSSL - APR/native 1.1.19 includes a workaround for this issue Right now, the quickest way to fix this is to switch to the APR/native connector and use 1.1.19 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSLv3/TLS man-in-middle vulnerability
Steve, it is not a vulnerability of Tomcat, nevertheless it can be fixed by it. You definitely _should_ fix it, since data integrity can not be assured on your https connections any more. I have little to no Windows experienc; but my understanding is, that while running Tomcat on Windows Server, it will make use of the SSL/TLS libraries provided by Windows. Means: the Openssl solution will not work your your. You would have to wait until MS provides a patch (some Windows guy should correct me on this if I'm mistaken). Meanwhile you should investigate if you can fix it by clever choosing the Tomcat Connector; maybe some Windows- Tomcat Expert jumps on it :) regards Jens Neu Health Services Network Administration Phone: +49 (0) 30 68905-2412 Mail: jens@biotronik.de "Steve G. Johnson" 01/18/2010 05:04 PM Please respond to "Tomcat Users List" To Tomcat Users List cc Subject SSLv3/TLS man-in-middle vulnerability The local IT Security team ran an HP "Web Inspect" and it showed a High vulnerability for SSLv3/TLS known as CVE-2009-3555. We are running JVM JRE 1.6.0._17 on the server. You state on the http://tomcat.apache.org/security-5.html site at end of page that this is not a vulnerability depending on a number of factors. This is very unclear tor us. www.biotronik.com BIOTRONIK SE & Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementärin: BIOTRONIK MT SE Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B Vorsitzender des Verwaltungsrats: Dr. Max Schaldach Geschäftsführende Direktoren: Christoph Böhmer, Dr. Werner Braun, Dr. Lothar Krings BIOTRONIK - A global manufacturer of advanced Cardiac Rhythm Management systems and Vascular Intervention devices. Quality, innovation, and reliability define BIOTRONIK and our growing success. We are innovators of technologies like the first wireless remote monitoring system - Home Monitoring®, Closed Loop Stimulation and coveted lead solutions as well as state-of-the-art stents, balloons and guide wires for coronary and peripheral indications. We highly invest in the development of drug eluting devices and are leading the industry with our bioabsorbable metal stent program. This e-mail and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this e-mail, please notify the sender immediately and delete the document.
Comet Connection Writeable?
Hi I am using comet connections for some time now in a server push manner: Whenever the server needs to inform the client about some event, it sends a packet to the client and waits for a reply in the same connection. As soon, as a READ event is triggered, that reply is read and the next message can be sent. Now, this requires a round-trip-time between the client and the server and is inappropriate for larger amounts of data especially on high latency connections. I am seeking for a way to determine (from a comet servlets point of view) if a connection is writeable - this is, if output buffers are empty and I can send additional data. Note, that sending a huge amount of data at once is not an option, I need to send distinct parts... So here are my questions: - How can I detect if a connection is writeable? - That is, how can I detect if the output buffers are empty? - Is there a way to use comet connection for something like a selector? Regards, Steffen smime.p7s Description: S/MIME cryptographic signature
SSLv3/TLS man-in-middle vulnerability
We recently installed Tomcat 5.5.23 in Windows server to support the Infor WebUI (webtop) application. We installed a cerificate and are using SSl on port 8443. This all works fine. The local IT Security team ran an HP "Web Inspect" and it showed a High vulnerability for SSLv3/TLS known as CVE-2009-3555. We are running JVM JRE 1.6.0._17 on the server. You state on the http://tomcat.apache.org/security-5.html site at end of page that this is not a vulnerability depending on a number of factors. This is very unclear tor us. The Web Inspect product sated that this must be fixed as follows: " Patches must be applied to the underlying web server and ssl library. OpenSSL Patch: http://www.openssl.org/source/openssl-0.9.8l.tar.gz Apache Mod-SSL Patch: http://www.apache.org/dist/httpd/patches/apply_to_2.2.14 /CVE-2009-3555-2.2.patch These patches may cause issues with sites that require renegotiation. (Sites requiring public HTTPS access with certain folders protected by client-side certificates) " What can we do to make the vulnerability shown in Web Inspect go away? Thanks. Steve Johnson (619) 237-8315 P Please consider the environment before printing this e-mail. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat crash dump on Windows
*** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. --- Begin Message --- Thanks Chris. Some useful info I can start looking at. Yes, it looked like a normal shutdown to me also, all connectors stopped, etc. The only issue was that I think I should have seen a 3rd servlet announce its shutdown in the app log, and it wasn't there. I'm having the developers look into that as the probable cause. Unfortunately, a test instance starts/stops just fine all day long, so it's not reproducible. I'm not a developer myself, so I'm not fully versed on the available tools for getting thread dumps, etc. Is there a HowTo page for thread dumps or beginner's debugging guide somewhere out there? Jeff -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Friday, January 15, 2010 9:39 AM To: Tomcat Users List Subject: Re: Tomcat crash dump on Windows -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey, On 1/15/2010 10:21 AM, Jeffrey Janner wrote: > Is there any procedure for generating a memory dump for Tomcat running > as a Windows service when the service dies and hangs? Yes: you want to set one (or more) of the following JVM flags: - -XX:-HeapDumpOnOutOfMemoryError - -XX:OnOutOfMemoryError="; " - -XX:OnError=";" I'm not sure if you can set "jstack" as the program to run on OOME or other error... it depends on the current state of the JVM. A full list of options can be found here: http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp > We had a > production instance stop responding last night and then it refused to > stop when the operator tried to shut it down using the services control > panel. We had to use task manager to kill it. It started up just fine. > > The log showed stopping messages for 2 out of the 3 servelts, so I'm > guessing the problem is with the unresponsive servlet, but a memory dump > would be helpful in determining cause. You could try traditional thread and/or heap dump techniques before killing the process. Does that work? I guess you'll have to wait for another fatal error. > Some good links to some helpful information is all I'm really looking > for. > > > > Also, can anyone shed some light on what the following INFO message > means from the catalina log: >Jan 14, 2010 4:58:35 PM org.apache.catalina.core.StandardWrapper > unload > >INFO: Waiting for 13 instance(s) to be deallocated > > Is that just the number of sessions active? Or something else I should > look into? StandardWrapper wraps a lot of things. I've never seen this message myself, but others have reported this message. It shouldn't be a problem (notice it's an INFO, not a WARN or ERROR or anything like that). > > > > Here is the full catalina log from the shutdown. It looks normal to me > except for the INFO statements, and the fact that the service never > actually stopped. > > Jan 14, 2010 4:58:34 PM org.apache.coyote.http11.Http11AprProtocol pause > > INFO: Pausing Coyote HTTP/1.1 on http-172.16.5.1-80 > > Jan 14, 2010 4:58:34 PM org.apache.coyote.http11.Http11AprProtocol pause > > INFO: Pausing Coyote HTTP/1.1 on http-172.16.5.1-443 > > Jan 14, 2010 4:58:35 PM org.apache.catalina.core.StandardService stop > > INFO: Stopping service GE > > Jan 14, 2010 4:58:35 PM org.apache.catalina.core.StandardWrapper unload > > INFO: Waiting for 13 instance(s) to be deallocated > > Jan 14, 2010 4:58:36 PM org.apache.catalina.core.StandardWrapper unload > > INFO: Waiting for 13 instance(s) to be deallocated > > Jan 14, 2010 4:58:37 PM org.apache.catalina.core.StandardWrapper unload > > INFO: Waiting for 13 instance(s) to be deallocated > > Jan 14, 2010 4:58:38 PM org.apache.coyote.http11.Http11AprProtocol > destroy > > INFO: Stopping Coyote HTTP/1.1 on http-172.16.5.1-80 > > Jan 14, 2010 4:58:38 PM org.apache.coyote.http11.Http11AprProtocol > destroy > > INFO: Stopping Coyote HTTP/1.1 on http-172.16.5.1-443 This looks like a standard shutdown to me. How many s do you have defined? I suspect that your webapp is launching a thread that is not set as daemon=true. When you shutdown Tomcat, it doesn't call System.exit(). Instead, if shuts down all its threads and then exits its main() method. After that, the JVM should shut down because no other threads are
Re: Log files? - [solved]
On 17/01/2010 16:08, Peter Crowther wrote: > 2010/1/17 Hassan Schroeder : >> You're welcome to your opinion, but personally I think the whole >> splatter-files-all-over-the-system repackaging approach is horribly >> flawed for apps like Tomcat > [...] > > Tomcat has a very strong view on where its files should live. > Some OSs have very strong views on where particular kinds of files should > live. > The two views are at odds. > > There are three ways of dealing with this: > Neither OS nor Tomcat teams do anything (leaving users and > re-packagers to deal with the mess). > OS teams become more flexible over file placement. > Tomcat team becomes more flexible over file placement. > > I suspect - without proof - that adding in that flexibility to Tomcat > using a well-defined configuration file would take less of the > committers' time than the time that is consumed debugging problems > with repackaged Tomcats now. The reason that the OS packages can put files 'all over the place' is that Tomcat is already pretty flexible about where the configuration files can be placed. It should simple be a case of find the script that starts Tomcat, see what server.xml and logging.properties file is being used and away you go. Concrete suggestions on how to make this easier (info messages in logs, info in manager app, etc) welcome. Concrete suggestions with patches are even better. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Cyclos Webapp Trouble (404) [solved]
On Mon, 2010-01-18 at 09:02 -0600, Caldarale, Charles R wrote: > > From: Rick Bragg [mailto:li...@gmnet.net] > > Subject: Re: Cyclos Webapp Trouble (404) > > > > Yes the above works perfect. I can log into MySQL in exactly that way. > > I also double checked the password. > > Just for grins, do a netstat -ano and verify that the MySQL pid really is > listening on 127.0.0.1:3306 (or 0.0.0.0:3306) and not some other IP address. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. That did it! changing my.cnf bind-address= 0.0.0.0 did the trick. OK, Now I will go pick up trash on the roadside for a while! Thanks all! Rick - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The code of method _jspService(...) is exceeding the 65535 byteslimit
Hi, I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me this length error. I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18. I know I can rewrite the code, and over time I probably will, but is there a way of configuring Tomcat 6 to enable me to compile these jsp's? Thanks, Iain Peter Hubbard wrote: > > On Fri, 2006-05-12 at 14:02 +0200, lk wrote: >> Hi, >> >> I got this bad error. >> >> Is there a way to solve this problem (maybe in the configurations file)? >> >> Thanks > > This simply means you have way too much jsp code in one file. > > Maybe you could split them up, or remove some of the functionality from > the jsp itself into helper classes. > > As far as I know, it is a limit placed on method size by the JVM - I'm > not sure if it can be changed. > > > -- > Peter Hubbard > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://old.nabble.com/The-code-of-method-_jspService%28...%29-is-exceeding-the-65535-byteslimit-tp4356835p27212087.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 1/18/2010 10:02 AM, Caldarale, Charles R wrote: >> From: Rick Bragg [mailto:li...@gmnet.net] >> Subject: Re: Cyclos Webapp Trouble (404) >> >> Yes the above works perfect. I can log into MySQL in exactly that way. >> I also double checked the password. > > Just for grins, do a netstat -ano and verify that the MySQL pid > really is listening on 127.0.0.1:3306 (or 0.0.0.0:3306) and not some > other IP address. +1 Depending on your version of MySQL (can't find what version you are running in the old posts... so many posts!), you may have to enable TCP/IP-based communication. If you are using PHP and Perl to connect to MySQL, they may be using the named pipe that MySQL used to use for localhost communication. Even using, as David suggests: mysql -P 3306 -h localhost -u cyclos -p ...the MySQL command-line program uses the named pipe because "localhost" is treated specially by that program. Try using "127.0.0.1" instead of "localhost" and verify that it works. If not, edit your /etc/mysql/my.cnf and make sure that "skip-networking" is not set to "true". - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktUfagACgkQ9CaO5/Lv0PDFAgCgr4lt4K/8IO/zb18KUigCrmuS wKQAn2pDHtP82T/T7UtKIQF0uXLi4PCx =1RNn -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Cyclos Webapp Trouble (404)
On Mon, 2010-01-18 at 09:02 -0600, Caldarale, Charles R wrote: > > From: Rick Bragg [mailto:li...@gmnet.net] > > Subject: Re: Cyclos Webapp Trouble (404) > > > > Yes the above works perfect. I can log into MySQL in exactly that way. > > I also double checked the password. > > Just for grins, do a netstat -ano and verify that the MySQL pid really is > listening on 127.0.0.1:3306 (or 0.0.0.0:3306) and not some other IP address. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > AHH, It is on one of my public IP's for some reason. I've got some db-admin to do. I have to ask around to find out why this was changed, and try everything out later. If this works, I will have some "community service" work to do for sure! Thanks! Rick - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Stack Trace debug to screen
Thanks, I read that but its not clear at all. I added java.util.logging.ConsoleHandler.useParentHandler = true but has not made a difference. Apache Tomcat 6.0.20 on XP. I have it working by now by deleting the loggers other than: handlers = 1catalina.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler as my apps have their own logging . This now enables me to see the exceptions in the console and they are in catalina.log - ideally I would also like to have them in my apps logs too, I use log4j so I am sure it is possible but I just don't have time to get that deeply into it. Thanks for getting me this far. Konstantin Kolinko wrote: > > 2010/1/18 iainmac : >> >> Hi, >> >> I am upgrading from Tomcat 5 to 6. >> >> When developing I run Tomcat from the command line so I can see the debug >> as >> it happens, but with Tomcat 6 I can see the debug that I have coded but >> when >> there is a Tomcat exception, it doesn't appear in the command line window >> any more although it is in the logs. e.g. >> >> >> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) >> >> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) >> >> org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:439) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:312) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:299) >> >> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586) >> >> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317) >> >> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) >> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >> >> org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:738) >> >> appears in the log, and in the browser but not in the debug in the >> command >> line window I have open. I am searching for the reason, but if any one >> knows what I need to do please let me know. Thanks. > > That message is logged by 2localhost.org.apache.juli.FileHandler (or > what the name of that log file is?) and does not reach the > ConsoleHandler that prints messages to the console. > > See > http://tomcat.apache.org/tomcat-6.0-doc/logging.html > > There is the following phrase: > "By default, loggers will not delegate to their parent if they have > associated handlers. This may be changed per logger using the > loggerName.useParentHandlers property, which accepts a boolean value." > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://old.nabble.com/Stack-Trace-debug-to-screen-tp27210579p27211979.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Log files? - [solved]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rick, On 1/17/2010 11:16 AM, Rick Bragg wrote: > OK, I did > #apt-get install --reinstall tomcat6 > And the log files are back! > > I'm definitely a newbe at this. The re-install kept my startup scripts > (and config files) all in tact. So this is a bit strange. > > Here are the changes I made in the /etc/init.d/tomcat6 file yesterday > > JDK_DIRS="/usr/lib/jvm/java-6-sun" > > if [ -z "$JAVA_OPTS" ]; then > JAVA_OPTS="-Djava.awt.headless=true -Xmx256M" > fi I suspect that, before your --reinstall, you had something broken in your /etc/init.d/tomcat6 script. Since you re-installed before posting back, we can't see what you did at the time. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAktUeuYACgkQ9CaO5/Lv0PDJVQCfW+bYCBef2W4afNl8RdYcUkYE fNsAmNRJZ544rPUqyucTSH3FRg0Gx1k= =i0Ht -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
18.01.2010 15:57, Rick Bragg: > On Mon, 2010-01-18 at 09:43 -0500, David Smith wrote: >> MySQL leave the tcp port disabled for security reasons. I've never >> understood the decision, but it happens. You can test w/ the mysql command: >> >> mysql -P 3306 -h localhost -u cyclos -p > Yes the above works perfect. I can log into MySQL in exactly that way. > I also double checked the password. And it still works, if you replace "localhost" with "127.0.0.1" (since that's what you configured)? I. e. mysql -P 3306 -h 127.0.0.1 -u cyclos -p -- Regards mks - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Cyclos Webapp Trouble (404)
> From: Rick Bragg [mailto:li...@gmnet.net] > Subject: Re: Cyclos Webapp Trouble (404) > > Yes the above works perfect. I can log into MySQL in exactly that way. > I also double checked the password. Just for grins, do a netstat -ano and verify that the MySQL pid really is listening on 127.0.0.1:3306 (or 0.0.0.0:3306) and not some other IP address. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Cyclos Webapp Trouble (404)
On Mon, 2010-01-18 at 09:43 -0500, David Smith wrote: > Rick Bragg wrote: > > On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote: > > > >>> From: Rick Bragg [mailto:li...@gmnet.net] > >>> Subject: RE: Cyclos Webapp Trouble (404) > >>> > >>> Yes I notices that as well, I forgot to post my cyclos.properies Here > >>> is the "mysql" section... > >>> > >>> hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos > >>> > >> The above doesn't jibe with the error message displayed at runtime: > >> > >> jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8 > >> > >> Note the use of "localhost" instead of "127.0.0.1", the lack of explicit > >> port number, and the database name. > >> > >> What you posted is not what you're actually running with. > >> > >> - Chuck > >> > >> > >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > >> MATERIAL and is thus for use only by the intended recipient. If you > >> received this in error, please contact the sender and delete the e-mail > >> and its attachments from all computers. > >> > > > > > > Sorry, that must have been one of my "variations"... > > > > To be clear, here are the files as of now. > > > > cyclos.properties (MySQL section) > > ### MySQL > > hibernate.dialect = org.hibernate.dialect.MySQLInnoDBDialect > > hibernate.connection.driver_class = com.mysql.jdbc.Driver > > hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos > > hibernate.connection.username = cyclos > > hibernate.connection.password = > > ### Connection provider properties > > hibernate.connection.provider_class = > > org.hibernate.connection.C3P0ConnectionProvider > > hibernate.c3p0.minPoolSize = 1 > > hibernate.c3p0.maxPoolSize = 100 > > hibernate.c3p0.acquireIncrement = 1 > > hibernate.c3p0.maxIdleTime = 21600 > > hibernate.c3p0.testConnectionOnCheckout = true > > hibernate.c3p0.preferredTestQuery = select 1 > > hibernate.c3p0.acquireRetryAttempts = 5 > > hibernate.c3p0.numHelperThreads = 3 > > > > > > and error log: > > > > Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log > > INFO: SessionListener: contextDestroyed() > > Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log > > INFO: ContextListener: contextDestroyed() > > Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log > > INFO: ContextListener: contextInitialized() > > Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log > > INFO: SessionListener: contextInitialized() > > Jan 18, 2010 8:22:51 AM org.apache.catalina.core.ApplicationContext log > > INFO: Initializing Spring root WebApplicationContext > > Jan 18, 2010 8:22:56 AM org.apache.catalina.core.StandardContext > > listenerStart > > SEVERE: Exception sending context initialized event to listener instance of > > class org.springframework.web.context.ContextLoaderListener > > org.springframework.beans.factory.BeanCreationException: Error creating > > bean with name 'sessionFactory' defined in class path resource > > [nl/strohalm/cyclos/spring/persistence.xml]: Invocation of init method > > failed; nested exception is java.lang.RuntimeException: Error connecting to > > database at > > jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 > > Caused by: java.lang.RuntimeException: Error connecting to database at > > jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 > >at > > nl.strohalm.cyclos.setup.DataBaseConfiguration.validateConnection(DataBaseConfiguration.java:342) > >at > > nl.strohalm.cyclos.setup.DataBaseConfiguration.run(DataBaseConfiguration.java:107) > >at > > nl.strohalm.cyclos.spring.CustomSessionFactoryBean.newSessionFactory(CustomSessionFactoryBean.java:42) > >at > > org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745) > > ... > > Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: > > Communications link failure > > ... > > Last packet sent to the server was 0 ms ago. > >at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > >at > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > >at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > >at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > >at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) > >at > > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) > >at com.mysql.jdbc.MysqlIO.(MysqlIO.java:335) > >at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2043) > >... 56 more > > Caused by: java.net.ConnectException: Connection refused > >at java.net.PlainSocketImpl.socketConnect(Native Method) > >at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > >at java.net.PlainSocket
Re: Cyclos Webapp Trouble (404)
Rick Bragg wrote: > On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote: > >>> From: Rick Bragg [mailto:li...@gmnet.net] >>> Subject: RE: Cyclos Webapp Trouble (404) >>> >>> Yes I notices that as well, I forgot to post my cyclos.properies Here >>> is the "mysql" section... >>> >>> hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos >>> >> The above doesn't jibe with the error message displayed at runtime: >> >> jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8 >> >> Note the use of "localhost" instead of "127.0.0.1", the lack of explicit >> port number, and the database name. >> >> What you posted is not what you're actually running with. >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you received >> this in error, please contact the sender and delete the e-mail and its >> attachments from all computers. >> > > > Sorry, that must have been one of my "variations"... > > To be clear, here are the files as of now. > > cyclos.properties (MySQL section) > ### MySQL > hibernate.dialect = org.hibernate.dialect.MySQLInnoDBDialect > hibernate.connection.driver_class = com.mysql.jdbc.Driver > hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos > hibernate.connection.username = cyclos > hibernate.connection.password = > ### Connection provider properties > hibernate.connection.provider_class = > org.hibernate.connection.C3P0ConnectionProvider > hibernate.c3p0.minPoolSize = 1 > hibernate.c3p0.maxPoolSize = 100 > hibernate.c3p0.acquireIncrement = 1 > hibernate.c3p0.maxIdleTime = 21600 > hibernate.c3p0.testConnectionOnCheckout = true > hibernate.c3p0.preferredTestQuery = select 1 > hibernate.c3p0.acquireRetryAttempts = 5 > hibernate.c3p0.numHelperThreads = 3 > > > and error log: > > Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log > INFO: SessionListener: contextDestroyed() > Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log > INFO: ContextListener: contextDestroyed() > Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log > INFO: ContextListener: contextInitialized() > Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log > INFO: SessionListener: contextInitialized() > Jan 18, 2010 8:22:51 AM org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > Jan 18, 2010 8:22:56 AM org.apache.catalina.core.StandardContext listenerStart > SEVERE: Exception sending context initialized event to listener instance of > class org.springframework.web.context.ContextLoaderListener > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'sessionFactory' defined in class path resource > [nl/strohalm/cyclos/spring/persistence.xml]: Invocation of init method > failed; nested exception is java.lang.RuntimeException: Error connecting to > database at > jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 > Caused by: java.lang.RuntimeException: Error connecting to database at > jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 >at > nl.strohalm.cyclos.setup.DataBaseConfiguration.validateConnection(DataBaseConfiguration.java:342) >at > nl.strohalm.cyclos.setup.DataBaseConfiguration.run(DataBaseConfiguration.java:107) >at > nl.strohalm.cyclos.spring.CustomSessionFactoryBean.newSessionFactory(CustomSessionFactoryBean.java:42) >at > org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745) > ... > Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: > Communications link failure > ... > Last packet sent to the server was 0 ms ago. >at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) >at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) >at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) >at java.lang.reflect.Constructor.newInstance(Constructor.java:513) >at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) >at > com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) >at com.mysql.jdbc.MysqlIO.(MysqlIO.java:335) >at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2043) >... 56 more > Caused by: java.net.ConnectException: Connection refused >at java.net.PlainSocketImpl.socketConnect(Native Method) >at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) >at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) >at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) >at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) >at java.net.Socket.connect(Socket.java:525) >at java.net.Socket.connect(Socket.j
RE: Cyclos Webapp Trouble (404)
> From: Rick Bragg [mailto:li...@gmnet.net] > Subject: RE: Cyclos Webapp Trouble (404) > > Error connecting to database at > jdbc:mysql://127.0.0.1:3306/cyclos You've still got some inconsistencies in your posts. You've stated that you're installing Tomcat+cyclos on a brand new machine, yet you also stated that this MySQL instance is in production use for other purposes. Are you sure MySQL is running on the *same* system that you have Tomcat+cyclos on? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
RE: Cyclos Webapp Trouble (404)
On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote: > > From: Rick Bragg [mailto:li...@gmnet.net] > > Subject: RE: Cyclos Webapp Trouble (404) > > > > Yes I notices that as well, I forgot to post my cyclos.properies Here > > is the "mysql" section... > > > > hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos > > The above doesn't jibe with the error message displayed at runtime: > > jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8 > > Note the use of "localhost" instead of "127.0.0.1", the lack of explicit port > number, and the database name. > > What you posted is not what you're actually running with. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. Sorry, that must have been one of my "variations"... To be clear, here are the files as of now. cyclos.properties (MySQL section) ### MySQL hibernate.dialect = org.hibernate.dialect.MySQLInnoDBDialect hibernate.connection.driver_class = com.mysql.jdbc.Driver hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos hibernate.connection.username = cyclos hibernate.connection.password = ### Connection provider properties hibernate.connection.provider_class = org.hibernate.connection.C3P0ConnectionProvider hibernate.c3p0.minPoolSize = 1 hibernate.c3p0.maxPoolSize = 100 hibernate.c3p0.acquireIncrement = 1 hibernate.c3p0.maxIdleTime = 21600 hibernate.c3p0.testConnectionOnCheckout = true hibernate.c3p0.preferredTestQuery = select 1 hibernate.c3p0.acquireRetryAttempts = 5 hibernate.c3p0.numHelperThreads = 3 and error log: Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log INFO: SessionListener: contextDestroyed() Jan 18, 2010 8:22:42 AM org.apache.catalina.core.ApplicationContext log INFO: ContextListener: contextDestroyed() Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log INFO: ContextListener: contextInitialized() Jan 18, 2010 8:22:50 AM org.apache.catalina.core.ApplicationContext log INFO: SessionListener: contextInitialized() Jan 18, 2010 8:22:51 AM org.apache.catalina.core.ApplicationContext log INFO: Initializing Spring root WebApplicationContext Jan 18, 2010 8:22:56 AM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [nl/strohalm/cyclos/spring/persistence.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Error connecting to database at jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 Caused by: java.lang.RuntimeException: Error connecting to database at jdbc:mysql://127.0.0.1:3306/cyclos?useUnicode=true&characterEncoding=utf8 at nl.strohalm.cyclos.setup.DataBaseConfiguration.validateConnection(DataBaseConfiguration.java:342) at nl.strohalm.cyclos.setup.DataBaseConfiguration.run(DataBaseConfiguration.java:107) at nl.strohalm.cyclos.spring.CustomSessionFactoryBean.newSessionFactory(CustomSessionFactoryBean.java:42) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745) ... Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure ... Last packet sent to the server was 0 ms ago. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.(MysqlIO.java:335) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2043) ... 56 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at java.net.Socket.(Socket.java:372) at java.net.Socket.(Socket.java:215) at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:253) at com.mysql.jdbc.MysqlIO.(Mysql
RE: Cyclos Webapp Trouble (404)
> From: Rick Bragg [mailto:li...@gmnet.net] > Subject: RE: Cyclos Webapp Trouble (404) > > Yes I notices that as well, I forgot to post my cyclos.properies Here > is the "mysql" section... > > hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos The above doesn't jibe with the error message displayed at runtime: jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8 Note the use of "localhost" instead of "127.0.0.1", the lack of explicit port number, and the database name. What you posted is not what you're actually running with. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
RE: Cyclos Webapp Trouble (404)
On Mon, 2010-01-18 at 07:42 -0600, Caldarale, Charles R wrote: > > From: Rick Bragg [mailto:li...@gmnet.net] > > Subject: RE: Cyclos Webapp Trouble (404) > > > > Error connecting to database at jdbc:mysql://localhost/cyclos3 > > Besides verifying that MySQL is actually running as David suggested, note > that there's a mismatch in the cyclos installation instructions compared to > what's in the cyclos.properties file. The instructions say to create a > database named "cyclos", but the properties file refers to one named > "cyclos3" in a couple of places - as does your error message. You need to > resolve the discrepancy. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers Thanks Chuck, Yes I notices that as well, I forgot to post my cyclos.properies Here is the "mysql" section... ### MySQL hibernate.dialect = org.hibernate.dialect.MySQLInnoDBDialect hibernate.connection.driver_class = com.mysql.jdbc.Driver hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos hibernate.connection.username = cyclos hibernate.connection.password = test1234 ### Connection provider properties hibernate.connection.provider_class = org.hibernate.connection.C3P0ConnectionProvider hibernate.c3p0.minPoolSize = 1 hibernate.c3p0.maxPoolSize = 100 hibernate.c3p0.acquireIncrement = 1 hibernate.c3p0.maxIdleTime = 21600 hibernate.c3p0.testConnectionOnCheckout = true hibernate.c3p0.preferredTestQuery = select 1 hibernate.c3p0.acquireRetryAttempts = 5 hibernate.c3p0.numHelperThreads = 3 my database name is "cyclos", MySQL is also in "production" so and is accessed by other php and perl libs on the local host. I have also tried some variations on the connection.url such as: hibernate.connection.url = jdbc:mysql://localhost:3306/cyclos and hibernate.connection.url = jdbc:mysql://localhost/cyclos In MySQL, I have the user set up privileges for the user to access via localhost AND 127.0.0.1 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
Rick Bragg wrote: > On Mon, 2010-01-18 at 07:39 -0500, David Smith wrote: > >>> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: >>> Communications link failure >>> >> To me this looks like it's outside of tomcat. Check that mysql is up, >> listening on tcp port 3306 (the standard mysql port) and there aren't >> any firewalls causing problems between tomcat and mysql. If you can on >> the Ubuntu box, su to the tomcat user acct and try connecting with mysql >> using the client program: mysql -P 3306 -h [mysql server hostname] -p >> -u [username for cyclos]. Replace the [...] in the command with real >> data and see what happens. >> >> --David >> >> > > OK, It is NOT security related. I set TOMCAT6_SECURITY=no > in /etc/default/tomcat6. > > I noticed that the user "tomcat6" has no shell in /etc/passwd > tomcat6:x:119:126::/usr/share/tomcat6:/bin/false > > Should I give this user the ability to shell (/bin/bash)? > > Rick > > > No... it doesn't need one. There are a number of "user" accounts in any linux system that do not have shells. They are just there for access control purposes limiting what different daemons and processes can do. Make sure tomcat can reach the mysql server and that should go a long ways towards fixing the issue. Also what Chuck said about the discrepancy in docs vs. config although I think that's a separate issue. Communications link failure is a network issue. --David - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
On Mon, 2010-01-18 at 07:39 -0500, David Smith wrote: > > > > Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: > > Communications link failure > To me this looks like it's outside of tomcat. Check that mysql is up, > listening on tcp port 3306 (the standard mysql port) and there aren't > any firewalls causing problems between tomcat and mysql. If you can on > the Ubuntu box, su to the tomcat user acct and try connecting with mysql > using the client program: mysql -P 3306 -h [mysql server hostname] -p > -u [username for cyclos]. Replace the [...] in the command with real > data and see what happens. > > --David > OK, It is NOT security related. I set TOMCAT6_SECURITY=no in /etc/default/tomcat6. I noticed that the user "tomcat6" has no shell in /etc/passwd tomcat6:x:119:126::/usr/share/tomcat6:/bin/false Should I give this user the ability to shell (/bin/bash)? Rick - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Stack Trace debug to screen
2010/1/18 iainmac : > > Hi, > > I am upgrading from Tomcat 5 to 6. > > When developing I run Tomcat from the command line so I can see the debug as > it happens, but with Tomcat 6 I can see the debug that I have coded but when > there is a Tomcat exception, it doesn't appear in the command line window > any more although it is in the logs. e.g. > > > org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) > > org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) > > org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:439) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:312) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:299) > > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586) > > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317) > > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) > javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > > org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:738) > > appears in the log, and in the browser but not in the debug in the command > line window I have open. I am searching for the reason, but if any one > knows what I need to do please let me know. Thanks. That message is logged by 2localhost.org.apache.juli.FileHandler (or what the name of that log file is?) and does not reach the ConsoleHandler that prints messages to the console. See http://tomcat.apache.org/tomcat-6.0-doc/logging.html There is the following phrase: "By default, loggers will not delegate to their parent if they have associated handlers. This may be changed per logger using the loggerName.useParentHandlers property, which accepts a boolean value." Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Stack Trace debug to screen
> From: iainmac [mailto:iain_macau...@hotmail.com] > Subject: Stack Trace debug to screen > > I am upgrading from Tomcat 5 to 6. Platform? JVM version? Precise Tomcat versions? Changes to the default logging.properties? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Cyclos Webapp Trouble (404)
> From: Rick Bragg [mailto:li...@gmnet.net] > Subject: RE: Cyclos Webapp Trouble (404) > > Error connecting to database at jdbc:mysql://localhost/cyclos3 Besides verifying that MySQL is actually running as David suggested, note that there's a mismatch in the cyclos installation instructions compared to what's in the cyclos.properties file. The instructions say to create a database named "cyclos", but the properties file refers to one named "cyclos3" in a couple of places - as does your error message. You need to resolve the discrepancy. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Stack Trace debug to screen
Hi, I am upgrading from Tomcat 5 to 6. When developing I run Tomcat from the command line so I can see the debug as it happens, but with Tomcat 6 I can see the debug that I have coded but when there is a Tomcat exception, it doesn't appear in the command line window any more although it is in the logs. e.g. org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:439) org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) org.apache.jasper.compiler.Compiler.compile(Compiler.java:312) org.apache.jasper.compiler.Compiler.compile(Compiler.java:299) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:738) appears in the log, and in the browser but not in the debug in the command line window I have open. I am searching for the reason, but if any one knows what I need to do please let me know. Thanks. -- View this message in context: http://old.nabble.com/Stack-Trace-debug-to-screen-tp27210579p27210579.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
>
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
To me this looks like it's outside of tomcat. Check that mysql is up,
listening on tcp port 3306 (the standard mysql port) and there aren't
any firewalls causing problems between tomcat and mysql. If you can on
the Ubuntu box, su to the tomcat user acct and try connecting with mysql
using the client program: mysql -P 3306 -h [mysql server hostname] -p
-u [username for cyclos]. Replace the [...] in the command with real
data and see what happens.
--David
Rick Bragg wrote:
> On Sun, 2010-01-17 at 21:55 -0600, Caldarale, Charles R wrote:
>
>>> From: Rick Bragg [mailto:li...@gmnet.net]
>>> Subject: Cyclos Webapp Trouble (404)
>>>
>>> After following these steps, and restarting tomcat6 I get a 404 error,
>>> Also, the database remains empty.
>>>
>> As stated before, using a real Tomcat download from tomcat.apache.org,
>> installing the most recent GA version of MySQL (5.1.42), and the current
>> cyclos (3.5.5), it all works fine. The problem you are now having appears
>> to be due to the use of a security manager; either turn that off, or update
>> the appropriate properties file to include all the necessary entries to
>> allow cyclos to work. I have no idea where Ubuntu places (or even names)
>> the security properties file, and certainly no idea what needs to be added
>> to make cyclos work with one.
>>
>> Again, I would strongly recommend that you uninstall the Ubuntu 3rd-party
>> version, and put in a real Tomcat, so we can all be looking at a common
>> setup.
>>
>> - Chuck
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you received
>> this in error, please contact the sender and delete the e-mail and its
>> attachments from all computers.
>>
>>
>
>
>
> Hi,
>
> Thanks Chuck, One could argue to not use a package manager at all,
> however I would rather use the package manager for this to make things
> easier down the road. I did manage to get a bit further, and you are
> right about the security manager.
>
> I got rid of the errors in the previous post by setting privileges for
> the classes and libs (see below), but now I'm stuck on mysql
>
> Here is a brief snip from my error log
>
> Jan 18, 2010 2:05:07 AM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListener
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'sessionFactory' defined in class path resource
> [nl/strohalm/cyclos/spring/persistence.xml]: Invocation of init method
> failed; nested exception is java.lang.RuntimeException: Error connecting to
> database at
> jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8
> Caused by: java.lang.RuntimeException: Error connecting to database at
> jdbc:mysql://localhost/cyclos3?useUnicode=true&characterEncoding=utf8
> at
> nl.strohalm.cyclos.setup.DataBaseConfiguration.validateConnection(DataBaseConfiguration.java:342)
> at
> nl.strohalm.cyclos.setup.DataBaseConfiguration.run(DataBaseConfiguration.java:107)
> ...
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
>
>
> I have the following policies in:
> vi /etc/tomcat6/policy.d/50local.policy
>
> // The permissions granted to the context WEB-INF/classes and lib directories
> grant codeBase "file:${catalina.base}/webapps/cyclos/WEB-INF/classes/-" {
> permission java.security.AllPermission;
> };
> grant codeBase "file:${catalina.base}/webapps/cyclos/WEB-INF/lib/-" {
> permission java.security.AllPermission;
> };
>
> // The permission granted to your JDBC driver
> grant codeBase
> "jar:file:${catalina.base}/webapps/cyclos/WEB-INF/lib/mysql-connector-java-5.1.7-bin.jar!/-"
> {
> permission java.net.SocketPermission "localhost:3306", "connect";
> };
>
>
> I think maybe my JDBC permissions are not quite right, or there is something
> with the driver, but I'm not sure...
>
> Anybody have any ideas?
>
> Thanks again!
> Rick
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Cyclos Webapp Trouble (404)
Rick Bragg wrote: ... I think maybe my JDBC permissions are not quite right, or there is something with the driver, but I'm not sure... A very quick way to see if the security manager has anything to do with this, is to turn it off temporarily. Undr Ubuntu, if it is like Debian, there is probably a setting in /etc/default/tomcatxx, like TOMCAT_SECURITY=YES change it to NO and restart Tomcat. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
