WebSocket: Special character escaping
Hi, I have written a web socket server using web socket API(JSR-356) and which runs on tomcat version 7.0.56. My test client sends some text which has some special characters over web socket connection to my server. the problem is that server is not getting the client's text as it is. the special character got modified to ?. The text that my client sends is Test701á. Server received is SIP701?. At server, I have just attached Text message handler to web socket session. This works fine with tomcat version 7.0.55. Please let me know if i am missing something here. Thank you, ganesh
Re: WebSocket: Special character escaping
On 13/05/2015 11:44, Ganesh Bms wrote: Sorry .. correction to line: The text that my client sends is Test701á. Server received is SIP701?. Actual: The text that my client sends is Test701á. Server received is Test701?. Lots of places this could go wrong. You need to make sure that everything is using UTF-8 everywhere. I'd check these first: - The client is sending the text encoding using UTF-8 - Your server application is displaying the received String using UTF-8 You can see if Tomcat handles this correctly by using the WebSocket chat example and sending special characters. Mark On Wed, May 13, 2015 at 3:33 PM, Ganesh Bms gbmsat...@gmail.com wrote: Hi, I have written a web socket server using web socket API(JSR-356) and which runs on tomcat version 7.0.56. My test client sends some text which has some special characters over web socket connection to my server. the problem is that server is not getting the client's text as it is. the special character got modified to ?. The text that my client sends is Test701á. Server received is SIP701?. At server, I have just attached Text message handler to web socket session. This works fine with tomcat version 7.0.55. Please let me know if i am missing something here. Thank you, ganesh - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
CoyoteAdapter.checkRecycled Encountered a non-recycled response and recycled it forcedly.
Tomcat experiencing problems that causes the following exception: 13-May-2015 15:39:42.886 INFO [http-apr-0.0.0.0-4089-exec-123] org.apache.catalina.connector.CoyoteAdapter.checkRecycled Encountered a non-recycled response and recycled it forcedly. org.apache.catalina.connector.CoyoteAdapter$RecycleRequiredException at org.apache.catalina.connector.CoyoteAdapter.checkRecycled(CoyoteAdapter.java:710) at org.apache.coyote.http11.AbstractHttp11Processor.recycle(AbstractHttp11Processor.java:1824) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.release(Http11AprProtocol.java:257) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:745) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:283) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2463) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2452) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Would appreciate your advice how this issue can be diagnosed. Information related to Tomcat version and environment: 13-May-2015 12:59:44.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.21 13-May-2015 12:59:44.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 23 2015 14:11:21 UTC 13-May-2015 12:59:44.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.21.0 13-May-2015 12:59:44.565 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: SunOS 13-May-2015 12:59:44.566 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 5.10 13-May-2015 12:59:44.566 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: sparcv9 13-May-2015 12:59:44.567 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /cma/java/jdk1.7.0_75/jre 13-May-2015 12:59:44.568 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.7.0_75-b13 13-May-2015 12:59:44.568 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation 13-May-2015 12:59:44.569 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /cma/depox/gateway 13-May-2015 12:59:44.570 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /cma/depox/gateway 13-May-2015 12:59:44.573 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/cma/depox/gateway/conf/logging.properties 13-May-2015 12:59:44.573 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 13-May-2015 12:59:44.574 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms4096m 13-May-2015 12:59:44.575 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m 13-May-2015 12:59:44.575 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xss512k 13-May-2015 12:59:44.576 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:PermSize=512m 13-May-2015 12:59:44.577 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=1024m 13-May-2015 12:59:44.578 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:CompileThreshold=100 13-May-2015 12:59:44.578 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=128m 13-May-2015 12:59:44.579 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+OptimizeStringConcat 13-May-2015 12:59:44.580 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseStringCache 13-May-2015 12:59:44.580 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseConcMarkSweepGC 13-May-2015 12:59:44.581 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSIncrementalMode 13-May-2015 12:59:44.582 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSIncrementalPacing 13-May-2015 12:59:44.583 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseParNewGC
Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue
Application uses log4j2 for generation of trace file (configuration is attached). During application execution I see multiple warnings related to AsycAppender: 2015-05-13 16:13:32,580 WARN Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue arASYNC_CORE 2015-05-13 16:15:21,047 WARN Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue arASYNC_CORE 2015-05-13 16:15:26,151 WARN Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue arASYNC_CORE 2015-05-13 16:15:31,272 WARN Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue arASYNC_CORE 2015-05-13 16:17:35,709 WARN Interrupted while waiting for a free slot in the AsyncAppender LogEvent-queue arASYNC_CORE According to my understanding, log files are generated in asynchronous mode and such situation should not happen. Google doest provide any advise for hit issue. Any idea what might be adjusted on Tomcat/Application level to resolve this issue? Kind regards, Maxim P.S. Tomcat version information: 13-May-2015 12:59:44.556 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.21 13-May-2015 12:59:44.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 23 2015 14:11:21 UTC 13-May-2015 12:59:44.564 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.21.0 13-May-2015 12:59:44.565 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: SunOS 13-May-2015 12:59:44.566 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 5.10 13-May-2015 12:59:44.566 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: sparcv9 13-May-2015 12:59:44.567 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /cma/java/jdk1.7.0_75/jre 13-May-2015 12:59:44.568 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.7.0_75-b13 13-May-2015 12:59:44.568 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation 13-May-2015 12:59:44.569 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /cma/depox/gateway 13-May-2015 12:59:44.570 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /cma/depox/gateway 13-May-2015 12:59:44.573 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/cma/depox/gateway/conf/logging.properties 13-May-2015 12:59:44.573 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 13-May-2015 12:59:44.574 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms4096m 13-May-2015 12:59:44.575 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m 13-May-2015 12:59:44.575 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xss512k 13-May-2015 12:59:44.576 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:PermSize=512m 13-May-2015 12:59:44.577 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=1024m 13-May-2015 12:59:44.578 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:CompileThreshold=100 13-May-2015 12:59:44.578 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=128m 13-May-2015 12:59:44.579 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+OptimizeStringConcat 13-May-2015 12:59:44.580 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseStringCache 13-May-2015 12:59:44.580 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseConcMarkSweepGC 13-May-2015 12:59:44.581 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSIncrementalMode 13-May-2015 12:59:44.582 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSIncrementalPacing 13-May-2015 12:59:44.583 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseParNewGC 13-May-2015 12:59:44.583 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+ExplicitGCInvokesConcurrent 13-May-2015 12:59:44.584 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ParallelGCThreads=4 13-May-2015 12:59:44.585 INFO [main]
Re: WebSocket: Special character escaping
Sorry .. correction to line: The text that my client sends is Test701á. Server received is SIP701?. Actual: The text that my client sends is Test701á. Server received is Test701?. On Wed, May 13, 2015 at 3:33 PM, Ganesh Bms gbmsat...@gmail.com wrote: Hi, I have written a web socket server using web socket API(JSR-356) and which runs on tomcat version 7.0.56. My test client sends some text which has some special characters over web socket connection to my server. the problem is that server is not getting the client's text as it is. the special character got modified to ?. The text that my client sends is Test701á. Server received is SIP701?. At server, I have just attached Text message handler to web socket session. This works fine with tomcat version 7.0.55. Please let me know if i am missing something here. Thank you, ganesh
RE: Tomcat 7.0.57 - Deployment Issue
-Original Message- From: Kiran Badi [mailto:ki...@poonam.org] Sent: Tuesday, May 12, 2015 9:30 PM To: Tomcat Users List Subject: Re: Tomcat 7.0.57 - Deployment Issue Thanks Hassan/Prabhu/Charles for reply. I tried the options given in this link. http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts but for some reasons still its not working.I have pasted the server xml for reference. I have unlimited website hosting plan with arvixe.com , but for some reasons it's still not working.Not sure if these guys needs to add something special to hosts file. here is link for actual site - homelyhotels.com - you will probably see cgi-bin folder. Below server xml, I have added just a second host tag for webapp2. I am bit hesitant to make changes wrt to webapp1(removing context tags etc due to lack of time on my end along with lack of sufficient knowledge in case something breaks,however I will eventually clean that as well). ... !-- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). Documentation at /docs/config/engine.html -- !-- You should set jvmRoute to support load-balancing via AJP ie : Engine name=Catalina defaultHost=localhost jvmRoute=jvm1 -- Engine name=Catalina defaultHost=localhost !--For clustering, please take a look at documentation at: /docs/cluster-howto.html (simple how to) /docs/config/cluster.html (reference documentation) -- !-- Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster/ -- !-- Use the LockOutRealm to prevent attempts to guess user passwords via a brute-force attack -- Realm className=org.apache.catalina.realm.LockOutRealm !-- This Realm uses the UserDatabase configured in the global JNDI resources under the key UserDatabase. Any edits that are performed against this UserDatabase are immediately available for use by the Realm. -- Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase/ /Realm Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true !-- SingleSignOn valve, share authentication between web applications Documentation at: /docs/config/valve.html -- !-- Valve className=org.apache.catalina.authenticator.SingleSignOn / -- !-- Access log processes all example. Documentation at: /docs/config/valve.html Note: The pattern used is equivalent to using pattern=common -- Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=localhost_access_log. suffix=.txt pattern=%h %l %u %t quot;%rquot; %s %b / /Host Host name=webapp1 appBase=/home/myhostid/tomcat/webapps Aliaswww.webapp1.com/Alias Aliasmyhostid.myserver.mywebhost.com/Alias Context path=/manager debug=0 privileged=true docBase=/home/myhostid/tomcat/webapps/manager /Context /Host Host name=webapp2.com appBase=/home/myhostid/hosts/webapp2/webapps xmlValidation=false xmlNamespaceAware=false unpackWARs=true autoDeploy=true Aliaswww.webapp2.com/Alias Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=webapp2_access_log. suffix=.txt pattern=%h %l %u %t quot;%rquot; %s %b / /Host /Engine /Service /Server Kiran - What no one has asked about yet is this: What does your directory structure look like? Where are the catalina_home and catalina_base environment variables pointed? Is it, I suspect, /home/myhostid/tomcat? If so, then deployment of the server using the above config will result in the following: For localhost and any request that comes in on the server's network interfaces that doesn't match your explicit host names or their alias, everything under the /home/myhostid/tomcat/webapps will be deployed once for the Host named localhost. So, for example http://localhost/webapp2/webapps/ would result in reaching the webapp2 pages (might need to add ROOT or webapp2 to the end, but you could reach it). For the Host named webapp1, you will essentially re-deploy the application(s) that was deployed for localhost. We call that double-deployment, and it's something to avoid. For the Host named webapp2.com, it will only deploy the application webapp2, but in so doing it will unpack the war into a directory named the same as the war file, which makes that application now available at the other hosts. What I'm saying is, don't
RE: String Cache Configuration
Hello Mark, No I haven't but I will look at it. However, I thought someone would know and be able to summarize it for me quickly :). Thanks for the response. Thone -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Wednesday, May 13, 2015 11:46 AM To: Tomcat Users List Subject: Re: String Cache Configuration On 13/05/2015 19:18, Thone Soungpanya wrote: Hello, Can anyone give me more information on what the String Cache Configuration does? This is a setting in the catalina.properties file. I searched the web and it does not give much info on the tomcat document site (https://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html). # String cache configuration. tomcat.util.buf.StringCache.byte.enabled=true Have you looked at the Javadoc and/or source code for the StringCache? 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 7 JNDI Realm credential password update availability
On 13/05/2015 19:13, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK INFORMATION INC at Cisco) wrote: Hello, We have a Tomcat 7 server running on Linux that must use LDAP over SSL to connect to an AD server for user authentication. This configuration we have working. The issue is the credentials used to connect to the AD server must have the password updated every 180 days, and therefore updated in the JNDI Realm configuration. Is there a way to update the password in server.xml that would allow it to be recognized as changed without restarting the Tomcat server. Or some other configuration what ever it may be that would achieve this. The goal is to update the password and have it recognized as updated with no down time for the application running on the server. Any thoughts would be appreciated. server.xml changes require a restart. Can you update it via JMX as well? (That should work but I am going from memory rather than testing it / looking at the source). Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: String Cache Configuration
On 13/05/2015 19:18, Thone Soungpanya wrote: Hello, Can anyone give me more information on what the String Cache Configuration does? This is a setting in the catalina.properties file. I searched the web and it does not give much info on the tomcat document site (https://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html). # String cache configuration. tomcat.util.buf.StringCache.byte.enabled=true Have you looked at the Javadoc and/or source code for the StringCache? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 JNDI Realm credential password update availability
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 5/13/15 2:45 PM, Mark Thomas wrote: On 13/05/2015 19:13, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK INFORMATION INC at Cisco) wrote: Hello, We have a Tomcat 7 server running on Linux that must use LDAP over SSL to connect to an AD server for user authentication. This configuration we have working. The issue is the credentials used to connect to the AD server must have the password updated every 180 days, and therefore updated in the JNDI Realm configuration. Is there a way to update the password in server.xml that would allow it to be recognized as changed without restarting the Tomcat server. Or some other configuration what ever it may be that would achieve this. The goal is to update the password and have it recognized as updated with no down time for the application running on the server. Any thoughts would be appreciated. server.xml changes require a restart. Can you update it via JMX as well? (That should work but I am going from memory rather than testing it / looking at the source). - From *my* memory, modifying things that come from server.xml via JMX often does nothing, because the component itself doesn't get re-initialized. You basically just change the in-memory representation of the configuration, but the component (Realm, in this case), just keeps doing what it was doing. A good example is the Connectors, though in that case, the Connector is just configuration that gets used to generate a Protocol+Endpoint so maybe I'm just thinking of this special case. Ultimately, JMX is the *right* way to do this, provided that the Realm notices that the configuration has changed and actually uses that configuration. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVU7PVAAoJEBzwKT+lPKRYOJwQAMrZi9Pu+MuG25bnTbgMCBtm gTAdkheI/ovuG2H2hjCAqUJo6x0B1piG71uOV7S0lTatTIdclUIeDR67mheZlLXx yY0oy4pFWSsH1UJE14LnTyqXUWQWGFTD1tAMmgGrXhMhkIVlltaFkBP9fxis33xN sjhJh8QL27jK80QL19PuVNhDLWJbAAAGhDlxHDqeCRZaxu9mC/9imWr4juTw/4vu l1xcy4Q8+G+nwpYjKlAv3ttpgMipfOKRlYSLVpxZO45yEbJmCZWJef51CSLL4Ib/ 0qxONW+aKndUJ1ZhAgc6ZSQL4N9Z+stNphD/IQhKK8I9SCdVuJrTrsdUjurpuMXZ d89uIduDKVLsIqnUyHH019M4zWa9xs26pJ/JJv9yyTZvkCfH2X5YAAO8tJE7kTm3 HTZA8hIWD09n4VZ0P0BZurmRt2aI/pTq6+aVhig0uEC0POA5MME5WWKidTVAat09 vRqKtQYgVWP0iBB7Cd2IVcpb2sE6ZpRgsF6K4Nw+brfr68uTk/FvD6kb/7JrpTYd Thkfyh102WQBVZxeTXOo952v1CKv0tAWdxx9/t1boRbCM9cNvDnsjKGzMgRkJ+0r Zx0/A19ORdC7uBn87+uW8Q9CgUIuN+NQuR89OS+nQSZdhnDU8pQgLZR1hoEuYCpO yRmNoIOIMQFnrKKPAqGC =psQ4 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Troy, On 5/13/15 1:55 PM, Troy Robinson wrote: Sorry about that. 'here' was just the Windows Services gui ... by highlighting the new Service called Apache Tomcat 7.0 Tomcat7 and clicking on Start the service. The error is a popup window titles Services with the following content. Windows could not start the Apache Tomcat 7.0 Tomcat7 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1. The Event Log had the following information : Event 7024, Service Control Manager The Apache Tomcat 7.0 Tomcat7 service terminated with the following service-specific error: Incorrect function. I'm no expert, but... This sounds like what might happen if you have a 64-bit OS+service runner, but you have a 32-bit JVM (or vice-versa). Can you double-check that your architectures match-up for all components? The commons-daemon service runner needs to match the architecture of your JVM. Did commons-daemon print anything to its own log files? You can check the configuration for where those log files will be by running Tomcat7w.exe - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVU7VTAAoJEBzwKT+lPKRYSzcQAK6w1LX9UCgQACPNOcZJA27E yZXXsKFD254LCM5Yxc/3cY8khzTps4YBLGkmKEvgN4wU3Saif36TiXaRWUvoF/YM ghlVFNuzbSWIUOV9rIBVWv0MToRWRSo//yCMEfVKQBxV+wXaWMeP8Cv/GKfY2V/X COO++cTkHN0RyzabaKKeua5LiFS1DnGRTv96X6HgTShuGFVj7CoerZSs5w3Afua7 9YXBSOcp510O/VXNAHeyw/aCtRwg18pf5iNHK90W6FqxbLN6L5EGyaZoSrtuEY+p +IPn9H3/ghpdi3FIqH2ymrUeTSn+lB2QpzipVUlDRxw0OoMBbRcj/C/qLmPkIL19 xM9elUGa4BvKVVIUWf8DUBhGDleF/xNFhqg9HwIWd30QrLKwSmP8dKhwIISLVuj8 4oPm4d7cV9f9lK2Y6AQ5YYmLwaD9vm4VODhd6uHyzSm4SHJ+YV5rAwXbZycOYIy0 tVjCJ8ep33F6M62s4Ai0jnd5xZ/yEdQl7K5jJWrBF6ysswB2N/Muwd2NOLWJK7hj 4OVJemrSEofCLlNdxYgTyJcKwd7+XsPFo2N9vxk4ds4ay+RZLoGGtcPcPcvRSdbf W2MPD5jeZAIIM2/WYh9mQMIYJmMygMMqVk+yLSMZnWF3hHhRjlJpmaZ/FYOKhfwv BCFhu1Rtz21EeuUFu0kE =DTex -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 JNDI Realm credential password update availability
John Beaulaurier -X (jbeaulau - ADVANCED NETWORK INFORMATION INC at Cisco) wrote: Hello, We have a Tomcat 7 server running on Linux that must use LDAP over SSL to connect to an AD server for user authentication. This configuration we have working. The issue is the credentials used to connect to the AD server must have the password updated every 180 days, and therefore updated in the JNDI Realm configuration. Is there a way to update the password in server.xml that would allow it to be recognized as changed without restarting the Tomcat server. Or some other configuration what ever it may be that would achieve this. The goal is to update the password and have it recognized as updated with no down time for the application running on the server. Any thoughts would be appreciated. The real issue there, is that the password must be updated every 180 days. That means that to connect to the AD server, you are probably using a normal user account, to which this kind of policy applies. You should probably request a special service account, of which the password does not run out. Yes, such a service account is probably harder to get, and you will probably have to go through some administrative burdens to get it, but that is the right way to run for your Tomcat, which is a service, and which should not be submitted to the same kind of policies as a normal user. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Issues with Tomcat 7.0.57 not loading ActionServlets
Hi Chris, Thanks for your response. Sorry for the late response as I was out of town. I verified struts-config.xml the files and have this plug-in className=org.apache.struts.validator.ValidatorPlugIn set-property property=pathnames value=/org/apache/struts/validator/validator-rules.xml, /WEB-INF/validator-rules.xml / /plug-in There is some changes in Tomcat 5.x and Tomcat 7.x as to how the classes are loaded, I have a feeling that is what is the issue. I changed the context.xml for my app so that loader delegate=true/ so the class loader should behave the same way but the issue is still present. Can you give some more pointers? Thanks Raj On Thu, May 7, 2015 at 6:56 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Raj, On 5/6/15 8:55 PM, Raj wrote: I upgraded my application from tomcat 5.5.15, JDK 1.5, Struts 1.1 on Debian 2.6.32 to tomcat 7.0.57, JDK 1.6, struts 1.1 on ubuntu14.04 and Action Servlets are not loading. I am thinking of this is something to do with version conflict. Please let me know what I am missing. I assure you that Struts 1.1 works on Tomcat 7.0.57 and Java 1.6. What you describe is my production environment, which works quite well. Below is the error Apr 24, 2015 9:00:20 PM org.apache.catalina.core.ApplicationContext log INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: RoundRobinRule@643fd34a] Apr 24, 2015 9:00:20 PM org.apache.catalina.core.ApplicationContext log INFO: Marking servlet action as unavailable Apr 24, 2015 9:00:20 PM org.apache.catalina.core.StandardContext loadOnStartup SEVERE: Servlet threw load() exception javax.servlet.UnavailableException: Cannot load a validator resource from '/WEB-INF/validator-rules.xml' Evidently, you are missing validator-rules.xml from your /WEB-INF/ directory. The Struts validator plug-in uses struts-config.xml to locate the validator-rules.xml file. Look at your web.xml to find out what file Struts is using to load its configuration. You are looking for the config init-param for the org.apache.struts.action.ActionServlet servlet. There may be more than one file listed under config; you'll have to check them all. Look in each of those config files. Look for the string org.apache.struts.validator.ValidatorPlugIn, which will define a plug-in. The pathnames property for the plug-in will list the files that the validator plug-in is going to try to load. All of those files need to be available on the classpath or filesystem. You probably have something like this: plug-in className=org.apache.struts.validator.ValidatorPlugIn set-property property=pathnames value=/org/apache/struts/validator/validator-rules.xml, /WEB-INF/validator-rules.xml / set-property property=stopOnFirstError value=false / /plug-in Check to see that all of those paths point to actual resources that can be loaded from your web application. Note that the first value (/org/apache/struts/validator/validator-rules.xml) is loaded from one of the Struts JAR files. BTW Struts 1-based applications also work just fine on Tomcat 8 and Java 8. Since you are upgrading, you should probably go all the way up. Hope that helps, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVS1LdAAoJEBzwKT+lPKRY0nkP/RL8V6S3QJ7U+ovgLio1igE2 ABq69Mz+fYrhyO7LcAgkQ3WDaYbfPNxPMhIQW+rffLiuEUKj1i5z+b9ow7Ywg21/ BwVeY7BhUHMmeLi3+9YyR4Z8MUL66fsra4r9Ux5QD2z6tMpWLBOOeG+7pn15p5SM 0ad2KlMQwiBFhNmmkf6rrC3Y4zM/XHFveLftJevpK2opeykmLY9bgBxRbZ2vTTAj YAYdaFCiXg+zNVfqbxUGVUmMU6W8W3Lh87cuDiZLsBv39vUWisGIFmF/5ZivIT/J MYTPmD8QP8hSMgILvHGtcDQMVL8XrXXwaP/H4sfMjb0HHlAt29EFBNHE8RPC7S/C EKWZhOlU6YaXagqhImPy/6ZnFHVlIP7TSHPenjziu9aaGHNTJrzxynZcv+F3napG u1MzkTZM3gkgiYfO90ogykOQm7mDjywAV+P4K3n53mf5pvAoZVJ/jpB+mQd+Z9e+ zthzYrREIwD7tEHcKIU3T950t7pDqv1Qu4999QKtcw0Tgr/tnLsm1eub5o+8Nfa/ YHOOe7yP4A9u0Olpd0i90aLi0+dfu0Qx5M6cAigwVvwvMwa9sleyuEm+f+RkUC7H sLP4R3i6V1Ch2zyJQKtfpuicfjuw4kXMGEVY1nrrWxpKiFxpKr0okfDybkb/uonD yuzDyjsDnJg3B+Ad6ZZe =5Jwr -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.57 - Deployment Issue
Thanks *Jeffrey Janner *and *Mark Eggers*, I was able to deploy the app successfully in its own virtual host. Actually I think apache httpd was interfering somewhere and I raised the support ticket with my provider.I think they made some changes to host file and it started working. I had done same set up as given in the link by Charles.Now it works like a charm and I also have manager interface to upload war files :) Sometimes I get this error while using manager interface, “Error invoking method check” when deploying a WAR on Tomcat http://stackoverflow.com/questions/1536364/error-invoking-method-check-when-deploying-a-war-on-tomcat But deployment happens quite successfully but it does not start the app. Need to restart the server fix this. Quick google search showed me that its related to OOM. Is this related to manager app or tomcat is starving of memory? On Wed, May 13, 2015 at 11:17 AM, Jeffrey Janner jeffrey.jan...@polydyne.com wrote: -Original Message- From: Kiran Badi [mailto:ki...@poonam.org] Sent: Tuesday, May 12, 2015 9:30 PM To: Tomcat Users List Subject: Re: Tomcat 7.0.57 - Deployment Issue Thanks Hassan/Prabhu/Charles for reply. I tried the options given in this link. http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts but for some reasons still its not working.I have pasted the server xml for reference. I have unlimited website hosting plan with arvixe.com , but for some reasons it's still not working.Not sure if these guys needs to add something special to hosts file. here is link for actual site - homelyhotels.com - you will probably see cgi-bin folder. Below server xml, I have added just a second host tag for webapp2. I am bit hesitant to make changes wrt to webapp1(removing context tags etc due to lack of time on my end along with lack of sufficient knowledge in case something breaks,however I will eventually clean that as well). ... !-- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). Documentation at /docs/config/engine.html -- !-- You should set jvmRoute to support load-balancing via AJP ie : Engine name=Catalina defaultHost=localhost jvmRoute=jvm1 -- Engine name=Catalina defaultHost=localhost !--For clustering, please take a look at documentation at: /docs/cluster-howto.html (simple how to) /docs/config/cluster.html (reference documentation) -- !-- Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster/ -- !-- Use the LockOutRealm to prevent attempts to guess user passwords via a brute-force attack -- Realm className=org.apache.catalina.realm.LockOutRealm !-- This Realm uses the UserDatabase configured in the global JNDI resources under the key UserDatabase. Any edits that are performed against this UserDatabase are immediately available for use by the Realm. -- Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase/ /Realm Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true !-- SingleSignOn valve, share authentication between web applications Documentation at: /docs/config/valve.html -- !-- Valve className=org.apache.catalina.authenticator.SingleSignOn / -- !-- Access log processes all example. Documentation at: /docs/config/valve.html Note: The pattern used is equivalent to using pattern=common -- Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=localhost_access_log. suffix=.txt pattern=%h %l %u %t quot;%rquot; %s %b / /Host Host name=webapp1 appBase=/home/myhostid/tomcat/webapps Aliaswww.webapp1.com/Alias Aliasmyhostid.myserver.mywebhost.com/Alias Context path=/manager debug=0 privileged=true docBase=/home/myhostid/tomcat/webapps/manager /Context /Host Host name=webapp2.com appBase=/home/myhostid/hosts/webapp2/webapps xmlValidation=false xmlNamespaceAware=false unpackWARs=true autoDeploy=true Aliaswww.webapp2.com/Alias Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=webapp2_access_log. suffix=.txt pattern=%h %l %u %t quot;%rquot; %s %b / /Host /Engine /Service /Server Kiran - What no one has asked about yet is this: What does your directory structure look
Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service
Hi, System: Windows Server 2012 Standard Apache Tomcat 7.0.59 Java jre 7 I'm experiencing an issue ... where Apache Tomcat will start fine using : %CATALINA_HOME%\bin\startup.bat But if use : %CATALINA_HOME%\bin\service.bat install The Service does now show up in the Windows Services gui but when I start it from here I get the following error : [image: Inline image 1] Any advice/suggestions/help greatly appreciated. Thanks -- Troy Robinson Programmer Analyst SaskTel Phone (306) 777-5491; Mobile (306) 531-3810 Email: troy.robin...@sasktel.com Right Solution, Right Time -- *NOTICE: This confidential e-mail message is only for the intended recipients. If you are not the intended recipient, be advised that disclosing, copying, distributing, or any other use of this message, is strictly prohibited. In such case, please destroy this message and notify the sender.*
RE: Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service
From: Troy Robinson [mailto:troy.robin...@sasktel.com] Subject: Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service Windows Server 2012 Standard Apache Tomcat 7.0.59 Java jre 7 Thanks for specifying the above; many people forget. I'm experiencing an issue ... where Apache Tomcat will start fine using : %CATALINA_HOME%\bin\startup.bat Good so far. But if use : %CATALINA_HOME%\bin\service.bat install The Service does now show up in the Windows Services gui but when I start it from here Where is here? I get the following error : Most attachments are automatically stripped by the list server, so you'll need to paste text, not an image. - 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: Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service
Hi, Sorry about that. 'here' was just the Windows Services gui ... by highlighting the new Service called Apache Tomcat 7.0 Tomcat7 and clicking on Start the service. The error is a popup window titles Services with the following content. Windows could not start the Apache Tomcat 7.0 Tomcat7 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1. The Event Log had the following information : Event 7024, Service Control Manager The Apache Tomcat 7.0 Tomcat7 service terminated with the following service-specific error: Incorrect function. On Wed, May 13, 2015 at 11:39 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Troy Robinson [mailto:troy.robin...@sasktel.com] Subject: Problem : Apache Tomcat 7.0 starts up fine using startup scripts; error when starting as Windows Service Windows Server 2012 Standard Apache Tomcat 7.0.59 Java jre 7 Thanks for specifying the above; many people forget. I'm experiencing an issue ... where Apache Tomcat will start fine using : %CATALINA_HOME%\bin\startup.bat Good so far. But if use : %CATALINA_HOME%\bin\service.bat install The Service does now show up in the Windows Services gui but when I start it from here Where is here? I get the following error : Most attachments are automatically stripped by the list server, so you'll need to paste text, not an image. - 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 -- Troy Robinson Programmer Analyst SaskTel Phone (306) 777-5491; Mobile (306) 531-3810 Email: troy.robin...@sasktel.com Right Solution, Right Time -- *NOTICE: This confidential e-mail message is only for the intended recipients. If you are not the intended recipient, be advised that disclosing, copying, distributing, or any other use of this message, is strictly prohibited. In such case, please destroy this message and notify the sender.*
Tomcat 7 JNDI Realm credential password update availability
Hello, We have a Tomcat 7 server running on Linux that must use LDAP over SSL to connect to an AD server for user authentication. This configuration we have working. The issue is the credentials used to connect to the AD server must have the password updated every 180 days, and therefore updated in the JNDI Realm configuration. Is there a way to update the password in server.xml that would allow it to be recognized as changed without restarting the Tomcat server. Or some other configuration what ever it may be that would achieve this. The goal is to update the password and have it recognized as updated with no down time for the application running on the server. Any thoughts would be appreciated. Thanks -John
String Cache Configuration
Hello, Can anyone give me more information on what the String Cache Configuration does? This is a setting in the catalina.properties file. I searched the web and it does not give much info on the tomcat document site (https://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html). # String cache configuration. tomcat.util.buf.StringCache.byte.enabled=true Thank you, Thone
