proxool-developer — Developer's discussion list

Re: [Proxool-developer] Staring with the doc pages

[Bill H. <bi...@lo...>]

Hei Christian!

Good to hear from you :)

Actually, as soon as I sent that last message I realised that I should have
been clearer and not confused a Wiki with forking. Let me deal with each of
those in turn:

GitHub is an obvious place to host a Git repository. It gives you a Wiki
that makes it much easier to maintain the documentation. The Wiki is only
editable by designated collaborators (equivalent to the small group of
committers we have at SourceForge). It's not the only solution by far but
it's much easier to change than the present documentation which is just
static HTML. I'm approaching this from the aspect of that there needs to be
almost zero developer effort since I'm not aware of anyone having time to
work on this. Copy and pasting from the current website into GitHub Wiki
would be relatively easy.

If anyone is prepared to put the effort in, getting the documentation under
source control would be wonderful. It isn't at the moment. I'm open to any
suggestions.

As to "collaboration through forking", Git makes it simple (even desirable)
for external collaborators (ones that we haven't chosen or selected in any
way) to fork the project and make their own changes as they see fit. Git
also makes it simple to pull those changes back into the master repository
(in a controlled way). The whole thing is much more democratic with each
commit making it back into the project on its own merits.

-
Bill

Re: [Proxool-developer] Staring with the doc pages

[Christian N. <chr...@em...>]

Hi.

Long time no hear :)

I haven't familiarized myself with Git yet. Could you elaborate a bit on
what you mean by "collaboration through forking" and why that is desirable?

In my opinion a Wiki is fine for HOWTOs and other secondary documentation,
but I think it's better to keep the formal documentation under version
control to keep it under adequate quality control and in sync with the
version the user actually are using.

Christian

On Thu, Apr 9, 2009 at 7:47 AM, Bill Horsman <bi...@lo...>wrote:

> Hello Abhishek,
>
> No it's not a Wiki but probably should be. I'm minded to move the whole
> project to Github - it allows a lot more collaboration through forking and
> the Wiki works well. Anyone have an opinion on that?
>
> -
> Bill
>
> 2009/4/8 Abhishek Manocha <abh...@gm...>
>
>> hi All,
>>
>> Started using proxool and found some descrepencies in documentation to
>> satrt with. Just for an example, AdminServlet fully qualifies location in
>> the Configuration doc page is not right. That's not on wiki I presume and
>> whom or how to get that corrected? Pointers?
>>
>> Abhishek Manocha
>> --
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> High Quality Requirements in a Collaborative Environment.
>> Download a free trial of Rational Requirements Composer Now!
>> http://p.sf.net/sfu/www-ibm-com
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

[Proxool-developer] house keeping sleep time

[Abhishek M. <abh...@gm...>]

in case of scenario of where 10 connections need to be maintained in the
pool,
what should be the simultaneous-build-throttle and house-keeping-sleep-time
in other words what these parameters are for?
Does housekeeping threads make connection to db in that case shouldn't I be
keeping that high instead of 30s default?

Regarding AdminServlet provided for checking out the bottleneck of the
connection, I am getting weird connections created at 30 40 secs or so
in lots of 2, 3 or 4 connections created at same time, my code is not
creating any such connections so the AdminServlet has complicated the matter
instead of solving.
Can you guys please help me in letting me know how to debug and check which
connections are not getting released through AdminServlet

Thanks
--Abhishek

[Proxool-developer] Configuring simultaneous-build-throttle and other

[Abhishek M. <abh...@gm...>]

how can i configure

simultaneous-build-throttle:
 maximum-connection-lifetime:
 maximum-active-time:

in proxool through proxool.xml or the or web.xml?
i mean should it go in init-param of Servletconfigurator or the proxool.xml
configuration?

[Proxool-developer] quick Clarification

[Abhishek M. <abh...@gm...>]

hi,

Will using
<init-param>
    <param-name>autoShutdown</param-name>
    <param-value>true</param-value>
  </init-param>

