Hi,
One thing that I would like to see is the ability to change
certain container properties at runtime. Currently the containers need
to be restarted for the changes to take effect. The following are the
properties I would like to be made configurable
BMP Container:- PoolSize
Stateless Container:- TimeOut,PoolSize,StrictPooling
Stateful Container:- TimeOut,PoolSize,BulkPassivate
MDB Container:- InstanceLimit.
The reason for this is that users using openejb embedded in an app
server say geronimo should be able to change these parameters at
runtime. Currently they need to restart the server. I didn't include
the other properties because they don't look like properties that
should be configured at runtime.
The general approach I am thinking of here is
a) PoolSize: If pool size is increased above the current limit just
expand the pool. If it is decreased prevent creation of new instances
until the pool size reduces to the new size.
b) For the other properties update the newly created instances with
the new values. So once the older instances are recycled the new
values will be in effect.
I would like to incorporate these changes into openejb before 3.0
final. Primary reason for this is to allow an administrator to
configure these from server console at runtime.
David Blevins was telling me the other day that the pooling
implementation in OEJB can be improved. Did a search in Apache showed
and found a project called commons-pool.Probably it can be
investigated and if found suitable the pooling can be rewritten to use
commons-pool.
Regards
Manu
On Mon, Mar 3, 2008 at 2:32 AM, Jonathan Gallimore
<[EMAIL PROTECTED]> wrote:
> Hi
>
> I posted this:
>
> http://www.nabble.com/ClassFormatError-when-deploying-an-EJB2-CMP-bean-with-a-many-to-one-relationship-td15148184.html
> on the mailing list a little while ago, and also added Jira issue 750.
>
> Basically I was running into some trouble deploying a CMP entity bean
> with a many to one relationship, and one of classes generated by the
> deployment process had duplicate methods in it.
>
> I'm not sure if I'm doing something wrong in my app, or whether its a
> bug - if its a bug I think it would be nice to have it fixed in the
> final release of 3.0. I attached a potential fix to the Jira (its only a
> three liner).
>
> Cheers
>
> Jon
>
>
>
>
> David Blevins wrote:
> > So it seems like we've gotten the feedback we're going to get on the
> > 3.0-beta-2. We just have a handful of issues left to clean up:
> >
> >
> >
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310530&fixfor=12312805
> >
> >
> > I'd say once we get these completed, we should cut the big 3.0 final.
> >
> > Anything you'd like to see get in not in that list? Thoughts?
> >
> > -David
> >
>
>
