Fixed this with JIRA https://issues.apache.org/jira/browse/GERONIMO-4883
Shawn Jiang resolved GERONIMO-4883.
---
Resolution: Fixed
Fix Version/s: 3.0
2.2
2.1.5
Fixed in 21 branch,22 branch, and trunk.
On Tue, Sep 15,
Right, I'm planing to ship both of them but mark ejb agent as
load=false. So that the user will use JMX as default monitoring agent.
When the users do not need EJB, they can create a EJB free assembly easily
without breaking the monitoring.
Does anyone have any other comments ?
On Mon, Sep
Then we would also need to change the default option when creating a server
to monitor in the monitoring console. Current default is EJB.
-Jack
On Mon, Sep 14, 2009 at 2:52 PM, Shawn Jiang genspr...@gmail.com wrote:
Right, I'm planing to ship both of them but mark ejb agent as
load=false.
On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:
Right, I'm planing to ship both of them but mark ejb agent as
load=false. So that the user will use JMX as default monitoring
agent.
When the users do not need EJB, they can create a EJB free assembly
easily without breaking the
On Mon, Sep 14, 2009 at 11:26 PM, Kevan Miller kevan.mil...@gmail.comwrote:
On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:
Right, I'm planing to ship both of them but mark ejb agent as
load=false. So that the user will use JMX as default monitoring agent.
When the users do not need
On Sep 14, 2009, at 8:41 AM, Shawn Jiang wrote:
On Mon, Sep 14, 2009 at 11:26 PM, Kevan Miller
kevan.mil...@gmail.com wrote:
On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:
Right, I'm planing to ship both of them but mark ejb agent as
load=false. So that the user will use JMX as
Good to see that happen :-)
So looks like it's a random choice...
If there's no particular reasons (like performance etc.), I'd recommend that
we use JMX agent as the default instead of the EJB agent, as the latter has
a dependency on the EJB container.
-Jack
On Thu, Sep 10, 2009 at 1:19 PM, Shawn Jiang
