This looks important. After restarting our server tonight, I notice this is in the Tomcat catalina.2013-11-28.log file...
> Nov 28, 2013 8:41:20 PM org.apache.coyote.http11.Http11Protocol pause > INFO: Pausing Coyote HTTP/1.1 on http-8888 > Nov 28, 2013 8:41:20 PM org.apache.catalina.connector.Connector pause > SEVERE: Protocol handler pause failed > java.net.UnknownHostException: augent3.mfst.net: augent3.mfst.net > at java.net.InetAddress.getLocalHost(InetAddress.java:1354) > at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:490) > at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:289) > at org.apache.jk.server.JkMain.pause(JkMain.java:725) > at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153) > at org.apache.catalina.connector.Connector.pause(Connector.java:1029) > at org.apache.catalina.core.StandardService.stop(StandardService.java:566) > at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744) > at org.apache.catalina.startup.Catalina.stop(Catalina.java:648) > at > org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:692) > Nov 28, 2013 8:41:21 PM org.apache.catalina.core.StandardService stop > INFO: Stopping service Catalina > Nov 28, 2013 8:41:21 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/host-manager] appears to have started a > thread named [CronPluginThread] but has failed to stop it. This is very > likely to create a memory leak. > Nov 28, 2013 8:41:21 PM org.apache.coyote.http11.Http11Protocol destroy > INFO: Stopping Coyote HTTP/1.1 on http-8888 > Nov 28, 2013 8:43:10 PM org.apache.catalina.core.AprLifecycleListener init > INFO: The APR based Apache Tomcat Native library which allows optimal > performance in production environments was not found on the > java.library.path: > /opt/openbd/jdk/jre/lib/i386/server:/opt/openbd/jdk/jre/lib/i386:/opt/openbd/jdk/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib > Nov 28, 2013 8:43:13 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-8888 > Nov 28, 2013 8:43:13 PM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 8427 ms > Nov 28, 2013 8:43:13 PM org.apache.catalina.core.StandardService start > INFO: Starting service Catalina > Nov 28, 2013 8:43:13 PM org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 > Nov 28, 2013 8:43:20 PM org.apache.commons.vfs.VfsLog info > INFO: Using "/opt/openbd/tomcat/temp/vfs_cache" as temporary files store. > Nov 28, 2013 8:43:48 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory other > Nov 28, 2013 8:43:48 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory bluedragon ... Any thoughts on what the error means and if it could be related to our troubles? On Wednesday, November 27, 2013 1:44:03 PM UTC-5, [email protected] wrote: > Hi there. Our web application is on CentOS Linux 5.9 and we are using > Apache, Tomcat, MySQL, and OpenBD. Unfortunately I can't find where to > tell what version of OpenBD we're currently on. Our application is very > AJAX-intensive (hand-written in JavaScript, no JSON), and at peak hours we > receive several dozen web requests per minute. Over the past few weeks we > have been receiving more and more complaints of random errors with > increasing frequency. It has been incredibly hard to duplicate these > errors since they seem to follow no rhyme or reason and can happen anywhere > on the site at any time. We also receive complaints about the pages often > running very slow even though their and our network connections seem > perfectly fine. I have finally observed that many of the errors coming > from Ajax simply report "NetworkError". > > We noticed our Bluedragon logs were filling up rapidly (25 mb) with tons > of... > > 11/06/13 14:26.46: Error decoding CLIENT data: > java.lang.ArrayIndexOutOfBoundsException > > So in bluedragon.xml (never could get the administrator to work on this > build for some reason), we changed our <clientstorage> from local to our > datasource, and that stopped these errors. However, the problems for our > clients have only continued to grow. I did a netstat on our server, and we > seem to have about 70 or so of these from various IP addresses... > > tcp 0 0 www.ourwebsite.net:https (ip address):17168 > TIME_WAIT > > I'm not sure if that is a lot or not, but our current reigning theory is > that the connections are maxing out and not clearing fast enough. That > would at least explain the random nature of the network errors. I found a > post about Tomcat where someone mentions solving a similar issue by > changing the following... > > 1) Changing the maxWait parameter in the context.xml file to "15" (15sec) > to remove the closed connection. > 2) Changed the removeAbandonedTimeout to "15" from 60 to lessen the time > that the closed connections are removed > 3) Changed the timeBetweenEvictionRunsMillis from 180000 to 900 > > However, I cannot find these fields in > \\opt\openbd\tomcat\conf\context.xml. I can't find them anywhere. Can > someone please help me figure out where to change these values or offer > other suggestions of what might be wrong? > > - Matt C > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
