I remember doing something like that when I worked initially on
Statistics but Gavin did not like it and I did not like it enough to
argue. I never committed it.
The main problem is that it feels odd for Hibernate to be responsible
for the Bean Server startup.
If we nevertheless go that p
To be sure, hibernate.generate_statistics is usually not enough if you
want to use a monitoring tool (since it is generally not the case that
your monitoring tool is running in the same VM as the hibernate app and
can access the statistics object directly).
The main problem is that it feels od
Since this code deals with JMX, I'd rather see this functionality as
part of the hibernate-jmx module which I am totally fine making JDK 1.5
specific. The implication of that though is that you'd need to move all
code outside of the hibernate-core module and bootstrap it another way
(perhaps as a
Hello,
because of HSEARCH-268( optimize indexes in parallel ) but also for
other purposes, I am in need to define a new ThreadPool in Hibernate
Search's
Lucene backend.
The final effect will actually be that all changes to indexes are
going to be performed in parallel (on different indexes).
I cons
On Nov 20, 2008, at 11:47, John Mazzitelli wrote:
To be sure, hibernate.generate_statistics is usually not enough if
you want to use a monitoring tool (since it is generally not the
case that your monitoring tool is running in the same VM as the
hibernate app and can access the statistics
I don't know the MBean security model. How do I
ensure that an given MBean is restricted in view / write access?
This is a good point. But I would say that security could be imposed on
the level of JMX remoting. For example, I could enable SSL on the JMX
connector using SUN's com.sun.managment
Sorry I wrote something stupid:
"3)use a size equal to the number of DirectoryProviders (this is the
optimal value, could be the default and be overriden by a parameter)"
is not true, this is not related to the optimal value. please discard
this option.
I think the best option would be to have a s
Spring and a lot of other containers like JBoss's Microcontainer make
it pretty easy to deploy the statistics MBean.
E.g. in Spring:
You assume the hibernate app is always running in a container that
supports that.
But, by definition, Hibernate is not required to be running in any kind
of container environment - it is designed to be able to run even in a
simple J2SE environment.
As such, it should not solely rely on its e
On Thu, Nov 20, 2008 at 5:00 PM, John Mazzitelli <[EMAIL PROTECTED]> wrote:
> You assume the hibernate app is always running in a container that supports
> that.
>
> But, by definition, Hibernate is not required to be running in any kind of
> container environment - it is designed to be able to run
But even under JSE it's
trivial to publish an MBean in a few lines of Java code as well:
Well, that's my whole point in this exercise. We shouldn't require
people to introduce this code (albeit trivial) in their app just so it
can be monitored (after all, how many app developers actually take
11 matches
Mail list logo
