java.sql.SQLException: E/A-Exception Broken pipe

[Former Member]

Hello everybody,

as you can see in the subject I have a strange exception. It occurs in the communication channel monitoring. There I can monitor the communication channels. I see there was a processing error in one communication channel and it says the following:

Error processing request in sax parser: Error when executing statement for table/stored proc. 'HOST_LVS' (structure 'STATEMENTNAME'): java.sql.SQLException: E/A-Exception: Broken pipe.

This is strange because the message was sent five minutes later to the receiver system.

Can someone explain me this error?

Regards, Florian

[Former Member · Accepted solution]

Floarain,

we have retry option for adapters before goes into error status in visual admin we can configure the details of retry option by default we have 3 times each with 5 mintues gap. if you want u can change this setttings.

so comingto ur case fristtime it tried but failed then after 5 mintues it tried again it is sucesfull. fof rist failure their network issuse or your DB may be down

[bhavesh_kantilal]

><i>This is strange because the message was sent five minutes later to the receiver system</i>

You adapter engine resends / retires to restart an error message 3 times at an interval of 5 minutes, before finally going into the System Error state.

My gut feeling here is that there was some temporary network issue the first time and then after 5 minutes when the automatic restart hapepned, the message was successfuly sent.

Regards

Bhavesh

[Former Member]

Thank you for your answers.

Now I ask myself how this error occurred?

[Former Member]

can be Network issuse or DB issues

[bhavesh_kantilal]

Like pointed by Sreeram, this error looks like some temporary network issue or some issue at the database level.

I did a goole on the "Broken pipe." and found some interesting discussions. Getting your basis and asking them to look at the DB for any traces would be the way to go ahead.

Regards

Bhavesh

[Former Member]

I did some research but I can't reproduce this error. I asked the basis but they didn't find anything strange. The DB administrator registered that there was no access from XI to the database. So the failure must occured in the network.

The good news is that this error didn't occured since then.

Regards

Florian