Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

intermittent error on solaris

3 views
Skip to first unread message

Alec Cove

unread,
Aug 25, 2000, 3:00:00 AM8/25/00
to
Weblogic 5.1 sp4
Solaris 7

Im getting this error intermittently in the shell. it doesnt seem to affect
the application. Any one know what causes it?

--------------------------------
Fri Aug 25 16:26:46 EDT 2000:<E> <Posix Performance Pack> Failure in
processSock
ets()
java.net.SocketException: Connection reset by peer: Connection reset by peer
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.socketRead(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.run(Compiled Code)

Mauricio Del Moral

unread,
Aug 25, 2000, 3:00:00 AM8/25/00
to

Maybe you should try modifying the properties above...to

weblogic.system.executeThreadCount=#
weblogic.system.percentSocketReaders=#

and check the configuration of your machine related with WLS.

Kumar Allamraju

unread,
Aug 25, 2000, 3:00:00 AM8/25/00
to
These exceptions are caused because the servlet has made a write system call and
the reader on the
other side of the pipe(socket in this case) has closed. Write will return EPIPE
which gets propagated as a Broken
Pipe in java

I suspect that a user has simply hit reload or stop in a browser while the
server was sending them a file.You can safely ignore this message.

These IOExceptions indicate a communication problem between client and server.
For whatever reason the socket from the server back to the client is dead. Among
many other things these communication errors can happen because:

1. The browser (client) breaks the socket connection to server by user either
hitting the stop button, or the user issuing another HTTP request prior to the
first request fininshing. (You can easily recreate this yourself)

2. Network congestion, latency, etc etc

3. Firewalls, timeouts, congestion etc etc etc.

These communication or IO exceptions can manifest themselves as:

Mon Jun 07 14:40:04 PDT 1999:<E> <WebLogicServer> java.net.SocketException:

Connection reset by peer

Mon Jun 07 15:10:58 PDT 1999:<E> <WebLogicServer> java.io.EOFException

Mon Jun 07 17:10:16 PDT 1999:<E> <HTTP> java.io.IOException: Broken pipe

Mon Jun 07 14:38:12 PDT 1999:<E> <HTTP> java.io.IOException: Socket Closed

Most often on Solaris you will see Broken pipe, as the underlying data structure
used in the socket commuincation is a pipe. Most often on NT you will see
Conneciton reset by peer. So, these errors can be indicative of user generated
errors beyond yourcontrol, network -- internet problems beyond your control, or
your own
network configuration that is causing problems. Their is no real "easy" way to
determine which it is, other than listen to customer complaints and try to
assess their environment and actions to determine if the issue is your network
configuration. You can also test your production network topology and
configuration vs your test configuration, as the later is usually less complex
and restrictive.

--
Kumar

Brian Benson

unread,
Aug 28, 2000, 3:00:00 AM8/28/00
to

The <Posix Performance Pack> Failure in processSock
ets() exceptions appear to be browser specific and occur only when accessing the solaris instance from an IE browser. This is ugly with a capital U. Is there a way to get rid of this exception? Users of our product are going to be calling _me_ about this exception :)
0 new messages