synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SYNAPSE-456) dbloopup gives com.mysql.jdbc.CommunicationsException after idling a night
Date Tue, 24 Mar 2009 18:44:51 GMT

     [ https://issues.apache.org/jira/browse/SYNAPSE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Asankha C. Perera resolved SYNAPSE-456.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3
         Assignee: Asankha C. Perera

Specify a valid and suitable query for validation, and this feature works as expected.

e.g. 
                        <property name="testonborrow" value="true"/>
                        <property name="validationquery" value="SELECT count(*) from company"/>

Also see http://wiki.apache.org/commons/DBCP

> dbloopup gives com.mysql.jdbc.CommunicationsException  after idling a night
> ---------------------------------------------------------------------------
>
>                 Key: SYNAPSE-456
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-456
>             Project: Synapse
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: debian on xen VM, mysql running on same host as wso2esb.
> versions:
> wso2esb v1.7.1
> mysql 5.0
> libmysql-java 5.0.4+dfsg-2 
>            Reporter: harm verhagen
>            Assignee: Asankha C. Perera
>             Fix For: 1.3
>
>         Attachments: synapse.xml
>
>
> I have a wso2 sequence  with dblookup/dbreport mediators.
> Basically every soap call is stored in the database.
> Every morning, the wso2esb bus is in a state it doesn't process any messages anymore
due to database access problems.
> 2008-09-28 20:14:33,480 [127.0.0.1-vloeki_v01] [HttpServerWorker-3] ERROR DBLookupMediator
Error executing statement : select
>  * from customer c where token = '00000000-00'; against DataSource :jdbc:mysql://localhost:3306/esb
> com.mysql.jdbc.CommunicationsException: Communications link failure due to
> underlying exception:
> ** BEGIN NESTED EXCEPTION **
> java.net.SocketException
> MESSAGE: Broken pipe
> During the night the bus is typically idle (zero messages).
> The database is _not_ down. mysql query browser is working just fine.
> full report & error on
> http://wso2.org/mailarchive/esb-java-user/2008-September/000897.html

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message