[ 
https://issues.apache.org/jira/browse/SYNAPSE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209120#comment-13209120
 ] 

Kasun Indrasiri commented on SYNAPSE-622:
-----------------------------------------

We came across this issue intermittently when timeouts occurs from the backend. 
Possible this is due to a typo in ClientHandler. 


ClinetHandler:
-------------------
public static final String CONNECTION_CREATION_TIME = 
"synapse.connectioCreationTime";
...
this.connectionCreationTime = (Long) conn.getContext().getAttribute(
                    ClientHandler.CONNECTION_CREATION_TIME);

Server handler:
----------------------

public static final String CONNECTION_CREATION_TIME = 
"synapse.connectionCreationTime";
...
conn.getContext().setAttribute(CONNECTION_CREATION_TIME, 
System.currentTimeMillis());


                
> NPE in ClientConnectionDebug.java:36 when running in a failover scenario 
> -------------------------------------------------------------------------
>
>                 Key: SYNAPSE-622
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-622
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>            Reporter: Rajika Kumarasiri
>            Assignee: Kasun Indrasiri
>            Priority: Critical
>             Fix For: 2.0
>
>         Attachments: SYNAPSE-622.patch
>
>
> When I run sample #52 with one of the leaf endpoint being timeout, following 
> NPE is thrown time to time. Once this is encountered that message is 
> permanently lost. I'll upload a small patch which will fix the problem. 

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to