Menu
▾
▴
opaltoolkit-users
|
From: Anthony B. <ant...@ir...> - 2009-08-28 14:38:15
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi!<br> We've had a problem using MySQL database for storing opal2 jobs data instead of the default HSQLDB.<br> It turned out it was a timeout problem which is quite well described at the following address: <a class="moz-txt-link-freetext" href="http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/">http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/</a>. Briefly: mysql closes connection after an 8h timeout (which is quite frequent for us, but not for servers where there is more activity).<br> We solved it by using c3p0 to manage database connection.<br> Here is what we have done to use it:<br> <br> -Added c3p0 package in $opal_sources/lib/ and modified build.xml consequently<br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --></style> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --></style>-Created $opal_sources /etc/c3p0.properties and added " c3p0.preferredTestQuery=SELECT 1; " in it.<br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css">!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --></style> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } --></style>-In build.xml, after <include name="OpalState.hbm.xml"/> added <include name="c3p0.properties"/><br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } -</style>-In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced:<br> <br> <!-- JDBC connection pool (use the built-in) --><br> <!--<property name="connection.pool_size">1</property>--> <br> <br> By these lines:<br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> <title></title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } -cd</style><br> <!-- JDBC connection pool (use c3p0) --><br> <property name="c3p0.min_size">1</property><br> <property name="c3p0.max_size">20</property><br> <property name="c3p0.timeout">1800</property><br> <property name="c3p0.max_statements">50</property><br> <property name="c3p0.idle_test_period">1800</property><br> <property name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property><br> <br> Maybe it would be a good idea to include it in a future version of opal?<br> Bye!<br> <br> </body> </html> |
|
From: Luca C. <lcl...@uc...> - 2009-08-28 18:49:53
|
Anthony Bretaudeau wrote: > Hi! > We've had a problem using MySQL database for storing opal2 jobs data > instead of the default HSQLDB. > It turned out it was a timeout problem which is quite well described at > the following address: > http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/. > Briefly: mysql closes connection after an 8h timeout (which is quite > frequent for us, but not for servers where there is more activity). > We solved it by using c3p0 to manage database connection. > Here is what we have done to use it: > Anthony, I expect the dashboard to have some problem visualizing the exec time of your jobs. Have a look at line 365: http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup Unfortunately I could not find a way to make the query working using Hibernate SQL and I had to use the local SQL dialect. Given that I think we should start using some connection manager since it is also recommended by the Hibernate guys. Sincerely, Luca > -Added c3p0 package in $opal_sources/lib/ and modified build.xml > consequently > -Created $opal_sources /etc/c3p0.properties and added " > c3p0.preferredTestQuery=SELECT 1; " in it. > -In build.xml, after <include name="OpalState.hbm.xml"/> added <include > name="c3p0.properties"/> > -In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced: > > <!-- JDBC connection pool (use the built-in) --> > <!--<property name="connection.pool_size">1</property>--> > > By these lines: > > <!-- JDBC connection pool (use c3p0) --> > <property name="c3p0.min_size">1</property> > <property name="c3p0.max_size">20</property> > <property name="c3p0.timeout">1800</property> > <property name="c3p0.max_statements">50</property> > <property name="c3p0.idle_test_period">1800</property> > <property > name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property> > > Maybe it would be a good idea to include it in a future version of opal? > Bye! > |
|
From: Anthony B. <ant...@ir...> - 2009-08-31 07:16:44
|
Oh yes, the exec time has a problem. I hadn't noticed that. Is this the only SQL request using local SQL dialect? In this case, something like "unix_timestamp( last_update_time - start_time_time ) as average" should work for MySQL (copying the rest of the request from PostgreSQL). If I have time, I'll try to test it. Thanks Anthony Luca Clementi a écrit : > Anthony Bretaudeau wrote: >> Hi! >> We've had a problem using MySQL database for storing opal2 jobs data >> instead of the default HSQLDB. >> It turned out it was a timeout problem which is quite well described >> at the following address: >> http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/. >> Briefly: mysql closes connection after an 8h timeout (which is quite >> frequent for us, but not for servers where there is more activity). >> We solved it by using c3p0 to manage database connection. >> Here is what we have done to use it: >> > > > Anthony, > I expect the dashboard to have some problem visualizing the exec time > of your jobs. > > Have a look at line 365: > http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup > > > Unfortunately I could not find a way to make the query working using > Hibernate SQL and I had to use the local SQL dialect. > > Given that I think we should start using some connection manager since > it is also recommended by the Hibernate guys. > > Sincerely, > Luca > >> -Added c3p0 package in $opal_sources/lib/ and modified build.xml >> consequently >> -Created $opal_sources /etc/c3p0.properties and added " >> c3p0.preferredTestQuery=SELECT 1; " in it. >> -In build.xml, after <include name="OpalState.hbm.xml"/> added >> <include name="c3p0.properties"/> >> -In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced: >> >> <!-- JDBC connection pool (use the built-in) --> >> <!--<property name="connection.pool_size">1</property>--> >> >> By these lines: >> >> <!-- JDBC connection pool (use c3p0) --> >> <property name="c3p0.min_size">1</property> >> <property name="c3p0.max_size">20</property> >> <property name="c3p0.timeout">1800</property> >> <property name="c3p0.max_statements">50</property> >> <property name="c3p0.idle_test_period">1800</property> >> <property >> name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property> >> >> >> Maybe it would be a good idea to include it in a future version of opal? >> Bye! >> > |
|
From: Anthony B. <ant...@ir...> - 2009-09-02 17:51:45
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi!<br>
After testing, I've managed to make job exec time visualization work
with the following code (replace line 389 with it in
src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java):<br>
<br>
}else if (dialect.equals("org.hibernate.dialect.MySQLDialect")){<br>
//this is MySQL<br>
query = "select jobInfo.start_time_date as date, " +<br>
//number of day <br>
" avg( ( last_update_date - start_time_date ) * 86400 +
" +<br>
//plus number of seconds (epoch returns seconds!)<br>
" ( time_to_sec(last_update_time) -
time_to_sec(start_time_time) )) as average " + queryTail;<br>
}<br>
<br>
Feel free to include this in next release if it can help other users.<br>
Thanks.<br>
Anthony<br>
<br>
Anthony Bretaudeau a écrit :
<blockquote cite="mid:4A9...@ir..." type="cite">
<pre wrap="">Oh yes, the exec time has a problem. I hadn't noticed that.
Is this the only SQL request using local SQL dialect? In this case,
something like "unix_timestamp( last_update_time - start_time_time ) as
average" should work for MySQL (copying the rest of the request from
PostgreSQL). If I have time, I'll try to test it.
Thanks
Anthony
Luca Clementi a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Anthony Bretaudeau wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi!
We've had a problem using MySQL database for storing opal2 jobs data
instead of the default HSQLDB.
It turned out it was a timeout problem which is quite well described
at the following address:
<a class="moz-txt-link-freetext" href="http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/">http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/</a>.
Briefly: mysql closes connection after an 8h timeout (which is quite
frequent for us, but not for servers where there is more activity).
We solved it by using c3p0 to manage database connection.
Here is what we have done to use it:
</pre>
</blockquote>
<pre wrap="">
Anthony,
I expect the dashboard to have some problem visualizing the exec time
of your jobs.
Have a look at line 365:
<a class="moz-txt-link-freetext" href="http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup">http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup</a>
Unfortunately I could not find a way to make the query working using
Hibernate SQL and I had to use the local SQL dialect.
Given that I think we should start using some connection manager since
it is also recommended by the Hibernate guys.
Sincerely,
Luca
</pre>
<blockquote type="cite">
<pre wrap="">-Added c3p0 package in $opal_sources/lib/ and modified build.xml
consequently
-Created $opal_sources /etc/c3p0.properties and added "
c3p0.preferredTestQuery=SELECT 1; " in it.
-In build.xml, after <include name="OpalState.hbm.xml"/> added
<include name="c3p0.properties"/>
-In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced:
<!-- JDBC connection pool (use the built-in) -->
<!--<property name="connection.pool_size">1</property>-->
By these lines:
<!-- JDBC connection pool (use c3p0) -->
<property name="c3p0.min_size">1</property>
<property name="c3p0.max_size">20</property>
<property name="c3p0.timeout">1800</property>
<property name="c3p0.max_statements">50</property>
<property name="c3p0.idle_test_period">1800</property>
<property
name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property>
Maybe it would be a good idea to include it in a future version of opal?
Bye!
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/bobj-july">http://p.sf.net/sfu/bobj-july</a>
_______________________________________________
Opaltoolkit-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opa...@li...">Opa...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users">https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users</a>
</pre>
</blockquote>
</body>
</html>
|
|
From: Sriram K. <sr...@sd...> - 2009-09-08 21:25:20
|
Hello Anthony,
I have committed your changes into SVN, and also added configuration
and jars for c3p0 and mysql. I tested everything and it seems to be
working fine. Please check out the latest version from SVN and let me
know if there are any issues.
This will be part of the next Opal release that we are planning for
end of this month. Thanks again for your contribution!
Cheers,
Sriram
On Sep 2, 2009, at 5:28 AM, Anthony Bretaudeau wrote:
> Hi!
> After testing, I've managed to make job exec time visualization work
> with the following code (replace line 389 with it in src/edu/sdsc/
> nbcr/opal/dashboard/persistence/DBManager.java):
>
> }else if
> (dialect.equals("org.hibernate.dialect.MySQLDialect")){
> //this is MySQL
> query = "select jobInfo.start_time_date as date, " +
> //number of day
> " avg( ( last_update_date - start_time_date ) *
> 86400 + " +
> //plus number of seconds (epoch returns seconds!)
> " ( time_to_sec(last_update_time) -
> time_to_sec(start_time_time) )) as average " + queryTail;
> }
>
> Feel free to include this in next release if it can help other users.
> Thanks.
> Anthony
>
> Anthony Bretaudeau a écrit :
>>
>> Oh yes, the exec time has a problem. I hadn't noticed that.
>> Is this the only SQL request using local SQL dialect? In this case,
>> something like "unix_timestamp( last_update_time -
>> start_time_time ) as
>> average" should work for MySQL (copying the rest of the request from
>> PostgreSQL). If I have time, I'll try to test it.
>> Thanks
>> Anthony
>>
>> Luca Clementi a écrit :
>>
>>> Anthony Bretaudeau wrote:
>>>
>>>> Hi!
>>>> We've had a problem using MySQL database for storing opal2 jobs
>>>> data
>>>> instead of the default HSQLDB.
>>>> It turned out it was a timeout problem which is quite well
>>>> described
>>>> at the following address:
>>>> http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/
>>>> .
>>>> Briefly: mysql closes connection after an 8h timeout (which is
>>>> quite
>>>> frequent for us, but not for servers where there is more activity).
>>>> We solved it by using c3p0 to manage database connection.
>>>> Here is what we have done to use it:
>>>>
>>>>
>>> Anthony,
>>> I expect the dashboard to have some problem visualizing the exec
>>> time
>>> of your jobs.
>>>
>>> Have a look at line 365:
>>> http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup
>>>
>>>
>>> Unfortunately I could not find a way to make the query working using
>>> Hibernate SQL and I had to use the local SQL dialect.
>>>
>>> Given that I think we should start using some connection manager
>>> since
>>> it is also recommended by the Hibernate guys.
>>>
>>> Sincerely,
>>> Luca
>>>
>>>
>>>> -Added c3p0 package in $opal_sources/lib/ and modified build.xml
>>>> consequently
>>>> -Created $opal_sources /etc/c3p0.properties and added "
>>>> c3p0.preferredTestQuery=SELECT 1; " in it.
>>>> -In build.xml, after <include name="OpalState.hbm.xml"/> added
>>>> <include name="c3p0.properties"/>
>>>> -In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced:
>>>>
>>>> <!-- JDBC connection pool (use the built-in) -->
>>>> <!--<property name="connection.pool_size">1</property>-->
>>>>
>>>> By these lines:
>>>>
>>>> <!-- JDBC connection pool (use c3p0) -->
>>>> <property name="c3p0.min_size">1</property>
>>>> <property name="c3p0.max_size">20</property>
>>>> <property name="c3p0.timeout">1800</property>
>>>> <property name="c3p0.max_statements">50</property>
>>>> <property name="c3p0.idle_test_period">1800</property>
>>>> <property
>>>> name
>>>> =
>>>> "connection
>>>> .provider_class">org.hibernate.connection.C3P0ConnectionProvider</
>>>> property>
>>>>
>>>>
>>>> Maybe it would be a good idea to include it in a future version
>>>> of opal?
>>>> Bye!
>>>>
>>>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports
>> 2008 30-Day
>> trial. Simplify your report design, integration and deployment -
>> and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Opaltoolkit-users mailing list
>> Opa...@li...
>> https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users
>>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> trial. Simplify your report design, integration and deployment - and
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july_______________________________________________
> Opaltoolkit-users mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users
|
|
From: Anthony B. <ant...@ir...> - 2009-09-11 09:22:14
Attachments:
OpalSOAPRequestWrapper.java
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi!<br>
I've finally installed svn version of Opal2 on a test server and I have
a few comments/questions:<br>
<br>
-First, I've found a bug in my "typed WSDL addon": on a freshly
installed opal2 with the addon, you cannot deploy any service. So I
attach a patched file to put in OpalSOAPRequestFilter package. Briefly,
the problem was that the file WEB-INF/server-config.wsdd (which is used
by the filter) doesn't exists when no service is deployed.<br>
<br>
-I see you've included c3p0 and mysql connector packages (which is
great!), but their are not the latest versions available (0.9.1.1
instead of 0.9.1.2 for c3p0 and 5.1.0 instead of 5.1.8 for mysql). I
have no particular problem with these older versions but I was
wondering if there was a reason for that...<br>
-Speaking about c3p0, I've seen you haven't included the
"c3p0.preferredTestQuery=SELECT 1;" property. Is this intended? It can
be defined in $OPAL_SOURCES/etc/hibernate-opal.cfg.xml using
"<property name="c3p0.preferredTestQuery">SELECT
1;</property>". Looking at the doc, it seems like it makes
testing database availability faster.<br>
<br>
-There's also a new bug in svn: our servers are not running on the 8080
port, so the dashboard has some problems with it (maybe you are aware
of it?). From what I have seen, there's at least one hard-coded 8080
port in webapps/opal2/dashboard-jsp/serviceList.jsp on line 51 (there
may be the same bug in other files). Making this configurable would be
quite useful!<br>
<br>
Apart from that, Opal2 is running smoothly and the new application list
is great!<br>
<br>
You told me you could give me commit access to svn: if you're still ok
with that, do I need to create a sourceforge account?<br>
<br>
Cheers<br>
Anthony<br>
<br>
Sriram Krishnan wrote:
<blockquote cite="mid:0EA...@sd..."
type="cite">Hello Anthony,
<div><br>
</div>
<div>I have committed your changes into SVN, and also added
configuration and jars for c3p0 and mysql. I tested everything and it
seems to be working fine. Please check out the latest version from SVN
and let me know if there are any issues.</div>
<div><br>
</div>
<div>This will be part of the next Opal release that we are planning
for end of this month. Thanks again for your contribution!</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Sriram</div>
<div><br>
<div>
<div>On Sep 2, 2009, at 5:28 AM, Anthony Bretaudeau wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000"> Hi!<br>
After testing, I've managed to make job exec time visualization work
with the following code (replace line 389 with it in
src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java):<br>
<br>
}else if (dialect.equals("org.hibernate.dialect.MySQLDialect")){<br>
//this is MySQL<br>
query = "select jobInfo.start_time_date as date, " +<br>
//number of day <br>
" avg( ( last_update_date - start_time_date ) * 86400 +
" +<br>
//plus number of seconds (epoch returns seconds!)<br>
" ( time_to_sec(last_update_time) -
time_to_sec(start_time_time) )) as average " + queryTail;<br>
}<br>
<br>
Feel free to include this in next release if it can help other users.<br>
Thanks.<br>
Anthony<br>
<br>
Anthony Bretaudeau a écrit :
<blockquote cite="mid:4A9...@ir..." type="cite">
<pre wrap="">Oh yes, the exec time has a problem. I hadn't noticed that.
Is this the only SQL request using local SQL dialect? In this case,
something like "unix_timestamp( last_update_time - start_time_time ) as
average" should work for MySQL (copying the rest of the request from
PostgreSQL). If I have time, I'll try to test it.
Thanks
Anthony
Luca Clementi a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Anthony Bretaudeau wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi!
We've had a problem using MySQL database for storing opal2 jobs data
instead of the default HSQLDB.
It turned out it was a timeout problem which is quite well described
at the following address:
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/">http://www.databasesandlife.com/automatic-reconnect-from-hibernate-to-mysql/</a>.
Briefly: mysql closes connection after an 8h timeout (which is quite
frequent for us, but not for servers where there is more activity).
We solved it by using c3p0 to manage database connection.
Here is what we have done to use it:
</pre>
</blockquote>
<pre wrap="">Anthony,
I expect the dashboard to have some problem visualizing the exec time
of your jobs.
Have a look at line 365:
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup">http://opaltoolkit.svn.sourceforge.net/viewvc/opaltoolkit/tags/opal2-core-2.0.0/src/edu/sdsc/nbcr/opal/dashboard/persistence/DBManager.java?revision=381&view=markup</a>
Unfortunately I could not find a way to make the query working using
Hibernate SQL and I had to use the local SQL dialect.
Given that I think we should start using some connection manager since
it is also recommended by the Hibernate guys.
Sincerely,
Luca
</pre>
<blockquote type="cite">
<pre wrap="">-Added c3p0 package in $opal_sources/lib/ and modified build.xml
consequently
-Created $opal_sources /etc/c3p0.properties and added "
c3p0.preferredTestQuery=SELECT 1; " in it.
-In build.xml, after <include name="OpalState.hbm.xml"/> added
<include name="c3p0.properties"/>
-In $OPAL_SOURCES/etc/hibernate-opal.cfg.xml, replaced:
<!-- JDBC connection pool (use the built-in) -->
<!--<property name="connection.pool_size">1</property>-->
By these lines:
<!-- JDBC connection pool (use c3p0) -->
<property name="c3p0.min_size">1</property>
<property name="c3p0.max_size">20</property>
<property name="c3p0.timeout">1800</property>
<property name="c3p0.max_statements">50</property>
<property name="c3p0.idle_test_period">1800</property>
<property
name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property>
Maybe it would be a good idea to include it in a future version of opal?
Bye!
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://p.sf.net/sfu/bobj-july">http://p.sf.net/sfu/bobj-july</a>
_______________________________________________
Opaltoolkit-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Opa...@li...">Opa...@li...</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users">https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users</a>
</pre>
</blockquote>
</div>
------------------------------------------------------------------------------<br>
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day <br>
trial. Simplify your report design, integration and deployment - and
focus on <br>
what you do best, core application coding. Discover what's new with <br>
Crystal Reports now. <a moz-do-not-send="true"
href="http://p.sf.net/sfu/bobj-july_______________________________________________">http://p.sf.net/sfu/bobj-july_______________________________________________</a><br>
Opaltoolkit-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Opa...@li...">Opa...@li...</a><br>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users">https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>
|
|
From: Luca C. <luc...@gm...> - 2009-09-13 22:35:18
|
On Fri, Sep 11, 2009 at 2:22 AM, Anthony Bretaudeau <ant...@ir...> wrote: > Hi! > > -There's also a new bug in svn: our servers are not running on the 8080 > port, so the dashboard has some problems with it (maybe you are aware of > it?). From what I have seen, there's at least one hard-coded 8080 port in > webapps/opal2/dashboard-jsp/serviceList.jsp on line 51 (there may be the > same bug in other files). Making this configurable would be quite useful! > Hey, That's my bad. It is from my last modification I made for the new service list. The second part of the URL at line 51 should be fetched from the OpalUrl param in the web.xml. Now on this computer I don't have any development tools, when I get a new computer if still there I will take a look at it. Sincerely, Luca |
|
From: Sriram K. <sr...@sd...> - 2009-09-14 22:47:48
|
Hello Anthony, Thanks for your comments. Responses inline - > -First, I've found a bug in my "typed WSDL addon": on a freshly > installed opal2 with the addon, you cannot deploy any service. So I > attach a patched file to put in OpalSOAPRequestFilter package. > Briefly, the problem was that the file WEB-INF/server-config.wsdd > (which is used by the filter) doesn't exists when no service is > deployed. Thanks. I will take a look at this once we are done with Opal release 2.1. A release candidate should be available soon, and we are hoping for a 2.1 release before the end of the month. > -I see you've included c3p0 and mysql connector packages (which is > great!), but their are not the latest versions available (0.9.1.1 > instead of 0.9.1.2 for c3p0 and 5.1.0 instead of 5.1.8 for mysql). I > have no particular problem with these older versions but I was > wondering if there was a reason for that... No particular reason. I had c3p0 version 0.9.1.1 and mysql version 5.1.0 working for another project - so decided to use that. However, I upgraded to the latest versions in SVN like you suggested, and everything still works fine. > -Speaking about c3p0, I've seen you haven't included the > "c3p0.preferredTestQuery=SELECT 1;" property. Is this intended? It > can be defined in $OPAL_SOURCES/etc/hibernate-opal.cfg.xml using > "<property name="c3p0.preferredTestQuery">SELECT 1;</property>". > Looking at the doc, it seems like it makes testing database > availability faster. This was an oversight on my part. It is now checked into SVN, and the performance does seem to be slightly better on initial testing. > -There's also a new bug in svn: our servers are not running on the > 8080 port, so the dashboard has some problems with it (maybe you are > aware of it?). From what I have seen, there's at least one hard- > coded 8080 port in webapps/opal2/dashboard-jsp/serviceList.jsp on > line 51 (there may be the same bug in other files). Making this > configurable would be quite useful! I fixed this in SVN. Now the serviceList.jsp uses the OPAL_URL parameter in the web.xml. I will add some documentation on how to configure this in the very near future. > Apart from that, Opal2 is running smoothly and the new application > list is great! > > You told me you could give me commit access to svn: if you're still > ok with that, do I need to create a sourceforge account? Yes, please. Send me an email with your SourceForge account, and I can give you access. We should also talk about protocols, practices, etc for committing code. Cheers, Sriram |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X