Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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, 2009 at 12:45 AM, David Jencks david_jen...@yahoo.comwrote: 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.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 EJB, they can create a EJB free assembly easily without breaking the monitoring. Does anyone have any other comments ? Agreed that this would be more convenient for most users. I don't recall any specific reason why agent-jmx wasn't included. Vaguely recall that ejb support was developed first because MEJB support is required per the EE spec. Does it mean that we still have to keep ejb agent on by default to meet the EE spec ? no, the monitoring is not part of the spec so we can use anything we want. thanks david jencks --kevan -- Shawn -- Shawn
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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 14, 2009 at 9:56 AM, Jack Cai greensi...@gmail.com wrote: 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 genspr...@gmail.com wrote: Whenever a user wants to use jmx monitor, he/she needs to install agent-car-jmx plugin firstly. Why not to ship this plugin with geronimo while keep it load=false in config.xml by default ? IMO, this size of agent-car-jmx plugin is only 13Kb. It's not a problem to bundle it with geronimo server as long as we make it load=false by default. Any ideas ? -- Shawn -- Shawn
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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. 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 14, 2009 at 9:56 AM, Jack Cai greensi...@gmail.com wrote: 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 genspr...@gmail.com wrote: Whenever a user wants to use jmx monitor, he/she needs to install agent-car-jmx plugin firstly. Why not to ship this plugin with geronimo while keep it load=false in config.xml by default ? IMO, this size of agent-car-jmx plugin is only 13Kb. It's not a problem to bundle it with geronimo server as long as we make it load=false by default. Any ideas ? -- Shawn -- Shawn
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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 monitoring. Does anyone have any other comments ? Agreed that this would be more convenient for most users. I don't recall any specific reason why agent-jmx wasn't included. Vaguely recall that ejb support was developed first because MEJB support is required per the EE spec. --kevan
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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 EJB, they can create a EJB free assembly easily without breaking the monitoring. Does anyone have any other comments ? Agreed that this would be more convenient for most users. I don't recall any specific reason why agent-jmx wasn't included. Vaguely recall that ejb support was developed first because MEJB support is required per the EE spec. Does it mean that we still have to keep ejb agent on by default to meet the EE spec ? --kevan -- Shawn
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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 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 ? Agreed that this would be more convenient for most users. I don't recall any specific reason why agent-jmx wasn't included. Vaguely recall that ejb support was developed first because MEJB support is required per the EE spec. Does it mean that we still have to keep ejb agent on by default to meet the EE spec ? no, the monitoring is not part of the spec so we can use anything we want. thanks david jencks --kevan -- Shawn
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
Good to see that happen :-)
Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?
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 genspr...@gmail.com wrote: Whenever a user wants to use jmx monitor, he/she needs to install agent-car-jmx plugin firstly. Why not to ship this plugin with geronimo while keep it load=false in config.xml by default ? IMO, this size of agent-car-jmx plugin is only 13Kb. It's not a problem to bundle it with geronimo server as long as we make it load=false by default. Any ideas ? -- Shawn
