[jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-12-16 Thread Forrest Xia (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Forrest Xia updated GERONIMO-5712:
--

Fix Version/s: 2.1.8

 Geronimo should remember the  monitoring server enablement status.
 --

 Key: GERONIMO-5712
 URL: https://issues.apache.org/jira/browse/GERONIMO-5712
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.6, 2.2, 3.0
Reporter: Shawn Jiang
Assignee: Shenghao Fang
 Fix For: 2.1.8, 3.0

 Attachments: G5712.patch, GERONIMO-5712-3.0.patch


 Currently , when a monitor user can use the monitoring function only after a 
 admin user add/enable the server and enable query on the servers.
 But after the server restart, the enable status become disable automatically 
 so the the admin user have to do the enablement again so that Monitor user 
 could continue use the monitoring console.
 To resolve this, we should make the server and query thread enablement status 
 persistent.   so that we could start the query thread once the server is 
 restarted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-08-01 Thread Shenghao Fang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shenghao Fang updated GERONIMO-5712:


Patch Info: [Patch Available]

 Geronimo should remember the  monitoring server enablement status.
 --

 Key: GERONIMO-5712
 URL: https://issues.apache.org/jira/browse/GERONIMO-5712
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.6, 2.2, 3.0
Reporter: Shawn Jiang
Assignee: Shenghao Fang
 Attachments: G5712.patch, GERONIMO-5712-3.0.patch


 Currently , when a monitor user can use the monitoring function only after a 
 admin user add/enable the server and enable query on the servers.
 But after the server restart, the enable status become disable automatically 
 so the the admin user have to do the enablement again so that Monitor user 
 could continue use the monitoring console.
 To resolve this, we should make the server and query thread enablement status 
 persistent.   so that we could start the query thread once the server is 
 restarted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: [jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-26 Thread Yi Xiao
All right, it's just some of my suggestions[?]

On Tue, Jul 26, 2011 at 1:43 PM, Shenghao Fang (JIRA) j...@apache.orgwrote:


 [
 https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]

 Shenghao Fang updated GERONIMO-5712:
 

 Attachment: GERONIMO-5712-3.0.patch

 The patch for Geronimo 3.0.

  Geronimo should remember the  monitoring server enablement status.
  --
 
  Key: GERONIMO-5712
  URL: https://issues.apache.org/jira/browse/GERONIMO-5712
  Project: Geronimo
   Issue Type: Bug
   Security Level: public(Regular issues)
 Affects Versions: 2.1.6, 2.2, 3.0
 Reporter: Shawn Jiang
 Assignee: Shenghao Fang
  Attachments: G5712.patch, GERONIMO-5712-3.0.patch
 
 
  Currently , when a monitor user can use the monitoring function only
 after a admin user add/enable the server and enable query on the servers.
  But after the server restart, the enable status become disable
 automatically so the the admin user have to do the enablement again so that
 Monitor user could continue use the monitoring console.
  To resolve this, we should make the server and query thread enablement
 status persistent.   so that we could start the query thread once the server
 is restarted.

 --
 This message is automatically generated by JIRA.
 For more information on JIRA, see: http://www.atlassian.com/software/jira





-- 
Best regards!


   John Xiao
330.gif

[jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-25 Thread Shenghao Fang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shenghao Fang updated GERONIMO-5712:


Attachment: GERONIMO-5712-3.0.patch

The patch for Geronimo 3.0.

 Geronimo should remember the  monitoring server enablement status.
 --

 Key: GERONIMO-5712
 URL: https://issues.apache.org/jira/browse/GERONIMO-5712
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.6, 2.2, 3.0
Reporter: Shawn Jiang
Assignee: Shenghao Fang
 Attachments: G5712.patch, GERONIMO-5712-3.0.patch


 Currently , when a monitor user can use the monitoring function only after a 
 admin user add/enable the server and enable query on the servers.
 But after the server restart, the enable status become disable automatically 
 so the the admin user have to do the enablement again so that Monitor user 
 could continue use the monitoring console.
 To resolve this, we should make the server and query thread enablement status 
 persistent.   so that we could start the query thread once the server is 
 restarted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-21 Thread Shenghao Fang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shenghao Fang updated GERONIMO-5712:


Affects Version/s: 3.0
 Assignee: Shenghao Fang  (was: Shawn Jiang)

 Geronimo should remember the  monitoring server enablement status.
 --

 Key: GERONIMO-5712
 URL: https://issues.apache.org/jira/browse/GERONIMO-5712
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.6, 2.2, 3.0
Reporter: Shawn Jiang
Assignee: Shenghao Fang
 Attachments: G5712.patch


 Currently , when a monitor user can use the monitoring function only after a 
 admin user add/enable the server and enable query on the servers.
 But after the server restart, the enable status become disable automatically 
 so the the admin user have to do the enablement again so that Monitor user 
 could continue use the monitoring console.
 To resolve this, we should make the server and query thread enablement status 
 persistent.   so that we could start the query thread once the server is 
 restarted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: [jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-21 Thread Yi Xiao
First, I think if the monitoring function does not effect the server's
runtime performance, we could start it automatically.
Otherwise, maybe we could give some options, also including the risk tips
when the user enable query on the server, such as, ask him/her whether need
to remember the enable operation.

On Thu, Jul 21, 2011 at 3:05 PM, Shenghao Fang (JIRA) j...@apache.orgwrote:


 [
 https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]

 Shenghao Fang updated GERONIMO-5712:
 

Affects Version/s: 3.0
 Assignee: Shenghao Fang  (was: Shawn Jiang)

  Geronimo should remember the  monitoring server enablement status.
  --
 
  Key: GERONIMO-5712
  URL: https://issues.apache.org/jira/browse/GERONIMO-5712
  Project: Geronimo
   Issue Type: Bug
   Security Level: public(Regular issues)
 Affects Versions: 2.1.6, 2.2, 3.0
 Reporter: Shawn Jiang
 Assignee: Shenghao Fang
  Attachments: G5712.patch
 
 
  Currently , when a monitor user can use the monitoring function only
 after a admin user add/enable the server and enable query on the servers.
  But after the server restart, the enable status become disable
 automatically so the the admin user have to do the enablement again so that
 Monitor user could continue use the monitoring console.
  To resolve this, we should make the server and query thread enablement
 status persistent.   so that we could start the query thread once the server
 is restarted.

 --
 This message is automatically generated by JIRA.
 For more information on JIRA, see: http://www.atlassian.com/software/jira





-- 
Best regards!


   John Xiao


Re: [jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-21 Thread Kevan Miller

On Jul 21, 2011, at 6:31 AM, Yi Xiao wrote:

 First, I think if the monitoring function does not effect the server's 
 runtime performance, we could start it automatically. 
 Otherwise, maybe we could give some options, also including the risk tips 
 when the user enable query on the server, such as, ask him/her whether need 
 to remember the enable operation.

Hi John,
Personally, I'm of the opinion that less is more. We know that starting the 
monitoring function will have *some* effect on startup time, memory, etc. 
Though probably only a small effect. I'd prefer to see it defaulting to off and 
remember when it has been enabled.

--kevan

Re: [jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2011-07-21 Thread Shenghao Fang
Agree with Kevan. Setting the status to off by default and keeping the
status when it has been enabled is a reasonable behavior.

2011/7/21 Kevan Miller kevan.mil...@gmail.com:

 On Jul 21, 2011, at 6:31 AM, Yi Xiao wrote:

 First, I think if the monitoring function does not effect the server's 
 runtime performance, we could start it automatically.
 Otherwise, maybe we could give some options, also including the risk tips 
 when the user enable query on the server, such as, ask him/her whether need 
 to remember the enable operation.

 Hi John,
 Personally, I'm of the opinion that less is more. We know that starting the 
 monitoring function will have *some* effect on startup time, memory, etc. 
 Though probably only a small effect. I'd prefer to see it defaulting to off 
 and remember when it has been enabled.

 --kevan



-- 
Michael


[jira] Updated: (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.

2010-12-07 Thread viola.lu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

viola.lu updated GERONIMO-5712:
---

Attachment: G5712.patch

Pls submit the patch to keep status true after stop.Thanks.


 Geronimo should remember the  monitoring server enablement status.
 --

 Key: GERONIMO-5712
 URL: https://issues.apache.org/jira/browse/GERONIMO-5712
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.1.6, 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
 Attachments: G5712.patch


 Currently , when a monitor user can use the monitoring function only after a 
 admin user add/enable the server and enable query on the servers.
 But after the server restart, the enable status become disable automatically 
 so the the admin user have to do the enablement again so that Monitor user 
 could continue use the monitoring console.
 To resolve this, we should make the server and query thread enablement status 
 persistent.   so that we could start the query thread once the server is 
 restarted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.