Intermittent java.io.IOException: The pipe is being closed
jjdevine Dec 10, 2013 3:59 AMHi,
I've been configuring JBoss EAP 6.1 (with JBoss AS 7.2) for a while now as we are trying to upgrade from our previous JBoss 5. I'm setting up the domain mode but I'm having a few problems, one of which is an intermittent "pipe is being closed" error on startup. As an example I have been doing some testing of another issue (VFS directory filling up every time a restart is done), this testing involves starting and stopping the app server lots of time. I had no problem doing this last night, but on doing the exact same thing this morning I find the following error in process-controller.log:
08:29:56,349 ERROR [org.jboss.as.process.Server:live-server.status] (ProcessController-threads - 3) JBAS012006: Failed to send data bytes to process 'Server:live-server' input stream: java.io.IOException: The pipe is being closed
at java.io.FileOutputStream.writeBytes(Native Method) [rt.jar:1.7.0_40]
at java.io.FileOutputStream.write(FileOutputStream.java:345) [rt.jar:1.7.0_40]
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) [rt.jar:1.7.0_40]
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) [rt.jar:1.7.0_40]
at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:160) [jboss-as-process-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:183) [jboss-as-process-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler.java:140) [jboss-as-process-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269) [jboss-as-process-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223) [jboss-as-process-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
The configuration is in domain mode such that I have 3 server groups, with one server in each, each with their own profile, however only 'live-server' is set to startup by default. I restarted my machine (local pc) and now the error isn't happening. I've had this happen before though, often after changing a configuration file (although without corrupting it as far as I can tell), although I haven't done that this morning.
Is this a known problem? Is the server not shutting down properly and locking down a port? I'm running JBoss as a windows service if that helps, but I've had this issue when running it from plain old domain.bat also.
Thanks.