[jira] Assigned: (GERONIMO-4823) role-based administration capabilities
[ https://issues.apache.org/jira/browse/GERONIMO-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4823: - Assignee: Shawn Jiang > role-based administration capabilities > -- > > Key: GERONIMO-4823 > URL: https://issues.apache.org/jira/browse/GERONIMO-4823 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.5, 2.2 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Attachments: monitor-role.patch > > > Provide role-based administration capabilities. > * Add a monitor group in geronimo-admin realm > * Only grant monitor group the permission to use the 4 portlets through > reconfiguring the filter rules > in console/console-portal-driver > 1, Monitoring portlet > 2, Information > 3, Java System Info > 4, Thread Pools > * Monitor group user can't create server/view/graph -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4823) role-based administration capabilities
[ https://issues.apache.org/jira/browse/GERONIMO-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vanessa Wang updated GERONIMO-4823: Attachment: monitor-role.patch > role-based administration capabilities > -- > > Key: GERONIMO-4823 > URL: https://issues.apache.org/jira/browse/GERONIMO-4823 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.5, 2.2 >Reporter: Shawn Jiang > Attachments: monitor-role.patch > > > Provide role-based administration capabilities. > * Add a monitor group in geronimo-admin realm > * Only grant monitor group the permission to use the 4 portlets through > reconfiguring the filter rules > in console/console-portal-driver > 1, Monitoring portlet > 2, Information > 3, Java System Info > 4, Thread Pools > * Monitor group user can't create server/view/graph -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] Release Blueprint 1.0.0 (4th try)
Hi, The vote has passed with the following +1s: Guillaume Nodet, Kevan Miller, Rick McGuire, Donald Woods, Joe Bohn, Jarek Gawor, Alan Cabrera. And no other votes. Thx to everyone ! I will promote the artifacts to the central Maven repository. On Fri, Sep 11, 2009 at 18:38, Guillaume Nodet wrote: > I've uploaded another 1.0.0 release of the blueprint project. > I think I've addressed all the issues raised in the discussion thread. > > The staging repository is available at: > https://repository.apache.org/content/repositories/geronimo-staging-005/ > > The corresponding tag is available at > http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ > > Please review and vote: > [ ] +1 Release > [ ] -1 Do not release > > The vote will remain open for 72 hours. > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > Open Source SOA > http://fusesource.com > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information
[ https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755874#action_12755874 ] viola.lu commented on GERONIMO-4855: Hi, i tried on tomcat also, its scenario and test results are same as geronimo, So pls close this jira.Agree?Thanks. > Clustering can not work when the application needs login information > > > Key: GERONIMO-4855 > URL: https://issues.apache.org/jira/browse/GERONIMO-4855 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 > Environment: windows sp2 > jdk1.6 >Reporter: liangkun > Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war > > > When I using WADI clustering and tomcat native clustering there are the same > problem: > If the application on the different node needs the security information to > access some page then firefox gives the following error information: > HTTP Status 404 - /demo/protect/j_security_check > type Status report > message /demo/protect/j_security_check > description The requested resource (/demo/protect/j_security_check) is not > available. > so it is likely clustering can not access any resource which need security > check. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4839) A non-existent EJB server also can run
[ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Du closed GERONIMO-4839. - The bug in openejb has been fixed, close it. > A non-existent EJB server also can run > -- > > Key: GERONIMO-4839 > URL: https://issues.apache.org/jira/browse/GERONIMO-4839 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.2 >Reporter: Siqi Du > Fix For: 2.2 > > Attachments: screenshot-1.jpg > > > 1, Add an existent ejb server, and it works > 2, Add an non-existent ejb server, and it also runs well. > I have investigated it and found that an issue(or a bug) of OpenEJB with the > help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response. > But for the end user, it is really a bug of Geronimo, I think it need to be > work around anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4839) A non-existent EJB server also can run
[ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Du resolved GERONIMO-4839. --- Resolution: Fixed > A non-existent EJB server also can run > -- > > Key: GERONIMO-4839 > URL: https://issues.apache.org/jira/browse/GERONIMO-4839 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.2 >Reporter: Siqi Du > Fix For: 2.2 > > Attachments: screenshot-1.jpg > > > 1, Add an existent ejb server, and it works > 2, Add an non-existent ejb server, and it also runs well. > I have investigated it and found that an issue(or a bug) of OpenEJB with the > help of Ivan. So I send a mail to OpenEJB maillist and haven't got a response. > But for the end user, it is really a bug of Geronimo, I think it need to be > work around anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-320) Provide facility to change id/pw associated with server instance (withing creating a new instance of the server)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-320. Resolution: Fixed Fix Version/s: 2.1.5 Although the function has been included in the admin console, I add an "manage account" button to the "security" section of "Overview" page. Note that, the button is only enabled in local host, doesn't work with a remote server. #815596 for trunk and #815595 for 2.1.5 branch > Provide facility to change id/pw associated with server instance (withing > creating a new instance of the server) > > > Key: GERONIMODEVTOOLS-320 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-320 > Project: Geronimo-Devtools > Issue Type: New Feature > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.5, 2.2.0 > > > There is no facility to change the account name or password associated with > the server instance created. Clicking on the properties for the server > instance displays a property sheet but with none of the properties used to > create it. It seems as if the the server adapter needs to add another page > to the properties dialog for changing account id or password. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4222: --- Attachment: PGtrial.patch Attaching a modified trial patch that hard code the fatal error codes. Even though this might fix the problem with Postgresql, it's far from the final solution. I realize that tranql does not take advantange of the PooledDatasource/PooledConnection implemenations that are available in most existing DBMS JDBC drivers. The PooledConnection can notify a listener when a fatal error occured and the connection should be discarded. I'd suggest that we improve tranql to use PooledDatasource, instead of relying on a customized ExceptionSorter that we have to write by ourselves for every DBMS. What do others think? > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, PGtrial.patch, > stacktrace.txt, tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4846) form based security for the web application does not work with Jetty WADI clustering.
[ https://issues.apache.org/jira/browse/GERONIMO-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4846: - Assignee: (was: Shawn Jiang) Don't have time to look into it for now. > form based security for the web application does not work with Jetty WADI > clustering. > - > > Key: GERONIMO-4846 > URL: https://issues.apache.org/jira/browse/GERONIMO-4846 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 >Reporter: Shawn Jiang > > This is a part of https://issues.apache.org/jira/browse/GERONIMO-4777, the > major issue has been resolved with the patch from Trygve Hardersen. > Opening this JIRA to track the remaining problems. > > However it does not work when combined with form based security for the web > application. The first problem is that > org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication > and org.eclipse.jetty.security.authentication.SessionCachingAuthenticator > are not serializable, so they can not be sent across the network. I made > these classes serializable, and then login works as long as there is only one > member in the cluster (well, not really a cluster...). When there are > multiple members in the cluster, login fails because there is no valid > constructor for > org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication. > I tried to add a default constructor, but it's an inner class, and it seems > to me like theAuthenticator and UserIdentity properties are required for it > to work so I did not try to extract the class. > As I said login works as long as there's only one member in the cluster, but > logout does not. Calling javax.servlet.http.HttpSession#invalidate() throws > an exception, because the curent session can not be found: > java.lang.AssertionError: Session > [org.apache.geronimo.clustering.wadi.wadisessionadap...@7f488ddb] is undefined > org.codehaus.wadi.replication.manager.ReplicationKeyNotFoundException: Key > [ccge2q2w9dz2] does not exist > I am attaching the patch for the WADIJettyClusteringBuilder > (WADIJettyClusteringBuilder.patch) and a sample project JGS (jgs.tar.gz) that > demonstrates the security problems I'm experiencing. The > web-formlogin-clustering-plugin of the JGS project uses form based security > and WADI clustering. The /customer page is protected, and to access it one > must login with any username and password, as long as they are the same. Use > test/test for instance. To test session invalidation, manually enter the URL > /logout. > It would be very helpful if someone can comment on the usability of WADI > clustering in combination with Jetty7. To me it seems like it has not been > tested much, and I think going back to Jetty6 again is the best option for > us, unless the issues described above can be easily solved. > Thanks for your help! > -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4851) Server will get into abnormal status when trying to edit/delete Tomcat Connector HTTPS BIO network listener
[ https://issues.apache.org/jira/browse/GERONIMO-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4851. - Closing it. > Server will get into abnormal status when trying to edit/delete Tomcat > Connector HTTPS BIO network listener > > > Key: GERONIMO-4851 > URL: https://issues.apache.org/jira/browse/GERONIMO-4851 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, Tomcat >Affects Versions: 2.2 > Environment: win server 2008, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang >Priority: Critical > Fix For: 2.2 > > > First of all, the default path of Tomcat Connector HTTPS BIO network listener > is /var/catalina. Thus, when trying to create a new HTTPS BIO > listener, the value of keystoreFile should be set to > ../security/keystores/geronimo-default. I suggest whether we could set the > default path into or other one, which will be more closer to > users' customs. > And this problem is somewhat related to the path setting. > Once you created a new HTTPS BIO listener, and set its keystoreFile as > var/security/keystores/geronimo-default (or someone else which doesn't > contain ".."). btw, under such circumstances, you won't be able to connect to > the port cause the path is wrong. And then, edit the newly added listener, > set keystoreFile to the correct value, i.e. > ../security/keystores/geronimo-default (you see, this time there exists ".." > in the setting). Click save, and you will find the server will seem to in > process for a long time. During this, you won't be able to stop the server > with normal procedure, i.e. shutdown or stop-server. And even you stop it > with closing the command line directly, you won't be able to start it again. > Under this circumstance, all you can do is to access a brand new server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4777) WADI clustering does not work with Jetty7
[ https://issues.apache.org/jira/browse/GERONIMO-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4777. - Closing it. > WADI clustering does not work with Jetty7 > - > > Key: GERONIMO-4777 > URL: https://issues.apache.org/jira/browse/GERONIMO-4777 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Jetty >Affects Versions: 2.2 > Environment: Tested on OS X 10.5 and Ubuntu 8.10, both running 64-bit > Java 1.6 >Reporter: Trygve Hardersen >Assignee: Shawn Jiang > Attachments: jgs.tar.gz, WADIJettyClusteringBuilder.patch > > > I've been trying to get WADI clustering to work with Jetty7, but I've found > numerous issues: > The first problem is that a Geronimo plugin that uses WADI clustering and > Jetty7 cannot be built. The WADIJettyClusteringBuilder is unable to locate > the web module in the deployment, so the build fails with the following error: > org.apache.maven.lifecycle.LifecycleExecutionException: could not package > plugin > Caused by: org.apache.maven.plugin.MojoExecutionException: could not package > plugin > Caused by: org.apache.geronimo.common.DeploymentException: Could not locate > web module gbean in web app configuration > I was able to resolve this by copying the code that creates the > webModuleQuery from the equivalent Jetty6 module into the Jetty7 module, see > WADIJettyClusteringBuilder.patch. With this the build succeeds, and I'm able > to deploy the plugin. I don't know if it breaks anything else, but I've not > seen issues with it. > AFAICT normal session replication works fine with this. However it does not > work when combined with form based security for the web application. The > first problem is that > org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication > and org.eclipse.jetty.security.authentication.SessionCachingAuthenticator > are not serializable, so they can not be sent across the network. I made > these classes serializable, and then login works as long as there is only one > member in the cluster (well, not really a cluster...). When there are > multiple members in the cluster, login fails because there is no valid > constructor for > org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication. > I tried to add a default constructor, but it's an inner class, and it seems > to me like theAuthenticator and UserIdentity properties are required for it > to work so I did not try to extract the class. > As I said login works as long as there's only one member in the cluster, but > logout does not. Calling javax.servlet.http.HttpSession#invalidate() throws > an exception, because the curent session can not be found: > java.lang.AssertionError: Session > [org.apache.geronimo.clustering.wadi.wadisessionadap...@7f488ddb] is undefined > org.codehaus.wadi.replication.manager.ReplicationKeyNotFoundException: Key > [ccge2q2w9dz2] does not exist > I am attaching the patch for the WADIJettyClusteringBuilder > (WADIJettyClusteringBuilder.patch) and a sample project JGS (jgs.tar.gz) that > demonstrates the security problems I'm experiencing. The > web-formlogin-clustering-plugin of the JGS project uses form based security > and WADI clustering. The /customer page is protected, and to access it one > must login with any username and password, as long as they are the same. Use > test/test for instance. To test session invalidation, manually enter the URL > /logout. > It would be very helpful if someone can comment on the usability of WADI > clustering in combination with Jetty7. To me it seems like it has not been > tested much, and I think going back to Jetty6 again is the best option for > us, unless the issues described above can be easily solved. > Thanks for your help! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4712) Some INFO log is not very good/useful.
[ https://issues.apache.org/jira/browse/GERONIMO-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4712. - Closing it. > Some INFO log is not very good/useful. > -- > > Key: GERONIMO-4712 > URL: https://issues.apache.org/jira/browse/GERONIMO-4712 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Logging >Affects Versions: 2.1.4, 2.1.5, 2.2 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Fix For: 2.1.5, 2.2 > > Attachments: G4712_trunk.patch > > > I believe there are some log that needs to be filtered out from current > server log because they are not good/useful information as part of default > INFO in log. All these kind of log messages could do is to bury the useful > info or to mislead the new users. > Some sample of them are: > 2009-06-12 16:53:55,171 INFO [PortletContextManager] Registering 24 portlets > for context /console-base > 2009-06-12 16:53:55,203 INFO [PortletContextManager] Portlet application > with application id '/console-base' already registered. > 2009-06-12 16:53:55,203 INFO [PortletContextManager] Registering 24 portlets > for context /console-base > 2009-06-12 16:53:55,234 INFO [PortletContextManager] Portlet application > with application id '/console-base' already registered. > 2009-06-12 16:53:55,234 INFO [PortletContextManager] Registering 24 portlets > for context /console-base > 2009-06-12 16:53:55,265 INFO [PortletContextManager] Portlet application > with application id '/console-base' already registered. > . > 2009-06-23 13:22:36,484 INFO [XSRFHandler] Created session for uid=null with > sessionId=2486E123C24B5E399859E9F5BAFD95BD, uniqueId=-7432393335768912086 > 2009-06-23 13:22:36,546 INFO [XSRFHandler] Updated HTML content with XSRF > JavaScript for requestURI=/ > Maybe we could just redirect them to another log file or just change these > kind of message to DEBUG from current INFO. Anyway, we must make sure the > default log be concise and only contain important info that users want to > know. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4742) Connector portlets for Tomcat does not work
[ https://issues.apache.org/jira/browse/GERONIMO-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4742. - Closing it. > Connector portlets for Tomcat does not work > --- > > Key: GERONIMO-4742 > URL: https://issues.apache.org/jira/browse/GERONIMO-4742 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Shawn Jiang > Fix For: 2.2 > > Attachments: G4742_B22.patch > > > After refactoriing Tomcat integratoin codes, currently, the connector > portlet does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4798) can't start server because of an error of Http11AprProtocol
[ https://issues.apache.org/jira/browse/GERONIMO-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4798. - Closing it. > can't start server because of an error of Http11AprProtocol > -- > > Key: GERONIMO-4798 > URL: https://issues.apache.org/jira/browse/GERONIMO-4798 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: windows xp sp3 > jdk6 >Reporter: Bin He >Assignee: Shawn Jiang > Fix For: 2.2, 3.0 > > Attachments: apr.7z > > > 1、move three attached files ：openssl.exe、tcnative.dll、tcnative_ipv4.dll into > C:\WINDOWS\system32 > 2、click "gsh.bat" in /bin > 3、input geronimo/start-server but the server can't start and it says : > 2009-08-18 13:42:21,859 INFO [Http11AprProtocol] Initializing Coyote > HTTP/1.1 on http-8080 > 2009-08-18 13:42:21,859 ERROR [Http11AprProtocol] Error initializing endpoint > java.lang.Exception: Invalid Server SSL Protocol > at org.apache.tomcat.jni.SSLContext.make(Native Method) > at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:693) > at > org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107) > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1058) > at > org.apache.catalina.core.StandardService.initialize(StandardService.java:677) > at > org.apache.catalina.core.StandardService.init(StandardService.java:689) > at > org.apache.catalina.core.StandardService.start(StandardService.java:503) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:710) > at > org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:135) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) > 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 > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) > at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:599) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2c2ce3ed.startConfiguration() > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78) > at > org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30) > 2009-08-18 13:42:21,875 ERROR [StandardService] Service initializing at > Catalina failed > LifecycleException: Protocol handler initialization failed: > java.lang.Exception: Invalid Server SSL Protocol > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1060) > at > org.apache.catalina.core.StandardService.initialize(StandardService.java:677) > at > org.apache.catalina.core.StandardService.init(StandardService.java:689) > at > org.apache.catalina.core.StandardService.start(StandardService.java:503) > at > org.apache.catalina.core.StandardSe
[jira] Resolved: (GERONIMO-4851) Server will get into abnormal status when trying to edit/delete Tomcat Connector HTTPS BIO network listener
[ https://issues.apache.org/jira/browse/GERONIMO-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4851. --- Resolution: Fixed This should have been fixed in another JIRA. > Server will get into abnormal status when trying to edit/delete Tomcat > Connector HTTPS BIO network listener > > > Key: GERONIMO-4851 > URL: https://issues.apache.org/jira/browse/GERONIMO-4851 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, Tomcat >Affects Versions: 2.2 > Environment: win server 2008, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang >Priority: Critical > Fix For: 2.2 > > > First of all, the default path of Tomcat Connector HTTPS BIO network listener > is /var/catalina. Thus, when trying to create a new HTTPS BIO > listener, the value of keystoreFile should be set to > ../security/keystores/geronimo-default. I suggest whether we could set the > default path into or other one, which will be more closer to > users' customs. > And this problem is somewhat related to the path setting. > Once you created a new HTTPS BIO listener, and set its keystoreFile as > var/security/keystores/geronimo-default (or someone else which doesn't > contain ".."). btw, under such circumstances, you won't be able to connect to > the port cause the path is wrong. And then, edit the newly added listener, > set keystoreFile to the correct value, i.e. > ../security/keystores/geronimo-default (you see, this time there exists ".." > in the setting). Click save, and you will find the server will seem to in > process for a long time. During this, you won't be able to stop the server > with normal procedure, i.e. shutdown or stop-server. And even you stop it > with closing the command line directly, you won't be able to start it again. > Under this circumstance, all you can do is to access a brand new server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4859) Default JMX monitoring MBeans list should include JVM MBean.
[
https://issues.apache.org/jira/browse/GERONIMO-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang closed GERONIMO-4859.
-
Closing it.
> Default JMX monitoring MBeans list should include JVM MBean.
>
>
> Key: GERONIMO-4859
> URL: https://issues.apache.org/jira/browse/GERONIMO-4859
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
> Fix For: 2.1.5, 2.2, 3.0
>
>
> Currently, the default EJB monitoring server MBean list is:
> {code}
>
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4
> /car,j2eeType=GBean,name=TomcatAJPConnector
>
> geronimo:J2EEServer=geronimo,j2eeType=JVM,name=JVM
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4/car,j2eeType=GBean,name=TomcatWebSSLConnector
>
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4/car,j2eeType=GBean,name=TomcatWebConnector
>
> {code}
> While the default list of JMX monitoring server is:
> {code}
>
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4
> /car,j2eeType=GBean,name=TomcatAJPConnector
>
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4/car,j2eeType=GBean,name=TomcatWebSSLConnector
>
>
> geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.4/car,j2eeType=GBean,name=TomcatWebConnector
>
> {code}
> This causes the user can't monitor JVM status with JMX monitor server. We
> should add
> geronimo:J2EEServer=geronimo,j2eeType=JVM,name=JVM
> to the JMX MBean list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4856) Some abnormal conditions with Tomcat NIO HTTPS Connector
[ https://issues.apache.org/jira/browse/GERONIMO-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4856. - Closing it. > Some abnormal conditions with Tomcat NIO HTTPS Connector > > > Key: GERONIMO-4856 > URL: https://issues.apache.org/jira/browse/GERONIMO-4856 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: win server 2008, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang > Fix For: 2.2 > > > These conditions happen when creating a new Tomcat NIO HTTPS Connector and > trying to access it. > First of all, the basic path of "keystoreFile" will change during > configuring. At the first time, it's set to \var\catalina. > Once your input can't help server to find configured file, and you try to > edit the connector. You will find this time, its basic path is > instead of the previous one. > After set corresponding parameters, for instance, set UniqueName, > keystoreFile, port and keystorePass, then save the settings and try to access > it via https://localhost:/console. You will find the following error > recorded in geronimo.log. > ERROR [NioEndpoint] java.lang.NullPointerException > at > org.apache.tomcat.util.net.NioEndpoint.isWorkerAvailable(NioEndpoint.java:) > at > org.apache.tomcat.util.net.NioEndpoint$Poller.processKey(NioEndpoint.java:1639) > at > org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:1580) > at java.lang.Thread.run(Thread.java:735) > And under some circumstances, this error will be shown in command line > circularly and constantly at a high speed that geronimo.log will be full > within several seconds. However, the latter kind of condition is not stable > reproduced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4853) Can't define tomcat connector with GBean.
[ https://issues.apache.org/jira/browse/GERONIMO-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4853. - Closing it. > Can't define tomcat connector with GBean. > - > > Key: GERONIMO-4853 > URL: https://issues.apache.org/jira/browse/GERONIMO-4853 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > > Can't define tomcat connector with GBean. Because persistent annotation are > missed in getXXX of connector GBeans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4858) Geronimo 2.2 doesn't add correct connector attributes to server.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4858. - Closing it. > Geronimo 2.2 doesn't add correct connector attributes to server.xml > --- > > Key: GERONIMO-4858 > URL: https://issues.apache.org/jira/browse/GERONIMO-4858 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector, console >Affects Versions: 2.2, 3.0 >Reporter: Quintin Beukes >Assignee: Shawn Jiang >Priority: Critical > Fix For: 2.2 > > Attachments: tomcat.patch > > > OK. So I extract the 2009-09-08 nightly snapshot (tomcat binary), and deploy > some repository JARs, a datasource and a security realm. Then I goto Web > Server portlet and create a new Tomcat BIO connector. I enter a name, and for > port I enter 80. This is a rough of the steps I took from a clean install. > So the bug is that when you add a connector, it immediately starts it on the > correct port (as can be seen with netstat), but it saves to > var/catalina/server.xml with port 8080. So once you restart the server you > receive a port conflict if you have another 8080, and if you don't it would > be like you never made the change, with your connector reverting to 8080. > Here is a snippet of what it saves after adding a port "801" BIO connector: > name="testConnector1" port="8080" protocol="HTTP/1.1" redirectPort="8443" > server=""/> > Q -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.
[ https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4850. - Resolution: Invalid I believe this is working as design. See comments in : http://www.nabble.com/Some-features-of-WADI-cluster-in-G22-td25287296s134.html#a25288801 > WADI clustering: the application no node B will not start up when start up > the node B. > --- > > Key: GERONIMO-4850 > URL: https://issues.apache.org/jira/browse/GERONIMO-4850 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 > Environment: windows sp2 > jdk1.6 >Reporter: liangkun >Assignee: Shawn Jiang > > 1.I configuration two nodes A and B following the WADI clustering and deploy > the cviewer.war on the node A the no the node B there is cviewer.war also and > they work well on 2 nodes. > 2.shutdown A node first and then shutdown B node, I find that the cviewer.war > load is set false in the config.xml of node B. > 3 .start A and B, the cviewer.war on the node B can not start automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Those jar files in each created jms resource adapter
Thanks, David ! Not sure if 2nd geronimo-activemq-ra is added, whether it would make the user feel confusion. 2009/9/15 David Jencks > > On Sep 15, 2009, at 7:57 AM, Ivan wrote: > > Hi, >>Currently, I found many ActiveMQ related jar files are included in each >> jms resource folder. Since the activemq-broker is the parent classloader of >> the each created resource adapter, I thought we should not have those files >> there. If they could be removed, the size of the whole binary files will >> reduce 6-7 M. >>Any comment or I miss anything ? Thanks ! >> > > If we want to do this we should set up a 2nd, empty, anq rar. Right now > the intent is that it should be possible to deploy the rar on a server that > doesn't have the amq broker installed. > > It would definitely be a good idea to review what is included and make sure > everything is necessary and that it is in fact possible to run an adapter > instance without the broker parent. > > thanks > david jencks > > -- >> Ivan >> > > -- Ivan
[jira] Resolved: (GERONIMO-4647) welcome files with servlet mappings
[ https://issues.apache.org/jira/browse/GERONIMO-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4647. Resolution: Fixed David has ported the fix to our private build in r814083. So change to "fixed" -Rex > welcome files with servlet mappings > --- > > Key: GERONIMO-4647 > URL: https://issues.apache.org/jira/browse/GERONIMO-4647 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: web >Affects Versions: 2.1.4 > Environment: JRE 1.5.0_06, Windows XP >Reporter: Bobby Lawrence >Assignee: Rex Wang > Fix For: 2.2 > > Attachments: GERONIMO-4647.patch, sampleapp.war, sampleapp.war > > > When you specify welcome files in web.xml Geronimo throws 404 errors if the > welcome file isn't a valid file resource. > Values that are URL mappings to a servlet are ignored by the app server even > through they are valid. > This means that I can't have a welcome file of "/index.jsf" or "/index.do" or > "/someservlet". > The only welcome files that Geronimo seems to not throw a 404 Not Found error > are actual files found in the web application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4790) Migrate debug-views code to base on the up-to-date dojo
[ https://issues.apache.org/jira/browse/GERONIMO-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4790. Resolution: Fixed Fix Version/s: 3.0 > Migrate debug-views code to base on the up-to-date dojo > --- > > Key: GERONIMO-4790 > URL: https://issues.apache.org/jira/browse/GERONIMO-4790 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 2.2, 3.0 > > Attachments: classloader-viewer.jpg, dependency-viewer.jpg, > jmx-viewer.jpg, JNDI-viewer.jpg, ldap-viewer.jpg > > > ref http://www.nabble.com/Re%3A-Which-dojo--p24293149s134.html > Currently, our console depends on two different versions of dojo library. One > is 1.3.0, which is used by EJB portlet and just updated from 1.2.1 > (GERONIMO-4723) and fixed a bug(GERONIMO-4746). I hope we can go on updating > it to the latest version 1.3.2. > The other one is 0.4.3, the legacy lib, which has not been supported by dojo > team, but used by our debug-view portlets, I prefer to update it to the > latest lib, and the advantage are as follows: > 1. keep consistent in the portlet page style with the EJB portlet > 2. reduce a bit to the geronimo footprint size > 3. Although we have ported the dojo-legacy to build the source in > external(GERONIMO-4750), with this update, we don't need that as well. > 4. will be more easy to maintainance the program logic by using the unified > dojo lib. > 5. the doc of 1.3.x is good and easy to find. > There are also some risks: > 1. There has been so much changes between the dojo versions that the effort > might be 1-2 week to complete. > 2. I did not find any documents for the old dojo lib, so it might be easier > to re-write the whole pages to base on 1.3.x and dwr 3.0.x(we have upgrade > the dwr successfully in GERONIMO-4753), but I not sure. > Any thoughts? > -Rex -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] xbean 3.6 3rd try
+1 given the updated checksums. --kevan On Sep 14, 2009, at 4:20 PM, Kevan Miller wrote: Looks good, except the md5/sha1 checksum errors. I'm -1 until they're fixed. --kevan On Sep 11, 2009, at 7:07 PM, David Jencks wrote: I've prepared a 3rd release candidate for xbean 3.6: https://repository.apache.org/content/repositories/geronimo-staging-007/ Site staged at: http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/ It looks like we fixed 13 issues for 3.6: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981 Please vote: [ ] +1 release this [ ] 0 dunno [ ] -1 Don't release this Vote will remain open 72 hours. Many thanks david jencks
[BUILD] trunk: Failed for Revision: 815581
Geronimo Revision: 815581 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test-reports [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@20142014 [INFO] [surefire:test] [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@20142014 [WARNING] Component returned which is not the same manager. Ignored
[VOTE] release geronimo's forked mavenized tomcat 6.0.20.0
For various reasons we are now using a forked copy of tomcat derived from the tomcat 6.0.20 release, built with maven, with maven dependencies, etc etc. The code changes from tomcat 6.0.20 are: r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line GERONIMO-4566 port fix for tomcats https://issues.apache.org/bugzilla/show_bug.cgi?id=47378 r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1 line GERONIMO-3451 "Restricted listeners property file not found" error logged during Tomcat server startup (Patch from Shawn Jiang) r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Some customizations of Tomcat properties. Server info is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the future. r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in MapperListener.registerHost(). I would expect that this fix would be in 6.0.22. So prolly won't require merging in the future r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This includes revision numbers 784303 and 784304. Does not include 787519, which should already be in 6.0.20 r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line fill-in ServerInfo properties - but I can't add that to archetype as ant task will fail Staging repo: https://repository.apache.org/content/repositories/geronimo-staging-023/ I forgot to include site generation stuff in the root pom before rolling the release. I generated a site by applying rev 815573 to the checkout used for the release build. The results are here: http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/ The structure is a little weird but I don't really want to spend time fixing it up. [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks david jencks
[RESULT] [VOTE] geronimo-jacc_1.1_spec version 1.0.2
vote passes with 5 +1 (dwoods, rmcguire, jgawor, kmiller, djencks) 1 -0 (gnodet) I'll promote the staging repo and move the site over. Meanwhile I've also fixed the license file in svn problem kevan noticed. thanks david jencks On Sep 10, 2009, at 5:16 PM, David Jencks wrote: I've built a release candidate for the jacc spec jar: https://repository.apache.org/content/repositories/geronimo-staging-002/ Site is staged here: http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/ Along with a bunch of build improvements this includes these fixes: GERONIMO-4357 don't double escape pre-escaped colons in web permissions GERONIMO-4587 fix EJBMethodPermission construction problem when a method param is an array, patch (slightly modified) from Shawn Jiang r788107 ensure HTTPMethodSpec.getActions() returns right information - otherwise reserialized permission objects could loose some vital information. Also, add serialVersionUID constants GERONIMO-4721 represent 'all http methods' with '' rather than '\!' when computing the actions string in web permissions GERONIMO-4735 serialize EJBMethodPermissionCollection contents only once GERONIMO-4734 fix web permissions HTTPMethodSpec equals method GERONIMO-4766, sort of. Use generics and make policy context handler registration slightly more thread safe. [ ] +1 release it [ ] 0 dunno [ ] -1 Don't release it Vote open for 72 hours thanks david jencks
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755804#action_12755804 ] David Jencks commented on GERONIMO-4222: Could you show the code you are using? I'm not entirely sure I think that a property file is easier to update than java code. You still have to repack everything and make sure you have it the right place and the right copy it seems to me that rebuilding the project might be easier and it is certainly much more friendly to tracking what code you are using. So, without more discussion I'd be much more in favor of not having a configurable exception sorter but just getting it right for postgres. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt, > tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] release jaspic implementation component 1.0
Vote passes with 5 +1 (dwoods, rmcguire, jgawor, djencks, kmiller) and no other votes I'll promote the staging repo and move the site. many thanks david jencks On Sep 10, 2009, at 7:08 PM, David Jencks wrote: It's time for the first release of our jaspic implementation for inclusion in g. 2.2. Release artifacts staged here: https://repository.apache.org/content/repositories/geronimo-staging-003/ Site staged here: http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/ When used in geronimo with tomcat or jetty, this passed the jaspic tck web profile. So far we don't try to implement the soap profile in geornimo; this implementation should support both. [ ] +1 release this [ ] 0 dunno [ ] -1 don't release this. Vote open for 72 hours. thanks david jencks
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
+1 On Sep 11, 2009, at 9:38 AM, Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding tag is available at http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ Please review and vote: [ ] +1 Release [ ] -1 Do not release The vote will remain open for 72 hours. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2
+1 Thanks for doing this. -Donald David Jencks wrote: After some discussion with the openjpa folks it seems like its a good idea to re-release our jpa 1 spec with an aritfactId of geronimo-jpa_1.0_spec rather than the original 3.0 version number. We don't really have a plan for what to do when jpa actually gets a 3.0 spec, but we don't have to deal with that for a bit. This is the same as the previous geronimo-jpa_3.0_spec but with updated build, license files, release profile, and of course artifactId. As an osgi bundle it imports what it exports. Staged here: https://repository.apache.org/content/repositories/geronimo-staging-021/ site staged here: http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/ [ ] +1 yes [ ] 0 dunno [ ] -1 no Vote open 72 hours many thanks david jencks
[BUILD] branches/2.2: Failed for Revision: 815424
Geronimo Revision: 815424 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 46 minutes 5 seconds
[INFO] Finished at: Tue Sep 15 14:51:10 EDT 2009
[INFO] Final Memory: 328M/969M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/logs-1400-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/logs-1400-jetty/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:56.956
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:21.488)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:39.347)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:45.817)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:25.183)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:32.503)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:24.180) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:17.149)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:57.596)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:14.447)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:51.710)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:38.334)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.630)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:40.139)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:56.181)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:25.706)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:52.045)
[INFO] enterprise-testsuite/sec-client-tests RUNNING
[INFO] enterprise-testsuite/sec-client-tests SUCCESS (0:00:36.638)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:59.688)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:58.964)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:38.117)
[INFO] web-testsuite/test-2.5-servlets
[VOTE] release geronimo-jpa_1.0_spec 1.1.2
After some discussion with the openjpa folks it seems like its a good idea to re-release our jpa 1 spec with an aritfactId of geronimo- jpa_1.0_spec rather than the original 3.0 version number. We don't really have a plan for what to do when jpa actually gets a 3.0 spec, but we don't have to deal with that for a bit. This is the same as the previous geronimo-jpa_3.0_spec but with updated build, license files, release profile, and of course artifactId. As an osgi bundle it imports what it exports. Staged here: https://repository.apache.org/content/repositories/geronimo-staging-021/ site staged here: http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jpa_1.0_spec/1.1.2/ [ ] +1 yes [ ] 0 dunno [ ] -1 no Vote open 72 hours many thanks david jencks
[BUILD] trunk: Failed for Revision: 815450
Geronimo Revision: 815450 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test-reports [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] skip non existing resourceDirectory /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/filtered-resources [INFO] Copying 3 resources [INFO] [compiler:compile] [INFO] Compiling 117 source files to /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/classes [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[101,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[102,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatEJBWebServiceContext.java:[244,20] [deprecation] setStatus(int,java.lang.String) in org.apache.catalina.connector.Response has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatServerGBean.java:[103,20] [deprecation] setServer(javax.management.MBeanServer) in org.apache.tomcat.util.modeler.Registry has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/HostGBean.java:[171,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/EngineGBean.java:[137,24] [deprecation] setServer(javax.management.MBeanServer) in org.apache.tomcat.util.modeler.Registry has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/ManagerGBean.java:[93,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [INFO] [resources:testResources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] skip non existing resourceDirectory /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources [INFO] Copying 3 resources [INFO] [compiler:testCompile] [INFO] Compiling 9 source files to /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/test-classes [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/AbstractWebModuleTest.java:[110,107] [deprecation] toURL() in java.io.File has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/ApplicationTest.java:[34,88] [deprecation] toURL() in java.io.File has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/StatTest.java:[39,79] [deprecation] toURL() in java.io.File has been deprecated [INFO] [surefire:test] [INFO] Surefire report directory: /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/surefire-reports --- T E S T S --- Running org.apache.geronimo.tomcat.ContainerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.626 sec Running org.apache.geronimo.tomcat.BasicTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.229 sec Running org.apache.geronimo.tomcat.TomcatServerGBeanTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.989 sec <<< FAILURE! Running org.apache.geronimo.tomcat.ApplicationTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.72 sec Running org.apache.geronimo.tomcat.JAASSecurityTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.906 sec Running org.apache.geronimo.tomcat.StatTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.647 sec Running org.apache.geronimo.tomcat.JACCSecurityTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.787 sec Results : Tests in error: Tests run: 8, Failures: 0, Errors: 2, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
+1 Jarek On Fri, Sep 11, 2009 at 12:38 PM, Guillaume Nodet wrote: > I've uploaded another 1.0.0 release of the blueprint project. > I think I've addressed all the issues raised in the discussion thread. > > The staging repository is available at: > https://repository.apache.org/content/repositories/geronimo-staging-005/ > > The corresponding tag is available at > http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ > > Please review and vote: > [ ] +1 Release > [ ] -1 Do not release > > The vote will remain open for 72 hours. > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > Open Source SOA > http://fusesource.com >
Re: Those jar files in each created jms resource adapter
On Sep 15, 2009, at 7:57 AM, Ivan wrote: Hi, Currently, I found many ActiveMQ related jar files are included in each jms resource folder. Since the activemq-broker is the parent classloader of the each created resource adapter, I thought we should not have those files there. If they could be removed, the size of the whole binary files will reduce 6-7 M. Any comment or I miss anything ? Thanks ! If we want to do this we should set up a 2nd, empty, anq rar. Right now the intent is that it should be possible to deploy the rar on a server that doesn't have the amq broker installed. It would definitely be a good idea to review what is included and make sure everything is necessary and that it is in fact possible to run an adapter instance without the broker parent. thanks david jencks -- Ivan
Those jar files in each created jms resource adapter
Hi, Currently, I found many ActiveMQ related jar files are included in each jms resource folder. Since the activemq-broker is the parent classloader of the each created resource adapter, I thought we should not have those files there. If they could be removed, the size of the whole binary files will reduce 6-7 M. Any comment or I miss anything ? Thanks ! -- Ivan
[jira] Reopened: (GERONIMO-4683) Transaction.commit method signature isn't entirely correctly
[ https://issues.apache.org/jira/browse/GERONIMO-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reopened GERONIMO-4683: --- I just realized that the SecurityException is also unchecked exception. So we are listing one but not the other. Seems we should be consistent here. > Transaction.commit method signature isn't entirely correctly > > > Key: GERONIMO-4683 > URL: https://issues.apache.org/jira/browse/GERONIMO-4683 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 2.1.4 >Reporter: Lin Sun >Assignee: Lin Sun > > I found out the Transaction.commit method signature isn't entirely correct. > Per JTA 1.1 for the Transaction interface: > commit > public void commit() throws RollbackException, > HeuristicMixedException, HeuristicRollbackException, > IllegalStateException, SecurityException, SystemException > geronimo-jta_1.1_spec has: > void commit() throws HeuristicMixedException, HeuristicRollbackException, > RollbackException, SecurityException, SystemException; > which is missing the IllegalStateException. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 815286
Geronimo Revision: 815286 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/build-0800.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 45 minutes 34 seconds
[INFO] Finished at: Tue Sep 15 08:51:28 EDT 2009
[INFO] Final Memory: 331M/969M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/logs-0800-tomcat/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.699
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:22.996)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:39.259)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:47.695)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:24.032)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:42.525)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:38.632) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:07.439)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:59.897)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:59.985)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:53.860)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:38.336)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:37.605)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:42.122)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:37.258)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:22.386)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:58.124)
[INFO] enterprise-testsuite/sec-client-tests RUNNING
[INFO] enterprise-testsuite/sec-client-tests SUCCESS (0:00:35.160)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:59.875)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:58.236)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.742)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:34.851)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test
[jira] Closed: (GERONIMO-4683) Transaction.commit method signature isn't entirely correctly
[ https://issues.apache.org/jira/browse/GERONIMO-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-4683. - Resolution: Invalid Assignee: Lin Sun > Transaction.commit method signature isn't entirely correctly > > > Key: GERONIMO-4683 > URL: https://issues.apache.org/jira/browse/GERONIMO-4683 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 2.1.4 >Reporter: Lin Sun >Assignee: Lin Sun > > I found out the Transaction.commit method signature isn't entirely correct. > Per JTA 1.1 for the Transaction interface: > commit > public void commit() throws RollbackException, > HeuristicMixedException, HeuristicRollbackException, > IllegalStateException, SecurityException, SystemException > geronimo-jta_1.1_spec has: > void commit() throws HeuristicMixedException, HeuristicRollbackException, > RollbackException, SecurityException, SystemException; > which is missing the IllegalStateException. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
Actually, I think this is the file where you need to add your key - http://www.apache.org/dist/geronimo/KEYS Reference this old post/question which didn't generate much interest at the time for details: http://www.nabble.com/public-keys-for-releases-tt17538242s134.html#a17538242 Also, you need to build up a web of trust for your key if you haven't already done so (infra will let you know if you don't). You can do this by having others retrieve and sign your key. I think infra recommends having at least 3 others sign your key to verify your identity. Joe Guillaume Nodet wrote: Added. On Mon, Sep 14, 2009 at 20:37, Kevan Miller wrote: Guillaume, Your PGP key is missing from the Geronimo KEYS file -- https://svn.apache.org/repos/asf/geronimo/KEYS --kevan On Sep 11, 2009, at 12:38 PM, Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding tag is available at http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ Please review and vote: [ ] +1 Release [ ] -1 Do not release The vote will remain open for 72 hours. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
[jira] Resolved: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector
[ https://issues.apache.org/jira/browse/GERONIMO-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4877. --- Resolution: Fixed Fixed in 22 branch and trunk. > Modification to keystoreFile doesn't work for HTTPS connector > - > > Key: GERONIMO-4877 > URL: https://issues.apache.org/jira/browse/GERONIMO-4877 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: win server 2008, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang > > Once I tried to edit a created HTTPS connector, either BIO or NIO, I found > that the modification to value of keystoreFile didn't work. After I saved my > modification and re-click on "edit" to check my setting, its value still > remained as the one I input at the first time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
+1 Joe Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding tag is available at http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ Please review and vote: [ ] +1 Release [ ] -1 Do not release The vote will remain open for 72 hours.
[jira] Commented: (GERONIMO-4878) Geronimo doesnt protect access to its Derby databases
[ https://issues.apache.org/jira/browse/GERONIMO-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755485#action_12755485 ] Donald Woods commented on GERONIMO-4878: Duplicate of https://issues.apache.org/jira/browse/GERONIMO-4296 > Geronimo doesnt protect access to its Derby databases > - > > Key: GERONIMO-4878 > URL: https://issues.apache.org/jira/browse/GERONIMO-4878 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.1.4 >Reporter: Radim Kolar > > run ij tool which comes with eclipse derby plugin and connect to geronimo. > ij> connect 'jdbc:derby://localhost/SystemDatabase'; > ij> show tables; > TABLE_SCHEM |TABLE_NAME|REMARKS > > SYS |SYSALIASES| > SYS |SYSCHECKS | > SYS |SYSCOLPERMS | > SYS |SYSCOLUMNS| > SYS |SYSCONGLOMERATES | > SYS |SYSCONSTRAINTS| > SYS |SYSDEPENDS| > SYS |SYSFILES | > SYS |SYSFOREIGNKEYS| > SYS |SYSKEYS | > SYS |SYSROUTINEPERMS | > SYS |SYSSCHEMAS| > SYS |SYSSTATEMENTS | > SYS |SYSSTATISTICS | > SYS |SYSTABLEPERMS | > SYS |SYSTABLES | > SYS |SYSTRIGGERS | > SYS |SYSVIEWS | > SYSIBM |SYSDUMMY1 | > APP |ACTIVEMQ_ACKS | > APP |ACTIVEMQ_LOCK | > APP |ACTIVEMQ_MSGS | > APP |TIMERTASKS| > 23 rows selected > ij> > no security restrictions are in place. Same for activemq message broker. > Network listeners should be password protected. > It would be great to have ability in administration console where we can > assign security realm protection to particular derby database(s) or queues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [FYI]Summary list for G2.2 doc updates
Hi all, FYI. 2 more topics updated for G2.2 doc. 1. Replacing the default realm in G2.2 http://cwiki.apache.org/GMOxDOC22/replacing-default-realm-in-geronimo.html 2. Tomcat native clustering--Enable session affinity on how-to http://cwiki.apache.org/GMOxDOC22/tomcat-native-clustering.html#TomcatNativeClustering-Enablingsessionaffinity Any comments, please post here. Thanks. Jeff C On Wed, Sep 2, 2009 at 2:35 PM, chi runhua wrote: > Hi, FYI. > > 2 more topics added based on discussion from mail-list: > > 1. JSP&Servlet reload setting for Tomcat in Geronimo > 2. OpenEJB options in Geronimo > > Both topics are placed within troubleshooting development issues. > > http://cwiki.apache.org/GMOxDOC22/development-issues.html > > Jeff C > > > On Mon, Aug 31, 2009 at 12:05 PM, chi runhua wrote: > >> Sorry for the inconvenience. >> >> I've fixed broken linkages within the page. >> >> Jeff C >> >> >> >> >> On Mon, Aug 31, 2009 at 10:07 AM, Jack Cai wrote: >> >>> This looks like a very comprehensive list! Thanks Jeff! >>> >>> I hit some "404 document not found" error when following the links in the >>> "Topic location" column though. >>> >>> -Jack >>> >>> >>> On Fri, Aug 28, 2009 at 5:45 PM, chi runhua wrote: >>> Sorry, here is the correct linkage http://cwiki.apache.org/confluence/display/GMOxDOC22/Apache+Geronimo+v2.2+documentation+development+status Jeff C On Fri, Aug 28, 2009 at 5:43 PM, chi runhua wrote: > Hi all, > > I did a quick summary for the updates to be made(already made) in G2.2 > doc so far. Please refer to (1) for more details. > > (1). > http://cwiki.apache.org/confluence/pages/editpage.action?pageId=101669 > > If I missed any topics, please feel free to append on the table or this > thread. > > > Jeff C > > > > > > > > >>> >> >
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
+1 Donald Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding tag is available at http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ Please review and vote: [ ] +1 Release [ ] -1 Do not release The vote will remain open for 72 hours.
[BUILD] trunk: Failed for Revision: 815305
Geronimo Revision: 815305 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test-reports [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@641c641c [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@70147014 [WARNING] Component returned which is not the same manager
Re: Geronimo Trunk compilation error with JDK5
Yes, right now we have to use Java 6 to compile trunk. -Jack On Tue, Sep 15, 2009 at 7:43 PM, Lasantha Ranaweera wrote: > Folks, > > Just noticed that G source cannot be build using JDK5 anymore due to the > following error. This error will not happen with JDK6. Is this is the > expected behavior? > > Regards, > Lasantha > > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: Compilation failure > > > /home/hd2/work/geronimo/server/plugins/jetty7/geronimo-jetty7/src/main/java/org/apache/geronimo/jetty7/connector/HTTPSocketConnector.java:[25,-1] > cannot access org.eclipse.jetty.server.bio.SocketConnector > bad class file: > /home/lasantha/.m2/repository/org/eclipse/jetty/jetty-server/8.0.0.M0-SNAPSHOT/jetty-server-8.0.0.M0-SNAPSHOT.jar(org/eclipse/jetty/server/bio/SocketConnector.class) > class file has wrong version 50.0, should be 49.0 > > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) > 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation > failure > /home/hd2/work/geronimo/server/plugins/jetty7/geronimo-jetty7/src/main/java/org/apache/geronimo/jetty7/connector/HTTPSocketConnector.java:[25,-1] > cannot access org.eclipse.jetty.server.bio.SocketConnector > bad class file: > /home/lasantha/.m2/repository/org/eclipse/jetty/jetty-server/8.0.0.M0-SNAPSHOT/jetty-server-8.0.0.M0-SNAPSHOT.jar(org/eclipse/jetty/server/bio/SocketConnector.class) > class file has wrong version 50.0, should be 49.0 > >
Geronimo Trunk compilation error with JDK5
Folks, Just noticed that G source cannot be build using JDK5 anymore due to the following error. This error will not happen with JDK6. Is this is the expected behavior? Regards, Lasantha [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure /home/hd2/work/geronimo/server/plugins/jetty7/geronimo-jetty7/src/main/java/org/apache/geronimo/jetty7/connector/HTTPSocketConnector.java:[25,-1] cannot access org.eclipse.jetty.server.bio.SocketConnector bad class file: /home/lasantha/.m2/repository/org/eclipse/jetty/jetty-server/8.0.0.M0-SNAPSHOT/jetty-server-8.0.0.M0-SNAPSHOT.jar(org/eclipse/jetty/server/bio/SocketConnector.class) class file has wrong version 50.0, should be 49.0 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure /home/hd2/work/geronimo/server/plugins/jetty7/geronimo-jetty7/src/main/java/org/apache/geronimo/jetty7/connector/HTTPSocketConnector.java:[25,-1] cannot access org.eclipse.jetty.server.bio.SocketConnector bad class file: /home/lasantha/.m2/repository/org/eclipse/jetty/jetty-server/8.0.0.M0-SNAPSHOT/jetty-server-8.0.0.M0-SNAPSHOT.jar(org/eclipse/jetty/server/bio/SocketConnector.class) class file has wrong version 50.0, should be 49.0
Re: [VOTE] Release Blueprint 1.0.0 (4th try)
+1 Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding tag is available at http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/ Please review and vote: [ ] +1 Release [ ] -1 Do not release The vote will remain open for 72 hours.
[jira] Created: (GERONIMO-4878) Geronimo doesnt protect access to its Derby databases
Geronimo doesnt protect access to its Derby databases - Key: GERONIMO-4878 URL: https://issues.apache.org/jira/browse/GERONIMO-4878 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1.4 Reporter: Radim Kolar run ij tool which comes with eclipse derby plugin and connect to geronimo. ij> connect 'jdbc:derby://localhost/SystemDatabase'; ij> show tables; TABLE_SCHEM |TABLE_NAME|REMARKS SYS |SYSALIASES| SYS |SYSCHECKS | SYS |SYSCOLPERMS | SYS |SYSCOLUMNS| SYS |SYSCONGLOMERATES | SYS |SYSCONSTRAINTS| SYS |SYSDEPENDS| SYS |SYSFILES | SYS |SYSFOREIGNKEYS| SYS |SYSKEYS | SYS |SYSROUTINEPERMS | SYS |SYSSCHEMAS| SYS |SYSSTATEMENTS | SYS |SYSSTATISTICS | SYS |SYSTABLEPERMS | SYS |SYSTABLES | SYS |SYSTRIGGERS | SYS |SYSVIEWS | SYSIBM |SYSDUMMY1 | APP |ACTIVEMQ_ACKS | APP |ACTIVEMQ_LOCK | APP |ACTIVEMQ_MSGS | APP |TIMERTASKS| 23 rows selected ij> no security restrictions are in place. Same for activemq message broker. Network listeners should be password protected. It would be great to have ability in administration console where we can assign security realm protection to particular derby database(s) or queues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4222: --- Attachment: tranql-connector-postgresql-common-1.1.jar As David pointed out, there's no stardard way to tell that an SQLException is fatal. So it might be hard to make the generic adapter detect dead connection. I went out writing an exception sorter that will regard the following SQL states as fatal for Postgresql. The list of fatal errors can be configured through the property file packaged in the attached jar. Does anybody want to test it with Geronimo (simply replace this jar with the one in Geronimo repo)? CONNECTION_UNABLE_TO_CONNECT: 08001 CONNECTION_DOES_NOT_EXIST: 08003 CONNECTION_REJECTED: 08004 CONNECTION_FAILURE: 08006 CONNECTION_FAILURE_DURING_TRANSACTION: 08007 PROTOCOL_VIOLATION: 08P01 COMMUNICATION_ERROR: 08S01 SYSTEM_ERROR: 6 > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt, > tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4818) Can not configure username and password of logging in the server through ldap
[ https://issues.apache.org/jira/browse/GERONIMO-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755433#action_12755433 ] Chi Runhua commented on GERONIMO-4818: -- Doc for G2.2 updated accordingly. http://cwiki.apache.org/GMOxDOC22/replacing-default-realm-in-geronimo.html Any questions, please let me know. Jeff C > Can not configure username and password of logging in the server through ldap > - > > Key: GERONIMO-4818 > URL: https://issues.apache.org/jira/browse/GERONIMO-4818 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security, Tomcat >Affects Versions: 2.2 > Environment: xp:sp2 > jdk 1.6 >Reporter: liangkun > Fix For: 2.2 > > Attachments: geronimo-realm.ldif, ldap.xml > > > 1.Setup Apache Directory Server > 2.Copy geronimo-real.ldif to your ldap server and run command to import your > ldap entries: > $ ldapmodify -h [your_ldap_server_ip] -p 10389 -D "uid=admin,ou=system" -w > secret -a -f [your_geronimo-realm_path] > aslo you can use other 3-rd party directory client tool such as Apache > directory studio to import this ldap file. > 3.Customize ldap server ip : ldap:// host ip>:10389 in ldap.xml and copy it to your wasce server , > and go to wasce server bin directory and run command: > deploy.sh/bat --user system --password manager deploy > /ldap.xml > also you can deploy it via admin console "deploy new"->"achive plan" > :ldap.xml > 4.Shutdown wasce server, and modify > $your_geronimo_server/var/config/config.xml as below: > change name="org.apache.geronimo.framework/server-security-config/2.1.4/car"/> to > > > > 5.Restart Geronimo server, and login it with username: test, password: > manager. > 5.Restart geronimo server, and login it with username: test, password: > manager. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: documentation is important too
Well, I think it's something missing in Geronimo. You might want to file a JIRA for this one. https://issues.apache.org/jira/browse/GERONIMO And I am also interested in the struggle you experienced, as you mentioned earlier, it took you almost entire day to write it correct. Could you let us more details about the scenario, I believe your experience could help us to improve the document. Thanks alot. Jeff C On Tue, Sep 15, 2009 at 4:27 PM, Radim Kolar wrote: > > > RunHua Chi wrote: > > > > As for the examples that you mentioned, in my understanding, G Doc > > already > > has certain topics for those: > > 1. Database security realm, you may refer to > > http://cwiki.apache.org/GMOxDOC22/database-sql-realm.html > > > Database security realm is something different, it is about checking > userids > against database. I am talking about restricting access to Derby > database itself. > Example: (G in default setup) > ij> connect 'jdbc:derby://localhost/SystemDatabase'; > ij> show tables; > TABLE_SCHEM |TABLE_NAME|REMARKS > > SYS |SYSALIASES| > SYS |SYSCHECKS | > SYS |SYSCOLPERMS | > SYS |SYSCOLUMNS| > > same for message queues. In short no security restrictions are in place. > -- > View this message in context: > http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25450084.html > Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com. > >
Re: documentation is important too
RunHua Chi wrote: > > As for the examples that you mentioned, in my understanding, G Doc > already > has certain topics for those: > 1. Database security realm, you may refer to > http://cwiki.apache.org/GMOxDOC22/database-sql-realm.html > Database security realm is something different, it is about checking userids against database. I am talking about restricting access to Derby database itself. Example: (G in default setup) ij> connect 'jdbc:derby://localhost/SystemDatabase'; ij> show tables; TABLE_SCHEM |TABLE_NAME|REMARKS SYS |SYSALIASES| SYS |SYSCHECKS | SYS |SYSCOLPERMS | SYS |SYSCOLUMNS| same for message queues. In short no security restrictions are in place. -- View this message in context: http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25450084.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Resolved: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id & context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-283. Resolution: Fixed Fix Version/s: 2.1.5 Cool, Rodger! Shiva, I think Rodger just provide what you want. Is it right? I will upload a new build to unstable site later, and you can verify it. #815203 for trunk and #815204 for 2.1.5 branch. Thanks! > Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id & > context root > - > > Key: GERONIMODEVTOOLS-283 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Reporter: Shiva Kumar H R >Priority: Minor > Fix For: 2.1.5, 2.2.0 > > Attachments: extend_rename.patch, screenshot-1.jpg, screenshot-2.jpg > > > When a Dynamic Web Project with name say "tt" is created, a Geronimo > deployment plan "geronimo-web.xml" will get created with module-id as > "default/tt-1.0.car" and context-root as "/tt". > When this project is re-factored to say "tz", the module-id will still be the > same "default/tt-1.0.car" (note that artifact id is not re-factored from "tt" > to "tz"). The context-root also remains the same "/tt". > Although this doesn't pose any problem, wouldn't it be better to refactor the > artifact-id & context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4876) "java.lang.Exception" when I shutdown the server
[
https://issues.apache.org/jira/browse/GERONIMO-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755407#action_12755407
]
Chi Runhua commented on GERONIMO-4876:
--
I encountered the same exception when shutting down the server.
My environment are as followed:
Ubuntu 9.0.4+JDK1.6+G2.2_0908 build
{code}
2009-09-15 14:39:14,602 ERROR [Connector] Protocol handler pause failed
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:530)
at java.net.Socket.connect(Socket.java:480)
at java.net.Socket.(Socket.java:377)
at java.net.Socket.(Socket.java:220)
at
org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:487)
at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:284)
at org.apache.jk.server.JkMain.pause(JkMain.java:683)
at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
at org.apache.catalina.connector.Connector.pause(Connector.java:1073)
at
org.apache.catalina.core.StandardService.stop(StandardService.java:563)
at
org.apache.geronimo.tomcat.TomcatContainer.doStop(TomcatContainer.java:253)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339)
at
org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661)
at
org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638)
at org.apache.geronimo.kernel.KernelGBean.shutdown(KernelGBean.java:382)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437)
at
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275)
at
java.security.AccessController.doPrivileged(AccessController.java:284)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1377)
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)
at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:310)
at sun.rmi.transport.Transport$1.run(Transport.java:171)
at
java.security.AccessController.doPrivilege
[jira] Resolved: (GERONIMODEVTOOLS-456) Add Security Realm Wizard to GEP to deploy security realm directly from GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-456. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! This patch adds security realm section, it's similar to the UI of admin console. It's another improvement for deployment plan editor. #815197 for trunk and #815198 for 2.1.5 branch. > Add Security Realm Wizard to GEP to deploy security realm directly from GEP > --- > > Key: GERONIMODEVTOOLS-456 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Saurabh Sharma >Assignee: Saurabh Sharma > Fix For: 2.1.5, 2.2.0 > > Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, > updated_security_realm.patch, wizard_for_add_security_realm_to_plan.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 815175
Geronimo Revision: 815175 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test-reports [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] skip non existing resourceDirectory /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/filtered-resources [INFO] Copying 3 resources [INFO] [compiler:compile] [INFO] Compiling 117 source files to /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/classes [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[101,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[102,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatEJBWebServiceContext.java:[244,20] [deprecation] setStatus(int,java.lang.String) in org.apache.catalina.connector.Response has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatServerGBean.java:[103,20] [deprecation] setServer(javax.management.MBeanServer) in org.apache.tomcat.util.modeler.Registry has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/HostGBean.java:[171,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/EngineGBean.java:[137,24] [deprecation] setServer(javax.management.MBeanServer) in org.apache.tomcat.util.modeler.Registry has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/ManagerGBean.java:[93,19] [deprecation] addOperation(java.lang.String) in org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated [INFO] [resources:testResources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] skip non existing resourceDirectory /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources [INFO] Copying 3 resources [INFO] [compiler:testCompile] [INFO] Compiling 9 source files to /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/test-classes [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/AbstractWebModuleTest.java:[110,107] [deprecation] toURL() in java.io.File has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/ApplicationTest.java:[34,88] [deprecation] toURL() in java.io.File has been deprecated [WARNING] /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/StatTest.java:[39,79] [deprecation] toURL() in java.io.File has been deprecated [INFO] [surefire:test] [INFO] Surefire report directory: /home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/surefire-reports --- T E S T S --- Running org.apache.geronimo.tomcat.ContainerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.681 sec Running org.apache.geronimo.tomcat.BasicTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.233 sec Running org.apache.geronimo.tomcat.TomcatServerGBeanTest Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.971 sec <<< FAILURE! Running org.apache.geronimo.tomcat.ApplicationTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.655 sec Running org.apache.geronimo.tomcat.JAASSecurityTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.94 sec Running org.apache.geronimo.tomcat.StatTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.645 sec Running org.apache.geronimo.tomcat.JACCSecurityTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.851 sec Results : Tests in error: Tests run: 8, Failures: 0, Errors: 2, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [
[jira] Resolved: (GERONIMODEVTOOLS-455) Add Database pool wizard in GEP to enable application specific pools
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-455. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! Although currently patch only list built-in database "derby", it's still an improvement for GEP. #815191 for 2.1.5 branch and #815188 for trunk > Add Database pool wizard in GEP to enable application specific pools > > > Key: GERONIMODEVTOOLS-455 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-455 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 2.1.3 >Reporter: Sainath Chowdary >Assignee: Sainath Chowdary > Fix For: 2.1.5, 2.2.0 > > Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, > wizard_for_adding_dbpool_to_application_plan.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-453) JAXB Classes support for schema geronimo-login-config-2.0.xsd
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-453. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! I pick up the patch from 455 and just commit part of it for this JIRA. #815171 for trunk and #815176 for 2.1.5 branch. > JAXB Classes support for schema geronimo-login-config-2.0.xsd > - > > Key: GERONIMODEVTOOLS-453 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-453 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 2.1.2, 2.1.3 >Reporter: Saurabh Sharma >Assignee: Saurabh Sharma > Fix For: 2.1.5, 2.2.0 > > Attachments: jaxb-loginconfig.patch > > > There is no JAXB class support for schema geronimo-login-config-2.0.xsd. > Login Configuration settings must be specified as a element of xml-reference > while generating security realm plan. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