in Servletconfigurator (or letting it default true)
remove all the proxool pools may be used by other web applications also in
same web server. Can't help, documentation was ambiguous at that point.

And the second more important one, how can I make sure that
Servletconfigurator is the last one to get destroyed and so the pools remain
active in my web app. My scenarios is that I have 4-5 servlets all getting
connection from the same pool, I want to make it absolute that
pool remains there through ServletConfigurator even if the service of other
servlets is not called for a considerable amount of time

--Abhishek Manocha

Re: [Proxool-developer] Staring with the doc pages

[Bill H. <bi...@lo...>]

Hello Abhishek,

No it's not a Wiki but probably should be. I'm minded to move the whole
project to Github - it allows a lot more collaboration through forking and
the Wiki works well. Anyone have an opinion on that?

-
Bill

2009/4/8 Abhishek Manocha <abh...@gm...>

> hi All,
>
> Started using proxool and found some descrepencies in documentation to
> satrt with. Just for an example, AdminServlet fully qualifies location in
> the Configuration doc page is not right. That's not on wiki I presume and
> whom or how to get that corrected? Pointers?
>
> Abhishek Manocha
> --
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

[Proxool-developer] Staring with the doc pages

[Abhishek M. <abh...@gm...>]

hi All,

Started using proxool and found some descrepencies in documentation to satrt
with. Just for an example, AdminServlet fully qualifies location in the
Configuration doc page is not right. That's not on wiki I presume and whom
or how to get that corrected? Pointers?

Abhishek Manocha
--

[Proxool-developer] Question about Proxool connection pool

[Shan, G. (GE H. consultant) <Guo...@ge...>]

Hi,
 
I have been using struts + spring + proxool for a few years in B/S
system, It works fine.
Recently, i have found the following error massage in log file

Exception message and stack trace:
org.springframework.jdbc.UncategorizedSQLException:
PreparedStatementCallback; uncategorized SQLException for SQL [ A Simple
SQL Query ]; SQL state [null]; error code [0]; Couldn't perform the
operation prepareStatement: You can't perform any operations on this
connection. It has been automatically closed by Proxool for some reason
(see logs).; nested exception is java.sql.SQLException: Couldn't perform
the operation prepareStatement: You can't perform any operations on this
connection. It has been automatically closed by Proxool for some reason
(see logs).
java.sql.SQLException: Couldn't perform the operation prepareStatement:
You can't perform any operations on this connection. It has been
automatically closed by Proxool for some reason (see logs).
 at
org.logicalcobwebs.proxool.WrappedConnection.invoke(WrappedConnection.ja
va:207)
 at
org.logicalcobwebs.proxool.WrappedConnection.intercept(WrappedConnection
.java:87)
 at
oracle.jdbc.internal.OracleConnection$$EnhancerByProxool$$df763430.prepa
reStatement(<generated>)
 at
org.springframework.jdbc.core.PreparedStatementCreatorFactory$PreparedSt
atementCreatorImpl.createPreparedStatement(PreparedStatementCreatorFacto
ry.java:216)
 at
org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:470
)
 at
org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:528)
 at
org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:553)
 at
org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:574)
 at org.springframework.jdbc.object.SqlQuery.execute(SqlQuery.java:102)
 at org.springframework.jdbc.object.SqlQuery.execute(SqlQuery.java:112)
 at
common.database.DBQueryProcessor.executeQuery(DBQueryProcessor.java:89)
 at common.dao.impl.LoginDao.getLoginUserInfo(LoginDao.java:159)
 at
common.service.impl.LoginService.getLoginUserInfo(LoginService.java:83)
 at common.action.LoginAction.login(LoginAction.java:75)
 at sun.reflect.GeneratedMethodAccessor186.invoke(Unknown Source)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at
org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.j
ava:270)
 at
org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:187
)
 at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.java:431)
 at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
236)
 at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
 at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
 at
com.gehc.nozomi.common.filter.AccessFilter.doFilter(AccessFilter.java:53
)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
 at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
r.java:96)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
 at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
