[
https://wso2.org/jira/browse/ESBJAVA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
indika kumara resolved ESBJAVA-475.
-----------------------------------
Resolution: Fixed
When two ends are communicating through TCP, if the receiving end closed the
connection while the sending end writing to the connection, in the sending end
'java.net.SocketException: Broken pipe' exception can be occurred. For example
, while the esb server is processing the request,if the browser closed
connection this exception can be occurred in the esb server. This may be
happened when you do requests through a browser in quick succession.
Logs are completely related to the tomcat.
are there any database related logs (java.sql.*)?. Because, It is possible that
for some reasons, if the database server has disconnected connection with esb
while accessing database.
> Statistics of endpoints and sequences are not displayed after successful
> invocation
> -----------------------------------------------------------------------------------
>
> Key: ESBJAVA-475
> URL: https://wso2.org/jira/browse/ESBJAVA-475
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Statistics
> Affects Versions: NIGHTLY
> Environment: buntu7.04, JDK1.5.0_14
> Reporter: Evanthika Amarasiri
> Assignee: indika kumara
> Fix For: 1.7
>
>
> Steps to reproduce
> 1. Created a sequence that access and endpoint defined as a local registry
> entry.
> 2. Enabled statistics for both the sequence and the endpoint.
> 3. Then invoked the client and after about 5 minutes checked the statistics
> page but the relevant statistics were not displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
