This week's book giveaway is in the Security forum.
We're giving away four copies of Penetration Testing Basics and have Ric Messier on-line!
See this thread for details.
Win a copy of Penetration Testing Basics this week in the Security forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Server.generalException faultString: Connection close:

Brian Mulcahy
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
New to the forums and new to Web Services so any help appreciated.

The Client of our Web Service is getting the following error intermittently:

faultCode: {}Server.generalException
faultString: Connection close: Read failed. Possible end of stream encountered.
faultActor: null
faultDetail: Connection close: Read failed. Possible end of stream encountered.

I've read a few posts that explain this error as:

When you execute a Web services client application with session persistence turned on or in a cluster environment, an error might display because the Web service client attempts to use a connection that has been closed by the HTTP server.

Two solutions are also given:
1) set
2) set the MaxSpareThreads property to the same value as the MaxClients property that is located in the httpd.conf file.

We are in the process of trying this but I just had a few questions around why this would happen.

1) What would cause the HTTP server to close the connection?
2) How does the server (on the service provider side) handle requests as they come in. Is each request designated a seperate thread?

And just a general question:
3) When we start our server we see the following in the console
JMXSoapAdapte A ADMC0013I: SOAP connector available at port 8880
Our HTTP port is set to 9080 so what exactly is listening at this port?

BTW, we are using Websphere V5. Our web services functioanlity was developed by an external company, they are gone now and
the handover was not exactly comprehensive.

  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic