Re: Reducing the dojo footprint in Geronimo
Shrey, As previously mentioned by Joe, the monitoring console uses pieces from dojox. This eliminates the possibility of removing the entirety of dojox, however you could break it apart keeping only the pieces required in, which would be mildly challenging, because as I recall there are a number of dependent files included in some of the charting components. Thanks, Erik B. Craig On Thu, Jun 26, 2008 at 3:33 AM, Shrey Banga [EMAIL PROTECTED] wrote: Hi all, I've been working on the EAR PlanCreator and I've observed that dojo is shipped with all the demos, tests and experimental widgets in place, causing the folder to be about 12.8 MB on the expanded server (2.2-SNAPSHOT). Looking at the various folders, I think we can achieve significant reduction in the dojo footprint and eventually of the server itself by removing the following components: dojo/tests - 579 KB dijit/tests - 551 KB dijit/demos - 909 KB dojox - 6.82 MB From a geronimo user's perspective, the tests suite is not of much use as they are meant to test the widgets provided by dojo itself which can be tested by separately downloading the given release instead of shipping it with the server. Similarly, the demos, which are used to exhibit dojo's capabilities, can be run directly from dojo's website or downloaded and run locally without the server. Also, people trying to learn from the demos tend to use the css provided for the purpose of the demo, which is not recommended. My rationale for removing the dojox is that these are marked as experimental by the dojo community and although some components are used often, keeping 6.8 MBs of code that is still experimental does not make sense. It is better to trust the dojo community to shift components from experimental to stable areas and then use them in further releases. Removing the stated components frees up about 8.7 MBs of space on the expanded server, which is huge for a javascript library. Since a Geronimo user can still include these components into his/her webapp we're not really stopping them from using these components, only transferring the overhead of using the lesser used components onto the user. -- Shrey Banga Bachelor of Technology, III year Department of Electrical Engineering Indian Institute of Technology Roorkee
Re: [ANNOUNCE] Welcoming Ted Kirby as a Geronimo Committer
Congratulations, Ted! On Thu, Jun 19, 2008 at 8:43 AM, Donald Woods [EMAIL PROTECTED] wrote: I'd like to welcome Ted Kirby as Geronimo's newest committer. Ted, keep up all the great work on the Eclipse Plugin and welcome aboard! -Donald -- Erik B. Craig
Re: Upgrading to Dojo 1.1.1
My only thoughts on this are... +1 On Jun 6, 2008, at 11:04 AM, Joseph Leong [EMAIL PROTECTED] wrote: Hi everyone, I've been tossing the idea around in my head of taking the initiative to upgrade the current items written in Dojo to 1.1.1, I know we still have some Dojo 0.4.3, which isn't supported anymore, in use and there has been vast improvements with their new Dijit package for widgets among many other items. Also, with some recently reported JIRAs about accessibility compatibility being an issue in these Dojo components we can make use of the a11y available in it. Overall, i also think we might also benefit a cleaner setup from streamlining our versions in terms of future development and maintenance as well. Although I haven't looked in complete detail in each of the AG Dojo pieces, i know that the 0.4.3 transition to 1.1.1 will take some work because the widget system has been separated out to it's own pieces (diji) and so simple work arounds will not do. That is, this will be a big block change rather than an incremental one. Does anyone have any thoughts - one way or the other on this undertaking? Thanks! Joseph Leong
Re: Upgrading to Dojo 1.1.1
Kevan, Actually I think the current 1.x version in trunk is 1.1.0, which is fully compatible with 1.1.1... as a result of this, it can just be upgraded in the 'dojo' plugin and be kept at the path of just /dojo On Fri, Jun 6, 2008 at 12:14 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Jun 6, 2008, at 11:52 AM, Jason Warner wrote: Would this let us remove Dojo 0.4.3 from the server or would we keep it there for users who might still be using it? If so, how long are we going to do that for? My vote would be to yank it out after we're no longer dependent on it, but I'm not sure what the community at large would think of that. Regardless, I like your idea, Joe. IMO, we would drop 0.4.3. I don't think we maintained for backward compatibility reasons, more because we didn't want to update the admin console code, at that point in time. I think it would be good to upgrade to 1.1.1. I also assume it would replace the current 1.0.2 version? Perhaps we should consider encoding the dojo version in the dojo path name. I'd prefer to see this work broken down into reasonable chunks (where possible), so that we can track progress (and others can participate). First add /dojo-1.1.1 and start incrementally moving code over to use new dojo. I don't know the internals of the admin console. So, not sure how well that work breaks down into manageable chunks. --kevan +1 On Fri, Jun 6, 2008 at 11:04 AM, Joseph Leong [EMAIL PROTECTED] wrote: Hi everyone, I've been tossing the idea around in my head of taking the initiative to upgrade the current items written in Dojo to 1.1.1, I know we still have some Dojo 0.4.3, which isn't supported anymore, in use and there has been vast improvements with their new Dijit package for widgets among many other items. Also, with some recently reported JIRAs about accessibility compatibility being an issue in these Dojo components we can make use of the a11y available in it. Overall, i also think we might also benefit a cleaner setup from streamlining our versions in terms of future development and maintenance as well. Although I haven't looked in complete detail in each of the AG Dojo pieces, i know that the 0.4.3 transition to 1.1.1 will take some work because the widget system has been separated out to it's own pieces (diji) and so simple work arounds will not do. That is, this will be a big block change rather than an incremental one. Does anyone have any thoughts - one way or the other on this undertaking? Thanks! Joseph Leong -- ~Jason Warner -- Erik B. Craig
Re: Upgrading to Dojo 1.1.1
And, erm... To further expand... I think having different versions of dojo in our plugins repository would be a good idea, at least having 0.4.x branch as well as the 1.x branch, with the latest being at /dojo, and any other (legacy) versions being installed would have a path of /dojo-x.x or /dojo/x.x (as is currently with dojo 0.4.3) On Fri, Jun 6, 2008 at 12:29 PM, Erik B. Craig [EMAIL PROTECTED] wrote: Kevan, Actually I think the current 1.x version in trunk is 1.1.0, which is fully compatible with 1.1.1... as a result of this, it can just be upgraded in the 'dojo' plugin and be kept at the path of just /dojo On Fri, Jun 6, 2008 at 12:14 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Jun 6, 2008, at 11:52 AM, Jason Warner wrote: Would this let us remove Dojo 0.4.3 from the server or would we keep it there for users who might still be using it? If so, how long are we going to do that for? My vote would be to yank it out after we're no longer dependent on it, but I'm not sure what the community at large would think of that. Regardless, I like your idea, Joe. IMO, we would drop 0.4.3. I don't think we maintained for backward compatibility reasons, more because we didn't want to update the admin console code, at that point in time. I think it would be good to upgrade to 1.1.1. I also assume it would replace the current 1.0.2 version? Perhaps we should consider encoding the dojo version in the dojo path name. I'd prefer to see this work broken down into reasonable chunks (where possible), so that we can track progress (and others can participate). First add /dojo-1.1.1 and start incrementally moving code over to use new dojo. I don't know the internals of the admin console. So, not sure how well that work breaks down into manageable chunks. --kevan +1 On Fri, Jun 6, 2008 at 11:04 AM, Joseph Leong [EMAIL PROTECTED] wrote: Hi everyone, I've been tossing the idea around in my head of taking the initiative to upgrade the current items written in Dojo to 1.1.1, I know we still have some Dojo 0.4.3, which isn't supported anymore, in use and there has been vast improvements with their new Dijit package for widgets among many other items. Also, with some recently reported JIRAs about accessibility compatibility being an issue in these Dojo components we can make use of the a11y available in it. Overall, i also think we might also benefit a cleaner setup from streamlining our versions in terms of future development and maintenance as well. Although I haven't looked in complete detail in each of the AG Dojo pieces, i know that the 0.4.3 transition to 1.1.1 will take some work because the widget system has been separated out to it's own pieces (diji) and so simple work arounds will not do. That is, this will be a big block change rather than an incremental one. Does anyone have any thoughts - one way or the other on this undertaking? Thanks! Joseph Leong -- ~Jason Warner -- Erik B. Craig -- Erik B. Craig
Re: [VOTE] ASF hosted machines for TCK Proposal
+1 On May 20, 2008, at 7:22 AM, Joe Bohn [EMAIL PROTECTED] wrote: If we are to take this proposal forward to the ASF Infrastructure team, they want assurance that the Geronimo PMC is behind the recommendation and supports the intended use of the systems. I think it also bodes well to demonstrate that the entire Geronimo community stands behind the proposal, particularly since we will administer the machines ourselves, - so I encourage all to vote. [ ] +1 I agree with the need and support the proposal. Present it to the ASF Infrastructure team. [ ] 0 No opinion [ ] -1 I don't see the need or disagree with the proposal. Do not present this proposal to the ASF Infrastructure team. I'll plan on calling this vote on Friday (5/23) morning (9 AM EST). PROPOSAL Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. This has allowed other Apache projects to test new products/releases by running JavaEE 5 TCK tests using the Apache Geronimo test infrastructure. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. A centralized testing environment allows the Geronimo community to more fully participate in the TCK process. Some committers don't have access to the hardware resources needed to run the Java EE TCK tests in a timely manner. Although some ad-hoc sharing of private machines has occurred, this is not ideal from a community perspective. Community controlled systems allow us to equitably share these resources. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine. We may increase the number of VM images if it is feasible. - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported. Admin Volunteers: - Joe Bohn (PMC) - Jay McHugh (PMC) - Jason Warner - Matt Hogstrom (PMC) - Kevan Miller (PMC)
Re: Google Analytics
Can someone add me to the list? [EMAIL PROTECTED] On Thu, May 15, 2008 at 2:32 AM, David Blevins [EMAIL PROTECTED] wrote: Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David -- Erik B. Craig
[jira] Assigned: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3996: --- Assignee: Erik B. Craig Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Erik B. Craig Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Geronimo Server 2.1.1 Release - RC2
+1 On Thu, Apr 24, 2008 at 6:41 AM, Joe Bohn [EMAIL PROTECTED] wrote: All, I've prepared a second release candidate of Geronimo Server 2.1.1 for your review and vote. The source for the Geronimo Server 2.1.1 release currently resides here: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.1 When the release vote is approved, I will svn mv the code to https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.1 An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-2.1.1-src.tar.gzhttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-2.1.1-src.tar.gz http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/http://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/contains the 10 Java EE, Minimal, and Framework server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES and source code archives for the release. For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-jetty6-javaee5-2.1.1-bin.ziphttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-jetty6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-jetty6-minimal-2.1.1-bin.ziphttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-jetty6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-tomcat6-javaee5-2.1.1-bin.ziphttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-tomcat6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-tomcat6-minimal-2.1.1-bin.ziphttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-tomcat6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist-rc2/geronimo-framework-2.1.1-bin.ziphttp://people.apache.org/%7Ejbohn/geronimo-2.1.1-dist-rc2/geronimo-framework-2.1.1-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.1-rc2/http://people.apache.org/%7Ejbohn/staging-repo/geronimo-2.1.1-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1.1 (please provide rationale) I'll plan on calling this vote on Sunday evening (11 PM EST). I will start tck runs shortly on these images. Joe Bohn -- Erik B. Craig
[jira] Commented: (GERONIMO-3972) Monitering Graphics failed to represent in IE 6 SP2
[ https://issues.apache.org/jira/browse/GERONIMO-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591588#action_12591588 ] Erik B. Craig commented on GERONIMO-3972: - Problem due to IE6 being picky about the definition of some of the custom data types from dojo charting. Tweaked to fix Committed revision 650799 to trunk Monitering Graphics failed to represent in IE 6 SP2 --- Key: GERONIMO-3972 URL: https://issues.apache.org/jira/browse/GERONIMO-3972 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Environment: Windows Reporter: YunFeng Ma Assignee: Erik B. Craig Fix For: 2.1.x, 2.2 There is a JavaScript error in IE 6 SP2: Error: 'text' is null or not an object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3972) Monitering Graphics failed to represent in IE 6 SP2
[ https://issues.apache.org/jira/browse/GERONIMO-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591592#action_12591592 ] Erik B. Craig commented on GERONIMO-3972: - Committed revision 650802 to branches/2.1 Monitering Graphics failed to represent in IE 6 SP2 --- Key: GERONIMO-3972 URL: https://issues.apache.org/jira/browse/GERONIMO-3972 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Environment: Windows Reporter: YunFeng Ma Assignee: Erik B. Craig Fix For: 2.1.x, 2.2 There is a JavaScript error in IE 6 SP2: Error: 'text' is null or not an object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3972) Monitering Graphics failed to represent in IE 6 SP2
[ https://issues.apache.org/jira/browse/GERONIMO-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3972: --- Assignee: Erik B. Craig Monitering Graphics failed to represent in IE 6 SP2 --- Key: GERONIMO-3972 URL: https://issues.apache.org/jira/browse/GERONIMO-3972 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Environment: Windows Reporter: YunFeng Ma Assignee: Erik B. Craig Fix For: 2.1.x, 2.2 There is a JavaScript error in IE 6 SP2: Error: 'text' is null or not an object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Policy for granting write access to our Wiki
I agree that we definitely need to address IP issues around documentation/the wiki... but isn't there any way to accomplish this without adding barriers to users editing content? Can we do something like wikipedia does for editing content where there is a checkbox or a notice or something saying You agree to license your contributions under the Apache Software License (similar to how JIRA is currently) -- Erik B. Craig On Wed, Apr 16, 2008 at 9:00 AM, Kevan Miller [EMAIL PROTECTED] wrote: All, To properly protect the IP rights of our Wiki-based documentation, we need to stop allowing unrestricted write access to our Wiki. Wiki contributors should be required to have an ICLA on file with the ASF. I also think that we need to hold a PMC vote before granting this access. I'll also take this opportunity to remind the community that Wiki updates are sent to [EMAIL PROTECTED] These updates need to be reviewed by the community, just like all code updates. IMO, we don't want this to be a heavy-weight process. We don't want there to be a significant hurdle to contributing documentation. For code updates, patch files attached to Jira's with the Grant license to ASF button checked takes care of these IP concerns. To my knowledge, there's no patch file equivalent for updates to a Wiki. We could require that documentation updates be contributed in the form of simple ascii text files that are attached to a Jira. This would address our IP concerns, but is not ideal IMO. To keep this as light-weight as possible, I propose we formalize the concept of contributor. A contributor would have write access to our Wiki documentation as well as the ability to assign Jira's to him/herself. I think the process would go something like this... 0. Reset write access to our wiki to be only the current set of committers on the project. 1. New documentation contributions from non-committers/contributors must be submitted via a Jira, with the Grant License to the ASF box checked. This is just like any code/bug-fix submission. 2. Once a new participant has expressed interest in contributing to the project and/or has contributed documentation or bug fixes, a PMC vote will be called to grant the new participant contributor rights. As all PMC votes, this vote is a majority vote, require a minimum of 3 +1 votes, and will last for a minimum of 72 hours. 3. Once a vote has passed, the participant will be invited to join the project as a 'contributor'. Assuming he/she accepts, the participant must then submit an ICLA to the ASF. Once the ICLA is on file, the new 'contributor' will give given write access to our wiki and the ability to assign Jira's. 4. The new contributor will be announced to the community. I've grouped Jira rights with wiki rights in the above. This is not strictly necessary, but grouping the two seems like a reasonable step. This is my first pass at a proposal. We can tweak this process in a number of ways and there are alternatives. I think the hard requirements are 1) the PMC must vote and 2) an ICLA must be filed with the ASF. Until we resolve this issue, we need to restrict Wiki write access to be the current set of Geronimo committers. --kevan
[jira] Closed: (GERONIMO-3911) Get version 1.1 migration sample apps checked in from wiki and cleaned up
[ https://issues.apache.org/jira/browse/GERONIMO-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig closed GERONIMO-3911. --- Resolution: Fixed Get version 1.1 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3911 URL: https://issues.apache.org/jira/browse/GERONIMO-3911 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3912) Get version 2.0 migration sample apps checked in from wiki and cleaned up
[ https://issues.apache.org/jira/browse/GERONIMO-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig closed GERONIMO-3912. --- Resolution: Fixed Committed revision 647303. License, Notice, license headers added Get version 2.0 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3912 URL: https://issues.apache.org/jira/browse/GERONIMO-3912 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3911) Get version 1.1 migration sample apps checked in from wiki and cleaned up
[ https://issues.apache.org/jira/browse/GERONIMO-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586679#action_12586679 ] Erik B. Craig commented on GERONIMO-3911: - Committed revision 645776. Cleaned up and checked in. Get version 1.1 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3911 URL: https://issues.apache.org/jira/browse/GERONIMO-3911 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
[ https://issues.apache.org/jira/browse/GERONIMO-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3950: Description: Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 (was: Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 1.x) Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
[ https://issues.apache.org/jira/browse/GERONIMO-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig closed GERONIMO-3950. --- Resolution: Fixed Committed revision 644462. Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3943) Upgrade dojo plugin to dojo version 1.1.0
Upgrade dojo plugin to dojo version 1.1.0 - Key: GERONIMO-3943 URL: https://issues.apache.org/jira/browse/GERONIMO-3943 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Plugins Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Dojo 1.1.0 is out and is backwards compatible with Dojo 1.0.x. Includes some new features useful in monitoring plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3943) Upgrade dojo plugin to dojo version 1.1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583390#action_12583390 ] Erik B. Craig commented on GERONIMO-3943: - Committed revision 642662. Upgrade dojo plugin to dojo version 1.1.0 - Key: GERONIMO-3943 URL: https://issues.apache.org/jira/browse/GERONIMO-3943 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Fix For: 2.2 Dojo 1.1.0 is out and is backwards compatible with Dojo 1.0.x. Includes some new features useful in monitoring plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3943) Upgrade dojo plugin to dojo version 1.1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3943. - Resolution: Fixed Fix Version/s: 2.2 Upgrade dojo plugin to dojo version 1.1.0 - Key: GERONIMO-3943 URL: https://issues.apache.org/jira/browse/GERONIMO-3943 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Fix For: 2.2 Dojo 1.1.0 is out and is backwards compatible with Dojo 1.0.x. Includes some new features useful in monitoring plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3937) java.lang.ArithmeticException: / by zero
[ https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3937: Affects Version/s: 2.1.1 java.lang.ArithmeticException: / by zero Key: GERONIMO-3937 URL: https://issues.apache.org/jira/browse/GERONIMO-3937 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Erik B. Craig I'm seeing the following exception when trying to display some graph with Timeframe set to 5 minutes: java.lang.ArithmeticException: / by zero at org.apache.geronimo.monitoring.snapshot.SnapshotDBHelper.getSpecificStatistics(SnapshotDBHelper.java:605) at org.apache.geronimo.monitoring.MasterRemoteControl.getSpecificStatistics(MasterRemoteControl.java:500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141) at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:210) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238) at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:129) at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:122) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60) at org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:76) at org.apache.openejb.server.ServiceAccessController.service(ServiceAccessController.java:55) at org.apache.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:118) at java.lang.Thread.run(Thread.java:595) The graph was created for TomcatWebConnector, Bytes Sent data series. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3937) java.lang.ArithmeticException: / by zero
[ https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig closed GERONIMO-3937. --- Resolution: Fixed Fix Version/s: 2.2 2.1.1 java.lang.ArithmeticException: / by zero Key: GERONIMO-3937 URL: https://issues.apache.org/jira/browse/GERONIMO-3937 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Erik B. Craig Fix For: 2.1.1, 2.2 I'm seeing the following exception when trying to display some graph with Timeframe set to 5 minutes: java.lang.ArithmeticException: / by zero at org.apache.geronimo.monitoring.snapshot.SnapshotDBHelper.getSpecificStatistics(SnapshotDBHelper.java:605) at org.apache.geronimo.monitoring.MasterRemoteControl.getSpecificStatistics(MasterRemoteControl.java:500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141) at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:210) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238) at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:129) at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:122) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60) at org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:76) at org.apache.openejb.server.ServiceAccessController.service(ServiceAccessController.java:55) at org.apache.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:118) at java.lang.Thread.run(Thread.java:595) The graph was created for TomcatWebConnector, Bytes Sent data series. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3937) java.lang.ArithmeticException: / by zero
[ https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583392#action_12583392 ] Erik B. Craig commented on GERONIMO-3937: - Committed revision 642673 to 2.1 Committed revision 642659 to trunk java.lang.ArithmeticException: / by zero Key: GERONIMO-3937 URL: https://issues.apache.org/jira/browse/GERONIMO-3937 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Erik B. Craig Fix For: 2.1.1, 2.2 I'm seeing the following exception when trying to display some graph with Timeframe set to 5 minutes: java.lang.ArithmeticException: / by zero at org.apache.geronimo.monitoring.snapshot.SnapshotDBHelper.getSpecificStatistics(SnapshotDBHelper.java:605) at org.apache.geronimo.monitoring.MasterRemoteControl.getSpecificStatistics(MasterRemoteControl.java:500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141) at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:210) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238) at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:129) at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:122) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60) at org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:76) at org.apache.openejb.server.ServiceAccessController.service(ServiceAccessController.java:55) at org.apache.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:118) at java.lang.Thread.run(Thread.java:595) The graph was created for TomcatWebConnector, Bytes Sent data series. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582926#action_12582926 ] Erik B. Craig commented on GERONIMO-3910: - Revision 642103 - Cleaned up samples/branches/1.0/migration-jca Revision 642104 - Cleaned up samples/branches/1.0/migration-jdbc Revision 642105 - Cleaned up samples/branches/1.0/migration-security Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582929#action_12582929 ] Erik B. Craig commented on GERONIMO-3910: - Revision 642109 - Cleaned up samples/branches/1.0/migration-webservices Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582150#action_12582150 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641178. branches/1.0/migration-ejb-mdb Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582151#action_12582151 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641179. branches/1.0/migration-ejb-session Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582152#action_12582152 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641180. branches/1.0/migration-hibernate Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581294#action_12581294 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 640084 - branches/1.0/migration-ejb-bmp has been cleaned up Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581296#action_12581296 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 640088 - webapp in branches/1.0/migration-ejb-bmp Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581300#action_12581300 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 640093. branches/1.0/migration-ejb-bmp, forgot apache.demo Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581305#action_12581305 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 640109. branches/1.0/migration-ejb-cmp cleaned up Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3937) java.lang.ArithmeticException: / by zero
[ https://issues.apache.org/jira/browse/GERONIMO-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3937: --- Assignee: Erik B. Craig java.lang.ArithmeticException: / by zero Key: GERONIMO-3937 URL: https://issues.apache.org/jira/browse/GERONIMO-3937 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Jarek Gawor Assignee: Erik B. Craig I'm seeing the following exception when trying to display some graph with Timeframe set to 5 minutes: java.lang.ArithmeticException: / by zero at org.apache.geronimo.monitoring.snapshot.SnapshotDBHelper.getSpecificStatistics(SnapshotDBHelper.java:605) at org.apache.geronimo.monitoring.MasterRemoteControl.getSpecificStatistics(MasterRemoteControl.java:500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158) at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141) at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:210) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165) at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238) at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:129) at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:122) at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84) at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60) at org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:76) at org.apache.openejb.server.ServiceAccessController.service(ServiceAccessController.java:55) at org.apache.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:118) at java.lang.Thread.run(Thread.java:595) The graph was created for TomcatWebConnector, Bytes Sent data series. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3912) Get version 2.0 migration sample apps checked in from wiki and cleaned up
[ https://issues.apache.org/jira/browse/GERONIMO-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3912: Component/s: sample apps Get version 2.0 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3912 URL: https://issues.apache.org/jira/browse/GERONIMO-3912 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3911) Get version 1.1 migration sample apps checked in from wiki and cleaned up
[ https://issues.apache.org/jira/browse/GERONIMO-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3911: Component/s: sample apps Get version 1.1 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3911 URL: https://issues.apache.org/jira/browse/GERONIMO-3911 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580687#action_12580687 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 639180 - migration-servlets is verified good and with acceptable class names. Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3719) Monitoring agent uses sun classes
[ https://issues.apache.org/jira/browse/GERONIMO-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3719. - Resolution: Fixed Committed revision 638039 to trunk, revision 638040 to branches/2.1 to remove remnants. Will open new jira for further tweaks Monitoring agent uses sun classes - Key: GERONIMO-3719 URL: https://issues.apache.org/jira/browse/GERONIMO-3719 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 SnapshotConfigXMLBuilder uses a couple sun classes to write out xml. This doesn't work on non-sun jvms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3925) Monitoring agent should use JAXB to do XML manipulation
Monitoring agent should use JAXB to do XML manipulation --- Key: GERONIMO-3925 URL: https://issues.apache.org/jira/browse/GERONIMO-3925 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1.1, 2.2 Reporter: Erik B. Craig xmlbeans is currently used to write out the xml in the monitoring agent. JAXB should be used to manipulation XML. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r636529 [1/15] - in /geronimo/samples/branches/1.0: ./ migration-ejb-bmp/ migration-ejb-bmp/dd/ migration-ejb-bmp/dd/META-INF/ migration-ejb-bmp/jndi/ migration-ejb-bmp/src/ migration-
Joe, I am trying to back-port the migration samples relevant for the older branches of the server into the svn repository. I started by cleaning up the ones intended for the 1.0 version of the server yesterday, and am working my way up from there, as all of them have not yet been verified or modified to work on later versions of the server, while some of them have and are attached to the wiki articles for those versions ( 1.1, 2.0, 2.1) On Thu, Mar 13, 2008 at 8:22 AM, Joe Bohn [EMAIL PROTECTED] wrote: Hi Eric, I'm confused about this new samples branch. Is it your intention to release these migration samples independently of the other samples (this seems to contradict your earlier affirmation on the discussion thread that we should release them concurrently and mirror the Geronimo version). When you mentioned you were thinking of putting the migration samples under samples/branches/#/migration-samplename I assumed the # was 2.1 (and echoed in trunk). Is this because you are trying to figure out how to include them given that they are not built with maven? Joe [EMAIL PROTECTED] wrote: Author: ecraig Date: Wed Mar 12 14:54:41 2008 New Revision: 636529 URL: http://svn.apache.org/viewvc?rev=636529view=rev Log: Initial check in of 1.0 migration demo apps from wiki License headers, LICENSE.txt, NOTICE.txt have been added to all packages/files. snip/ -- Erik B. Craig
Re: [DISCUSS] Geronimo 2.1 samples
On Thu, Mar 13, 2008 at 1:47 PM, Joe Bohn [EMAIL PROTECTED] wrote: Joe Bohn wrote: David Jencks wrote: On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote: Donald Woods wrote: Joe Bohn wrote: 2) When to release the samples? I think we should make an effort to release the samples concurrent with each Geronimo release. This is important because the jsp servlet examples are referenced from within the welcome page on Geronimo. I suppose we could remove that reference and eliminate the need to release concurrently. why not move the samples back under geronimo/server, so they are maintained and versioned with each release and can then be used as additional testsuite tests? If not, releasing right after a server release is fine. I was thinking about doing this. It seems everybody thinks we should release them together anyway so what is the real value with them being split out? Does anybody object to moving them back with the server? well, since I thought our next goal with the server build was to separate it into independently released plugins, I think putting the samples in with the main server build would be a big step backwards. Well, I agree that it would appear to be a step backwards from that perspective. However, it would ensure the following: 1) The samples would get released (not forgotten as has been the case with 2.1) 2) The samples would be released concurrent with the Geronimo release so that they are available for use, education, and documentation from day 1. It seems almost everybody is in favor of this. 3) They could be leveraged in the testsuite tests (as Donald pointed out) to help validate our build and find problems earlier. I fail to see too many negatives from a practical perspective but I'm certainly open to discussion I want to do what is best. Perhaps we need to refine our plugin strategy. There are situations where it makes sense to split things apart but there are also situations where it might make sense to bundle things. Joe Would those folks that feel strongly about not pulling these samples back into the server repo please provide some rationale for their argument as I have done for including them? It appears that the samples were removed without much thought given to how they might eventually be released in conjunction with a server release. I like the idea of modularity but in this case I don't see clear benefits to keeping them separate. Please keep in mind that including the samples in the server source branch and releasing them concurrent with the server does not mean that they are bundled with the server. They are still independent artifacts. However, it would ensure that they are vetted with the server release and are available when the server release is available. The samples are really only there to show value on top of a Geronimo server and they are tied to a specific server release (at least that is how we have managed and documented them thus far) so having released independent of the server doesn't appear to bring any value. Well, hey, as long as they aren't necessarily bundled with the server then I'm pretty okay with it. As far as the migration samples go though, this is definitely not the place for them, as they are intended to be checked out by the user, who is then guided through converting them to be deployed on geronimo - they aren't necessarily able to be deployed on geronimo prior to following the documentation, nor are they necessarily able to be compiled used maven. I looked back through a number of old email threads and these samples were included in the welcome page with a lot of support at the time (with a desire to have even more samples included or downloadable from the welcome page) ... several folks stating that they should be included with the server image itself. I certainly don't want to bundle the samples with the server image but having the released with the server makes sense to me. Joe -- Erik B. Craig
Re: [DISCUSS] Geronimo 2.1 samples
that feel strongly about not pulling these samples back into the server repo please provide some rationale for their argument as I have done for including them? It appears that the samples were removed without much thought given to how they might eventually be released in conjunction with a server release. I like the idea of modularity but in this case I don't see clear benefits to keeping them separate. Please keep in mind that including the samples in the server source branch and releasing them concurrent with the server does not mean that they are bundled with the server. They are still independent artifacts. However, it would ensure that they are vetted with the server release and are available when the server release is available. The samples are really only there to show value on top of a Geronimo server and they are tied to a specific server release (at least that is how we have managed and documented them thus far) so having released independent of the server doesn't appear to bring any value. I looked back through a number of old email threads and these samples were included in the welcome page with a lot of support at the time (with a desire to have even more samples included or downloadable from the welcome page) ... several folks stating that they should be included with the server image itself. I certainly don't want to bundle the samples with the server image but having the released with the server makes sense to me. I'm speculating a bit here. This might be similar to the testsuite being a bit monolithic. As a thought experiment, what if we... - made the welcome page a plugin, and the piece of build including it also builds the samples - the maven generated site includes the stuff you need to download (zips etc) (I think this is doable) Are we using any maven site today? what type of info goes there? who consumes it? .zip samples download shouldn't be any different from the other downloads we have, right? Cheers! Hernan - the welcome page links to the maven generated site - this leaves the door open to making the welcome page + samples independently versioned in the future, and possibly to selenium testing. - we split up the testsuite into integration tests for plugins or plugin groups, and they assemble the servers they need on the fly - assemblies may or may not include the welcome page plugin. dunno how practical this is for 2.1.1 thanks david jencks Joe -- ~Jason Warner -- Erik B. Craig
Re: [DISCUSS] Geronimo 2.1 samples
... - made the welcome page a plugin, and the piece of build including it also builds the samples - the maven generated site includes the stuff you need to download (zips etc) (I think this is doable) Are we using any maven site today? what type of info goes there? who consumes it? .zip samples download shouldn't be any different from the other downloads we have, right? Cheers! Hernan - the welcome page links to the maven generated site - this leaves the door open to making the welcome page + samples independently versioned in the future, and possibly to selenium testing. - we split up the testsuite into integration tests for plugins or plugin groups, and they assemble the servers they need on the fly - assemblies may or may not include the welcome page plugin. dunno how practical this is for 2.1.1 thanks david jencks Joe -- ~Jason Warner -- ~Jason Warner -- ~Jason Warner -- Erik B. Craig
Re: [DISCUSS] Geronimo 2.1 samples
On Thu, Mar 13, 2008 at 3:32 PM, Hernan Cunico [EMAIL PROTECTED] wrote: Erik B. Craig wrote: On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Well, from the wiki - Geronimo documentation, there are 3main sets of samples, well actually 3 now. 1- Migration samples 2- Sample applications 3- Tutorials 1- Migration samples. These should not be in svn unless we plan to maintain and test sample applications that are intended for JBoss, WebLogic, WAS, Tomcat or any other platform we want to explain how to migrate from. It could potentially include the need to maintain features/technologies we do not support or may never support. Isn't that what's already occurring? I believe the migration samples have applications attached to them that are designed for JBoss and the sample explains how to convert it to Geronimo. These would need to be updated based on the changes that occur both in JBoss and Geronimo. Correct, this is what I'm working on because they haven't been really kept up to date - and we don't want to get burned by someone trying to get something going or migrated that we say we have support for but have no supporting documentation or samples. When rewriting sample apps and documentation for 2.0, they are all meant to go from jboss to geronimo. The process involves validating functionality on the latest JBoss release (4.2.2GA in that case), updating documentation where necessary, updating code where necessary, and then ensuring the migration steps are still valid, and making changes to both documentation and code where needed. Ok, so we all know what it'll take and agree to carry on with this. Then we should figure out a way to link what's on svn and the corresponding doc. Confluence still does not support svn so I haven't figured out an alternative way to ensure they are in sync. Any idea? Well, as far as that goes I have came up with two solutions... 1. Reference a branch or tag and document checking the code out via SVN and have this in the step-by-step in the document 2. Release versions as archives of the source code, that can be published much as we do with the server and server sources, and linked to this in the wiki articles Cheers! Hernan ... -- Erik B. Craig
Re: [DISCUSS] Geronimo 2.1 samples
I also am in agreement with David on this, I think it would be a far better approach to not include them within trunk. While it may be a bit more work to release them separately from the actual server release, it would seem to be a big step backwards with what we have been working on. Perhaps we need a more thorough / checklist style release process to ensure certain requisites are always met (I.E. samples are ready as well) Thanks, Erik B. Craig [EMAIL PROTECTED] David Jencks wrote: On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote: Donald Woods wrote: Joe Bohn wrote: 2) When to release the samples? I think we should make an effort to release the samples concurrent with each Geronimo release. This is important because the jsp servlet examples are referenced from within the welcome page on Geronimo. I suppose we could remove that reference and eliminate the need to release concurrently. why not move the samples back under geronimo/server, so they are maintained and versioned with each release and can then be used as additional testsuite tests? If not, releasing right after a server release is fine. I was thinking about doing this. It seems everybody thinks we should release them together anyway so what is the real value with them being split out? Does anybody object to moving them back with the server? well, since I thought our next goal with the server build was to separate it into independently released plugins, I think putting the samples in with the main server build would be a big step backwards. thanks david jencks Joe
[jira] Created: (GERONIMO-3910) Rename classes, remove IBM references
Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3911) Get version 1.1 migration sample apps checked in from wiki and cleaned up
Get version 1.1 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3911 URL: https://issues.apache.org/jira/browse/GERONIMO-3911 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3912) Get version 2.0 migration sample apps checked in from wiki and cleaned up
Get version 2.0 migration sample apps checked in from wiki and cleaned up -- Key: GERONIMO-3912 URL: https://issues.apache.org/jira/browse/GERONIMO-3912 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Affects Versions: 1.1.x Reporter: Erik B. Craig Assignee: Erik B. Craig LICENCE.txt, NOTICE.txt, and ASF license headers need to be added, as well as all line endings converted to unix format and tabs converted to spaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Geronimo 2.1 samples
Joe, 1. I agree on releasing samples collectively 2. My opinion on when to release is that they should be at the very least concurrent with each release, if not slightly before. I believe functional, relevant samples can help reduce barrier to entry. 3. As far as where to keep the source to the samples -Definitely within SVN 4. Mirrored versioning is a must. 5. Since we are really pushing the plugin format in general, it's probably a good idea to have the samples themselves be in all plugin format Additionally - We need to figure a way to work in the migration examples. Right now they exist only as .zip files attached to wiki articles. I am working on putting the proper license/notice files in them, as well as the asf headers. There are a couple hitches though. 1. where to put them (I was thinking maybe just under samples/branches/ #/migration-samplename) 2. They are mostly made to be compiled with ant for ease of deploying on either jboss or geronimo depending on the build - is this a problem at all? Thanks, Erik B. Craig [EMAIL PROTECTED] On Mar 11, 2008, at 12:20 PM, Joe Bohn wrote: A bit of unfinished business from 2.1 is the release of samples. I think we need to get these fixed and available fairly soon for 2.1. Here are some questions for discussion around that and how we should manage the samples in general. 1) Do we release all the samples collectively or individually? My vote would be collectively. 2) When to release the samples? I think we should make an effort to release the samples concurrent with each Geronimo release. This is important because the jsp servlet examples are referenced from within the welcome page on Geronimo. I suppose we could remove that reference and eliminate the need to release concurrently. 3) Managing sample source. IMO the only place we should maintain source for the samples is in svn. I think Jarek managed to update all of the sample doc with references to the svn repo for each sample but I think there might be a place or two where we include a zip of the source in the wiki in addition to the SVN reference (at least I recall seeing some not too long ago). I plan to hunt them out and remove those attachments where they are already checked into svn. 4) More on managing source I think our source for the samples should mirror the source for the server in terms of branches/tags. 5) Should we make all samples plugins? At the moment the jsp- examples, servlet-examples, and ldap-sample-app are plugins. The other 12 samples are not. I'd be in favor of creating a plugin for each and will work on doing this unless I hear objections. I'm sure there are a lot of other issues this is just to get the ball rolling. Joe
Re: [DISCUSS] Release J2G 1.0.0 RC1
It looks like this did indeed fall completely by the wayside. I think at the bare minimum we should get a 1.0 release binary put out for this. Donald, are you still willing to push that? If not, I am willing to take that over... can I even do that without being PMC? If I can, I'll figure out what needs to be done and such. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 26, 2008, at 10:17 AM, Jason Warner wrote: --=_Part_1659_18852684.1204042635536 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline What happened to this vote? I checked the tags and the code was never moved over. Did this pass? Do we have an official binary I can link to on the wiki docs? On Mon, Nov 12, 2007 at 4:52 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Nov 6, 2007, at 9:03 PM, Lin Sun wrote: The .project and .classpath files are used when the plugins are loaded in Eclipse IDE.You are right they don't have ASL license headers but I don't see license headers associated with these files normally. The files in the geronimo eclipse plugin don't have ASL license headers either. Also, these files are not in the assembly. Are these files machine generated? Whether or not they end up in an assembly doesn't really matter... They seem non-trivial to me and should have a license header. I am not sure what we need to do with jboss here. Of course we are using it since it is a migration tool from jboss to geronimo. Any advice here? I did a little research for this. It seems we must avoid implying that JBoss is the source of this code. As long as the distribution name (and executable name, I would think) don't use JBoss in the name we're doing this. Internal file names should be fine. So, in my opinion, we're ok here... So, pending the license header and file permission questions, I'd say this looks good. --kevan -- ~Jason Warner --=_Part_1659_18852684.1204042635536 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline What happened to this vote?nbsp; I checked the tags and the code was never moved over.nbsp; Did this pass?nbsp; Do we have an official binary I can link to on the wiki docs?brbrdiv class=gmail_quoteOn Mon, Nov 12, 2007 at 4:52 PM, Kevan Miller lt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/ agt; wrote:br blockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;div class=Ih2E3dbr On Nov 6, 2007, at 9:03 PM, Lin Sun wrote:br br gt; The .project and .classpath files are used when the plugins are loadedbr gt; in Eclipse IDE. nbsp; nbsp;You are right they don#39;t have ASL license headersbr gt; but I don#39;t see license headers associated with these files normally.br gt; The files in the geronimo eclipse plugin don#39;t have ASL licensebr gt; headers either. nbsp; Also, these files are not in the assembly.br br /divAre these files machine generated? Whether or not they end up in anbr assembly doesn#39;t really matter... They seem non-trivial to me andbr should have a license header.br div class=Ih2E3dbr gt;br gt;br gt; I am not sure what we need to do with jboss here. nbsp; Of course we arebr gt; using it since it is a migration tool from jboss to geronimo. nbsp;Anybr gt; advice here?br br br /divI did a little research for this. It seems we must avoid implying thatbr JBoss is the source of this code. As long as the distribution namebr (and executable name, I would think) don#39;t use quot;JBossquot; in the namebr we#39;re doing this. Internal file names should be fine. So, in mybr opinion, we#39;re ok here...br br So, pending the license header and file permission questions, I#39;d saybr this looks good.br font color=#88br --kevanbr br /font/blockquote/divbrbr clear=allbr-- br~Jason Warner --=_Part_1659_18852684.1204042635536--
[jira] Commented: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573962#action_12573962 ] Erik B. Craig commented on GERONIMO-3833: - Committed revision 632438 to Trunk removing hard coded paths from the .sql file Committed revision 632440 to 2.1 branch Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Monitoring portlet - Server with JMX as protocol has problems
On that note, While i was making sure everything was okay, seems as though the plugin repository we host at geronimo.apache.org is out of date for 2.1 (version on everything is still 2.1-snapshot), and is also therefore lacking the JMX agent... so, heads up on that until that gets updated. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 25, 2008, at 1:30 PM, Vamsavardhana Reddy wrote: Aah... that is the missing link. Thanks. ++Vamsi On Tue, Feb 26, 2008 at 12:53 AM, Erik B. Craig [EMAIL PROTECTED] wrote: Vamsi, Did you deploy the JMX Monitoring agent plugin before attempting to connect? Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote: In the monitoring portlet, I have added a server with JMX as the protocol. Upon clicking, Enable Query, the following error is displayed. MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1: geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent- car-jmx/2.1/ car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean Is this a known problem?
Re: Monitoring portlet - Server with JMX as protocol has problems
Vamsi, Did you deploy the JMX Monitoring agent plugin before attempting to connect? Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 25, 2008, at 1:08 PM, Vamsavardhana Reddy wrote: In the monitoring portlet, I have added a server with JMX as the protocol. Upon clicking, Enable Query, the following error is displayed. MRC ERROR: Snapshot thread could NOT be started on server 127.0.0.1: geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent- car-jmx/2.1/ car,J2EEServer=geronimo,name=MasterRemoteControlJMX,j2eeType=GBean Is this a known problem?
[jira] Updated: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3833: Affects Version/s: (was: 2.0.x) 2.2 2.1.1 Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3685: Fix Version/s: 2.2 Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly - Key: GERONIMO-3685 URL: https://issues.apache.org/jira/browse/GERONIMO-3685 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Environment: All Reporter: Anita Kulshreshtha Priority: Critical Fix For: 2.1.1, 2.2 . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'totalTime/count' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3870) Expose JSR77 stats in OpenEJB
[ https://issues.apache.org/jira/browse/GERONIMO-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3870: Affects Version/s: 2.2 2.1.1 2.1 Fix Version/s: 2.2 Expose JSR77 stats in OpenEJB - Key: GERONIMO-3870 URL: https://issues.apache.org/jira/browse/GERONIMO-3870 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, OpenEJB Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Erik B. Craig Fix For: 2.2 There should be JSR77 compliant statistics exposed in OpenEJB so that they may be monitored/tracked with the monitoring plug-in -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3685) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3685: Affects Version/s: 2.2 2.1.1 2.1 Fix Version/s: (was: 2.1.1) Monitoring Console should display TimeStatistics and BoundedRangeStatistics correctly - Key: GERONIMO-3685 URL: https://issues.apache.org/jira/browse/GERONIMO-3685 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Reporter: Anita Kulshreshtha Priority: Critical Fix For: 2.2 . The Monitoring Console (MC) should display TimeStatistics and BoundedRangeStatistics as a single value. For example JVM Heap or RequestTime or openConnections with a single link for graph. . A band-aid solution to displaying TimeStatistics and BoundedRangeStatistics, and RangeStatistics is to add a field 'StatisticsType' to activeDB. and graph 'totalTime/count' for Timestatistics and 'current' for BoundedRangeStatistics, RangeStatistics. . The graph builder recomputes min, max and avg. It is wasteful but acceptable for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3833) Hard-coded gbean names and versions in monitoring code
[ https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3833: Fix Version/s: 2.2 2.1.1 Hard-coded gbean names and versions in monitoring code -- Key: GERONIMO-3833 URL: https://issues.apache.org/jira/browse/GERONIMO-3833 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Fix For: 2.1.1, 2.2 The monitoring code has hard-coded values in Java code and sql file: 1) The ./plugins/monitoring/mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MRCConnector.java contains the following constant: private static final String PATH = geronimo:ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1-SNAPSHOT/car,J2EEServer=geronimo, name=MasterRemoteControlJMX,j2eeType=GBean; 2) The ./plugins/monitoring/mconsole-ear/src/main/resources/MonitoringClientDB.sql contains a bunch of the following values: 'geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1/car,j2eeType=GBean,name=TomcatWebConnector' I'm not sure how these are used but in general these type of hardcoded values should be avoided. It's really hard to maintain and keep track of. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3697) Monitoring Console fix ups
[ https://issues.apache.org/jira/browse/GERONIMO-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572200#action_12572200 ] Erik B. Craig commented on GERONIMO-3697: - Anita, what is the status of this Jira? Do you consider it finished? Monitoring Console fix ups --- Key: GERONIMO-3697 URL: https://issues.apache.org/jira/browse/GERONIMO-3697 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Assignee: Anita Kulshreshtha This issue is for minor fixes to monitoring console and monitoring agent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3682) The Monitoring Console should keep information about Stats available from a managed object
[ https://issues.apache.org/jira/browse/GERONIMO-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3682: Affects Version/s: 2.2 2.1.1 The Monitoring Console should keep information about Stats available from a managed object -- Key: GERONIMO-3682 URL: https://issues.apache.org/jira/browse/GERONIMO-3682 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Reporter: Anita Kulshreshtha The monitoring console should do a getStats on each of the available StatisticsProvider (without the query being enabled). It should use this information to build a DB about the nature of the statistics. This information should be used to fill in the default values in 'add a graph page'. Currently the description, x label, y label show as empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3719) Monitoring agent uses sun classes
[ https://issues.apache.org/jira/browse/GERONIMO-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3719: Affects Version/s: 2.2 Fix Version/s: 2.2 Monitoring agent uses sun classes - Key: GERONIMO-3719 URL: https://issues.apache.org/jira/browse/GERONIMO-3719 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.1.1, 2.2 SnapshotConfigXMLBuilder uses a couple sun classes to write out xml. This doesn't work on non-sun jvms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3681) The Monitoring Console should allow the type of graph to be chosen
[ https://issues.apache.org/jira/browse/GERONIMO-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3681: Affects Version/s: 2.2 2.1.1 The Monitoring Console should allow the type of graph to be chosen -- Key: GERONIMO-3681 URL: https://issues.apache.org/jira/browse/GERONIMO-3681 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Reporter: Anita Kulshreshtha The CountStatistics can be displayed in 2 ways, the raw count and the throughput/utilization (count/sec). For raw count like ErrorCount a bar graph is more appropriate. The curvedArea is good for throughput. The user should be able to choose which graph style (bar, curvedArea, etc) to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3680) The Monitoring agent should optimize DB activity
[ https://issues.apache.org/jira/browse/GERONIMO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3680: Affects Version/s: 2.2 2.1.1 Fix Version/s: 2.2 The Monitoring agent should optimize DB activity Key: GERONIMO-3680 URL: https://issues.apache.org/jira/browse/GERONIMO-3680 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Reporter: Anita Kulshreshtha Fix For: 2.2 Attachments: view4.jpg Currently the agent needs to be loaded in the same JVM as the server being monitored. The agent skews the statistics being monitered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3530) provide activemq destination and connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572203#action_12572203 ] Erik B. Craig commented on GERONIMO-3530: - Anita, What is the status of this patch/jira? provide activemq destination and connector stats Key: GERONIMO-3530 URL: https://issues.apache.org/jira/browse/GERONIMO-3530 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: linux, windows Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.2 Attachments: geronimo-3530.patch there are some stats that can easily be surfaced with how we use AMQ in our source. These are JSR 77 compliant statistics that are being provided by AMQ (DestinationStatistics and ConnectorStatistics). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3530) provide activemq destination and connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3530: Affects Version/s: 2.2 2.1.1 Fix Version/s: 2.2 provide activemq destination and connector stats Key: GERONIMO-3530 URL: https://issues.apache.org/jira/browse/GERONIMO-3530 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: linux, windows Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.2 Attachments: geronimo-3530.patch there are some stats that can easily be surfaced with how we use AMQ in our source. These are JSR 77 compliant statistics that are being provided by AMQ (DestinationStatistics and ConnectorStatistics). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3774) monitoring agent should separate any constant assignment inside one class
[ https://issues.apache.org/jira/browse/GERONIMO-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3774: Affects Version/s: 2.2 2.1.1 Fix Version/s: 2.2 monitoring agent should separate any constant assignment inside one class - Key: GERONIMO-3774 URL: https://issues.apache.org/jira/browse/GERONIMO-3774 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: windows Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Trivial Fix For: 2.2 There are constant variables such as DEFAULT_RETENTION that are used by both the agent-jmx and agent-ejb. These constants should be placed inside a class dedicated to just constants in agent-jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Questions about using Gshell on a remote server instance
Jason, I'm not sure how it's *supposed* to be by design, but my expectations would be the same as yours - it would shutdown the the instance that you are remotely connected to and not the local instance. As such, I agree that it may confuse users. Perhaps this behavior should be changed? Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 21, 2008, at 12:16 PM, Jason Warner wrote: I was working with gshell in trunk and noticed something that I thought was odd. I had used deploy/connect to connect to a remote instance of geronimo. I then went to issue a geronimo/stop-server command but I didn't provide the hostname or port for the remote server. The command attempted to shutdown a local instance of geronimo. I was confused as to why this would be the case. My expectation would be that if I were connected to a remote instance, then any commands sent to a geronimo server would be directed at that instance. I think this behavior might confuse users. Is there a reason things are working the way they currently are? Is it technically feasible to accomplish this with the way the command is written or is it just not worth the effort? I'd like to see what other think about this, but I'm definitely going to document it in the wiki. Thanks, -- ~Jason Warner
Re: Geronimo Tomcat 2.0.3-SNAPSHOT: SESSIONS.ser written to workDir
Donald, I have had this thought myself. Often times it seems we are far more focused on the next major release (I.E. current trunk) as opposed to introducing some more necessary fixes into other smaller releases. I think we should definitely continue to support / release on the 2.0 branch as much as possible, and would be happy to assist in integration of patches and changes that have been made since then. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 21, 2008, at 9:32 AM, Donald Woods wrote: Aka the 2.0 branch - https://svn.apache.org/repos/asf/geronimo/server/branches/2.0 We need to continue supporting our user community and stop forcing them to the latest and greatest release. Look at how Tomcat and the HTTP Server handle support with tons of . releases. I'm not saying we should have as many maintenance releases as Tomcat (ie. 5.5.26) but we should try to keep supporting a release by integrating patches for say 6 months after the last maintenance release, which would mean we're still in the 2.0.x 6 months window (released 20071019.) If a committer is willing to help solve a user's problem on a prior release, then +1000 to them. There are still users asking about 1.1.1 on the users mailing list, so obviously we need to do a better job of supporting our releases and stop this try the latest release and try the latest snapshot approach that we have been doing. My 2 cents -Donald Jacek Laskowski wrote: On Tue, Feb 19, 2008 at 3:37 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: With Geronimo Tomcat 2.0.3-SNAPSHOT, when a web app is stopped, I am noticing that the call to stop() in GeronimoStandardContext.kill() is making the sessions to be written to a SESSIONS.ser under the workDir for the application. But then destroy() called immediately is resulting in the deletion of the workDir altogether. Under what situations will this workDir be not deleted and how this SESSIONS.ser will be used/supposed to be used? What's 2.0.3-SNAPSHOT? I have never seen it mentioned before. Should we care about it rather than pushing 2.1 to our end users? Why are you working with the older version? Jacek
[jira] Created: (GERONIMO-3870) Expose JSR77 stats in OpenEJB
Expose JSR77 stats in OpenEJB - Key: GERONIMO-3870 URL: https://issues.apache.org/jira/browse/GERONIMO-3870 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring, OpenEJB Reporter: Erik B. Craig There should be JSR77 compliant statistics exposed in OpenEJB so that they may be monitored/tracked with the monitoring plug-in -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Diagnostic Utility For AG
David, I don't think that such a thing should/would be built to necessarily automatically generate the wiki itself, but more of automatically generate a URL based on say, an MD5 hash, that if the user were to go to this URL, would create a wiki page at that time (for example, http://geronimo.apache.org/bugs/ md5 hash here). Upon visiting this URL, users could put any kind of information they want on this wiki-style page... what they were doing, environment, etc... if they have figured a way to prevent or fix it.. that kind of thing. If the page is already created/someone else has already posted information on this particular crash circumstance, this information would be viewable by all subsequent visitors. I agree with you that it would be preferable to have a human-readable key, but also like you I'm at a loss currently as to how to generate such a thing. Perhaps it could be built so that those inputing information based on this hash could also provide a human readable key to access the same page, so that the same information could be accessed by either http://geronimo.apache.org/bugs/md5 hash or http://geronimo.apache.org/bugs/human readable key Bottom line, the best thing for this would be to not have fully automatic communication, but more along the lines of user-opted/ controlled submission. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 18, 2008, at 12:53 PM, David Jencks wrote: On Feb 18, 2008, at 10:14 AM, Joseph Leong wrote: Hi all, I wanted to toss an idea out to the community and get some feedback. A few other members of the community and myself are interested in creating a diagnostic utility for AG. This diagnostic utility would perform something similar to what one would see when an application crashes and a prompter allows the end user to send a report to the developers. However this idea has an open source twist to it - rather than the developers exclusively being able to view the issue or contribute a solution, any user can. When an error or issue occurs in AG it'll generate a sort of unique message key that will be used to automatically generate a wiki type page somewhere. This wiki page will include vital information that will help in debugging the issue. There any user/ developer can post solutions or thoughts. In addition, we'd try to aim to create some sort of standardized way to generate these message keys so if another user encounters the same error it will redirect or build upon the existing wiki another user has already opened. Ultimately... the hopes are that this tool can serve as a convenient way for users to get help on their issues and expedite that process by automating a process and presenting it in an organized fashion. I know theres plenty room for ideas and improvements to this.. so please feel to comment anything! I'm not sure I understand your proposal. I think that letting a geronimo installation communicate with anything not specifically configured by the system administrator, in particular communicating with a wiki at apache, is not acceptable. I'd be fine with the geronimo build having a profile that constructs wiki pages for each error if they are not already present in the wiki and having the error message include a key to the wiki page. I think it might be good to have the key be human-readable, but I don't have an idea on how to accomplish that. thanks david jencks To start.. does anyone have a list of what they'd like to see in the error reporting diagnostics? Wishing you all the best, Joseph Leong
Re: [VOTE] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases
[ ] +1 Release Geronimo 2.1 and TxManager 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please provide rationale) +1 Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 10, 2008, at 10:46 PM, Kevan Miller wrote: All, I've prepared a 2.1 release candidate for your review and vote. I've also prepared a 2.1.1 TxManager release candidate for review and vote. For simplicity, I'm holding a single vote for both releases. The Geronimo server release is dependent upon the TxManager 2.1.1 release. The source for the Geronimo 2.1 release currently resides here: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.0 When the release vote is approved, I will svn mv the code to https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.0 An archive of this source code can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-2.1-src.tar.gz http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/ contains the 8 Java EE and Minimal server binary distributions to be released (tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES and source code archives for the release. For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-javaee5-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-jetty6-minimal-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-javaee5-2.1-bin.zip http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist/geronimo-tomcat6-minimal-2.1-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1/ or in the following archive (warning, this file is 458 megs): http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-2.1-dist.tar.gz When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. Due to the discovery of a bug in the Connector component of Geronimo TxManager, a new release of TxManager was needed. TxManager 2.1.1 is also part of this vote. The source code for the TxManager 2.1.1 release can be found here: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.1 The maven artifacts for TxManager 2.1.1 can be found here: http://people.apache.org/~kevan/release-votes/G-2.1/geronimo-txmanager-2.1.1/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. Please review these releases and register your vote. [ ] +1 Release Geronimo 2.1 and TxManager 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1 and TxManager 2.1.1 (please provide rationale) I'll plan on calling this vote on Wednesday evening (11 PM EST). --kevan
Re: branches/2.1 freeze notice
Kevan, I have a very small change to make to mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/MonitoringPortlet.java to prevent a potential stack trace if the user clicks the portlet 'edit' button at the top of the portlet. Would it be possible to get this in? Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 8, 2008 11:01 AM, Kevan Miller [EMAIL PROTECTED] wrote: On Feb 6, 2008, at 10:29 AM, Kevan Miller wrote: All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. OK. I've created branches/2.1.0 for the final release work. I've updated the versions on branches/2.1 to be 2.1.1-SNAPSHOT. So, branches/2.1 is open for business. Please don't make any updates to branches/2.1.0 --kevan
Re: branches/2.1 freeze notice
Viet, It's an error that should've been prevented but wasn't being, it's just some error checking being added. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 8, 2008, at 11:18 AM, Viet Nguyen wrote: Erik, I do not think we should prevent this stack trace. I think it's important that the user knows what's up. So we should at least write it to a log. Thanks, Viet On Feb 8, 2008 12:14 PM, Erik B. Craig [EMAIL PROTECTED] wrote: Kevan, I have a very small change to make to mconsole-war/src/main/java/org/apache/geronimo/monitoring/console/ MonitoringPortlet.java to prevent a potential stack trace if the user clicks the portlet 'edit' button at the top of the portlet. Would it be possible to get this in? Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 8, 2008 11:01 AM, Kevan Miller [EMAIL PROTECTED] wrote: On Feb 6, 2008, at 10:29 AM, Kevan Miller wrote: All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. OK. I've created branches/2.1.0 for the final release work. I've updated the versions on branches/2.1 to be 2.1.1-SNAPSHOT. So, branches/2.1 is open for business. Please don't make any updates to branches/2.1.0 --kevan
Re: GBean permissions: how important are they?
Vamsi, I do agree with you that there should be a mechanism to enforce GBean permissions, but I'm not entirely sure how prevalent the desire for 'shared hosting' on Geronimo really is, but this might be a direct result of the problem at hand. I think it is true that for a JEE app server, real world paid hosting services would often be either a dedicated machine or at least a virtualized instance. I also thing that Geronimo would mostly be used in a true 'shared hosting' (multiple clients information deployed under one instance) environment only when being managed by the hosting company, so as to not necessitate giving the client any abilities to muck with the server via admin console or other means... in this case a solid GBean security mechanism would be critical. Other than this, as far as hosts are concerned, what they might consider to be a 'shared hosting' configuration of Geronimo may be simply multiple instances/VMs bound to different IP addresses sharing hardware and giving clients administrative access to their own instance of Geronimo. Thanks, Erik B. Craig [EMAIL PROTECTED] On Feb 8, 2008, at 3:43 AM, Vamsavardhana Reddy wrote: I have always felt that Geronimo won't be suitable for a hosting kind of environment where applications owned by unrelated parties may be hosted on the same server (does such a thing happen in reality?). Irrespective of this, GBeans permissions appears to be something we can consider to have. The following is an excerpt from a private conversation I had with David Jencks on IRC. Read on... vamsic007: The usability of Geronimo in a hosting kind of environment has always bothered me. djencks : how? vamsic007: Any application running in G can get hold of any other application related GBeans and do what ever vamsic007: Any app can stop any configuration it wishes to djencks : realistically does anyone run apps from unrelated people on the same server? vamsic007: won't that be the situation in a hosting environment? djencks : I don't know djencks : I would expect if I rent server space I'd probably get my own vm djencks : but I'm not a hosting company vamsic007: hmm... vamsic007: will have to find out if my concern is genuine or I am worried unnecessarily. vamsic007: I always thought that we should have a mechanism to enforce GBean permissions. djencks : I can see several places gbean permissions could work djencks : 1. getting gbean from kernel. This is pretty non-intrusive djencks : 2. actually calling operations/accessing attributes on a gbean. I think this would require putting proxies back in djencks : there's also a bootstrap question of what enforces the permissions until the jacc system is operational djencks : since e.g datasources bound in jndi end up calling a gbean operation to get the datasource, this would have a lot of intersection with the normal server operations vamsic007: May be I will initiate a discussion on this on [EMAIL PROTECTED] to get others inputs too. I do not want to go on dev-list coz it is related to security and do not want to make the users feel insecure unnecessarily. djencks : I'd prefer to talk about it on dev, I think we could use all the input we can get. vamsic007: thanks David. Comments? Suggestions? Am I worried unnecessarily? Are GBean permissions something that we should consider? Thank you. ++Vamsi
[jira] Created: (GERONIMO-3818) Monitoring console should open individual graphs in actual new window rather than tabs in firefox
Monitoring console should open individual graphs in actual new window rather than tabs in firefox - Key: GERONIMO-3818 URL: https://issues.apache.org/jira/browse/GERONIMO-3818 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Monitoring console should open individual graphs in actual new window rather than tabs in firefox -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3730) monitoring plugin to support jmx connections in mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3730. - Resolution: Fixed Assignee: Erik B. Craig (was: Viet Hung Nguyen) JMX connection support is implemented and functional monitoring plugin to support jmx connections in mconsole Key: GERONIMO-3730 URL: https://issues.apache.org/jira/browse/GERONIMO-3730 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Erik B. Craig There should be another collecting agent that does not use MEJB, but JMX instead. This should probably be a separate plugin than the existing agent because we do not want to pull in OpenEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3803. - Resolution: Fixed monitoring plugin: agent-jmx does not provide the correct interface for mconsole Key: GERONIMO-3803 URL: https://issues.apache.org/jira/browse/GERONIMO-3803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3803.patch the agent-jmx does not specify the right method signatures that the mconsole needs to run properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3817) mconsole should display axis labels
mconsole should display axis labels --- Key: GERONIMO-3817 URL: https://issues.apache.org/jira/browse/GERONIMO-3817 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Fix For: 2.1, 2.1.1 THe monitoring console is not currently displaying axis labels and should be doing so in some fashion -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3633) Monitoring client should auto redraw graphs/the page on any page that has graphs
[ https://issues.apache.org/jira/browse/GERONIMO-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3633. - Resolution: Fixed Assignee: Erik B. Craig Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk Monitoring client should auto redraw graphs/the page on any page that has graphs Key: GERONIMO-3633 URL: https://issues.apache.org/jira/browse/GERONIMO-3633 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Monitoring client should auto redraw graphs/the page on any page that has graphs based on the snapshot duration of the server the graphs are pulled from. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3818) Monitoring console should open individual graphs in actual new window rather than tabs in firefox
[ https://issues.apache.org/jira/browse/GERONIMO-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3818. - Resolution: Fixed Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk Monitoring console should open individual graphs in actual new window rather than tabs in firefox - Key: GERONIMO-3818 URL: https://issues.apache.org/jira/browse/GERONIMO-3818 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Monitoring console should open individual graphs in actual new window rather than tabs in firefox -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3817) mconsole should display axis labels
[ https://issues.apache.org/jira/browse/GERONIMO-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3817. - Resolution: Fixed Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk mconsole should display axis labels --- Key: GERONIMO-3817 URL: https://issues.apache.org/jira/browse/GERONIMO-3817 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Fix For: 2.1, 2.1.1 THe monitoring console is not currently displaying axis labels and should be doing so in some fashion -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
[ https://issues.apache.org/jira/browse/GERONIMO-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565634#action_12565634 ] Erik B. Craig commented on GERONIMO-3810: - Fixed in rev. 618493 for 2.1 branch Fixed in rev. 618526 for trunk. mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3810) mconsole shows no indication of 'shutting down' thread from jmx agent
[ https://issues.apache.org/jira/browse/GERONIMO-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3810. - Resolution: Fixed mconsole shows no indication of 'shutting down' thread from jmx agent - Key: GERONIMO-3810 URL: https://issues.apache.org/jira/browse/GERONIMO-3810 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Currently the monitoring console does not indicate when the snapshot thread is pending a shutdown, leading to some user confustion. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12564994#action_12564994 ] Erik B. Craig commented on GERONIMO-3803: - Patch Committed revision 617721. Hold Jira open until I see whether or not it needs to be committed to 2.1 branch as well Thanks Viet monitoring plugin: agent-jmx does not provide the correct interface for mconsole Key: GERONIMO-3803 URL: https://issues.apache.org/jira/browse/GERONIMO-3803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3803.patch the agent-jmx does not specify the right method signatures that the mconsole needs to run properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3804: --- Assignee: Erik B. Craig monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Erik B. Craig Priority: Critical the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3804) monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx
[ https://issues.apache.org/jira/browse/GERONIMO-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565030#action_12565030 ] Erik B. Craig commented on GERONIMO-3804: - Committed revision 617750. Thanks viet monitoring pluging: mconsole-graphs does not detect any servers that was connected through jmx -- Key: GERONIMO-3804 URL: https://issues.apache.org/jira/browse/GERONIMO-3804 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3804.patch the mconsole does not detect any servers connected using jmx when trying to add a graph. I suspect it has something to do with the db query, because it detects all servers connected through MEJB just fine. I checked to ensure an instance of the server-jmx was present in the mconsole db and it is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New plugin idea for debug viewer component
Joe, If this is something that is intended for eventual inclusion in a full assembly/replacing or upgrading the classloader and dependency viewers, then you should probably be looking into using dojo 1.0.2, especially giving that the current stuff is already written to use dojo 0.4.3, and shouldn't be that completely terrible of a task to migrate them / improve them. Thanks, Erik B. Craig [EMAIL PROTECTED] On Jan 30, 2008, at 3:22 PM, Joseph Leong wrote: Hi All, So i was thinking about creating a neat new little plugin piece that would help represent the data in the ClassLoader Viewer and Dependency Viewer better visually. The purpose of this is to represent the current data/hierarchy in a more complete and graphical format..ultimately hoping that this node and arc format will be found useful to those who prefer a diagram representation. Does anyone have any ideas of what they'd like to see be put in this plugin that would help them? This is definitely going to be Ajax, but i am still undecided and researching with what to go with ... currently going to try and compare different packages with graph library/engines. The best, Joseph Leong
Re: [ANNOUNCE] Viet Nguyen as Geronimo's most recent committer
Congrats Viet! Thanks, Erik B. Craig [EMAIL PROTECTED] On Jan 30, 2008, at 9:47 PM, Kevan Miller wrote: All, I'd like to welcome Viet Nguyen as a new committer on the Geronimo project. Viet has made a number of contributions to Geronimo, including our new monitoring capabilities, the J2G conversion tool, as well as a number of bug fixes, and other helpful contributions. Let's lay some props on Viet! --kevan
[jira] Commented: (GERONIMO-3730) monitoring plugin to support jmx connections in mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563452#action_12563452 ] Erik B. Craig commented on GERONIMO-3730: - Progress Committed revision 616237. agent-jmx is missing the 'isSnapshotRunning' method, need this implemented. EJB still works flawless, JMX testing is held up by this currently. monitoring plugin to support jmx connections in mconsole Key: GERONIMO-3730 URL: https://issues.apache.org/jira/browse/GERONIMO-3730 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen There should be another collecting agent that does not use MEJB, but JMX instead. This should probably be a separate plugin than the existing agent because we do not want to pull in OpenEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563666#action_12563666 ] Erik B. Craig commented on GERONIMO-3790: - Patch Committed revision 616518. Thanks Viet. monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch, geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3794) Monitoring Console should give option of using JMX to connect to the Monitoring Agent
Monitoring Console should give option of using JMX to connect to the Monitoring Agent - Key: GERONIMO-3794 URL: https://issues.apache.org/jira/browse/GERONIMO-3794 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Fix For: 2.1 The Monitoring Console should be able to connect to either the EJB or the JMX flavor of the Monitoing agent, specified at the addition of a server to the connection list/database, all other differences being seamless -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3794) Monitoring Console should give option of using JMX to connect to the Monitoring Agent
[ https://issues.apache.org/jira/browse/GERONIMO-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3794: Remaining Estimate: (was: 12h) Original Estimate: (was: 12h) Monitoring Console should give option of using JMX to connect to the Monitoring Agent - Key: GERONIMO-3794 URL: https://issues.apache.org/jira/browse/GERONIMO-3794 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Erik B. Craig Assignee: Erik B. Craig Fix For: 2.1 The Monitoring Console should be able to connect to either the EJB or the JMX flavor of the Monitoing agent, specified at the addition of a server to the connection list/database, all other differences being seamless -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Deleted: (GERONIMO-3794) Monitoring Console should give option of using JMX to connect to the Monitoring Agent
[ https://issues.apache.org/jira/browse/GERONIMO-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig deleted GERONIMO-3794: Monitoring Console should give option of using JMX to connect to the Monitoring Agent - Key: GERONIMO-3794 URL: https://issues.apache.org/jira/browse/GERONIMO-3794 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Erik B. Craig Assignee: Erik B. Craig The Monitoring Console should be able to connect to either the EJB or the JMX flavor of the Monitoing agent, specified at the addition of a server to the connection list/database, all other differences being seamless -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3730) monitoring plugin to support jmx connections in mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563113#action_12563113 ] Erik B. Craig commented on GERONIMO-3730: - Progress Committed revision 615847. Still need to implement MRCConnectorJMX add additional checks on protocol to determine which class to use monitoring plugin to support jmx connections in mconsole Key: GERONIMO-3730 URL: https://issues.apache.org/jira/browse/GERONIMO-3730 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen There should be another collecting agent that does not use MEJB, but JMX instead. This should probably be a separate plugin than the existing agent because we do not want to pull in OpenEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSSION] Geronimo v2.1 documentation - Content
Hernan, I have been working on the monitoring documentation, once finished with that, I can take up the J2G as well if you would like Thanks, Erik B. Craig [EMAIL PROTECTED] On Jan 28, 2008, at 10:48 AM, Hernan Cunico wrote: Hi All, these are some of the topics I think we should cover for the 2.1 documentation. It is not a full list so we need your help to make it as complete as possible. Pls chime in with the topics you would like to see addressed in the documentation. * What's new in 2.1? ** New features ** Component versions ** Configuration changes ** Backwards compatibility * Geronimo architecture ** GBeans ** Subprojects ** Components *** Distributions ** Repositories ** Configuration ** Customize the server * Installation ** Planning ** Binary ** Source ** Configuration *** Ports interaction *** Repositories *** Logging *** Security * Deployment ** What changed? ** New deployment options *** Command line - standard *** Command line - GShell *** Plugins *** Console Deployment plan wizard * Geronimo Administration Console ** What changed? ** Console enhancements ** The pluggable console ** Expert mode ** Deployment plans wizard ** CA helper * GShell ** What is it? ** Benefits ** What it does/replaces ** Tools and commands ** How-to samples * Monitoring ** What is it? ** What can I monitor ** Impact on the server workload? ** Install ** Customization * Pluggable console ** What is it? ** Benefits ** Architecture ** Install/deploy ** Customization ** Developing new portlets * Plugin infrastructure ** What are the plugins? ** Enhancements from previous releases ** Plugin infrastructure/architecture ** plugin.xml ** Plugins install ** Pluggable console ** GShell commands option * Security ** Enhancements ** Planning ** Configuration * Tooling ** Devtools *** Geronimo eclipse plugin ** j2g * Clustering * Sample applications * Tutorials Now that you see this list we also need your help to *develop* some of these topics. Pls chime in. Cheers! Hernan
Re: Unable to shutdown G 2.1 server
I have seen it take a very long time to shut down, or even give a wonderfully lengthy stack trace on a shut down if the JVM runs out of memory for some reason or another... so that might be something to look into. Thanks, Erik B. Craig [EMAIL PROTECTED] On Jan 27, 2008, at 4:02 PM, Vamsavardhana Reddy wrote: I am unable to shutdown G 2.1 Tomcat server either from admin console or by pressing Ctrl+C in the command window on Windows XP. Has anyone else run into this situation? ++Vamsi
[jira] Commented: (GERONIMO-3790) monitoring agent should provide jmx support
[ https://issues.apache.org/jira/browse/GERONIMO-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563061#action_12563061 ] Erik B. Craig commented on GERONIMO-3790: - Patch Committed revision 615738. Keep the jira open until it's confirmed all is well Thanks monitoring agent should provide jmx support --- Key: GERONIMO-3790 URL: https://issues.apache.org/jira/browse/GERONIMO-3790 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Attachments: geronimo-3790.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Remove old JVM Memory graph from console?
All, Currently in the admin console there is an 'Information' page under the 'Server' group that contains among other things a DWR driven graph that updates every second showing the current JVM memory usage. Now that we have the monitoring plugin rolled in with everything, I suggest this be removed as it is now antiquated and no longer necessary, perhaps leaving the 'Information' page to just show a snapshot of information on page load instead of automatically updating every second. If nobody objects to this, I will go ahead and make this change Thanks, Erik B. Craig [EMAIL PROTECTED]
