RE: [ebxmlms-general] Problems after lost connection to database

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

YES, but...

- Tomcat already has this with it
- As does Jetty
- As do all j2ee appservers

So build on that and not include Jakarta commons DBCP ourselves. The =
pure db stuff is not to difficult to swapout, I've done that before, but =
the project was not realy interested since they wanted to be =
independent.=20

If you swap out the proprietary db stuff for a standards based solution, =
one thing that has to be done is to get some kind of transaction over =
the database and file operations. This is for us one of the major issues =
our ASP (and me as an architect, but I like to blame others ;-)) does =
not let hermes run in production.

Ronald

-----Oorspronkelijk bericht-----
Van: ebx...@li... =
[mailto:ebx...@li...] Namens Mattias J
Verzonden: maandag 27 juni 2005 10:25
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-general] Problems after lost connection to =
database

Yes, why not include for example Jakarta Commons DBCP?

At 2005-06-27 09:29, you wrote:
>I guess the problem is that you have implemented=20
>your own databasepool, without sophisticated recovery mechanism.
>Our own application use javax.sql.DataSource, to=20
>get a connection. I guess there is a recovery=20
>mechanism in that solution, as our own=20
>application runs fine when the connection gets back.
>Is there anyway to use javax.sql.DataSource=20
>instead of your implementation of the connection=20
>pool? I guess my question is more to why you are=20
>using your own implemtation, are you using some=20
>extra stuff, I can't get from javax.sql.DataSource?
>
>Regards Kenneth
>
>>From: Patrick Yee <kc...@ce...>
>>To: ebx...@li...
>>CC: tr...@ho...
>>Subject: Re: [ebxmlms-general] Problems after lost connection to =
database
>>Date: Sun, 26 Jun 2005 19:19:35 +0800
>>
>>We have not implemented a sophisticated=20
>>recovery mechanism in the database connection=20
>>pool. The only mechanism we have done is,=20
>>whenever a connection is proved to be bad, we=20
>>will not put it back to the connection pool.=20
>>Actually there was a suggestion some time ago=20
>>that we can do a "select *" on some tables=20
>>before we use the pooled database connection.=20
>>We think that will create certain performance=20
>>issue, and so we shelved that idea. Of course,=20
>>if you want it, you can just patch the database=20
>>connection pool classes and implement any=20
>>advanced recovery mechanism as you like. :-)
>>Regards, -Patrick
>>
>>
>>Kenneth Pedersen wrote:
>>
>>>Hi
>>>
>>>If I loose the connection to my database for a=20
>>>short time (1-2minutes), MSH do not operate properly afterwards.
>>>
>>>When the connection is lost this occurs in the MSH_client.log:
>>>
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D> =
DbConnectionPool.getConnection
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: <=3D =
DbConnectionPool.getConnection
>>>2005-06-21 09:13:34,384 ERROR [Thread-8]: [10002] Unknown error
>>>Exception: java.sql.SQLException
>>>Message: I/O Error: Connection reset by peer: socket write error
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D>=20
>>>Transaction.rollback (txID: #2321)
>>>2005-06-21 09:13:34,384 ERROR [Thread-8]: [10315] Cannot rollback DB =
changes
>>>Exception: java.sql.SQLException
>>>Message: Invalid state, the Connection object is closed.
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D> =
DbConnectionPool.freeConnection
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: <=3D =
DbConnectionPool.freeConnection
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: <=3D Transaction.rollback
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D>=20
>>>MessageServiceHandler.getNextUndeliveredMessage
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D>=20
>>>MessageServer.getUndeliveredMessages
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D> =
DbConnectionPool.getConnection
>>>2005-06-21 09:13:34,384 DEBUG [Thread-8]: =3D>=20
>>>DbConnectionPool.createConnection
>>>2005-06-21 09:13:35,352 ERROR [Thread-8]:=20
>>>[10306] Cannot create DB connection Exception:=20
>>>java.sql.SQLException Message: Network error
>>>IOException: Connection refused: connect
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: =3D>=20
>>>Transaction.rollback (txID: #2323)
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: <=3D Transaction.rollback
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: =3D>=20
>>>MessageServiceHandler.getNextUndeliveredMessage
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: =3D>=20
>>>MessageServer.getUndeliveredMessages
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: =3D> =
DbConnectionPool.getConnection
>>>2005-06-21 09:13:35,352 DEBUG [Thread-8]: =3D>=20
>>>DbConnectionPool.createConnection
>>>
>>>
>>>After the connection is restored MSH do not seem to get a proper =
connection.
>>>This occurs then in the MSH_Client.log:
>>>
>>>2005-06-21 09:13:42,384 ERROR [Thread-8]:=20
>>>[10306] Cannot create DB connection
>>>Exception: java.sql.SQLException Message: Network error
>>>IOException: Connection refused: connect
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: =3D>=20
>>>Transaction.rollback (txID: #2338)
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: <=3D Transaction.rollback
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: =3D>=20
>>>MessageServiceHandler.getNextUndeliveredMessage
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: =3D>=20
>>>MessageServer.getUndeliveredMessages
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: =3D> =
DbConnectionPool.getConnection
>>>2005-06-21 09:13:42,384 DEBUG [Thread-8]: =3D>=20
>>>DbConnectionPool.createConnection
>>>2005-06-21 09:13:43,384 ERROR [Thread-8]:=20
>>>[10306] Cannot create DB connection
>>>Exception: java.sql.SQLException
>>>Message: Network error IOException: Connection refused: connect
>>>
>>>
>>>
>>>When i try to send a message through MSH i get this:
>>>hk.hku.cecid.phoenix.message.handler.RequestException:
>>>Failed to send query to MSH.
>>>  HTTP response code =3D 200
>>>  HTTP response message =3D OK
>>>     at=20
>>> =
hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknown =
Source)
>>>     at=20
>>> =
hk.hku.cecid.phoenix.message.handler.Request.sendMessageServiceHandlerCon=
fig(Unknown=20
>>> Source)
>>>     at=20
>>> hk.hku.cecid.phoenix.message.handler.Request.register(Unknown =
Source)
>>>     at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown =
Source)
>>>     at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown =
Source)
>>>     at=20
>>> =
com.mysupply.ebxi.msh.MessageManager.sendMessage(MessageManager.java:149)=

>>>
>>>And of course I can not receive any messages through MSH either.
>>>
>>>Does anybody have the same problems, after a=20
>>>lost database connection? The other part of my=20
>>>application that uses MSH, is right back in=20
>>>action when the database connection is restored, but not MSH.
>>>
>>>The app is running on jboss-4.0.1 (Tomcat=20
>>>5.0.28), Java jdk1.5.0_01. The database is=20
>>>Microsofts MSSQL 2000. The driver for MSSQL is JTDS 1.0.
>>>I have added this:
>>><check-valid-connection-sql>select * from=20
>>>some_table</check-valid-connection-sql>
>>>to my datasource file: mssql-ds.xml which is deployed along with =
msh.war.
>>>
>>>Everything is working fine, for days, until I=20
>>>loose the database connection for a few minutes.
>>>
>>>_________________________________________________________________
>>>Del din verden med MSN Spaces  http://spaces.msn.com
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>SF.Net email is sponsored by: Discover Easy Linux Migration =
Strategies
>>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>>informative Webcasts and more! Get everything you need to get up to
>>>speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
>>>_______________________________________________
>>>ebxmlms-general mailing list
>>>ebx...@li...
>>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>>
>
>_________________________________________________________________
>Undg=E5 pop-ups med MSN Toolbar -  http://toolbar.msn.dk/ hent den =
gratis!
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general