You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2006/12/08 15:52:21 UTC

[jira] Created: (UIMA-113) socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry

socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry
----------------------------------------------------------------------------------------

                 Key: UIMA-113
                 URL: http://issues.apache.org/jira/browse/UIMA-113
             Project: UIMA
          Issue Type: Bug
          Components: Transport Adapters - SOAP, Vinci
    Affects Versions: 2.1
         Environment: Vinci service timeout
            Reporter: Eddie Epstein
         Assigned To: Adam Lally
             Fix For: 2.1


Eddie,

this is not related to our timeout problems, but might be interesting for you. IIRC, you said the reopening of the connection should not happen in 1.4.4 when a socket timeout exception happens. However, as illustrated in the following log, the socket timeout exception is (sometimes?) embedded in sax exception, thus preventing the fix to work:

[11/29/06 3:58 PM] Trying to reopen connection due to exception: java.io.IOException: SAX Exception: org.xml.sax.SAXException: IOException: java.net.SocketException: Connection timed out
[11/29/06 3:58 PM] Resolved com.ibm.upload_ibm to: 195.39.92.173:10035

Martin

--------

Hmmm..  I can see how this might be possible, although I'm not sure under what circumstances it would or would not happen.  I'm kind of surprised I never saw this myself.  You could open a JIRA issue for me to look at.

-Adam

-- 
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

        

[jira] Resolved: (UIMA-113) socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/UIMA-113?page=all ]

Adam Lally resolved UIMA-113.
-----------------------------

    Resolution: Fixed

Although I was unable to reproduce this kind of error on the client, I did manage to generate a similar exception message on the service side if the client dies:
java.io.IOException: SAX Exception: org.xml.sax.SAXException: IOException: java.net.SocketException:Socket write error

I believe I've fixed the code so that such cases of an "IOException wraps a SAXException wraps an IOException" can no longer happen.  Now the inner IOException will directly be thrown.  This should fix the reported issue, so I'm resolving the JIRA issue.  It can be reopened later if it is discovered the fix did not work.



> socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry
> ----------------------------------------------------------------------------------------
>
>                 Key: UIMA-113
>                 URL: http://issues.apache.org/jira/browse/UIMA-113
>             Project: UIMA
>          Issue Type: Bug
>          Components: Transport Adapters - SOAP, Vinci
>    Affects Versions: 2.1
>         Environment: Vinci service timeout
>            Reporter: Eddie Epstein
>         Assigned To: Adam Lally
>             Fix For: 2.1
>
>
> Eddie,
> this is not related to our timeout problems, but might be interesting for you. IIRC, you said the reopening of the connection should not happen in 1.4.4 when a socket timeout exception happens. However, as illustrated in the following log, the socket timeout exception is (sometimes?) embedded in sax exception, thus preventing the fix to work:
> [11/29/06 3:58 PM] Trying to reopen connection due to exception: java.io.IOException: SAX Exception: org.xml.sax.SAXException: IOException: java.net.SocketException: Connection timed out
> [11/29/06 3:58 PM] Resolved com.ibm.upload_ibm to: 195.39.92.173:10035
> Martin
> --------
> Hmmm..  I can see how this might be possible, although I'm not sure under what circumstances it would or would not happen.  I'm kind of surprised I never saw this myself.  You could open a JIRA issue for me to look at.
> -Adam

-- 
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

        

[jira] Assigned: (UIMA-113) socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally reassigned UIMA-113:
-------------------------------

    Assignee: Eddie Epstein  (was: Adam Lally)

> socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry
> ----------------------------------------------------------------------------------------
>
>                 Key: UIMA-113
>                 URL: https://issues.apache.org/jira/browse/UIMA-113
>             Project: UIMA
>          Issue Type: Bug
>          Components: Transport Adapters - SOAP, Vinci
>    Affects Versions: 2.1
>         Environment: Vinci service timeout
>            Reporter: Eddie Epstein
>         Assigned To: Eddie Epstein
>             Fix For: 2.1
>
>
> Eddie,
> this is not related to our timeout problems, but might be interesting for you. IIRC, you said the reopening of the connection should not happen in 1.4.4 when a socket timeout exception happens. However, as illustrated in the following log, the socket timeout exception is (sometimes?) embedded in sax exception, thus preventing the fix to work:
> [11/29/06 3:58 PM] Trying to reopen connection due to exception: java.io.IOException: SAX Exception: org.xml.sax.SAXException: IOException: java.net.SocketException: Connection timed out
> [11/29/06 3:58 PM] Resolved com.ibm.upload_ibm to: 195.39.92.173:10035
> Martin
> --------
> Hmmm..  I can see how this might be possible, although I'm not sure under what circumstances it would or would not happen.  I'm kind of surprised I never saw this myself.  You could open a JIRA issue for me to look at.
> -Adam

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (UIMA-113) socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry

Posted by "Adam Lally (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Lally closed UIMA-113.
---------------------------


Users confirmed problem seems to be fixed.

> socket timeout exception is (sometimes?) embedded in sax exception, resulting in a retry
> ----------------------------------------------------------------------------------------
>
>                 Key: UIMA-113
>                 URL: https://issues.apache.org/jira/browse/UIMA-113
>             Project: UIMA
>          Issue Type: Bug
>          Components: Transport Adapters - SOAP, Vinci
>    Affects Versions: 2.1
>         Environment: Vinci service timeout
>            Reporter: Eddie Epstein
>         Assigned To: Eddie Epstein
>             Fix For: 2.1
>
>
> Eddie,
> this is not related to our timeout problems, but might be interesting for you. IIRC, you said the reopening of the connection should not happen in 1.4.4 when a socket timeout exception happens. However, as illustrated in the following log, the socket timeout exception is (sometimes?) embedded in sax exception, thus preventing the fix to work:
> [11/29/06 3:58 PM] Trying to reopen connection due to exception: java.io.IOException: SAX Exception: org.xml.sax.SAXException: IOException: java.net.SocketException: Connection timed out
> [11/29/06 3:58 PM] Resolved com.ibm.upload_ibm to: 195.39.92.173:10035
> Martin
> --------
> Hmmm..  I can see how this might be possible, although I'm not sure under what circumstances it would or would not happen.  I'm kind of surprised I never saw this myself.  You could open a JIRA issue for me to look at.
> -Adam

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.