Thanks for response. I alredy use netstat and not appear nothing of strange.I have connection on IPV4/IPV6 it look as:
Proto Indirizzo locale Indirizzo esterno Stato TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:443 0.0.0.0:0 LISTENING TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:3873 0.0.0.0:0 LISTENING TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING TCP 0.0.0.0:4446 0.0.0.0:0 LISTENING TCP 0.0.0.0:4999 0.0.0.0:0 LISTENING TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING TCP 0.0.0.0:49159 0.0.0.0:0 LISTENING TCP 0.0.0.0:61028 0.0.0.0:0 LISTENING TCP 0.0.0.0:61029 0.0.0.0:0 LISTENING TCP 0.0.0.0:61030 0.0.0.0:0 LISTENING TCP 0.0.0.0:61032 0.0.0.0:0 LISTENING TCP 127.0.0.1:1433 127.0.0.1:61047 ESTABLISHED TCP 127.0.0.1:1433 127.0.0.1:61048 ESTABLISHED TCP 127.0.0.1:1434 0.0.0.0:0 LISTENING TCP 127.0.0.1:61047 127.0.0.1:1433 ESTABLISHED TCP 127.0.0.1:61048 127.0.0.1:1433 ESTABLISHED TCP 192.160.0.200:139 0.0.0.0:0 LISTENING TCP 192.160.0.200:3389 192.168.0.18:29440 ESTABLISHED TCP 192.160.0.200:61013 192.160.0.223:445 ESTABLISHED TCP [::]:80 [::]:0 LISTENING TCP [::]:135 [::]:0 LISTENING TCP [::]:443 [::]:0 LISTENING TCP [::]:1098 [::]:0 LISTENING TCP [::]:1099 [::]:0 LISTENING TCP [::]:1433 [::]:0 LISTENING TCP [::]:3389 [::]:0 LISTENING TCP [::]:3873 [::]:0 LISTENING TCP [::]:4444 [::]:0 LISTENING TCP [::]:4445 [::]:0 LISTENING TCP [::]:4446 [::]:0 LISTENING TCP [::]:8009 [::]:0 LISTENING TCP [::]:8083 [::]:0 LISTENING TCP [::]:8093 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49155 [::]:0 LISTENING TCP [::]:49159 [::]:0 LISTENING TCP [::]:61028 [::]:0 LISTENING TCP [::]:61029 [::]:0 LISTENING TCP [::]:61030 [::]:0 LISTENING TCP [::]:61032 [::]:0 LISTENING TCP [::1]:1434 [::]:0 LISTENING UDP 0.0.0.0:123 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 127.0.0.1:51207 *:* UDP 127.0.0.1:51211 *:* UDP 127.0.0.1:61591 *:* UDP 192.160.0.200:137 *:* UDP 192.160.0.200:138 *:* UDP [::]:123 *:* UDP [::]:500 *:* Ok the actul situation is: JBOSS on port 80 (i start jboss service with bind=0.0.0.0) other port 80 also port 443 i have enable. So the actul connector configuration in C:\jboss-4.2.3.GA\server\default\deploy\jboss-web. deployer\server are: <Connector port="80" address="${jboss.bind.address}" minSpareThreads="50" maxSpareThreads="150" maxThreads="350" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="443" acceptCount="200" connectionTimeout="20000" disableUploadTimeout="true" /> .... <Connector port="443" address="${jboss.bind.address}" protocol="HTTP/1.1" SSLEnabled="true" minSpareThreads="25" maxSpareThreads="100" maxThreads="250" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="C:\CertificatiHTTPS\aa.pfx" keystorePass="xxx" keystoreType="PKCS12" /> ... <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" redirectPort="443" /> This last connector is the default connector th i don't modify. Every morning at 6.30 AM i stop jboss and at 6.35 AM start jboss the log on startup is similar to: Starting JBoss Application Server 4.2.3 [2010-05-23 20:50:49] =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: C:\jboss-4.2.3.GA JAVA: C:\jdk1.6\bin\java JAVA_OPTS: -Dcom.sun.management.jmxremote -Xrs -Dprogram.name=run.bat - server -Xms384m -Xmx1024m -XX:MaxPermSize=128m -Dsun.rmi.dgc.client. gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: C:\jdk1.6\lib\tools.jar;C:\jboss-4.2.3.GA\bin\run.jar =============================================================================== 20:50:49,560 INFO [Server] Starting JBoss (MX MicroKernel)... 20:50:49,560 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417) 20:50:49,560 INFO [Server] Home Dir: C:\jboss-4.2.3.GA 20:50:49,560 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/ 20:50:49,560 INFO [Server] Patch URL: null 20:50:49,560 INFO [Server] Server Name: default 20:50:49,560 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default 20:50:49,560 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3. GA/server/default/ 20:50:49,560 INFO [Server] Server Log Dir: C:\jboss-4.2.3. GA\server\default\log 20:50:49,560 INFO [Server] Server Temp Dir: C:\jboss-4.2.3. GA\server\default\tmp 20:50:49,560 INFO [Server] Root Deployment Filename: jboss-service.xml 20:50:49,747 INFO [ServerInfo] Java version: 1.6.0_16,Sun Microsystems Inc. 20:50:49,747 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.2-b01, Sun Microsystems Inc. 20:50:49,747 INFO [ServerInfo] OS-System: Windows Server 2008 6.0,x86 20:50:50,043 INFO [Server] Core system initialized 20:50:51,603 INFO [WebService] Using RMI server codebase: http://cup_new: 8083/ 20:50:51,603 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 20:50:51,900 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 20:50:51,900 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 20:50:52,040 INFO [TransactionManagerService] Starting recovery manager 20:50:52,118 INFO [TransactionManagerService] Recovery manager started 20:50:52,118 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 20:50:53,881 INFO [EJB3Deployer] Starting java:comp multiplexer 20:50:55,472 INFO [NativeServerConfig] JBoss Web Services - Native 20:50:55,472 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044) 20:50:56,127 INFO [Embedded] Catalina naming disabled 20:50:56,236 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\jdk1.6\bin;.;C:\Windows\Sun\Java\bin;C: \Windows\system32;C:\Windows;C:\oracle\product\10.2.0\client_3\bin;C: \oracle\product\10.2.0\client_1;C:\oracle\product\10.2.0\client_2;C: \Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C: \Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C: \Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;C:\jdk1. 6\bin 20:50:56,268 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http- 0.0.0.0-80 20:50:56,720 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http- 0.0.0.0-443 20:50:56,736 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0- 8009 20:50:56,736 INFO [Catalina] Initialization processed in 606 ms 20:50:56,736 INFO [StandardService] Starting service jboss.web 20:50:56,736 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1. GA 20:50:56,767 INFO [Catalina] Server startup in 32 ms 20:50:56,829 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss- web.deployer/ROOT.war/ 20:50:57,219 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=... /deploy/http-invoker.sar/invoker.war/ 20:50:57,313 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=... /deploy/jbossws.sar/jbossws-context.war/ 20:50:57,422 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=... /deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 20:50:57,890 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=... /deploy/management/console-mgr.sar/web-console.war/ 20:50:58,186 INFO [MailService] Mail Service bound to java:/Mail 20:50:58,280 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar 20:50:58,296 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar 20:50:58,327 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/jboss-local-jdbc.rar 20:50:58,342 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/jboss-xa-jdbc.rar 20:50:58,389 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/jms/jms-ra.rar 20:50:58,436 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/mail-ra.rar 20:50:58,467 INFO [RARDeployment] Required license terms exist, view META- INF/ra.xml in .../deploy/quartz-ra.rar 20:50:58,467 INFO [QuartzResourceAdapter] start quartz!!! 20:50:58,514 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main 20:50:58,530 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 20:50:58,530 INFO [RAMJobStore] RAMJobStore initialized. 20:50:58,530 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' 20:50:58,530 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 20:50:58,530 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 20:50:58,951 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java: DefaultDS' 20:50:59,154 INFO [A] Bound to JNDI name: queue/A 20:50:59,154 INFO [B] Bound to JNDI name: queue/B 20:50:59,154 INFO [C] Bound to JNDI name: queue/C 20:50:59,154 INFO [D] Bound to JNDI name: queue/D 20:50:59,154 INFO [ex] Bound to JNDI name: queue/ex 20:50:59,185 INFO [testTopic] Bound to JNDI name: topic/testTopic 20:50:59,185 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 20:50:59,185 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 20:50:59,185 INFO [testQueue] Bound to JNDI name: queue/testQueue 20:50:59,216 INFO [UILServerILService] JBossMQ UIL service available at : /0. 0.0.0:8093 20:50:59,232 INFO [DLQ] Bound to JNDI name: queue/DLQ 20:50:59,325 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java: JmsXA' 20:50:59,341 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/SIT. war/ 20:50:59,466 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=... /deploy/jmx-console.war/ 20:51:00,526 INFO [TomcatDeployer] deploy, ctxPath=/probe, warUrl=... /tmp/deploy/tmp3011910486448452255probe-exp.war/ 20:51:00,729 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0- 80 20:51:00,745 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0- 443 20:51:00,760 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009 20:51:00,760 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 11s:200ms 20:52:33,144 INFO [STDOUT] ------ %%%%%%%%%%%% pocs_blogin %%%%%%%%%%% ------- 20:52:33,144 INFO [STDOUT] Blocco - TOT, ing di solo su e sysdm abilitato, msg: ,Si avvertono tutti gli operatori che .... C: \tomcat\webapps\SIT\Export\ 20:52:33,160 INFO [STDOUT] pocs_blogin strAppart - strAfferenz: - 20:52:33,160 INFO [STDOUT] pocs_blogin gDistrAA=%gStruttSA=%gDistrPS=% gStrSDO=% gCom:% Grp:1.0 gLoc:% tim:2010-05-23 20:52:33.0 20:52:33,175 INFO [STDOUT] IP Host connesso:93.41.28.195 sessione: DD1C807C875BABAAAC0A5BC6B55798BC 20:52:33,191 INFO [STDOUT] ====> Classe di Utenti: 08 20:52:33,253 INFO [STDOUT] == fn_leggi_ultimi_log == nlog passato 3.0 record contati:0.0 uteSIT:7.0 20:52:33,441 INFO [STDOUT] === fn_recupera_msg_new === user,codMsg: 7.0,0.0 idMsg recuperato: 0 20:52:34,345 INFO [STDOUT] == fn_recupera_ODBC_da_dbconfig == Svilupp -93.41.28.195 ^JDBCConnectionURL.1=jdbc\:sqlserver\://localhost\:1433; DatabaseName\=SIT 20:52:55,780 INFO [STDOUT] Stringa 1 Disp ASSOLUTA: 3411020004042010-05-2408: 00 20:53:32,331 INFO [STDOUT] == fn_numtot_prestaz_prenotabili == 20:53:32,768 INFO [STDOUT] Num Prestaz prenotabili da tutti: NAZ, NAZdist, SPICCADist:3166.0,429.0,146.0 20:53:32,768 INFO [STDOUT] ritorno: 000031660000042900000146 20:53:35,248 INFO [STDOUT] == fn_numtot_prestaz_prenotabili == 20:53:35,342 INFO [STDOUT] Num Prestaz prenotabili da tutti: NAZ, NAZdist, SPICCADist:3166.0,429.0,146.0 20:53:35,342 INFO [STDOUT] ritorno: 00003166000004290000014..... ....... sometimes after some STDOUT (that are print from my appliction) i have, especially when the number of user increase around to 8.30 AM (two o tree user not arise problem): ERROR [org.apache.tomcat.util.net.JIoEndpoint] Socket accept failed java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket (DefaultServerSocketFactory.java:61) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java: 309) at java.lang.Thread.run(Thread.java:619) When this occours the page of my appliction initially freeze but when the number of error increase the connector on port 80 block completely web-console or jmx-consolw of jboss. The connector on port 443 stays alive for other few minutes and after also this is blocked. Have you some ideas? In the past the max number of thread used in tomct 5.5.28 (view with probe) were about 130. Can you suggest me some investigation for resolve the problem? I thinking of do more strong my configuration i'd like install Tomct 6.0.26 and my be ApacheHTTPD server in front. Is this a good idea? Best regards Agostino >----Messaggio originale---- >Da: p...@pidster.com >Data: 23/05/2010 13.12 >A: "Tomcat Users List"<users@tomcat.apache.org> >Ogg: Re: intermittent SocketException on startup tomcat 5.5.28 and under JBOSS 4.2.3GA > >On 22/05/2010 23:23, ago...@libero.it wrote: >> >> Thanks for response. >> >> The first server on I install tomcat 5.5.28 is win2003 server and after I >> install jboss on win2008 server . >> All server have 32bit SO and i don't have a firewall . I disenable all >> firewall, all antivirus. >> >> I suppose that two different errors regard different JVM and/or Application >> server (first Tomct 5.5.28 on win2003 and after Jboss4.2.3GA on win2008) >> At any rate i have now only log by Tomcat 5.5.28 under win2003: > > >> But don't have a intere log file. >> May be IPV6? I don't disinstall this protocol becuse is important on win2008, >> but i hve clent that use IPV4. > >Do you have any other services running on the server that might >interfere with this one, by binding to the ports you have configured? > >Try using the "netstat" command to see what ports and addresses the >server is listening on. > > http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en- us/netstat.mspx?mfr=true > >To eliminate the ip4/ip6 problem, you can specify an address="n.n.n.n" >for the connector to bind to, in server.xml. (where n.n.n.n is the IP >v4 address assigned to your server). > > >p > >> Have you n idea? >> How can resolve problem. >> Plese is imporatnt for me? >> >>> ----Messaggio originale---- >>> Da: p...@pidster.com >>> Data: 22/05/2010 12.47 >>> A: "Tomcat Users List"<users@tomcat.apache.org> >>> Ogg: Re: intermittent SocketException on startup tomcat 5.5.28 and under >> JBOSS 4.2.3GA >>> >>> On 22/05/2010 09:28, ago...@libero.it wrote: >>>> Good Morning >>>> >>>> Excuse for my poor english >>>> >>>> I have a strange error that occours on startup and after some minutes >> this >>>> cause the block of my appliction, only stop webserver from lot minutes or >>>> restart server sometime resolve the problem. But often the problem >> persist. >>>> >>>> In Short: >>>> I have a web appliction deployed initially under tomcat 5.5.28 (with jre- >>>> 1_5_0_22 and SO win2003 Server 32 bit) that sometimes cause specially on >>>> startup the follow error: >>>> >>>> 17-apr-2010 7.00.49 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0, >> localport=443]] >>>> ignored exception: java.net.SocketException: socket closed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) >>>> at java.net.PlainSocketImpl.accept(Unknown Source) >>>> at java.net.ServerSocket.implAccept(Unknown Source) >>>> at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) >>>> at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket >>>> (JSSESocketFactory.java:117) >>>> at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket (PoolTcpEndpoint. >>>> java:408) >>>> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt >>>> (LeaderFollowerWorkerThread.java:71) >>>> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPool. >>>> java:689) >>>> at java.lang.Thread.run(Unknown Source) >>>> 17-apr-2010 7.01.10 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> AVVERTENZA: Reinitializing ServerSocket >>>> 17-apr-2010 7.52.33 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0, >> localport=443]] >>>> ignored exception: java.net.SocketException: socket closed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) >>>> at java.net.PlainSocketImpl.accept(Unknown Source) >>>> at java.net.ServerSocket.implAccept(Unknown Source) >>>> at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) >>>> at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket >>>> (JSSESocketFactory.java:117) >>>> at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket (PoolTcpEndpoint. >>>> java:408) >>>> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt >>>> (LeaderFollowerWorkerThread.java:71) >>>> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPool. >>>> java:689) >>>> at java.lang.Thread.run(Unknown Source) >>>> 17-apr-2010 7.52.54 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> AVVERTENZA: Reinitializing ServerSocket >>>> 17-apr-2010 7.52.55 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0, >> localport=443]] >>>> ignored exception: java.net.SocketException: socket closed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) >>>> at java.net.PlainSocketImpl.accept(Unknown Source) >>>> at java.net.ServerSocket.implAccept(Unknown Source) >>>> at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) >>>> at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket >>>> (JSSESocketFactory.java:117) >>>> at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket (PoolTcpEndpoint. >>>> java:408) >>>> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt >>>> (LeaderFollowerWorkerThread.java:71) >>>> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPool. >>>> java:689) >>>> at java.lang.Thread.run(Unknown Source) >>>> 17-apr-2010 7.53.16 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> AVVERTENZA: Reinitializing ServerSocket >>>> 17-apr-2010 7.53.17 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0, >> localport=443]] >>>> ignored exception: java.net.SocketException: socket closed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) >>>> at java.net.PlainSocketImpl.accept(Unknown Source) >>>> at java.net.ServerSocket.implAccept(Unknown Source) >>>> at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source) >>>> at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket >>>> (JSSESocketFactory.java:117) >>>> at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket (PoolTcpEndpoint. >>>> java:408) >>>> at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt >>>> (LeaderFollowerWorkerThread.java:71) >>>> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >> (ThreadPool. >>>> java:689) >>>> at java.lang.Thread.run(Unknown Source) >>>> 17-apr-2010 7.53.38 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> AVVERTENZA: Reinitializing ServerSocket >>>> 17-apr-2010 7.53.39 org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket >>>> GRAVE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0, >> localport=443]] >>>> ignored exception: java.net.SocketException: socket closed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) ..... >>>> >>>> in tomcat server.xml i have configured 2 connector: one su port 80 and >> other >>>> on port 443, The connectors configuration is: >>>> >>>> Connector port="80" maxHttpHeaderSize="8192" >>>> maxThreads="350" minSpareThreads="25" maxSpareThreads=" 100" >>>> enableLookups="false" redirectPort="443" acceptCount=" 100" >>>> connectionTimeout="20000" disableUploadTimeout="true" /> >>>> ....... >>>> >>>> <Connector port="443" maxHttpHeaderSize="8192" >>>> maxThreads="150" minSpareThreads="25" maxSpareThreads=" 75" >>>> enableLookups="false" disableUploadTimeout="true" >>>> acceptCount="100" scheme="https" secure="true" >>>> clientAuth="false" sslProtocol="TLS" >>>> keystoreFile="C:\CertificatiHTTPS\aaa.pfx" >>>> keystorePass="xxx" >>>> keystoreType="PKCS12" >>>> /> >>>> >>>> This problem never occours in the past but arise after we transfer the >> router >>>> from site to another. After this transfer sometime occours the error, It's >>>> strange. The HW,SW is the same and number of Users is bout the same. >>>> >>>> So we think to upgrade in tecnology and after installed jdk 1.6.16 and >> JBOSS4. >>>> 2.3 and deployed the same web application the problem sometime occours >>>> (specially in first 5 minutes on startup.. NOTE in jBOSS we change >>>> JAVA_OPTIONS : -Xms384m -Xmx1024m -XX:MaxPermSize=128m only ) the error is: >>>> >>>> 010-05-17 12:53:24,112 ERROR [org.apache.tomcat.util.net.JIoEndpoint] >> Socket >>>> accept failed >>>> java.net.SocketException: socket closed >>>> at java.net.PlainSocketImpl.socketAccept(Native Method) >>>> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390) >>>> at java.net.ServerSocket.implAccept(ServerSocket.java:453) >>>> at java.net.ServerSocket.accept(ServerSocket.java:421) >>>> at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket >>>> (DefaultServerSocketFactory.java:61) >>>> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java: >> 309) >>>> at java.lang.Thread.run(Thread.java:619) >>>> 2010-05-17 12:53:24,127 ERROR [org.apache.tomcat.util.net.JIoEndpoint] >> Socket >>>> accept failed >>>> >>>> in this case we have the same configuration of tomcat connector under >> jboss >>>> (file C:\jboss-4.2.3.GA\server\default\deploy\jboss-web.deployer\server. >> xml): >>>> >>>> <Connector port="80" address="${jboss.bind.address}" >>>> minSpareThreads="25" maxSpareThreads="100" >>>> maxThreads="350" maxHttpHeaderSize="8192" >>>> emptySessionPath="true" protocol="HTTP/1.1" >>>> enableLookups="false" redirectPort="443" acceptCount="200" >>>> connectionTimeout="20000" disableUploadTimeout="true" /> >>>> .... >>>> <Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" >>>> minSpareThreads="25" maxSpareThreads="100" >>>> maxThreads="250" scheme="https" secure="true" >>>> clientAuth="false" sslProtocol="TLS" >>>> keystoreFile="C:\CertificatiHTTPS\aaa.pfx" >>>> keystorePass="xxx" >>>> keystoreType="PKCS12" >>>> /> >>>> >>>> Can anyone help me because the problem is present in production enviroment. >>> >>> >>> If I'm reading the stack trace correctly, the listening socket is being >>> closed shortly after being opened. Do you have a firewall that is >>> blocking the port perhaps? >>> >>> If you start a completely new log file, what messages appear before the >>> error appears? >>> >>> >>> p >>> >>>> thanks a lot for every hint . >>>> >>>> Agostino >>>> >>>> --------------------------------------------------------------------- >>>> 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 >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org