sociationValve.java:175)
 at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
ava:74)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
 at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnecti
onValve.java:156)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
 at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
 at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
697)
 at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.
java:889)
 at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)
 at java.lang.Thread.run(Thread.java:595)
 
the configuration file of Proxool is:
 
<?xml version="1.0" encoding="UTF-8"?>
<proxool-config>
 <proxool>
  <alias>XX</alias>
  <driver-url>
   jdbc:oracle:thin:@XX.XX.XX.XX:port:SID
  </driver-url>
  <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
  <driver-properties>
   <property name="user" value="XX" />
   <property name="password" value="XX" />
  </driver-properties>
  <maximum-connection-lifetime>7200000</maximum-connection-lifetime>
  <maximum-active-time>300000</maximum-active-time>
  <minimum-connection-count>30</minimum-connection-count>
  <maximum-connection-count>500</maximum-connection-count>
  <house-keeping-sleep-time>90000</house-keeping-sleep-time>
  <house-keeping-test-sql>
   SELECT CURRENT_DATE FROM DUAL
  </house-keeping-test-sql>
 </proxool>
</proxool-config>

 
the Env of System is :
OS: Sun Solaris10
DB: Oracle10g(RAC)
JDK: 1.5.6
Framework: 
    Struts 1.0
    Spring 1.2.8
    DWR 2.0.5
    Proxool 0.9.0RC3
 
This error often happens when we do query operation. For example, when
we click on a button in a page to search data from DB,the error page
happened. The error massage is shown above.But when we go back and do
the same operation on that page, the error will probaly not happen.A
moment later, this error may happen again.
 
Would you please give me some advice on this problem?
I am looking forward to your reply.Thanks.
 
Best Regards,
Joe
 

Re: [Proxool-developer] suggestion

[Bill H. <bi...@lo...>]

Hello,

You're not the first person to ask for this. It's not as simple as it
sounds, although it is possible. Our design decision was based on early JVMs
that weren't very good at coping when things got busy. We reckoned that if
the site was so busy that we'd used up all the connections to our powerful
database then we really needed it to degrade nicely. Queueing up requests
just increased the load on the server and made the customers wait for an
unresponsive page. Much better to give a snappy answer to the customer to
say that we were unusually busy and to try again later.

Of course, not all situations are the same and JVM are a lot more mature
now. I can certainly see that it would make sense to build a queue.
Volunteers?

I don't do much Java these days and this project has slipped - it's not
getting the attention it deserves. I would like to releases 0.9.0 after it's
somewhat excessive release candidate period but can't promise when that will
be. I more than happy to give advice to anyone wishing to get their toes wet
in this project.

Good luck,
-
Bill

[Proxool-developer] suggestion

[黄文龙 <gz...@12...>]

 I have a question, when my all connections have been used,if a new thread want to get a new, it will get a wrong message, that is because have no visable connecion, it may be not good so.
I tested DBCP, when have no connecion for new request thread, it will wait there, not get a error message, and then return, so, I suggest proxool may should implementaed in such a way like BDCP.
 

--

不可乘喜而轻诺，不可因醉而生嗔，不可乘快而多事，不可因倦而鲜终。

[Proxool-developer] Congratulations

[jorge m. <jor...@ho...>]

Congratulations for your software, easy installation, easy use, well explained.
 
Success in your task.
 
 
Jorge
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx

[Proxool-developer] Proxool:How to connect SQL Server2005 Mirror Database?

[维波 张 <zwb...@ho...>]

HI:
         I don’t know to send a message to proxool developer, so I write this letter and want to deliver to them.
         Question: My databse is SQL Server 2005 Mirror Databse. Principal database(192.168.0.11), Mirror Databse(192.168.0.12) and Witness Databse(192.168.0.13).
         Proxool.xml setup:
         <?xml version="1.0" encoding="UTF-8"?>
