ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Cannot c

[lauri]

Hello.

Do you probably know if such (see subject) error message mean serious trouble?

Jboss 4.2.2 + jbossws 3.0.1 are installed.

Quite often, may be on every WS call a error message is posted to the log

18:40:52,551 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Cannot close output stream
18:40:56,699 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Cannot close output stream
18:41:21,552 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Cannot close output stream

source of org.jboss.wsf.stack.jbws.RequestHandlerImpl
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossws/branches/jbossws-2.0/integration/native/src/main/java/org/jboss/wsf/stack/jbws/RequestHandlerImpl.java?view=markup&pathrev=3507
gives no explanation

......
try
 {
 ServletRequestContext reqContext = new ServletRequestContext(context, req, res);
 handleWSDLRequest(endpoint, out, reqContext);
 }
 catch (Exception ex)
 {
 handleException(ex);
 }
 finally
 {
 try
 {
 out.close();
 }
 catch (IOException ioex)
 {
 log.error("Cannot close output stream");
 }
 }
....

Questions
1) Do you probably know if such (see subject) error message mean serious trouble?
2) What can be reason of the error message?
3) Can it be that WS code has inappropriate code which somehow closes that stream?

[wangfei90]

I got the same error log message. Could anyone help me?

[bbucy]

Any update on this? I get the same error on the server side.

Using same version (e.g. jbossws-3.0.1-native-2.0.4.GA). Wondering if this has something to do with the client's classpath. Had this all working at work no issue (Windows XP), but the other developers had issues related to the client's classpath of my project (e.g. unrelated to this error).

Working on the classpath fix, think I have the client's classpath straightened out, but getting this error on the server side. I am running OSX here at home, maybe my computer is just to fast (e.g. client closes connection, before server).

Bob

[smeverts]

I realize that this thread is over a year old however I am getting this same message and not sure if it caused the server crash that I saw last week. Basically the server crashed because of "too many open files" ... so I started checking the log files and I see this on every soap message that we issue.... anyone have any thoughts / comments?