[SYNAPSE-456] dbloopup gives com.mysql.jdbc.CommunicationsException after idling a night

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 2.0
• 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
• Assignee: Asankha Chamath Perera
• Reporter: harm verhagen
• Created: 30/Sep/08 11:34
• Updated: 25/Mar/09 07:49
• Resolved: 24/Mar/09 18:42

Description

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