<something-else-entirely>
    <proxool>
       <alias>Proxool</alias>
        <driver-url>jdbc:sqlserver://192.168.0.11:1433;DatabaseName=TestMirror;failoverParnter= 192.168.0.12</driver-url>
       <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
       <driver-properties>
           <property name="user" value="sa"/>
           <property name="password" value="zzzz"/>
       </driver-properties>
       <minimum-connection-count>50</minimum-connection-count>
       <maximum-connection-count>3000</maximum-connection-count>
       <maximum-active-time>300000</maximum-active-time>
       <house-keeping-sleep-time>30000</house-keeping-sleep-time>
       <house-keeping-test-sql>select CURRENT_DATE</house-keeping-test-sql>
    </proxool>
</something-else-entirely>
 
The web server I used is tomcat 5.5.9. Begin,tomcat setup,this setup is working normally.  When I stop the principal databse and the mirror databse is working ,the proxool setup is not working. If I restart tomcat server, the proxool is working normally. I don’t know the reason. Does the proxool not support Sql server 2005 mirror?
 
Please tell me the solutions. 
 
Best regards.
 
George
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

Re: [Proxool-developer] Thread safety?

[Bill H. <bi...@lo...>]

Hi Steve,

Sorry for the slow response. I think I'd like to see a test case running
with QuickFIX/J that reproduces this problem. It's pretty tricky to solve
this indirectly - there are just too many variables. And the log output
would be so useful.

-
Bill

Re: [Proxool-developer] Thread safety?

[Steve B. <st...@te...>]

> We do pay a lot of attention to thread safety and have made us of Doug
> Lea's
> concurrency libraries to solve that problem. It's possible that there
> is a bug, sure, but it's something we've thought a lot about and
> haven't had problems with before. (I mean, specifically the
> simultaneous build throttle).
>
> Can you tell me how you are configuring Proxool and how you are using it?

Hi Bill,

First, my users have seen this problem but I haven't personally seen it.
I want to do some more investigation about the version of QuickFIX/J they
are using. A user posted a bug related to the simultaneous build throttle
setting in 0.9.0RC2 and we worked around it. However, the user may be using
a version prior to the fix.

http://www.quickfixj.org/jira/browse/QFJ-316

As for how we use Proxool, it's pretty basic. We create a data source, set
some bean properties to configure it, and then proceed to use it.

> Also, your log file should output the configuration (if you make it
> appropriately verbose). It would be interesting to see whether you have
> more pools than you expect - or if that error occurs before the pool
> has been configured.

I'll need to ask my user to do this.

Looking at the 0.9.1, I'm not sure how the configuration could be thread
safe. The settings are stored in unprotected member fields. The data
source
getConnection() method can be called from multiple threads and those
configuration fields might not be consistent across processor caches.

I'm also wondering about the comment in the FastArrayList used to store
the pooled connections. It says the implementation is not cross-platform
and may fail unexpectedly on some architectures (presumedly due to
insufficient synchronization). If "some architectures" means multicore or
multiprocessor architectures, those are becoming very common. I noticed
the comment is from version 0.6. Is this not a concern?

Regards,

Steve

Re: [Proxool-developer] Thread safety?

[Steve B. <st...@te...>]

> We do pay a lot of attention to thread safety and have made us of Doug
> Lea's
> concurrency libraries to solve that problem. It's possible that there
> is a bug, sure, but it's something we've thought a lot about and
> haven't had problems with before. (I mean, specifically the
> simultaneous build throttle).
>
> Can you tell me how you are configuring Proxool and how you are using it?

Hi Bill,

First, my users have seen this problem but I haven't personally seen it.
I want to do some more investigation about the version of QuickFIX/J they
are using. A user posted a bug related to the simultaneous build throttle
setting in 0.9.0RC2 and we worked around it. However, the user may be using
a version prior to the fix.

http://www.quickfixj.org/jira/browse/QFJ-316

As for how we use Proxool, it's pretty basic. We create a data source, set
some bean properties to configure it, and then proceed to use it.

> Also, your log file should output the configuration (if you make it
> appropriately verbose). It would be interesting to see whether you have
> more pools than you expect - or if that error occurs before the pool
> has been configured.

