You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexei Fedotov (JIRA)" <ji...@apache.org> on 2006/10/30 18:14:23 UTC
[jira] Commented: (HARMONY-1904) Signals interrupt hysock_select
calls.
[ http://issues.apache.org/jira/browse/HARMONY-1904?page=comments#action_12445659 ]
Alexei Fedotov commented on HARMONY-1904:
-----------------------------------------
The bug can possibly affect class library test runs, see http://wiki.apache.org/harmony/Unit_Tests_Pass_on_DRLVM
Here is an explanation what shulf be fixed in DRLVM:
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200610.mbox/%3c4540C461.7020206@pobox.com%3e
A separate issue should be opened against class library to process EINTR return code of hysock_select() correctly (try again).
> Signals interrupt hysock_select calls.
> --------------------------------------
>
> Key: HARMONY-1904
> URL: http://issues.apache.org/jira/browse/HARMONY-1904
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: linux
> Reporter: Artem Aliev
> Attachments: hysock.diff
>
>
> DRLVM uses linux signals in thread suspend calls.
> The signals interrupt select() call in port lib.
> This cause the JBoss failure with following stack trace:
> java.net.SocketException: The call was cancelled
> at org.apache.harmony.luni.platform.OSNetworkSystem.availableStreamImpl(OSNetworkSystem.java)
> at org.apache.harmony.luni.platform.OSNetworkSystem.availableStream(OSNetworkSystem.java:216)
> at org.apache.harmony.luni.net.PlainSocketImpl.available(PlainSocketImpl.java:150)
> at org.apache.harmony.luni.net.SocketInputStream.available(SocketInputStream.java:50)
> at com.mysql.jdbc.util.ReadAheadInputStream.available(ReadAheadInputStream.java:212)
> at com.mysql.jdbc.MysqlIO.clearInputStream(MysqlIO.java:774)
> See following mail thread for details
> http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200610.mbox/%3c4534F08F.9000208@pobox.com%3e
> Workaround is attached, but see the e-mail for complains on this workaround
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira