[jira] Created: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
The version of the application when deploying an EBA is set incorrectly --- Key: GERONIMO- URL: https://issues.apache.org/jira/browse/GERONIMO- Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0-M1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 3.0 When deploying an EBA into Apache Geronimo the version set for the application is pulled from the Application Metadata but it appears that it is constructing the version incorrectly. For example, in the following deployment the application version is set to 0.2.2-incubating rather than 0.2.0-incubating: b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT./bin/deploy -u system -p manager deploy ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba Using GERONIMO_HOME: /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Deployed application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
Geronimo admin console seems to be missing the System Modules portlet page -- Key: GERONIMO-5556 URL: https://issues.apache.org/jira/browse/GERONIMO-5556 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Joe Bohn I happened to notice that with the latest trunk image the System Modules portlet page is missing. I suspect that this was the result of some recent change reorganizing the navigation panel. It seems that currently the Plugins page and the System Modules page are attempting to occupy the same slot and so the last one processed (Plugins in this case) wins. I'll update the plan and find an unoccupied slot for System Modules. We might want to reconsider this processing where basically any plugin installed later can trump and earlier entry in the admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[ https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-5556: -- Assignee: Joe Bohn Geronimo admin console seems to be missing the System Modules portlet page -- Key: GERONIMO-5556 URL: https://issues.apache.org/jira/browse/GERONIMO-5556 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Joe Bohn Assignee: Joe Bohn I happened to notice that with the latest trunk image the System Modules portlet page is missing. I suspect that this was the result of some recent change reorganizing the navigation panel. It seems that currently the Plugins page and the System Modules page are attempting to occupy the same slot and so the last one processed (Plugins in this case) wins. I'll update the plan and find an unoccupied slot for System Modules. We might want to reconsider this processing where basically any plugin installed later can trump and earlier entry in the admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[ https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-5556. Fix Version/s: 3.0 Resolution: Fixed Geronimo admin console seems to be missing the System Modules portlet page -- Key: GERONIMO-5556 URL: https://issues.apache.org/jira/browse/GERONIMO-5556 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 3.0 I happened to notice that with the latest trunk image the System Modules portlet page is missing. I suspect that this was the result of some recent change reorganizing the navigation panel. It seems that currently the Plugins page and the System Modules page are attempting to occupy the same slot and so the last one processed (Plugins in this case) wins. I'll update the plan and find an unoccupied slot for System Modules. We might want to reconsider this processing where basically any plugin installed later can trump and earlier entry in the admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
[ https://issues.apache.org/jira/browse/GERONIMO-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-. Resolution: Fixed The version of the application when deploying an EBA is set incorrectly --- Key: GERONIMO- URL: https://issues.apache.org/jira/browse/GERONIMO- Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-M1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 3.0 When deploying an EBA into Apache Geronimo the version set for the application is pulled from the Application Metadata but it appears that it is constructing the version incorrectly. For example, in the following deployment the application version is set to 0.2.2-incubating rather than 0.2.0-incubating: b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT./bin/deploy -u system -p manager deploy ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba Using GERONIMO_HOME: /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Deployed application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[ https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-5556. -- Regression: [Regression] Geronimo admin console seems to be missing the System Modules portlet page -- Key: GERONIMO-5556 URL: https://issues.apache.org/jira/browse/GERONIMO-5556 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 3.0 I happened to notice that with the latest trunk image the System Modules portlet page is missing. I suspect that this was the result of some recent change reorganizing the navigation panel. It seems that currently the Plugins page and the System Modules page are attempting to occupy the same slot and so the last one processed (Plugins in this case) wins. I'll update the plan and find an unoccupied slot for System Modules. We might want to reconsider this processing where basically any plugin installed later can trump and earlier entry in the admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
[ https://issues.apache.org/jira/browse/GERONIMO-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-. -- The version of the application when deploying an EBA is set incorrectly --- Key: GERONIMO- URL: https://issues.apache.org/jira/browse/GERONIMO- Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-M1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 3.0 When deploying an EBA into Apache Geronimo the version set for the application is pulled from the Application Metadata but it appears that it is constructing the version incorrectly. For example, in the following deployment the application version is set to 0.2.2-incubating rather than 0.2.0-incubating: b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT./bin/deploy -u system -p manager deploy ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba Using GERONIMO_HOME: /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Deployed application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5285) deploy, undeploy, deploy of blog sample fails
[ https://issues.apache.org/jira/browse/GERONIMO-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863959#action_12863959 ] Joe Bohn commented on GERONIMO-5285: Not sure if this will help but here is my experience. - I was able to uninstall (at least once) and then reinstall and I didn't hit this error. I think I was using a build from yesterday afternoon (but perhaps not - see below). I performed the uninstall from the web console rather than the command line - if that makes a difference. But I reinstalled from the command line. - After seeing this JIRA I updated my code and rebuilt. Now I am getting the same error on install and it doesn't seem to matter how the uninstall if performed (command line or web console). - It is possible that I didn't refresh my running image with the new build yesterday as I had intended. If that is the case, then it would mean that the error might have been introduced in the past few days as I'm fairly sure I updated my running image on Thursday or Friday of last week. Joe deploy, undeploy, deploy of blog sample fails - Key: GERONIMO-5285 URL: https://issues.apache.org/jira/browse/GERONIMO-5285 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Kevan Miller Fix For: 3.0 After undeploy of blog sample: ./deploy undeploy ../../samples/org.apache.aries.samples.blog.jpa.eba-0.1-incubating.eba A subsequent deploy fails: $ ./deploy deploy ../../samples/org.apache.aries.samples.blog.jpa.eba-0.1-incubating.eba Using GERONIMO_HOME: /Users/kevan/Demo/geronimo-tomcat7-javaee6-3.0-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home 2010-05-04 11:31:34,077 ERROR [DeployTool] Error: org.apache.geronimo.common.DeploymentException: Unable to deploy org.apache.aries.samples.blog.jpa.eba-0.1-incubating.eba: java.io.IOException: Sum file already exists Sum file already exists at org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43) at org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148) at org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:173) at org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64) at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5270) Enforce Java1.6 for Geronimo 3.0 build in maven and perhaps enforce the required maven version as well (2.2.1?).
Enforce Java1.6 for Geronimo 3.0 build in maven and perhaps enforce the required maven version as well (2.2.1?). - Key: GERONIMO-5270 URL: https://issues.apache.org/jira/browse/GERONIMO-5270 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0 Reporter: Joe Bohn Fix For: 3.0 I believe that Geronimo 3.0 must be built using java 1.6 and fails if that is not the case. However, it isn't a nice failure. We should configure maven to check the java version and fail if it isn't 1.6. We should also consider checking the maven version and enforcing a minimum maven version - I've heard that 2.2.1 is required. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751011#action_12751011 ] Joe Bohn commented on DAYTRADER-68: --- Forrest, Is this a patch for trunk? Was it created after the most recent structure changes? I believe that the /daytrader-webonly/ directory and it's contents are all but physically removed from svn now and has been replaced with /assemblies/web/daytrader-web-jdbc/ Joe A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Fix For: 2.2 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly-updated.patch, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4722) XSS/XSRF filters are triggering Session object creation for unknown URLs
[ https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12725723#action_12725723 ] Joe Bohn commented on GERONIMO-4722: It appears that we were too aggressive in the application of the XSSXSRFFilter. There is no strong reason that this should be applied to the welcome application which has a context-root of /'. Combine that with the filter URL pattern of /* registered for the filter on the welcome application and nearly every url is inspected. It seems we can remove this filter from welcome. Refer to this thread for more details: http://www.nabble.com/Session-creation-triggered-by-XSS-XSRF-filter-to24272007s134.html XSS/XSRF filters are triggering Session object creation for unknown URLs Key: GERONIMO-4722 URL: https://issues.apache.org/jira/browse/GERONIMO-4722 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Assignee: Joe Bohn Priority: Minor Fix For: 2.1.5, 2.2 The XSS/XSRF filters are causing session objects to be created for unknown urls. For instance, a request for localhost:8080/nonexistenturl creates a session, as indicated in following stack trace: http-0.0.0.0-808...@10 daemon, priority=5, in group 'main', status: 'RUNNING' at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:284) at org.apache.catalina.connector.Request.doGetSession(Request.java:2,312) at org.apache.catalina.connector.Request.getSession(Request.java:2,075) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at org.apache.geronimo.console.filter.XSRFHandler.isInvalidSession(XSRFHandler.java:79) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4722) XSS/XSRF filters are triggering Session object creation for unknown URLs
[ https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4722: -- Assignee: Joe Bohn XSS/XSRF filters are triggering Session object creation for unknown URLs Key: GERONIMO-4722 URL: https://issues.apache.org/jira/browse/GERONIMO-4722 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Assignee: Joe Bohn Priority: Minor Fix For: 2.1.5, 2.2 The XSS/XSRF filters are causing session objects to be created for unknown urls. For instance, a request for localhost:8080/nonexistenturl creates a session, as indicated in following stack trace: http-0.0.0.0-808...@10 daemon, priority=5, in group 'main', status: 'RUNNING' at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:284) at org.apache.catalina.connector.Request.doGetSession(Request.java:2,312) at org.apache.catalina.connector.Request.getSession(Request.java:2,075) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at org.apache.geronimo.console.filter.XSRFHandler.isInvalidSession(XSRFHandler.java:79) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4722) XSS/XSRF filters are triggering Session object creation for unknown URLs
[ https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4722. Resolution: Fixed I've committed changes in branches/2.1 (rev. 789881) and trunk (rev. 789885). This seems to resolve the problem you observed with session creation. Please validate before closing. XSS/XSRF filters are triggering Session object creation for unknown URLs Key: GERONIMO-4722 URL: https://issues.apache.org/jira/browse/GERONIMO-4722 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Assignee: Joe Bohn Priority: Minor Fix For: 2.1.5, 2.2 The XSS/XSRF filters are causing session objects to be created for unknown urls. For instance, a request for localhost:8080/nonexistenturl creates a session, as indicated in following stack trace: http-0.0.0.0-808...@10 daemon, priority=5, in group 'main', status: 'RUNNING' at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:284) at org.apache.catalina.connector.Request.doGetSession(Request.java:2,312) at org.apache.catalina.connector.Request.getSession(Request.java:2,075) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at org.apache.geronimo.console.filter.XSRFHandler.isInvalidSession(XSRFHandler.java:79) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12710753#action_12710753 ] Joe Bohn commented on DAYTRADER-68: --- Donald, Can you clarify your comments regarding geronimo plugins? Daytrader trunk already creates several plugins for both tomcat and jetty (streamer-client, ws-client, and the core sample itself) along with plugins for various datasources and jms. In fact, I think these were part of the 2.1.3 release you had assembled and put up for vote a few months back. Introducing a web-only version of the core sample and making plugins for it available for tomcat and jetty seems consistent with what is already in place. I see no reason to extract the plugin generation from Daytrader and include it in Geronimo Samples. If daytrader is to be a subproject of Geronimo then it seems appropriate that it would contain some Geronimo specific content. However, I would hope that the addition of Geronimo plugins would not hinder our ability to generate the vanilla war/ear versions for deployment in other web/app servers since that is my current interest at the moment. A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Fix For: 2.2 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12710795#action_12710795 ] Joe Bohn commented on DAYTRADER-68: --- I agree that we shouldn't break the non-plugin install. What is currently in trunk installs in tomcat as-is. I updated the build so that commons-logging is included in the war's web-inf/lib. The only other dependency that must be manually placed in the tomcat/lib is the derby jar ... at least that worked for me. A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Fix For: 2.2 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned DAYTRADER-68: - Assignee: Joe Bohn (was: Forrest Xia) A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved DAYTRADER-68. --- Resolution: Fixed Fix Version/s: 2.2 A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Fix For: 2.2 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709873#action_12709873 ] Joe Bohn commented on DAYTRADER-68: --- I decided to go ahead and checkin the code so that further collaboration could take place in svn. I added the missing headers, fixed the build, included commons-logging in the war (not included in tomcat 6 and decided it was better in the war than manually pulling it into tomcat) and beautified some code. Included in trunk rev. 775187 Still needed is to create plugins for Geronimo jetty and tomcat. We also need to reconcile the datasource issues for Geronimo (perhaps we can share a common datasource with the full sample). A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Joe Bohn Fix For: 2.2 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708651#action_12708651 ] Joe Bohn commented on DAYTRADER-68: --- Some more comments and questions: - I noticed that ./daytrader-webonly/daytrader-datasource-plan.xml and ./daytrader-webonly/src/main/webapp/META-INF/context.xml are missing the Apache License header. Can you please add them with your contribution? - We probably need some more description (in the README?) about the datasource and how to handle this for Geronimo installations and possibly Tomcat installs as well. I can see where it might be confusing with the daytrader-derby-datasource that we also have out there. Perhaps we need to include webonly in this name as well. - were you working on the tomcat/jetty plugins of this that were discussed on the original proposal? A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708034#action_12708034 ] Joe Bohn commented on DAYTRADER-68: --- Another issue: Although there are some problems with building daytrader trunk without this patch applied once it is applied there is a new problem: Project 'org.apache.geronimo.daytrader:daytrader-web' is duplicated in the reactor Looks like there is a conflict because we now have to projects named daytrader-web - the original one under modules/web/ and the new one. A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707533#action_12707533 ] Joe Bohn commented on DAYTRADER-68: --- Hi Forrest, That definitely fixed the line-ending issues. However, I think we still need some more work to this patch before we apply it. It is named as being a web-only version of daytrader but it is also tomcat specific. There was discussion when this was first proposed that we should support both jetty and tomcat. If we cannot have a single generic version than we should perhaps create two webonly versions - one for tomcat and one for jetty. I wonder if we can configure this something like the console so that we can have a generic war and then tomcat and jetty specific plugins for easy installation. We need to think about this some more ... but I wanted to post the concern so you were aware of the issue. Thanks, Joe A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706578#action_12706578 ] Joe Bohn commented on DAYTRADER-68: --- Hi Forrest, I attempted to apply this patch locally but encountered some problems due to inconsistent line-endings on the files. I think the problem is related to not having the right config setting for svn. Please reference http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html and after making the appropriate changes generate a new patch. Thanks, Joe A version of daytrader for Tomcat 6 --- Key: DAYTRADER-68 URL: https://issues.apache.org/jira/browse/DAYTRADER-68 Project: DayTrader Issue Type: New Feature Security Level: public(Regular issues) Components: Web Tier Affects Versions: 2.2 Environment: Tomcat 6.0.18 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: daytrader-webonly.patch I have a trimmed version of daytrader for tomcat 6, and want to contribute to daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4437) Upgrade to Jetty 6.1.11
[ https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4437: -- Assignee: (was: Joe Bohn) Upgrade to Jetty 6.1.11 --- Key: GERONIMO-4437 URL: https://issues.apache.org/jira/browse/GERONIMO-4437 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies, Jetty Affects Versions: 2.2 Reporter: Donald Woods Fix For: Wish List Upgrade to newer Jetty release, 6.1.11. We looked into 6.1.14 but that causes some tck issues for us so we'll use 6.1.11 for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3572) Disable access log by default and provide an easy way for the user to enable/disable logging at will.
[ https://issues.apache.org/jira/browse/GERONIMO-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-3572: -- Assignee: (was: Joe Bohn) Disable access log by default and provide an easy way for the user to enable/disable logging at will. - Key: GERONIMO-3572 URL: https://issues.apache.org/jira/browse/GERONIMO-3572 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, Jetty, Tomcat Affects Versions: 2.1 Reporter: Joe Bohn Currently access logging is enabled by default in both the Tomcat and Jetty assemblies of Geronimo. This is different than the default for Tomcat which is that the access log is initially disabled and apparently different than most servers typically ship with logging disabled. Logging can be a significant drain on the performance of the system and is seldom required. We should do the following in Geornimo: 1) change the default to have access logging disabled for Tomcat and if possible for Jetty 2) Provide a mechanism so that the user can easily enable/disable access logging - preferably via the web console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4597) Validate Web Admin Console input - address admin console security vulnerabilities
[ https://issues.apache.org/jira/browse/GERONIMO-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4597: --- Description: This JIRA addresses the following security vulnerabilities in the web admin console: CVE-2008-5518: Apache Geronimo web administration console directory traversal vulnerabilities. A vulnerability was found in several portlets including Services/Repository, Embedded DB/DB Manager, and Security/Keystores when running the Apache Geronimo server on Windows. This issue may allow a remote attacker to upload any file in any directory. This affects all full JavaEE Geronimo assemblies or other distributions which include the administration web console up to and including Apache Geronimo 2.1.3. An alternative workaround (if you choose to not upgrade to Apache Geronimo 2.1.4) would be to stop or undeploy the administration web console application in the server. Credit: The Apache Geronimo project would like to thank Digital Security Research Group (dsecrg.com) for responsibly reporting this issue and assisting us with validating our fixes. CVE-2009-0038: Apache Geronimo web administration console XSS vulnerabilities Various linked and stored cross-site scripting (XSS) vulnerabilities were found in the Apache Geronimo administrative console and related utilities. Using this vulnerability an attacker can steal an administrator's cookie and then authenticate as administrator or perform certain administrative actions. For example, a user can inject XSS in some URLs or in several input fields in various portlets. This affects all full JavaEE Geronimo assemblies or other distributions which include the administration web console up to and including Apache Geronimo 2.1.3. An alternative workaround (if you choose to not upgrade to Apache Geronimo 2.1.4) would be to stop or undeploy the administration web console application in the server. Credit: The Apache Geronimo project would like to thank Digital Security Research Group (dsecrg.com) and Marc Schoenefeld (Red Hat Security Response Team) for responsibly reporting this issue and assisting us with validating our fixes. CVE-2009-0039: Apache Geronimo web administration console XSRF vulnerabilities Various cross-site request forgery (XSRF or CSRF) vulnerabilities were identified in the Apache Geronimo web administration console. Exploiting these issues may allow a remote attacker to perform certain administrative actions, e.g. change web administration password, upload applications, etc... using predictable URL requests once the user has authenticated and obtained a valid session with the server. This affects all full JavaEE Geronimo assemblies or other distributions which include the administration web console up to and including Apache Geronimo 2.1.3. An alternative workaround (if you choose to not upgrade to Apache Geronimo 2.1.4) would be to stop or undeploy the administration web console application in the server. Credit: The Apache Geronimo project would like to thank Digital Security Research Group (dsecrg.com) for responsibly reporting this issue and assisting us with validating our fixes. It corrects the issues with the addition of directory checks and a servlet filter to check for XSS and XSRF vulnerabilities Summary: Validate Web Admin Console input - address admin console security vulnerabilities (was: Validate Web Admin Console input) Validate Web Admin Console input - address admin console security vulnerabilities - Key: GERONIMO-4597 URL: https://issues.apache.org/jira/browse/GERONIMO-4597 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 This JIRA addresses the following security vulnerabilities in the web admin console: CVE-2008-5518: Apache Geronimo web administration console directory traversal vulnerabilities. A vulnerability was found in several portlets including Services/Repository, Embedded DB/DB Manager, and Security/Keystores when running the Apache Geronimo server on Windows. This issue may allow a remote attacker to upload any file in any directory. This affects all full JavaEE Geronimo assemblies or other distributions which include the administration web console up to and including Apache Geronimo 2.1.3. An alternative workaround (if you choose to not upgrade to Apache Geronimo 2.1.4) would be to stop or undeploy the administration web console application in the server. Credit: The Apache Geronimo project would like to thank Digital Security Research Group (dsecrg.com) for responsibly reporting this issue
[jira] Updated: (GERONIMO-4605) Text based apache license at the bottom of every console pages
[ https://issues.apache.org/jira/browse/GERONIMO-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4605: --- Affects Version/s: 2.2 Text based apache license at the bottom of every console pages -- Key: GERONIMO-4605 URL: https://issues.apache.org/jira/browse/GERONIMO-4605 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP Reporter: Shawn Jiang Assignee: Joe Bohn Priority: Minor Attachments: G4605.patch There are text based apache licenses at the bottom of every console pages like this: --- * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the License); you may not use this file except in compliance with * the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ --- It's not a big but an annoying problem from user's perspective. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4605) Text based apache license at the bottom of every console pages
[ https://issues.apache.org/jira/browse/GERONIMO-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4605. Resolution: Fixed Fix Version/s: 2.2 2.1.5 fixed integrated in branches/2.1 with rev. 759950 and trunk with rev. 759952 Text based apache license at the bottom of every console pages -- Key: GERONIMO-4605 URL: https://issues.apache.org/jira/browse/GERONIMO-4605 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP Reporter: Shawn Jiang Assignee: Joe Bohn Priority: Minor Fix For: 2.1.5, 2.2 Attachments: G4605.patch There are text based apache licenses at the bottom of every console pages like this: --- * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the License); you may not use this file except in compliance with * the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ --- It's not a big but an annoying problem from user's perspective. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4597) Validate Web Admin Console input
[ https://issues.apache.org/jira/browse/GERONIMO-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4597. Resolution: Fixed Fix Version/s: 2.1.5 checked into branches/2.1.4 with rev. 758252, branches/2.1 with rev. 758274, and trunk with rev. 758297 Validate Web Admin Console input Key: GERONIMO-4597 URL: https://issues.apache.org/jira/browse/GERONIMO-4597 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4588) Adding multiple server with the same host in monitoring portlet results in a sql error
[ https://issues.apache.org/jira/browse/GERONIMO-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4588: -- Assignee: Joe Bohn (was: Jarek Gawor) Adding multiple server with the same host in monitoring portlet results in a sql error -- Key: GERONIMO-4588 URL: https://issues.apache.org/jira/browse/GERONIMO-4588 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.4, 2.2 Environment: Windows XP, Geronimo V2.1.4 Reporter: Ashish Jain Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Attachments: geronimo-4588.patch, Geronimo-4588_Jack.patch Adding multiple server with same host in monitoring portlet results in a sql error. It seems the IP attribute in Servers table is defined to be unique. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4588) Adding multiple server with the same host in monitoring portlet results in a sql error
[ https://issues.apache.org/jira/browse/GERONIMO-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4588. Resolution: Fixed Fix Version/s: 2.1.5 checked into branches/2.1.4 (rev. 757917) and branches/2.1 (rev. 757919) Adding multiple server with the same host in monitoring portlet results in a sql error -- Key: GERONIMO-4588 URL: https://issues.apache.org/jira/browse/GERONIMO-4588 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1.4, 2.2 Environment: Windows XP, Geronimo V2.1.4 Reporter: Ashish Jain Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 Attachments: geronimo-4588.patch, Geronimo-4588_Jack.patch Adding multiple server with same host in monitoring portlet results in a sql error. It seems the IP attribute in Servers table is defined to be unique. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4593) Upgrade to OpenJPA 1.2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4593. Resolution: Fixed Updated in branches/2.1.4 rev. 756943 Updated in branches/2.1 rev 756945 Updated in trunk in rev 756946 Upgrade to OpenJPA 1.2.1 Key: GERONIMO-4593 URL: https://issues.apache.org/jira/browse/GERONIMO-4593 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.1.4, 2.1.5, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 Upgrade to OpenJPA 1.2.1 when released -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4593) Upgrade to OpenJPA 1.2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4593: --- Affects Version/s: 2.2 2.1.5 Fix Version/s: 2.2 2.1.5 Upgrade to OpenJPA 1.2.1 Key: GERONIMO-4593 URL: https://issues.apache.org/jira/browse/GERONIMO-4593 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: persistence Affects Versions: 2.1.4, 2.1.5, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5, 2.2 Upgrade to OpenJPA 1.2.1 when released -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager
[ https://issues.apache.org/jira/browse/GERONIMO-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4595: -- Assignee: Joe Bohn script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager --- Key: GERONIMO-4595 URL: https://issues.apache.org/jira/browse/GERONIMO-4595 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: IE7 + windows XP + sun JDK 1.5 Reporter: Shawn Jiang Assignee: Joe Bohn Priority: Minor Attachments: patch_script_error.patch reproduce steps: 1, Use IE to login to console. 2, Click the update button in portlet console --- server --- Server Logs -- Log Manager expected result: no error actual result: there's a script error logFile is not defined -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager
[ https://issues.apache.org/jira/browse/GERONIMO-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12683865#action_12683865 ] Joe Bohn commented on GERONIMO-4595: I can not reproduce the error. I have only attempted this in 2.1.4 but that and 2.1.5 are the only affected releases stated in the description. Are there any more specifics necessary to reproduce? I used IE7 and did the steps listed without any other changes in the portlet. Are you also making some changes in the config file listed or something? script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager --- Key: GERONIMO-4595 URL: https://issues.apache.org/jira/browse/GERONIMO-4595 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: IE7 + windows XP + sun JDK 1.5 Reporter: Shawn Jiang Assignee: Joe Bohn Priority: Minor Attachments: patch_script_error.patch reproduce steps: 1, Use IE to login to console. 2, Click the update button in portlet console --- server --- Server Logs -- Log Manager expected result: no error actual result: there's a script error logFile is not defined -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4597) Validate Web Admin Console input
Validate Web Admin Console input Key: GERONIMO-4597 URL: https://issues.apache.org/jira/browse/GERONIMO-4597 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1.3, 2.1.2, 2.1.1, 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager
[
https://issues.apache.org/jira/browse/GERONIMO-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12683939#action_12683939
]
Joe Bohn commented on GERONIMO-4595:
Ok, so it isn't quite so obvious of an error ... but we still might as well fix
it since it's small and it has been identified. Thanks for catching it.
I'm going to check-in a modified version of your patch. IIUC there is no need
to query or check for a non-existent logFile ... so instead I've updated it to
check for the configFile. This also gets the reset function working again.
function portlet:namespace/validateForm(){
with(document.portlet:namespace/update){
-if(trim(logFile.value).length == ){
-alert(Please input the log file name.);
-logFile.value=;
-logFile.focus();
+if(trim(configFile.value).length == ){
+alert(Please input the configuration file name.);
+configFile.value=;
+configFile.focus();
return false;
}
-if(trim(layoutPattern.value) == ){
-alert(Please input layout pattern.);
-layoutPattern.value=;
-layoutPattern.focus();
-return false;
-}
-
}
return true;
}
script error when clicking the update button in portlet console
---server---Server Logs -- Log Manager
---
Key: GERONIMO-4595
URL: https://issues.apache.org/jira/browse/GERONIMO-4595
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: IE7 + windows XP + sun JDK 1.5
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
Attachments: patch_script_error.patch
reproduce steps:
1, Use IE to login to console.
2, Click the update button in portlet console --- server --- Server Logs
-- Log Manager
expected result: no error
actual result: there's a script error logFile is not defined
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager
[
https://issues.apache.org/jira/browse/GERONIMO-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12683939#action_12683939
]
Joe Bohn edited comment on GERONIMO-4595 at 3/20/09 10:08 AM:
--
Ok, so it isn't quite so obvious of an error ... but we still might as well fix
it since it's small and it has been identified. Thanks for catching it.
I'm going to check-in a modified version of your patch. IIUC there is no need
to query or check for a non-existent logFile ... so instead I've updated it to
check for the configFile. This also gets the reset function working again.
{noformat}
function portlet:namespace/validateForm(){
with(document.portlet:namespace/update){
-if(trim(logFile.value).length == ){
-alert(Please input the log file name.);
-logFile.value=;
-logFile.focus();
+if(trim(configFile.value).length == ){
+alert(Please input the configuration file name.);
+configFile.value=;
+configFile.focus();
return false;
}
-if(trim(layoutPattern.value) == ){
-alert(Please input layout pattern.);
-layoutPattern.value=;
-layoutPattern.focus();
-return false;
-}
-
}
return true;
}
{noformat}
was (Author: jbohn):
Ok, so it isn't quite so obvious of an error ... but we still might as well
fix it since it's small and it has been identified. Thanks for catching it.
I'm going to check-in a modified version of your patch. IIUC there is no need
to query or check for a non-existent logFile ... so instead I've updated it to
check for the configFile. This also gets the reset function working again.
function portlet:namespace/validateForm(){
with(document.portlet:namespace/update){
-if(trim(logFile.value).length == ){
-alert(Please input the log file name.);
-logFile.value=;
-logFile.focus();
+if(trim(configFile.value).length == ){
+alert(Please input the configuration file name.);
+configFile.value=;
+configFile.focus();
return false;
}
-if(trim(layoutPattern.value) == ){
-alert(Please input layout pattern.);
-layoutPattern.value=;
-layoutPattern.focus();
-return false;
-}
-
}
return true;
}
script error when clicking the update button in portlet console
---server---Server Logs -- Log Manager
---
Key: GERONIMO-4595
URL: https://issues.apache.org/jira/browse/GERONIMO-4595
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: IE7 + windows XP + sun JDK 1.5
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
Attachments: patch_script_error.patch
reproduce steps:
1, Use IE to login to console.
2, Click the update button in portlet console --- server --- Server Logs
-- Log Manager
expected result: no error
actual result: there's a script error logFile is not defined
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager
[ https://issues.apache.org/jira/browse/GERONIMO-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4595. Resolution: Fixed Fix Version/s: 2.1.5 2.1.4 script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager --- Key: GERONIMO-4595 URL: https://issues.apache.org/jira/browse/GERONIMO-4595 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4, 2.1.5, 2.2 Environment: IE7 + windows XP + sun JDK 1.5 Reporter: Shawn Jiang Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.1.5 Attachments: patch_script_error.patch reproduce steps: 1, Use IE to login to console. 2, Click the update button in portlet console --- server --- Server Logs -- Log Manager expected result: no error actual result: there's a script error logFile is not defined -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4529) Corba port 1050 is not released after stopping j2ee-corba-yoko configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12683013#action_12683013 ] Joe Bohn commented on GERONIMO-4529: I think you should apply this patch to both branches/2.1 and trunk for consistency. When we have a yoko solution we can remove the change. However, I would not want to risk regression of function if we end up shipping a 2.1.5 or 2.2 release before we have a fix in yoko. We should also close this JIRA so that it shows the issue as being addressed in the release notes when generated. You can open another JIRA to reverse these changes and link it to the yoko JIRA. Corba port 1050 is not released after stopping j2ee-corba-yoko configuration Key: GERONIMO-4529 URL: https://issues.apache.org/jira/browse/GERONIMO-4529 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: CORBA Affects Versions: 2.1.4, 2.2 Environment: Windows XP JDK 1.5 Geronimo 2.2 SNAPSHOT 20090202 Reporter: Ivan Assignee: Ivan Fix For: 2.2 Attachments: fix-g4529-jeffyin.patch After stopping the corba component in the console, port 1050 is not released. Use command netstat or connect it with Eclipse Debug. Those two threads are still running. Yoko:Server:StartedThread. It seems it is still blocked on ServerSocket.accept method. And I could not start the Corba service in the admin console due to address already in use. Thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4592) Upgrade to OpenEJB 3.0.1
Upgrade to OpenEJB 3.0.1 Key: GERONIMO-4592 URL: https://issues.apache.org/jira/browse/GERONIMO-4592 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4 Upgrade to newly release OpenEJB 3.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4592) Upgrade to OpenEJB 3.0.1
[ https://issues.apache.org/jira/browse/GERONIMO-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4592: --- Description: Upgrade to newly released OpenEJB 3.0.1 (was: Upgrade to newly release OpenEJB 3.0.1) Upgrade to OpenEJB 3.0.1 Key: GERONIMO-4592 URL: https://issues.apache.org/jira/browse/GERONIMO-4592 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4 Upgrade to newly released OpenEJB 3.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4593) Upgrade to OpenJPA 1.2.1
Upgrade to OpenJPA 1.2.1 Key: GERONIMO-4593 URL: https://issues.apache.org/jira/browse/GERONIMO-4593 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: persistence Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4 Upgrade to OpenJPA 1.2.1 when released -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4592) Upgrade to OpenEJB 3.0.1
[ https://issues.apache.org/jira/browse/GERONIMO-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12683027#action_12683027 ] Joe Bohn commented on GERONIMO-4592: updated in rev. 755595 for branches/2.1.4 and rev. 755597 in branches/2.1 Upgrade to OpenEJB 3.0.1 Key: GERONIMO-4592 URL: https://issues.apache.org/jira/browse/GERONIMO-4592 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4 Upgrade to newly released OpenEJB 3.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4592) Upgrade to OpenEJB 3.0.1
[ https://issues.apache.org/jira/browse/GERONIMO-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4592. Resolution: Fixed Fix Version/s: 2.1.5 Upgrade to OpenEJB 3.0.1 Key: GERONIMO-4592 URL: https://issues.apache.org/jira/browse/GERONIMO-4592 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.1.5 Upgrade to newly released OpenEJB 3.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4507: --- Fix Version/s: (was: 2.1.4) 2.1.5 Assignee: (was: Joe Bohn) updated release version as it appears this won't make 2.1.4. Also removed myself as assigned so that others could investigate potential fixes. Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Priority: Minor Fix For: 2.1.5, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2_v22.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4553: --- Assignee: (was: Joe Bohn) unassigned so that others can pick it up and provide a fix. Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Fix For: 2.1.5, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at
[jira] Resolved: (GERONIMO-4473) Validate the artifact fields when adding an archive to the repository
[ https://issues.apache.org/jira/browse/GERONIMO-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4473. Resolution: Fixed Validate the artifact fields when adding an archive to the repository - Key: GERONIMO-4473 URL: https://issues.apache.org/jira/browse/GERONIMO-4473 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to exclude ( ) , ; : \ / ' and .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682733#action_12682733 ] Joe Bohn commented on GERONIMO-4507: We need a patch for this in the next day or two or it will not make it into Geronimo 2.1.4. Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2_v22.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680509#action_12680509 ] Joe Bohn commented on GERONIMO-4553: Yes, I came to the same conclusions Forrest. My patch was only intended to provide an error message when creating a duplicate stand-alone security realm. I was not trying to support the scenario of permitting the creation of duplicate realms or making the geronimo-admin realm a standalone realm. It was my understanding that this JIRA was primarily created because of the lack of any indication in the console when creating duplicate realms and was specifically written against the console. My change does address the scenario of standalone realms but unfortunately does not address the case of a duplicate realm between standalone and non-standalone configurations. For that we need more than just console changes (as you noted) since the portlet receives no indication of any failure in this scenario. I didn't get to dig any deeper into this yet so if you want to pull together a patch that would be great. However, I think we can release 2.1.4 without a fix for this issue if necessary. Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at
[jira] Commented: (GERONIMO-4558) Update to latest TranQL DB2 driver
[ https://issues.apache.org/jira/browse/GERONIMO-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680217#action_12680217 ] Joe Bohn commented on GERONIMO-4558: What is the state of this? The comment indicates that a new DB2-XA tranql adapter was pushed but I don't see one out there (the latest is still 1.2 released in April, 2008). Is there work to release 1.3 very soon (like in the next day or so)? Comment on the update to 1.3-SNAPSHOT is that there is some issue that is being worked. Are things close to being resolved? If not, then this won't make 2.1.4. Update to latest TranQL DB2 driver -- Key: GERONIMO-4558 URL: https://issues.apache.org/jira/browse/GERONIMO-4558 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Fix For: 2.1.4, 2.2 Matt has pushed out a new TranQL driver for DB2 XA. We should pick it up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680242#action_12680242 ] Joe Bohn commented on GERONIMO-4297: Is there anything else we need to wait on or can we just upgrade our pom dependency to pull in the 1.4 tranql-connector-oracle-local and tranql-connector-oracle-xa connectors and close this out? Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680259#action_12680259 ] Joe Bohn commented on GERONIMO-4297: Hmm ... I don't see entries for any of the Oracle connectors in the wizard, let alone the RAC one. I guess we need to add all of them for Oracle. Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680266#action_12680266 ] Joe Bohn commented on GERONIMO-4297: I take it back ... not sure what I was looking at ... but they are there (not RAC of course). Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4297: -- Assignee: Joe Bohn (was: David Jencks) Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680295#action_12680295 ] Joe Bohn commented on GERONIMO-4297: updated branches/2.1 to pull in new Oracle RAC connector and upgrade all Oracle tranql connectors to 1.4 in rev 751861. It would be good if somebody that has an Oracle RAC db could validate things work as expected. Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4297) Include TranQL connector for Oracle RAC
[ https://issues.apache.org/jira/browse/GERONIMO-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680308#action_12680308 ] Joe Bohn commented on GERONIMO-4297: updated trunk in rev. 751883 Include TranQL connector for Oracle RAC --- Key: GERONIMO-4297 URL: https://issues.apache.org/jira/browse/GERONIMO-4297 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Can be accomplished once patch is provided in TRANQL-10 and a new connector released by TranQL team. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679627#action_12679627 ] Joe Bohn commented on GERONIMO-4507: Applied locale-priority_fix2_v22.patch to trunk in rev 750949. Please verify and provide a patch for branches/2.1. Thanks! Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2_v22.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4532: --- Fix Version/s: (was: 2.1.4) Port the GERONIMO-4484 patch for V2.1 - Key: GERONIMO-4532 URL: https://issues.apache.org/jira/browse/GERONIMO-4532 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor I think that this issue is very important. After the GERONIMO-4485 patches are committed, I will try to port GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679631#action_12679631 ] Joe Bohn commented on GERONIMO-4532: Some of the updates to trunk for GERONIMO-4484 seem to have messed up the formatting of some of the views. Likewise, we are nearly ready to ship a Geronimo 2.1.4 release and there is not yet a patch available. At this point I don't think it makes sense to add this into 2.1.4. I'm removing 2.1.4 from the fix version. We can consider this for a future 2.1.* release once issues have been resolved and we have a branches/2.1 patch available. Port the GERONIMO-4484 patch for V2.1 - Key: GERONIMO-4532 URL: https://issues.apache.org/jira/browse/GERONIMO-4532 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor I think that this issue is very important. After the GERONIMO-4485 patches are committed, I will try to port GERONIMO-4484 patches for 2.1 version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4550) No error message displays in console when fail to create jms resource
[ https://issues.apache.org/jira/browse/GERONIMO-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4550: --- Fix Version/s: (was: 2.1.4) It appears that this fix is dependent upon the common message update which is not yet available in 2.1 and there is only a patch for 2.2. We're getting close to a 2.1.4 release and introducing these changes would be too disruptive at this point in time. Therefore, I'm removing the fix version of 2.1.4 from the JIRA. No error message displays in console when fail to create jms resource - Key: GERONIMO-4550 URL: https://issues.apache.org/jira/browse/GERONIMO-4550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:redhat 5.2 JDK 1.5 Reporter: viola.lu Assignee: Donald Woods Priority: Minor Fix For: 2.2 Attachments: fix-g4550-jeffyin.patch, fix-g4550-v22-jeffyin.patch, screenshot-1.jpg, screenshot-2.jpg 1.Create a console.jms/org.ibm.samples/1.0/rar resouce from admin console 2.Receate a console.jms/org.ibm.samples/1.0/rar resource , but no error in conosle but error message in geronimo.out :Deployer operation failed: Module console.jms/org.ibm.samples/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. 3.So no error message when fail to create a jms resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679693#action_12679693 ] Joe Bohn commented on GERONIMO-4549: So it seems that this really is an XBean issue. We should create a JIRA under their project: http://issues.apache.org/jira/browse/XBEAN For us to get this into Geronimo 2.1.4 we would need another xbean release first. It would most likely delay 2.1.4 more than just a few days. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4549_0307.patch Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4576) Make persistence exceptions more visible to client
Make persistence exceptions more visible to client -- Key: GERONIMO-4576 URL: https://issues.apache.org/jira/browse/GERONIMO-4576 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: persistence Affects Versions: 2.2 Environment: Linux, Windows Reporter: Joe Bohn Assignee: David Jencks Priority: Minor Fix For: 2.2 See http://issues.apache.org/jira/browse/GERONIMO-3907 for details of the original problem. That core problem was resolved. However, upon resolution it was mentioned that it would be beneficial to report more specific failure information back to the client. From GERONIMO-3907: Ralf Baumhof - 06/May/08 06:17 AM Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed. If the server gets an error on trying a commit, this error is now thrown to the web bean. Exception text: javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled back, presumably because setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for rollback Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the server console, but can not be reported to the user. It would be very nice if you could change this in a later release. Thanks for your help. Vincent MATHON - 06/Nov/08 02:03 AM I agree that exceptions on the server side should not be thrown to the client side since such exceptions types might not be known by the client. However, for unit testing purpose, it is useful to attach the root cause to the RollBackException. I have modified a few lines in org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of RollBackException and it works for my unit testing purpose (I have not enough background on the java transaction architecture topic to submit a patch for production). It would be great to define a configuration parameter that permits to provide the root cause to the client and keep the current behaviour that does not by default. Geoff Callender - 22/Dec/08 03:36 AM It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679706#action_12679706 ] Joe Bohn commented on GERONIMO-3907: I created http://issues.apache.org/jira/browse/GERONIMO-4576 to address the further enhancements that are mentioned in this JIRA so that it can be closed as it appears the original problem was resolved in Geronimo 2.1.1. Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) 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.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) 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.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at
[jira] Updated: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3907: --- Fix Version/s: (was: 2.1.4) (was: 2.2) 2.1.1 Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.1 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) 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.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) 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.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:54) at javax.faces.component.UICommand.broadcast(UICommand.java:121) at
[jira] Resolved: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3907. Resolution: Fixed As confirmed in comments the core issue was resolved in 2.1.1. Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.1 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) 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.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) 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.el.parser.AstValue.invoke(AstValue.java:131) at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:68) at javax.faces.component._MethodExpressionToMethodBinding.invoke(_MethodExpressionToMethodBinding.java:75) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:54) at javax.faces.component.UICommand.broadcast(UICommand.java:121) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:292)
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679222#action_12679222 ] Joe Bohn commented on GERONIMO-4549: I see no trace of the name anywhere after I uninstall - even under Global context. Are you sure you are seeing this problem with the latest 2.1.4-SNAPSHOT? Either it's been resolved or there is some nuance to the scenario that I'm not hitting (which might help narrow down the cause and proposed fix a bit more). JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.4 Reporter: Forrest Xia Assignee: Jack Cai Priority: Blocker Fix For: 2.1.4, 2.2 Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4507) Admin console should honor the priority of user agent's language setting
[ https://issues.apache.org/jira/browse/GERONIMO-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679229#action_12679229 ] Joe Bohn commented on GERONIMO-4507: I suspect we need unique patches for trunk and branches/2.1. Also, please create patches from the root directory for the appropriate branch. Thank you. Admin console should honor the priority of user agent's language setting Key: GERONIMO-4507 URL: https://issues.apache.org/jira/browse/GERONIMO-4507 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3, 2.2 Environment: All Reporter: Jack Cai Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Attachments: locale-priority.patch, locale-priority_fix.patch, locale-priority_fix2.patch, locale-priority_V21.patch See discussion: http://www.nabble.com/Geronimo-Console-tp21369352s134p21383628.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679241#action_12679241 ] Joe Bohn commented on GERONIMO-4549: Ok, I see the failure now. You must add a destination in addition to a connection factory. Adding a connection factory alone to the resource group and all still works as expected on uninstall - the connection factory jndi name *is* removed from the global context. However, if you add both a connection factory and a destination into the same plan and deploy it both the connection factory and destination will remain under global context even after uninstall. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.4 Reporter: Forrest Xia Assignee: Jack Cai Priority: Blocker Fix For: 2.1.4, 2.2 Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4549: --- Priority: Minor (was: Blocker) Affects Version/s: 2.2 2.1.1 2.1.2 2.1.3 I moved this from blocker back to minor. I saw no justification for why it was made a blocking issue. I also verified the same issue is present in 2.1.1, 2.1.2, and 2.1.3. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679405#action_12679405 ] Joe Bohn commented on GERONIMO-4549: BTW, one other interesting tidbit. Once you have at least one jndi resource entry that is not removed subsequent entries will likewise not be removed (even if you then deploy and uninstall a resource group with just a connector). For example, if you deploy and undeploy a resource group with just one connector and no destination the connector entry will be removed from the jndi global context. If you deploy a resource group with both a connector and destination the global context entries will not be removed on uninstall. And, if you subsequently deploy and undeploy another resource group with just a connector (no destination) after the failure to cleanup mentioned above the new connector will also continue to exist in global context after the uninstall. JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Forrest Xia Assignee: Jack Cai Priority: Minor Fix For: 2.1.4, 2.2 Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4554) Cant deploy an ejb web service as a plugin using car-maven-plugin
[
https://issues.apache.org/jira/browse/GERONIMO-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678780#action_12678780
]
Joe Bohn commented on GERONIMO-4554:
I agree with Forrest. This breaks backward compatibility and as such is not an
acceptable change.
Cant deploy an ejb web service as a plugin using car-maven-plugin
-
Key: GERONIMO-4554
URL: https://issues.apache.org/jira/browse/GERONIMO-4554
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: car-maven-plugin
Affects Versions: 2.1.3
Reporter: David Jencks
Assignee: David Jencks
Fix For: 2.1.4, 2.2
I tried to deploy an ejb web service using the car-maven-plugin. The cxf and
axis2 ejb deployers set up the wslink gbean with a reference to the web
container. This is set in the plan for the deployers as WebContainer but
the geronimo-plugin.xml overrides this to ${webContainer}. The jetty and
tomcat plugins use a config-substitutions entry to e.g. set
webContainer=JettyWebContainer
So, this all works on a server where all the plugins are installed. However
it doesn't work when using the car-maven-plugin since the config.xml
overrides and config-substitutions are not applied.
We need to either make the config modifications work for the car-maven-plugin
or make sure none of the deployers the car-maven-plugin might use depend on
these customizations to work. For instance, we could change all the names to
WebContainer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3907) Persistence Exception is not visible/lost for client.
[ https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3907: --- Priority: Minor (was: Blocker) I have updated the status of this problem to minor from blocker because it appears that the original issue (no error returned) has been resolved. The remaining issue seems to be the detail of the error reported. Are there any additional enhancements planned for this JIRA in this area? If not, we should close this issue. Actually, since the core problem has been resolved we should perhaps close the issue and open a new issue requesting the enhancement. If there are no additional enhancements planned for Geronimo 2.1.4 we should remove it from the fix versions. It appears that the original problem was fixed in 2.1.1. Persistence Exception is not visible/lost for client. -- Key: GERONIMO-3907 URL: https://issues.apache.org/jira/browse/GERONIMO-3907 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 2.0.2, 2.1 Environment: Linux, Windows Reporter: Ralf Baumhof Assignee: David Jencks Priority: Minor Fix For: 2.1.4, 2.2 Original Estimate: 0.08h Remaining Estimate: 0.08h I am trying an insert on a table. The Entity class is wrong annotated, one column was renamed in the table. Then the following situation occurs. The call to persist(entity) is successfully, no exception is thrown. On leaving the ejb container and returning to tomact a commit is performed (it's a managed datasource, so container performs commit). This leads to the insert on database. This insert fails, a rollback is performed. On return to the JSF bean no exception can be seen by the bean. In the same class i have got a query method. If i replace the call to persist with the call to the query method everything works ok. The exception is thrown and is visible at the client site. This is the geronimo console output. The last line comes from the JSB bean which reports a successful insert. 11:58:04,390 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back openjpa-1.0.1-r420667:592145 fatal general error org.apache.openjpa.persistence.PersistenceException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2107) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1954) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1852) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1770) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:514) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:499) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:400) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:257) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:245) at org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:141) at org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75) at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:233) 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.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217) at org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy75.anlegenBenutzer(Unknown Source) at de.nrw.hagen.ggrz.benutzer.controler.BenutzerControler.anlegenBenutzer(BenutzerControler.java:44) 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
[jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
[ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678864#action_12678864 ] Joe Bohn commented on GERONIMO-4549: Perhaps I don't fully understand the problem ... but I attempted to recreate it and in my case the jndi entry was removed. I did the following: - selected Services-JMS Resources from the navigation - created a new resource group for ActiveMQ as follows: - specified a group of myRG and kept the defaults for all else - created a new connection factory under the Resource Group called myFactory and kept the defaults for all else - deployed the plan - validated that the resource group was running and visible in the JMS Resources view, the J2EE Connectors view (and running) and the JNDI viewer under ResourceAdapterModule - from the J2EE Connectors view I uninstalled my resource group rar - It was removed from the J2EE Connectors view, the JMS Resources view, and the JNDI Viewer Am I completely missing the issue? JMS resource jndi entries are not removed after uninstalling the JMS connect adapter Key: GERONIMO-4549 URL: https://issues.apache.org/jira/browse/GERONIMO-4549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.4 Reporter: Forrest Xia Priority: Blocker Fix For: 2.1.4, 2.2 Steps to reproduce this problem: 1. login admin console 2. Create a ActiveMQ resource connector with the wizard 3. Deploy it and check it is in running state 4. Click J2EE connector to uninstall it 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4553) Possible to create security realm with duplicate name in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4553: -- Assignee: Joe Bohn Possible to create security realm with duplicate name in admin console -- Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at
[jira] Updated: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4553: --- Summary: Admin console does not show error when creating duplicate security realm (was: Possible to create security realm with duplicate name in admin console) Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at
[jira] Commented: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678451#action_12678451 ] Joe Bohn commented on GERONIMO-4553: It seems that the error is different when creating a duplicate geronimo-admin realm vs. another realm (such test). In either case, the realm creation fails but the stack trace is different. I just checked in a small change in branches/2.1 (rev. 749758) to notify the user if the save fails when attempting to create the realm for any reason. It's only moderately better than no error ... but better than what we have now in my opinion. Do you think this is sufficient David? I'll merge the same change into trunk just to keep things consistent. Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at
[jira] Commented: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678457#action_12678457 ] Joe Bohn commented on GERONIMO-4553: Hmmm ... things are a bit more strange than I thought. I can realm named geronimo-admin (no error is returned to the portlet at all). The name is different than our default realm (which is geronimo-realm) - but there is still the error that you mentioned originally. If I attempt to create a second geronimo-admin realm then I get a different error (that is echoed back to the portlet) and my code will display an error. So there is more going on here than I first thought. I think the change I made is still valid but I'm not sure it addresses this issue completely. Thoughts? Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at
[jira] Issue Comment Edited: (GERONIMO-4553) Admin console does not show error when creating duplicate security realm
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678457#action_12678457 ] jbohn edited comment on GERONIMO-4553 at 3/3/09 2:29 PM: Hmmm ... things are a bit more strange than I thought. I can create a realm named geronimo-admin (no error is returned to the portlet at all). The name is different than our default realm (which is geronimo-realm) - but there is still the error that you mentioned originally. If I attempt to create a second geronimo-admin realm then I get a different error (that is echoed back to the portlet) and my code will display an error to the user. So there is more going on here than I first thought. I think the change I made is still valid but I'm not sure it addresses this issue completely. Thoughts? was (Author: jbohn): Hmmm ... things are a bit more strange than I thought. I can realm named geronimo-admin (no error is returned to the portlet at all). The name is different than our default realm (which is geronimo-realm) - but there is still the error that you mentioned originally. If I attempt to create a second geronimo-admin realm then I get a different error (that is echoed back to the portlet) and my code will display an error. So there is more going on here than I first thought. I think the change I made is still valid but I'm not sure it addresses this issue completely. Thoughts? Admin console does not show error when creating duplicate security realm Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Assignee: Joe Bohn Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at
[jira] Assigned: (GERONIMO-4562) 405 error when create plugin via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4562: -- Assignee: Joe Bohn 405 error when create plugin via admin console -- Key: GERONIMO-4562 URL: https://issues.apache.org/jira/browse/GERONIMO-4562 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.4 Environment: OS:windows JDk 1.5 Reporter: viola.lu Assignee: Joe Bohn 1.login admin console, go to application-plugin-create plugin section -choose an item and click export-click next to save plugin data but error page: HTTP Status 405 - HTTP method POST is not supported by this URL type Status report message HTTP method POST is not supported by this URL description The specified HTTP method is not allowed for the requested resource (HTTP method POST is not supported by this URL). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4562) 405 error when create plugin via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677985#action_12677985 ] Joe Bohn commented on GERONIMO-4562: Thanks for finding this. This was introduced when we were attempting to clean-up the form processing by using POST in place of GET. I'll revert the portion of the change that affected this function. 405 error when create plugin via admin console -- Key: GERONIMO-4562 URL: https://issues.apache.org/jira/browse/GERONIMO-4562 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.4 Environment: OS:windows JDk 1.5 Reporter: viola.lu Assignee: Joe Bohn 1.login admin console, go to application-plugin-create plugin section -choose an item and click export-click next to save plugin data but error page: HTTP Status 405 - HTTP method POST is not supported by this URL type Status report message HTTP method POST is not supported by this URL description The specified HTTP method is not allowed for the requested resource (HTTP method POST is not supported by this URL). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4562) 405 error when create plugin via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4562. Resolution: Fixed Fix Version/s: 2.2 2.1.4 Regression: [Regression] 405 error when create plugin via admin console -- Key: GERONIMO-4562 URL: https://issues.apache.org/jira/browse/GERONIMO-4562 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.4 Environment: OS:windows JDk 1.5 Reporter: viola.lu Assignee: Joe Bohn Fix For: 2.1.4, 2.2 1.login admin console, go to application-plugin-create plugin section -choose an item and click export-click next to save plugin data but error page: HTTP Status 405 - HTTP method POST is not supported by this URL type Status report message HTTP method POST is not supported by this URL description The specified HTTP method is not allowed for the requested resource (HTTP method POST is not supported by this URL). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4552) Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6
Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6 --- Key: GERONIMO-4552 URL: https://issues.apache.org/jira/browse/GERONIMO-4552 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Affects Versions: 2.1.4 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4 Upgrade to the latest Geronimio JavaMail provider (1.7) and JavaMail spec (1.6) that were just released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4237) Elements jndi-name, jndi-local-name and jndi ignored in openejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4237: --- Affects Version/s: 2.1.3 Fix Version/s: 2.2 2.1.4 Elements jndi-name, jndi-local-name and jndi ignored in openejb-jar.xml - Key: GERONIMO-4237 URL: https://issues.apache.org/jira/browse/GERONIMO-4237 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming, OpenEJB Affects Versions: 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3 Reporter: David Blevins Assignee: David Blevins Fix For: 2.1.4, 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4553) Possible to create security realm with duplicate name in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4553: --- Fix Version/s: 2.2 2.1.4 Possible to create security realm with duplicate name in admin console -- Key: GERONIMO-4553 URL: https://issues.apache.org/jira/browse/GERONIMO-4553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 2.1.4, 2.2 Reporter: David Jencks Fix For: 2.1.4, 2.2 If you create a security realm with a duplicate name (such as geronimo-admin) using the admin console, everything appears to work in the ui however the command line console shows the error: 2009-02-24 09:47:11,123 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry named: geronimo-admin already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfiguration(GeronimoLoginConfiguration.java:112) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAdded(GeronimoLoginConfiguration.java:97) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyCollection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdded(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget(GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running(GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at
[jira] Resolved: (GERONIMO-4552) Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4552. Resolution: Fixed Fix Version/s: 2.2 changes committed in rev. 747423 for branches/2.1 http://svn.apache.org/viewvc?rev=747423view=rev changes committed in rev. 747529 in trunk http://svn.apache.org/viewvc?rev=747529view=rev Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6 --- Key: GERONIMO-4552 URL: https://issues.apache.org/jira/browse/GERONIMO-4552 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to the latest Geronimio JavaMail provider (1.7) and JavaMail spec (1.6) that were just released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4552) Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4552: --- Affects Version/s: 2.2 Upgrade to Geronimo JavaMail provider 1.7 and JavaMail spec 1.6 --- Key: GERONIMO-4552 URL: https://issues.apache.org/jira/browse/GERONIMO-4552 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to the latest Geronimio JavaMail provider (1.7) and JavaMail spec (1.6) that were just released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4324) Upgrade to MyFaces v1.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4324. Resolution: Fixed Fix Version/s: 2.0.4 update checked into trunk (rev. 739267) branches/2.1 (rev. 739268) and branches/2.0 (rev. 739269) Upgrade to MyFaces v1.2.6 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.0.4, 2.1.4, 2.2 Upgrade to MyFaces v1.2.6 released on January 26, 2009 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4324) Upgrade to MyFaces v1.2.4
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4324: -- Assignee: Joe Bohn Upgrade to MyFaces v1.2.4 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: Wish List Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4324) Upgrade to MyFaces v1.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667701#action_12667701 ] Joe Bohn commented on GERONIMO-4324: MyFaces 1.2.6 was released. Upgrade to MyFaces v1.2.6 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4324) Upgrade to MyFaces v1.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4324: --- Fix Version/s: (was: Wish List) 2.2 2.1.4 Summary: Upgrade to MyFaces v1.2.6 (was: Upgrade to MyFaces v1.2.4) Upgrade to MyFaces v1.2.6 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4324) Upgrade to MyFaces v1.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4324: --- Description: Upgrade to MyFaces v1.2.6 released on January 26, 2009 was: Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 Upgrade to MyFaces v1.2.6 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.1.4, 2.2 Upgrade to MyFaces v1.2.6 released on January 26, 2009 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4369) The new attribute values are overwrote while restarting the DB pool connector
[ https://issues.apache.org/jira/browse/GERONIMO-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4369: --- Assignee: Ivan (was: Joe Bohn) The new attribute values are overwrote while restarting the DB pool connector - Key: GERONIMO-4369 URL: https://issues.apache.org/jira/browse/GERONIMO-4369 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: Geronimo 2.2 snapshot JDK 1.5 Windows XP Reporter: Ivan Assignee: Ivan Fix For: 2.1.4, 2.2 Attachments: Geronimo-4369-11.13.patch, Geronimo-4369-11.17.patch, Geronimo-4369-11.19.patch After editing the values in the db pool, then restart it in the console, the new values lost. When saving the new attribute values, such as user name, the gbeandata in the configurationManager is not updated, so while restarting the connector, the gbinstance copies those old values from it. So the new persistent values do not take effect, Do I miss anything, thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4324) Upgrade to MyFaces v1.2.4
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12662055#action_12662055 ] Joe Bohn commented on GERONIMO-4324: FYI ... I've been talking with the MyFaces team and they are planning to create a new release that resolves the tck issue. I have not yet heard when it will be available. Upgrade to MyFaces v1.2.4 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Priority: Minor Fix For: Wish List Upgrade to MyFaces v1.2.4 released on August 30th. Release Notes - https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600styleName=Htmlversion=12313378 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4473) Validate the artifact fields when adding an archive to the repository
Validate the artifact fields when adding an archive to the repository - Key: GERONIMO-4473 URL: https://issues.apache.org/jira/browse/GERONIMO-4473 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to excluding ( ) , ; : \ / ' and .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4473) Validate the artifact fields when adding an archive to the repository
[ https://issues.apache.org/jira/browse/GERONIMO-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-4473: --- Description: Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to exclude ( ) , ; : \ / ' and .. (was: Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to excluding ( ) , ; : \ / ' and ..) Validate the artifact fields when adding an archive to the repository - Key: GERONIMO-4473 URL: https://issues.apache.org/jira/browse/GERONIMO-4473 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.3, 2.1.4, 2.2 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1.4, 2.2 Validate the group, artifact, version and type field when adding an archive to the repository to prevent illegal characters that don't make sense in an artifact id. At the moment I'm planning to exclude ( ) , ; : \ / ' and .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4467) null pointer acess in code.
[
https://issues.apache.org/jira/browse/GERONIMO-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn reassigned GERONIMO-4467:
--
Assignee: Joe Bohn
null pointer acess in code.
---
Key: GERONIMO-4467
URL: https://issues.apache.org/jira/browse/GERONIMO-4467
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
Fix For: 2.1.4, 2.2
Attachments: 4467_shawn.patch
null pointer acess in code.
{code}
if (file == null) {
throw new IOException(Entry not found: name= +
file.getAbsolutePath());
} else if (file.isDirectory()) {
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4467) null pointer acess in code.
[
https://issues.apache.org/jira/browse/GERONIMO-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-4467.
Resolution: Fixed
Comitted in trunk rev. 726699 and branches/2.1 rev. 726700 - Thanks for the
patch!
null pointer acess in code.
---
Key: GERONIMO-4467
URL: https://issues.apache.org/jira/browse/GERONIMO-4467
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Shawn Jiang
Assignee: Joe Bohn
Priority: Minor
Fix For: 2.1.4, 2.2
Attachments: 4467_shawn.patch
null pointer acess in code.
{code}
if (file == null) {
throw new IOException(Entry not found: name= +
file.getAbsolutePath());
} else if (file.isDirectory()) {
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4437) Upgrade to Jetty 6.1.11
[ https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reopened GERONIMO-4437: It seems using 6.1.11 caused a hang in one of our tests. I'll revert this change until I have chance to look into the issue. Upgrade to Jetty 6.1.11 --- Key: GERONIMO-4437 URL: https://issues.apache.org/jira/browse/GERONIMO-4437 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies, Jetty Affects Versions: 2.2 Reporter: Donald Woods Assignee: Joe Bohn Fix For: 2.2 Upgrade to newer Jetty release, 6.1.11. We looked into 6.1.14 but that causes some tck issues for us so we'll use 6.1.11 for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4437) Upgrade to Jetty 6.1.14
[ https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reopened GERONIMO-4437: Jetty 6.1.14 causes some problems - we're moving to 6.1.11 for now. Upgrade to Jetty 6.1.14 --- Key: GERONIMO-4437 URL: https://issues.apache.org/jira/browse/GERONIMO-4437 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies, Jetty Affects Versions: 2.2 Reporter: Donald Woods Assignee: Joe Bohn Fix For: 2.2 Jetty 6.1.14 was released on Nov 18. There are several classes in the Geronimo Jetty integration that will need to be updated, due to org.mortbay.component.LifeCycle needing to be implemented in anything that implements/extends a Handler derived class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4437) Upgrade to Jetty 6.1.14
[ https://issues.apache.org/jira/browse/GERONIMO-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-4437: -- Assignee: Joe Bohn (was: Donald Woods) Upgrade to Jetty 6.1.14 --- Key: GERONIMO-4437 URL: https://issues.apache.org/jira/browse/GERONIMO-4437 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies, Jetty Affects Versions: 2.2 Reporter: Donald Woods Assignee: Joe Bohn Fix For: 2.2 Jetty 6.1.14 was released on Nov 18. There are several classes in the Geronimo Jetty integration that will need to be updated, due to org.mortbay.component.LifeCycle needing to be implemented in anything that implements/extends a Handler derived class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