I'll need to ask my user to do this.

Looking at the 0.9.1, I'm not sure how the configuration could be thread
safe. The settings are stored in unprotected member fields. The data
source
getConnection() method can be called from multiple threads and those
configuration fields might not be consistent across processor caches.

I'm also wondering about the comment in the FastArrayList used to store
the pooled connections. It says the implementation is not cross-platform
and may fail unexpectedly on some architectures (presumedly due to
insufficient synchronization). If "some architectures" means multicore or
multiprocessor architectures, those are becoming very common. I noticed
the comment is from version 0.6. Is this not a concern?

Regards,

Steve

Re: [Proxool-developer] Thread safety?

[Bill H. <bi...@lo...>]

Hi Steve,

We do pay a lot of attention to thread safety and have made us of Doug Lea's
concurrency libraries to solve that problem. It's possible that there is a
bug, sure, but it's something we've thought a lot about and haven't had
problems with before. (I mean, specifically the simultaneous build
throttle).

Can you tell me how you are configuring Proxool and how you are using it?
Also, your log file should output the configuration (if you make it
appropriately verbose). It would be interesting to see whether you have more
pools than you expect - or if that error occurs before the pool has been
configured.

-
Bill

[Proxool-developer] Thread safety?

[Steve B. <st...@te...>]

Hello,

 

I'm using the Proxool DataSource support within another open source project,
QuickFIX/J. Some of my users are reporting a problem that results in
exceptions like the following.

 

java.sql.SQLException: We are already in the process of making 1 connections
and the number of simultaneous 

builds has been throttled to 0

 

I am explicitly setting the simultaneous build throttle value to 10
(although that's supposed to be the default) and the error still occurs at
times. I'm wondering if it's possible that the configuration information is
not stored in a thread-safe manner (that would explain the "stale" zero
value). I see that the configuration properties are not final (makes sense)
and also not synchronized or declared volatile. Are the throttling
configurations potentially accessed by multiple threads? If so, shouldn't
they be synchronized or volatile?

 

This error has been reported with older versions of Proxool. I've upgraded
to the latest version, but I noticed the configurations are still not
synchronized or volatile so I'm wondering if this might still be an issue.

 

Thanks for any help you can provide.

 

Steve

 

Re: [Proxool-developer] new release of proxool

[Bill H. <bi...@lo...>]

Hi all,

Well, 0.9.0 is finally out :)

-
Bill

Re: [Proxool-developer] new release of proxool

[Bill H. <bi...@lo...>]

Good points. It would be nice to get it back up to speed. I'll take a look
at it next week when I'm back home.- Bill

On Sat, Aug 2, 2008 at 12:27 PM, <mor...@gm...> wrote:

It would be great to see a new release of proxool.  There are some bugs that
> have been fixed for a while in CVS (like the ProxoolDataSource user/password
> being overwritten).  This would make it an easier drop in replacement for
> DBCPs BasicDataSource.  Plus I know some companies can be official release
> oriented.
>
> Keep up the good work.  The events and admin servlets are good adds.
>
>

[Proxool-developer] new release of proxool

[<mor...@gm...>]

It would be great to see a new release of proxool.  There are some bugs that
have been fixed for a while in CVS (like the ProxoolDataSource user/password
being overwritten).  This would make it an easier drop in replacement for
DBCPs BasicDataSource.  Plus I know some companies can be official release
oriented.

Keep up the good work.  The events and admin servlets are good adds.

Re: [Proxool-developer] Proxool Alive?

[Bill H. <bi...@lo...>]

Hi Glen,

I'm glad Proxool is working well for you.

I guess the proxool-user list is the best place for advice about
maximum-connection-count, but since you're here... I'd choose a number such
that:

1. Your database can cope with the load. There's no point having 4,000
connections if each simple query is going to take several seconds.

2. Your app can take the load too. Even if the database is fantastic and can
execute whatever you can throw at it with ease, your app has still got to
cope too.

