Bug 1075695 - Cannot reload server welcome page after server reload
Summary: Cannot reload server welcome page after server reload
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER2
: EAP 6.3.0
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
Russell Dickenson
URL:
Whiteboard:
: 1074640 1081036 (view as bug list)
Depends On: 1083568
Blocks: eap63-beta-blockers 1081009 1085844
TreeView+ depends on / blocked
 
Reported: 2014-03-12 15:31 UTC by Petr Kremensky
Modified: 2014-06-28 15:30 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-28 15:30:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1090291 0 unspecified CLOSED java.nio.channels.ShutdownChannelGroupException during shutdown on Windows 2021-02-22 00:41:40 UTC

Internal Links: 1090291

Description Petr Kremensky 2014-03-12 15:31:41 UTC
Description of problem:
 Reload operation seem to be breaking the web subsystem. I didn't find other components affected by reload so far.

Version-Release number of selected component (if applicable):
 EAP 6.3.0.DR3

How reproducible:
 Always

Steps to Reproduce:
 1. Start the standalone server.
 2. Reload the server via CLI
 3. Open browser in http://localhost:8080/ and reload the page for a several times (Ctrl + R).

Actual results:
Server throws ERROR message with every page reload. 
16:23:04,521 ERROR [stderr] (Thread-126) Exception in thread "Thread-126" java.nio.channels.ShutdownChannelGroupException
16:23:04,522 ERROR [stderr] (Thread-126) 	at sun.nio.ch.Invoker.invokeIndirectly(Invoker.java:210)
16:23:04,522 ERROR [stderr] (Thread-126) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishRead(UnixAsynchronousSocketChannelImpl.java:432)
16:23:04,522 ERROR [stderr] (Thread-126) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:191)
16:23:04,523 ERROR [stderr] (Thread-126) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
16:23:04,523 ERROR [stderr] (Thread-126) 	at sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:293)
16:23:04,523 ERROR [stderr] (Thread-126) 	at java.lang.Thread.run(Thread.java:724)

Expected results:
 No error messages.

Additional info:
 Regression introduced in EAP 6.3.0.DR2. 
 I was able to reproduce it also with some testing application (not an issue of welcome page itself)

Comment 1 Petr Kremensky 2014-03-13 07:33:18 UTC
Reproduced also with DR4. Issue is happening only with jdk17+

Unable to reproduce with:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)

Reproduced with:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b128)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b69, mixed mode)

Comment 2 Jean-frederic Clere 2014-03-13 07:51:15 UTC
It is linked with the new NIO2 connector apparently.

Comment 3 Petr Kremensky 2014-03-13 11:15:00 UTC
I saw this also during clean EAP startup tests during shutdown.

Comment 4 Jean-frederic Clere 2014-03-13 16:22:47 UTC
fixed in jbossweb by r2389

Comment 5 Michal Karm Babacek 2014-03-13 16:47:49 UTC
*** Bug 1074640 has been marked as a duplicate of this bug. ***

Comment 6 Michal Karm Babacek 2014-03-13 16:58:26 UTC
Simple search for ShutdownChannelGroupException would have revealed the former bugzilla and saved us some tormenting bewilderedness :-)

Comment 7 Michal Karm Babacek 2014-03-14 19:47:15 UTC
{noformat}
INFO  [org.apache.coyote.http11.Http11NioProtocol] (MSC service thread 1-16) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.88.17:8080
INFO  [org.apache.coyote.http11.Http11NioProtocol] (MSC service thread 1-16) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.88.17:8080
ERROR [org.apache.tomcat.util.net] (http-/10.16.88.17:8080-Acceptor) JBWEB003011: Error allocating socket processor: java.util.concurrent.RejectedExecutionException: Task org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor@5eb732bc rejected from java.util.concurrent.ThreadPoolExecutor@4d640538[Shutting down, pool size = 3, active threads = 0, queued tasks = 0, completed tasks = 4]
    at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) [rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) [rt.jar:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) [rt.jar:1.7.0_45]
    at org.apache.tomcat.util.net.NioEndpoint.processChannel(NioEndpoint.java:453) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
    at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:566) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
{noformat}

Related stuff? Clean shutdown, no load, several requests made. Oracle JDK 1.7., RHEL7 x86_64.

Comment 8 Petr Sakař 2014-03-18 12:18:11 UTC
The issue is present as intermittent failures in JBossWS testsuite as well. It causes test failures Caused by: java.net.SocketTimeoutException: Read timed out

