Re: [ebxmlms-general] Re: native connectionpools

[Ronald v. K. <rv...@ab...>]

Thanks for the response

Patrick Yee wrote:

>>btw. Can somebody explain why there is a normal and a raw connection?
>>    
>>
>
>A normal connection is pooled. A raw is not. For a pooled one, we have put
>effort to make sure it works. 
>
This part I found out from the code ;-), but thanks anyway for explaining

>(In some cases, we find DB server cutting idle
>connections, so the idle pooled db connection object is not usable after a
>while). To check the validity of the pooled connection, we do a simple
>select on one of a table.
>  
>
This can be done with the other connectionpools to (e.g. tomcat, jboss, 
weblogic), sometimes even in the driver (mysql)

>But when Hermes starts up in the first time, it may create the tables. So
>before the tables are created, we cannot use the pooled connections (all
>pooled ones are "considered" as invalid as it cannot do the select on the
>table). In that case, we use raw connection.
>  
>
Ok, so it is not because you want to have the guarantee that even if the 
connectionpool is fully used you could still use a raw connection?

Any change of making an interface an changing some things to the 
MessageServiceHandler.java so it could be easy to give others the option 
to use the connectionpools that come with the appserver/servlet engine?

Ronald

> 
>Hope it is clear.
>
>Regards, -Patrick
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: ApacheCon 2003,
>16-19 November in Las Vegas. Learn firsthand the latest
>developments in Apache, PHP, Perl, XML, Java, MySQL,
>WebDAV, and more! http://www.apachecon.com/
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>  
>