> i'm searching for a problem we've been having about opening multiple XA Data
> sources for oracle,
> (opening the second hands jboss and throws an meta-aware exception, this
> happens in jboss 4.2)
This might help :-)
http://management-platform.blogspot.com/2008/11/transaction-recovery-in-jb
> Though I have less knowledge in Hibernate. I am interested in working
> with new development and fixes
Feel free to finish this for me :)
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3593
Read the full thread for background and what needs to be done:
http://lists.jboss.org/
hibernate-jmx is actually news to me - I didn't realize there was such a
module.
Is it easy for someone with an existing app to plop this hibernate-jmx
module (.jar?) in their app deployment and have it "just work"?
I'm curious if this is going to be shipped with, say, JBossAS, so its
alread
That's saying "use the platform MBeanServer" *and* "use the
MBeanServer with a default domain name of "my_mbean_server". Which
takes effect? I didn't want someone to do something confusing like this.
I understand. But we can raise a config exception and fail fast. With
your approach, if I nam
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
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
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
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
I recently added support to Jopr, The JBoss management platform project
( http://www.jboss.org/jopr ) to be able to monitor Hibernate via the
Hibernate Statistics MBean.
For background, see my blog entry:
http://management-platform.blogspot.com/2008/11/monitoring-hibernate.html
and more spec
