0001750: Too much logging if session store fails because server is unavailable

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001750

[Resin]

minor

always

05-22-07 06:03

05-22-07 15:23

Reporter

sam

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.1.1

Summary

0001750: Too much logging if session store fails because server is unavailable

Description

(rep by K Köppert)

If we restart a server we get this following error, even with our log at info level.

        [19:52:56.306] java.net.SocketTimeoutException: Read timed out
        [19:52:56.306] at java.net.SocketInputStream.socketRead0(Native
Method)
        [19:52:56.306] at
java.net.SocketInputStream.read(SocketInputStream.java:129)
        [19:52:56.306] at com.caucho.vfs.TcpStream.read(TcpStream.java:163)
        [19:52:56.306] at
com.caucho.vfs.ReadStream.readBuffer(ReadStream.java:1001)
        [19:52:56.306] at
com.caucho.vfs.ReadStream.read(ReadStream.java:306)
        [19:52:56.306] at
com.caucho.server.cluster.ClusterStore.saveObject(ClusterStore.java:772)
        [19:52:56.306] at
com.caucho.server.cluster.ClusterStore.saveServer(ClusterStore.java:707)
        [19:52:56.306] at
com.caucho.server.cluster.ClusterStore.store(ClusterStore.java:649)
        [19:52:56.306] at
com.caucho.server.cluster.ClusterObject.store(ClusterObject.java:423)
        [19:52:56.306] at
com.caucho.server.session.SessionImpl.save(SessionImpl.java:915)
        [19:52:56.306] at
com.caucho.server.session.SessionImpl.saveAfterRequest(SessionImpl.java:904)
        [19:52:56.306] at
com.caucho.server.session.SessionImpl.finish(SessionImpl.java:866)
        [19:52:56.306] at
com.caucho.server.connection.AbstractHttpRequest.finish(AbstractHttpRequest.
java:2379)

Additional Information

Attached Files

Relationships

Notes
(0001936) sam 05-22-07 06:04	With the log level at "info", Resin should not log the whole exception because this error is normal behaviour when one of the servers is not available. The error is occurring because the server is trying to write a copy of the session to it's peer, but the peer is not available. The peer is not available because it has been manually taken offline.

Issue History
Date Modified	Username	Field	Change
05-22-07 06:03	sam	New Issue
05-22-07 06:04	sam	Note Added: 0001936
05-22-07 15:23	ferg	Assigned To	=> ferg
05-22-07 15:23	ferg	Status	new => closed
05-22-07 15:23	ferg	Resolution	open => fixed
05-22-07 15:23	ferg	Fixed in Version	=> 3.1.2

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.