That second reason is partly why we made Proxool reject connections when we
reached the maximum. We figured that by the time we'd used them all up our
app was struggling to keep up and all we wanted to do was quickly respond
with a "please try later" message. Otherwise everything ground to a halt.

Cheers,
-- 
Bill Horsman
http://www.logicalcobwebs.com/bill_horsman

Re: [Proxool-developer] Proxool Alive?

[Glen P. <gl...@or...>]

We have been using it in production with JRE1.6 for a few months now
and it works very well, both in Linux (RHEL and a little bit on
Xubuntu) and Windows (XP).  We switched from c3p0 to Proxool because
we wanted to distribute our product to a customer and couldn't abide
by the LGPL.  Proxool has all the features (especially the license) we
need and has been very stable except for the issue you mention: when
too many people connect at once it rejects connections (we only see
this during security tests, not under actual load).

While we're on the subject, does anyone know what the largest safe
value is for jdbc-0.proxool.maximum-connection-count?  What's the
down-side of setting this to some fairly large value like 4,000?  Is
this even the right forum for asking such questions?

- Glen Peterson

On Tue, Jul 29, 2008 at 2:41 PM, Bill Horsman <bi...@lo...> wrote:
> Hi Alex,
>
> It's not quite dead yet! You're right about the long time since the last
> update.
>
> The 0.x does reflect it not being feature complete but I do consider it
> stable. Things have moved on a fair bit since we last actively developed it
> - we haven't looked at compatibility with JDK1.6 for instance. One feature
> request that comes up every now and again is the ability to queue
> connections rather than just rejecting them when the maximum connection
> count is reached.
>
> The mailing list, although very quiet, is still monitored.
>
> Tom's right - we are still accepting patches and make those available on
> CVS. Rolling 0.9.0 out the door would take me a couple of hours (mostly to
> do with updating the website, documentation and building the binaries) and
> it never quite gets done... I would like to do it but don't think I should
> make any promises about when it will get done.
>
> If anyone feels strongly about getting stuff done then let's talk about it.
> Most of the time, people don't seem that bothered.
>
> Cheers,
> --
> Bill Horsman
> http://www.logicalcobwebs.com/bill_horsman
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer

Re: [Proxool-developer] Proxool Alive?

[Bill H. <bi...@lo...>]

Hi Alex,

It's not quite dead yet! You're right about the long time since the last
update.

The 0.x does reflect it not being feature complete but I do consider it
stable. Things have moved on a fair bit since we last actively developed it
- we haven't looked at compatibility with JDK1.6 for instance. One feature
request that comes up every now and again is the ability to queue
connections rather than just rejecting them when the maximum connection
count is reached.

The mailing list, although very quiet, is still monitored.

Tom's right - we are still accepting patches and make those available on
CVS. Rolling 0.9.0 out the door would take me a couple of hours (mostly to
do with updating the website, documentation and building the binaries) and
it never quite gets done... I would like to do it but don't think I should
make any promises about when it will get done.

If anyone feels strongly about getting stuff done then let's talk about it.
Most of the time, people don't seem that bothered.

Cheers,
-- 
Bill Horsman
http://www.logicalcobwebs.com/bill_horsman

Re: [Proxool-developer] Proxool Alive?

[Tom D. <td...@te...>]

Hi Alex,

On Jul 29, 2008, at 1:22 PM, S. Alexandre M. Lemaire wrote:

> Just wondering if Proxool has been abandoned at all?  There haven’t  
> been any updates in a very long time, and the 0.x version leaves to  
> believe that the author deemed it incomplete as of its last  
> incarnation.

Can't speak for the development team but we're using it on a couple  
projects here and last time I submitted a patch it was accepted OK,  
although I don't think a new version was ever released...

Tom

[Proxool-developer] Proxool Alive?

[S. A. M. L. <sa...@sa...>]

Hi guys,

 

Just wondering if Proxool has been abandoned at all?  There haven't been any
updates in a very long time, and the 0.x version leaves to believe that the
author deemed it incomplete as of its last incarnation.

 

Bill?

 

Cheers.

Alex