Example:
Server log:
[0m[0m11:35:46,919 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.Alpha1 (AS 7.4.0.Final-redhat-4) started in 154ms - Started 154 of 192 services (56 services are lazy, passive or on-demand)
[0mWARN: can't find jboss-cli.xml. Using default configuration values.
Mar 18, 2014 11:35:47 AM org.jboss.qa.management.ws.cli.CLITestUtils info
INFO: Execute CLI command deploy /tmp/CLIWebServicesEndPointConfigIT.war
[0m11:35:47,796 INFO  [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/development/jbossqe/JBEAP-6.3.0.DR4/build/jboss-eap-6.3/standalone/data/content/25/dff6d5288ea4b7a7935a9caf49cf3407c507c0/content
[0m[0m11:35:47,799 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "CLIWebServicesEndPointConfigIT.war" (runtime-name: "CLIWebServicesEndPointConfigIT.war")
[0m[0m11:35:47,838 INFO  [org.jboss.ws.cxf.metadata] (MSC service thread 1-7) JBWS024061: Adding service endpoint metadata: id=org.jboss.qa.management.ws.cli.AnnotatedServiceWithTestEndpointConfigImpl
 address=http://localhost:8080/CLIWebServicesEndPointConfigIT/EndpointConfigTest
 implementor=org.jboss.qa.management.ws.cli.AnnotatedServiceWithTestEndpointConfigImpl
 serviceName={http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}EndpointConfigTest
 portName={http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}AnnotatedServiceWithTestEndpointConfigImplPort
 annotationWsdlLocation=null
 wsdlLocationOverride=null
 mtomEnabled=false
[0m[0m11:35:47,850 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}EndpointConfigTest from class org.jboss.qa.management.ws.cli.AnnotatedServiceWithTestEndpointConfigIface
[0m[0m11:35:47,886 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/CLIWebServicesEndPointConfigIT/EndpointConfigTest
[0m[0m11:35:47,897 INFO  [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/development/jbossqe/JBEAP-6.3.0.DR4/build/jboss-eap-6.3/standalone/data/wsdl/CLIWebServicesEndPointConfigIT.war/EndpointConfigTest.wsdl
[0m[0m11:35:47,897 INFO  [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.port-component-link
[0m[0m11:35:47,899 INFO  [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."CLIWebServicesEndPointConfigIT.war"."org.jboss.qa.management.ws.cli.AnnotatedServiceWithTestEndpointConfigImpl"
[0m[0m11:35:47,901 INFO  [org.jboss.web] (ServerService Thread Pool -- 24) JBAS018210: Register web context: /CLIWebServicesEndPointConfigIT
[0m[0m11:35:47,926 INFO  [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "CLIWebServicesEndPointConfigIT.war" (runtime-name : "CLIWebServicesEndPointConfigIT.war")
[0mMar 18, 2014 11:35:47 AM org.jboss.qa.management.ws.cli.CLITestUtils info
INFO: Result {"outcome" => "success","result" => {"step-1" => {"outcome" => "success"},"step-2" => {"outcome" => "success"}}}
[31m11:35:49,125 ERROR [stderr] (Thread-63) Exception in thread "Thread-63" java.nio.channels.ShutdownChannelGroupException
[0m[31m11:35:49,125 ERROR [stderr] (Thread-63) 	at sun.nio.ch.Invoker.invokeIndirectly(Invoker.java:210)
[0m[31m11:35:49,126 ERROR [stderr] (Thread-63) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishRead(UnixAsynchronousSocketChannelImpl.java:432)
[0m[31m11:35:49,126 ERROR [stderr] (Thread-63) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:191)
[0m[31m11:35:49,126 ERROR [stderr] (Thread-63) 	at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
[0m[31m11:35:49,126 ERROR [stderr] (Thread-63) 	at sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:293)
[0m[31m11:35:49,126 ERROR [stderr] (Thread-63) 	at java.lang.Thread.run(Thread.java:724)
[0m

Test result:

javax.xml.ws.WebServiceException: Could not send Message.
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
	at com.sun.proxy.$Proxy42.say(Unknown Source)
	at org.jboss.qa.management.ws.cli.CLIWebServicesEndPointConfigIT.assertServiceIsFunctional(CLIWebServicesEndPointConfigIT.java:255)
	at org.jboss.qa.management.ws.cli.CLIWebServicesEndPointConfigIT.assertEndpointConfigApplied(CLIWebServicesEndPointConfigIT.java:240)
	at org.jboss.qa.management.ws.cli.CLIWebServicesEndPointConfigIT.assertEndpointConfigApplied(CLIWebServicesEndPointConfigIT.java:236)
	at org.jboss.qa.management.ws.cli.CLIWebServicesEndPointConfigIT.testPredefinedEndpointConfigIsApplied(CLIWebServicesEndPointConfigIT.java:150)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
	at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
	at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
	at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
	at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
	at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
	at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
	at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
	at org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28)
Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/CLIWebServicesEndPointConfigIT/EndpointConfigTest: Read timed out
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1339)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1323)
	at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
	at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:628)
	at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
	at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330)
	at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
	... 69 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:150)
	at java.net.SocketInputStream.read(SocketInputStream.java:121)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
	at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
	at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
	at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:266)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1531)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1504)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1310)
	... 79 more

Comment 10 Petr Sakař 2014-03-26 13:13:53 UTC
The issue is still present in EAP 6.3.0.DR6.
I've seen it on RHEL  openjdk 1.7

org.jboss.test.ws.jaxws.cxf.jbws3060.JBWS3060EJB3TestCase.testConcurrentOneWayInvocations

Error Message

javax.xml.ws.WebServiceException: Could not send Message.
Stacktrace

java.util.concurrent.ExecutionException: javax.xml.ws.WebServiceException: Could not send Message.
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
	at org.jboss.test.ws.jaxws.cxf.jbws3060.JBWS3060Tests.runConcurrentTests(JBWS3060Tests.java:95)
	at org.jboss.test.ws.jaxws.cxf.jbws3060.JBWS3060Tests.testConcurrentOneWayInvocations(JBWS3060Tests.java:76)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at junit.framework.TestCase.runTest(TestCase.java:168)
	at junit.framework.TestCase.runBare(TestCase.java:134)
	at junit.framework.TestResult$1.protect(TestResult.java:110)
	at junit.framework.TestResult.runProtected(TestResult.java:128)
	at junit.framework.TestResult.run(TestResult.java:113)
	at junit.framework.TestCase.run(TestCase.java:124)
	at junit.framework.TestSuite.runTest(TestSuite.java:243)
	at junit.framework.TestSuite.run(TestSuite.java:238)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at org.jboss.wsf.test.JBossWSTestSetup$1.protect(JBossWSTestSetup.java:142)
	at junit.framework.TestResult.runProtected(TestResult.java:128)
	at org.jboss.wsf.test.JBossWSTestSetup.run(JBossWSTestSetup.java:149)
	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: javax.xml.ws.WebServiceException: Could not send Message.
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
	at com.sun.proxy.$Proxy58.echoOneWay(Unknown Source)
	at org.jboss.test.ws.jaxws.cxf.jbws3060.JBWS3060Tests$CallableOne.call(JBWS3060Tests.java:135)
	at org.jboss.test.ws.jaxws.cxf.jbws3060.JBWS3060Tests$CallableOne.call(JBWS3060Tests.java:117)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://[::1]:8080/jaxws-cxf-jbws3060/ServiceOne/EndpointOne: Read timed out
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1339)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1323)
	at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
	at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:628)
	at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
	at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377)
	at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330)
	at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
	at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
	... 7 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:152)
	at java.net.SocketInputStream.read(SocketInputStream.java:122)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
	at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
	at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1323)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
	at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:266)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1531)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1504)
	at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1310)
	... 17 more

Comment 11 Petr Sakař 2014-03-26 13:23:25 UTC
the comment#10 can be related but do not have to. It is tracked in separate issue
https://bugzilla.redhat.com/show_bug.cgi?id=1072242

Comment 12 Radim Hatlapatka 2014-03-27 08:01:54 UTC
The issue is still valid even for EAP 6.3.0.DR6 (jbossweb 7.4.0.Final). I have decompiled the jar and verified that the commit mentioned in comment #4.

So there must be additional culprit.

To reproduce, use the steps specified in Description of this issue.

Comment 13 Rostislav Svoboda 2014-04-04 11:27:49 UTC
*** Bug 1081036 has been marked as a duplicate of this bug. ***

Comment 16 Radim Hatlapatka 2014-04-08 09:29:05 UTC
I have tried your fix using upstream jbossweb build and it seems working. Please make sure that this fix will become part of EAP 6.3.0.ER2 build.

Comment 17 Rémy Maucherat 2014-04-08 11:13:25 UTC
Please read my comment though: NIO2 cannot have clean shutdown (on Windows for example), so parsing for random strings in the logs is wrong.

Comment 18 Radim Hatlapatka 2014-04-08 11:23:13 UTC
In my testcase I am not parsing logs looking for errors.

Nevertheless if NIO2 cannot have clean shutdown, it should be considered NOT to use it as a default http connector (currently it is set as default for JDK 1.7 and higher).

Comment 19 Petr Sakař 2014-04-08 11:30:47 UTC
We are not parsing any logs during testing of JBossWS

Comment 20 Radim Hatlapatka 2014-04-08 12:42:11 UTC
Are those cases harmless errors, could you give us example of case when not clean shutdown can appear and what message it would give. 

If it is harmless error, would it be possible to lower the log level?

Comment 21 Rémy Maucherat 2014-04-08 12:50:36 UTC
No.

If the logs are not parsed, I don't really understand how this logging causes failures.

Comment 22 Radim Hatlapatka 2014-04-08 13:00:55 UTC
The bugzilla is not about logging but it is about the issue described in description which seems to be fixed by r2399 as I wrote in comment 16.

The comment 18 - comment 20 are just reaction to your comment 17. For EAP there is requirement for clean start up and shutdown (of course only for cases where no error occurs - no errors should appear in default configuration).

Comment 23 Radim Hatlapatka 2014-04-23 08:58:34 UTC
Verified with EAP 6.3.0.ER2

Comment 24 Scott Mumford 2014-05-14 00:49:10 UTC
Marking for exclusion from 6.3.0 Beta release notes as both 'affects' and 'fix' versions are listed as 6.3.0, suggesting this was not a customer-facing issue.


Note You need to log in before you can comment on or make changes to this bug.