Consulting opportunity
We have what we believe is approximately a one week assignment to cluster several instances of Tomcat. The clustering should be relatively straight forward except that most of the classes on the server side extend a class which contains the datasource and is therefore not serializable. Although we believe we could do this ourselves from a technical point of view, we don't have the resources to spare. We are currently running Tomcat 8.0.9 against Java 8.0.20 running on the latest Slackware servers. We are located in Charleston, SC. If you have some interest, please email me directly. Thanks, Carl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 6 SSL issue
Hi; I have created a keystore and CSR for SSL with the following command: %JAVA_HOME%\bin\keytool -genkey -alias server -keyalg RSA \ -keystore \path\to\my\keystore Then I received 2 files from the certificate authority, abc.com.cer and abc.om.p7b >From this point, no matter what I have done, i couldn't make the SSL work on my Tomcat 6. I followed the steps under, http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html but I failed to import p7b so I convert it crt file and successfully import it. My application for http, is using 55012 and I want to use the port 443 for https. Following is my server.xml Now my questions are 1) my keystore alias is server and i send my csr after this. To clean the things up, I want to delete my keystore but is it fine if I generate the key with another alias, e.g. tomcat as in the tomcat documentation? 2) I have the files, cer and crt (p7b), so is fine or should I need stg extra? 3) Is the order of import important?`first crt then cer? 4) What are the correct import commands? Should I trust tomcat documentation or authorities documentation? My tomcat version is as follows: Server version: Apache Tomcat/6.0.36 Server built: Oct 16 2012 09:59:09 Server number: 6.0.36.0 OS Name:Windows 7 OS Version: 6.1 Architecture: amd64 JVM Version:1.7.0_21-b11 JVM Vendor: Oracle Corporation Regards.
Re: Quite a few TCP connection established on start of Tomcat
There are settings to handle sessions and the connections pertains the same. Pankaj On Fri, Oct 10, 2014 at 11:39 PM, Gangadhar Tumkur wrote: > Thanks for taking time to reply to my question. I have a follow-up > question. What do you mean by "This is only done as you have configured on > the settings."? Is there a setting by which we allow Tomcat to use port's? > > Raj > > On Fri, Oct 10, 2014 at 1:13 PM, Pankaj Singh wrote: > > > These are locally established connections, pertains to the local socket > > connectivity of tomcat thread with different ports/sockets randomly. > > > > This is only done as you have configured on the settings. > > > > > > Thanks > > Pankaj Singh > > > > On Fri, Oct 10, 2014 at 10:39 PM, Gangadhar Tumkur > > wrote: > > > > > The text of the image: > > > > > > TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED > > > [java.exe] > > > > > > TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED > > > [java.exe] > > > > > > > > > > > > > > > On Fri, Oct 10, 2014 at 12:39 PM, Daniel Mikusa > > > wrote: > > > > > > > On Fri, Oct 10, 2014 at 12:33 PM, Gangadhar Tumkur < > rajmc...@gmail.com > > > > > > > wrote: > > > > > > > > > Hello, > > > > > > > > > > We have moved to Tomcat 7.0.51 from JBoss 4x as the application > > server > > > > for > > > > > our product using Java 8.0.20. After starting Tomcat application > > server > > > > and > > > > > when we run netstat -a -b we see that there are quite a few TCP > > > > connections > > > > > established related to Tomcat as you see below. > > > > > > > > > > [image: Inline image 1] > > > > > > > > > > > > > I can't see the picture. It looks like the list may have stripped > it. > > > Can > > > > you just copy and paste the text? > > > > > > > > Dan > > > > > > > > > > > > > > > > > > Does anyone have an answer as to why so many connections opened? > > > > > > > > > > Thanks for taking time to answer. > > > > > > > > > > Raj > > > > > > > > > > > > > > >
Re: Quite a few TCP connection established on start of Tomcat
Thanks for taking time to reply to my question. I have a follow-up question. What do you mean by "This is only done as you have configured on the settings."? Is there a setting by which we allow Tomcat to use port's? Raj On Fri, Oct 10, 2014 at 1:13 PM, Pankaj Singh wrote: > These are locally established connections, pertains to the local socket > connectivity of tomcat thread with different ports/sockets randomly. > > This is only done as you have configured on the settings. > > > Thanks > Pankaj Singh > > On Fri, Oct 10, 2014 at 10:39 PM, Gangadhar Tumkur > wrote: > > > The text of the image: > > > > TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED > > [java.exe] > > > > TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED > > [java.exe] > > > > > > > > > > On Fri, Oct 10, 2014 at 12:39 PM, Daniel Mikusa > > wrote: > > > > > On Fri, Oct 10, 2014 at 12:33 PM, Gangadhar Tumkur > > > > wrote: > > > > > > > Hello, > > > > > > > > We have moved to Tomcat 7.0.51 from JBoss 4x as the application > server > > > for > > > > our product using Java 8.0.20. After starting Tomcat application > server > > > and > > > > when we run netstat -a -b we see that there are quite a few TCP > > > connections > > > > established related to Tomcat as you see below. > > > > > > > > [image: Inline image 1] > > > > > > > > > > I can't see the picture. It looks like the list may have stripped it. > > Can > > > you just copy and paste the text? > > > > > > Dan > > > > > > > > > > > > > > Does anyone have an answer as to why so many connections opened? > > > > > > > > Thanks for taking time to answer. > > > > > > > > Raj > > > > > > > > > >
Re: Quite a few TCP connection established on start of Tomcat
Hello Chuck, There were 10, I did NOT copy all of them. Thanks, Raj On Fri, Oct 10, 2014 at 1:16 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Gangadhar Tumkur [mailto:rajmc...@gmail.com] > > Subject: Re: Quite a few TCP connection established on start of Tomcat > > > The text of the image: > > > TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED > > [java.exe] > > > TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED > > [java.exe] > > Don't top post - read the mailing list guidelines: > http://tomcat.apache.org/lists.html#tomcat-users > > Two does not seem to be "quite a few". How many are there really? > > - 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: Quite a few TCP connection established on start of Tomcat
> From: Gangadhar Tumkur [mailto:rajmc...@gmail.com] > Subject: Re: Quite a few TCP connection established on start of Tomcat > The text of the image: > TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED > [java.exe] > TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED > [java.exe] Don't top post - read the mailing list guidelines: http://tomcat.apache.org/lists.html#tomcat-users Two does not seem to be "quite a few". How many are there really? - 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: Quite a few TCP connection established on start of Tomcat
These are locally established connections, pertains to the local socket connectivity of tomcat thread with different ports/sockets randomly. This is only done as you have configured on the settings. Thanks Pankaj Singh On Fri, Oct 10, 2014 at 10:39 PM, Gangadhar Tumkur wrote: > The text of the image: > > TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED > [java.exe] > > TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED > [java.exe] > > > > > On Fri, Oct 10, 2014 at 12:39 PM, Daniel Mikusa > wrote: > > > On Fri, Oct 10, 2014 at 12:33 PM, Gangadhar Tumkur > > wrote: > > > > > Hello, > > > > > > We have moved to Tomcat 7.0.51 from JBoss 4x as the application server > > for > > > our product using Java 8.0.20. After starting Tomcat application server > > and > > > when we run netstat -a -b we see that there are quite a few TCP > > connections > > > established related to Tomcat as you see below. > > > > > > [image: Inline image 1] > > > > > > > I can't see the picture. It looks like the list may have stripped it. > Can > > you just copy and paste the text? > > > > Dan > > > > > > > > > > Does anyone have an answer as to why so many connections opened? > > > > > > Thanks for taking time to answer. > > > > > > Raj > > > > > >
Re: Quite a few TCP connection established on start of Tomcat
The text of the image: TCP127.0.0.1:57945ACNU34794GD:57946 ESTABLISHED [java.exe] TCP127.0.0.1:57946ACNU34794GD:57945 ESTABLISHED [java.exe] On Fri, Oct 10, 2014 at 12:39 PM, Daniel Mikusa wrote: > On Fri, Oct 10, 2014 at 12:33 PM, Gangadhar Tumkur > wrote: > > > Hello, > > > > We have moved to Tomcat 7.0.51 from JBoss 4x as the application server > for > > our product using Java 8.0.20. After starting Tomcat application server > and > > when we run netstat -a -b we see that there are quite a few TCP > connections > > established related to Tomcat as you see below. > > > > [image: Inline image 1] > > > > I can't see the picture. It looks like the list may have stripped it. Can > you just copy and paste the text? > > Dan > > > > > > Does anyone have an answer as to why so many connections opened? > > > > Thanks for taking time to answer. > > > > Raj > > >
Re: Quite a few TCP connection established on start of Tomcat
On Fri, Oct 10, 2014 at 12:33 PM, Gangadhar Tumkur wrote: > Hello, > > We have moved to Tomcat 7.0.51 from JBoss 4x as the application server for > our product using Java 8.0.20. After starting Tomcat application server and > when we run netstat -a -b we see that there are quite a few TCP connections > established related to Tomcat as you see below. > > [image: Inline image 1] > I can't see the picture. It looks like the list may have stripped it. Can you just copy and paste the text? Dan > > Does anyone have an answer as to why so many connections opened? > > Thanks for taking time to answer. > > Raj >
Quite a few TCP connection established on start of Tomcat
Hello, We have moved to Tomcat 7.0.51 from JBoss 4x as the application server for our product using Java 8.0.20. After starting Tomcat application server and when we run netstat -a -b we see that there are quite a few TCP connections established related to Tomcat as you see below. [image: Inline image 1] Does anyone have an answer as to why so many connections opened? Thanks for taking time to answer. Raj
Re: Tomcat JVM Crash
Hi, So I have found a long term solution to our crash problem. We were using JSSE for SSL, switching to APR and OpenSSL fixed the problems. So my findings are this JSSE has a bug in it that can cause the Tomcat server to crash brought on by SSL, Chrome and a form post of a specific amount of data. The server crashes can be mitigated by starting Tomcat with "-XX:CompileCommand=exclude,com/sun/crypto/provider/*.*". Instead of the server crashing Chrome returns net::ERR_SSL_PROTOCOL_ERROR and you can actually catch the error, the stack trace is below. I have reported my findings to Oracle. They need to fix the bug, but for us the best solution was just to move away from JSSE and switch to APR OpenSSL which is the recommend solution to begin with. Thanks, Chad 07-Oct-2014 10:10:58.057 SEVERE [http-nio-443-exec-38] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [Controller] in context with path [/mtg] threw exception java.lang.NullPointerException at java.lang.System.arraycopy(Native Method) at com.sun.crypto.provider.GCTR.reset(GCTR.java:125) at com.sun.crypto.provider.GCTR.doFinal(GCTR.java:116) at com.sun.crypto.provider.GaloisCounterMode.doLastBlock(GaloisCounterMode.java:343) at com.sun.crypto.provider.GaloisCounterMode.decryptFinal(GaloisCounterMode.java:511) at com.sun.crypto.provider.CipherCore.finalNoPadding(CipherCore.java:1023) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:960) at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:479) at javax.crypto.CipherSpi.bufferCrypt(CipherSpi.java:830) at javax.crypto.CipherSpi.engineDoFinal(CipherSpi.java:730) at javax.crypto.Cipher.doFinal(Cipher.java:2416) at sun.security.ssl.CipherBox.decrypt(Unknown Source) at sun.security.ssl.EngineInputRecord.decrypt(Unknown Source) at sun.security.ssl.SSLEngineImpl.readRecord(Unknown Source) at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source) at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source) at javax.net.ssl.SSLEngine.unwrap(Unknown Source) at org.apache.tomcat.util.net.SecureNioChannel.read(SecureNioChannel.java:439) at org.apache.tomcat.util.net.NioBlockingSelector.read(NioBlockingSelector.java:173) at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:251) at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:232) at org.apache.coyote.http11.InternalNioInputBuffer.fill(InternalNioInputBuffer.java:133) at org.apache.coyote.http11.InternalNioInputBuffer$SocketInputBuffer.doRead(InternalNioInputBuffer.java:177) at org.apache.coyote.http11.filters.IdentityInputFilter.doRead(IdentityInputFilter.java:110) at org.apache.coyote.http11.AbstractInputBuffer.doRead(AbstractInputBuffer.java:413) at org.apache.coyote.Request.doRead(Request.java:459) at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:338) at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:395) at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:363) at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:190) at org.apache.catalina.connector.Request.readPostBody(Request.java:3034) at org.apache.catalina.connector.Request.parseParameters(Request.java:2983) at org.apache.catalina.connector.Request.getParameter(Request.java:1077) at org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:380) at com.mtg.mtg.controller.Controller.doPost(Controller.java:41) at javax.servlet.http.HttpServlet.service(HttpServlet.java:644) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve
Re: Tomcat JDBC pool - auto reconnect
On Fri, Oct 10, 2014 at 9:51 AM, Vasily Kukhta wrote: > Hi friends, > > I have a question regarding the ability of Tomcat JDBC pool to reconnect > automatically to a database in case of temporarily network failures. > > I'm developing a high-load application which uses Oracle 11g database. It > may happen that the DB can become unavailable for several minutes - it is > located in another geographic region, so network failures can happen > sometimes and the DB becomes unresponsive. Can the Tomcat JDBC pool > automatically reconnect to the DB when it becomes online again? In a manner of speaking. You can configure the pool to test connections, remove bad ones and try to replace them with new, good connections. See "validationQuery", "testWhileIdle and "testOn*" here. http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Common_Attributes The trick is that the pool doesn't know when your DB comes back online, so you might get exceptions while the DB is offline (especially if it's down for a long time). It will start talking again once the DB comes back online though. > Is this done by default or it should be configured somehow? > No. You need to set a validation query and set at least one of the "test*" attributes to "true". Dan > > Thank you in advance! > > Best regards, > Vasily Kukhta. >
Tomcat JDBC pool - auto reconnect
Hi friends, I have a question regarding the ability of Tomcat JDBC pool to reconnect automatically to a database in case of temporarily network failures. I'm developing a high-load application which uses Oracle 11g database. It may happen that the DB can become unavailable for several minutes - it is located in another geographic region, so network failures can happen sometimes and the DB becomes unresponsive. Can the Tomcat JDBC pool automatically reconnect to the DB when it becomes online again? Is this done by default or it should be configured somehow? Thank you in advance! Best regards, Vasily Kukhta.
Re: Where do System.out and System.err go in Tomcat?
sorry for typos. In catalina.sh in *nix environment and catalina.bat in windows environment. Regards, Ameer Mawia On Oct 10, 2014 3:35 PM, "Ameer Mawia" wrote: > Hi, > > Tomcat by default dump both console output and error in catalina.out under > tomcat-home/log directory. But you can change it any day by modifying > startup script catalina.sh/catalina.bat in *nix environment or > catalina.bat in bin directory of tomcat home. > > Regards, > Ameer Mawia > On Oct 10, 2014 2:19 PM, "M. D." wrote: > >> Hello devs, >> >> I saw this post on the Internet: >> http://www.jguru.com/faq/view.jsp?EID=302980 >> >> > Where do System.out and System.err go in Tomcat? >> > By default, they will go to the console where the tomcat is started. >> You have to modify the startup >> > scripts to redirect them to appropriate files. See Tomcat Mailing List >> for a discussion on how to >> > redirect the System.out and System.err. >> >> > On the other hand, if you are running Tomcat as an NT Service, you can >> modify the conf/wrapper.properties > file and set wrapper.stdout and >> wrapper.stderr properties to point to your log files. >> >> So... what do I have to do in order so that Tomcat5 can redirect >> System.err to logfile instead of just the console. >> >> Best regards, >> Marin >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >>
Re: Where do System.out and System.err go in Tomcat?
Btw if you want the console logs from your application to go in your application log file, then in that case you have to add a console appender to your log4j configuation file(assuming you are infact using log4j). On Oct 10, 2014 3:37 PM, "Ameer Mawia" wrote: > sorry for typos. > > In catalina.sh in *nix environment and catalina.bat in windows environment. > > Regards, > Ameer Mawia > On Oct 10, 2014 3:35 PM, "Ameer Mawia" wrote: > >> Hi, >> >> Tomcat by default dump both console output and error in catalina.out >> under tomcat-home/log directory. But you can change it any day by modifying >> startup script catalina.sh/catalina.bat in *nix environment or >> catalina.bat in bin directory of tomcat home. >> >> Regards, >> Ameer Mawia >> On Oct 10, 2014 2:19 PM, "M. D." wrote: >> >>> Hello devs, >>> >>> I saw this post on the Internet: >>> http://www.jguru.com/faq/view.jsp?EID=302980 >>> >>> > Where do System.out and System.err go in Tomcat? >>> > By default, they will go to the console where the tomcat is started. >>> You have to modify the startup >>> > scripts to redirect them to appropriate files. See Tomcat Mailing List >>> for a discussion on how to >>> > redirect the System.out and System.err. >>> >>> > On the other hand, if you are running Tomcat as an NT Service, you can >>> modify the conf/wrapper.properties > file and set wrapper.stdout and >>> wrapper.stderr properties to point to your log files. >>> >>> So... what do I have to do in order so that Tomcat5 can redirect >>> System.err to logfile instead of just the console. >>> >>> Best regards, >>> Marin >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>>
Re: Where do System.out and System.err go in Tomcat?
Hi, Tomcat by default dump both console output and error in catalina.out under tomcat-home/log directory. But you can change it any day by modifying startup script catalina.sh/catalina.bat in *nix environment or catalina.bat in bin directory of tomcat home. Regards, Ameer Mawia On Oct 10, 2014 2:19 PM, "M. D." wrote: > Hello devs, > > I saw this post on the Internet: > http://www.jguru.com/faq/view.jsp?EID=302980 > > > Where do System.out and System.err go in Tomcat? > > By default, they will go to the console where the tomcat is started. You > have to modify the startup > > scripts to redirect them to appropriate files. See Tomcat Mailing List > for a discussion on how to > > redirect the System.out and System.err. > > > On the other hand, if you are running Tomcat as an NT Service, you can > modify the conf/wrapper.properties > file and set wrapper.stdout and > wrapper.stderr properties to point to your log files. > > So... what do I have to do in order so that Tomcat5 can redirect > System.err to logfile instead of just the console. > > Best regards, > Marin > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Where do System.out and System.err go in Tomcat?
Hello devs, I saw this post on the Internet: http://www.jguru.com/faq/view.jsp?EID=302980 > Where do System.out and System.err go in Tomcat? > By default, they will go to the console where the tomcat is started. You have > to modify the startup > scripts to redirect them to appropriate files. See Tomcat Mailing List for a > discussion on how to > redirect the System.out and System.err. > On the other hand, if you are running Tomcat as an NT Service, you can modify > the conf/wrapper.properties > file and set wrapper.stdout and wrapper.stderr > properties to point to your log files. So... what do I have to do in order so that Tomcat5 can redirect System.err to logfile instead of just the console. Best regards, Marin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
