[jira] [Updated] (GERONIMO-5750) override rat plugin to exclude the files we won't need to scan to make the rat:check result cleaner.
[ https://issues.apache.org/jira/browse/GERONIMO-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5750: -- Fix Version/s: (was: 2.1.8) (was: 2.2.2) (was: 3.0) > override rat plugin to exclude the files we won't need to scan to make the > rat:check result cleaner. > > > Key: GERONIMO-5750 > URL: https://issues.apache.org/jira/browse/GERONIMO-5750 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Shawn Jiang > > We should override rat plugin to exclude the files we won't need to scan to > make the rat:check result cleaner. > > org.apache.rat > apache-rat-plugin > 0.7 > > > src/**/* > pom.xml > > > **/*/emptyfile1 > **/*/goals.txt > **/*/hello.txt > **/*/RELEASE_NOTES-*.txt > **/*/MANIFEST.MF > .git > .gitignore > > > > > verify > > check > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-6116) differentiate the two "OpenEJB ORB Adapter" displayed in "Linstening on Ports" after server startup.
[ https://issues.apache.org/jira/browse/GERONIMO-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reopened GERONIMO-6116: --- not fixed for 2.1 and 2.2 branch, reopen it > differentiate the two "OpenEJB ORB Adapter" displayed in "Linstening on > Ports" after server startup. > -- > > Key: GERONIMO-6116 > URL: https://issues.apache.org/jira/browse/GERONIMO-6116 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: CORBA, general >Affects Versions: 2.1.8, 2.2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Han Hong Fang > Fix For: 3.0 > > > Listening on Ports: > 1050 0.0.0.0 CORBA Naming Service > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 2001 0.0.0.0 OpenEJB ORB Adapter > 4201 0.0.0.0 OpenEJB Daemon > 6882 0.0.0.0 OpenEJB ORB Adapter > 8009 0.0.0.0 Tomcat Connector AJP TomcatAJPConnector > 8080 0.0.0.0 Tomcat Connector HTTP BIO TomcatWebConnector > 8443 0.0.0.0 Tomcat Connector HTTPS BIO TomcatWebSSLConnector > 0.0.0.0 JMX Remoting Connector > 61616 0.0.0.0 ActiveMQ Transport Connector > 2001 is normal ORB server while 6882 is secure ORB server, we should > differentiate them in the desciption. > The gbean of orb server is : org.apache.geronimo.corba.CORBAEjbBeanGBean > the plan to defined the 2 server is: > plugins\corba\j2ee-corba-yoko\src\main\plan\plan.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5991) org.apache.myfaces.el.VariableResolverImpl throws java.lang.IllegalStateException when it unsets the scope as null
[ https://issues.apache.org/jira/browse/GERONIMO-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5991. --- Resolution: Fixed > org.apache.myfaces.el.VariableResolverImpl throws > java.lang.IllegalStateException when it unsets the scope as null > -- > > Key: GERONIMO-5991 > URL: https://issues.apache.org/jira/browse/GERONIMO-5991 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: myfaces >Affects Versions: 2.1.7 > Environment: Linux > Apache Geronimo 2.1.7 >Reporter: Mohan Reddy >Assignee: Forrest Xia > Fix For: 2.1.8 > > > The following issue has been reported in MyFaces community under JIRA > MYFACES-3166. This Geronimo JIRA is created to track the fix integration into > geronimo. > I am running an application in Geronimo 2.1.7 that requires valid scope and > it fails with the following exception > Servlet.service() for servlet jsp threw exception > > java.lang.IllegalStateException: unknown scope defined: null > at > org.apache.myfaces.el.VariableResolverImpl.resolveVariable(VariableResol > verImpl.java:71) > at > org.apache.myfaces.el.convert.VariableResolverToELResolver.getValue(Vari > ableResolverToELResolver.java:93) > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > --- > --- > Servlet.service() for servlet jsp threw exception > > java.lang.NullPointerException > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.access$3 > 01(FacesCompositeELResolver.java:46) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver$4.invoke > (FacesCompositeELResolver.java:108) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.invoke(F > acesCompositeELResolver.java:148) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue > (FacesCompositeELResolver.java:104) > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6234) Upgrade some components for 2.1.8 release
[ https://issues.apache.org/jira/browse/GERONIMO-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6234: -- Description: Components upgrade for 2.1.8: JAXB 2.0.5 -> 2.1.13 OPENEJB 3.0.3 -> 3.0.4 TOMCAT 6.0.29.1 -> 6.0.35.1 ACTIVEMQ 4.1.2-G20100308 -> 4.1.2-G20110506 MYFACES 1.2.8 -> 1.2.8-G2.1.8 tranql-connector-db2-xa 1.6 -> 1.7 tranql-connector-sqlserver2008-xa n/a -> 1.0 tranql-connector-db2ISeries-xa 1.0 -> 1.1 was: Components upgrade for 2.1.8: JAXB 2.0.5 -> 2.1.13 OPENEJB 3.0.3 -> 3.0.4 TOMCAT 6.0.33.1 -> 6.0.35.1 ACTIVEMQ 4.1.2-G20100308 -> 4.1.2-G20110506 MYFACES 1.2.8 -> 1.2.8-G2.1.8 tranql-connector-db2-xa 1.6 -> 1.7 tranql-connector-sqlserver2008-xa n/a -> 1.0 tranql-connector-db2ISeries-xa 1.0 -> 1.1 > Upgrade some components for 2.1.8 release > - > > Key: GERONIMO-6234 > URL: https://issues.apache.org/jira/browse/GERONIMO-6234 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.1.8 > > > Components upgrade for 2.1.8: > JAXB 2.0.5 -> 2.1.13 > OPENEJB 3.0.3 -> 3.0.4 > TOMCAT 6.0.29.1 -> 6.0.35.1 > ACTIVEMQ 4.1.2-G20100308 -> 4.1.2-G20110506 > MYFACES 1.2.8 -> 1.2.8-G2.1.8 > tranql-connector-db2-xa 1.6 -> 1.7 > tranql-connector-sqlserver2008-xa n/a -> 1.0 > tranql-connector-db2ISeries-xa 1.0 -> 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5689) User-defined derby connection user name and password should be honored when enabling derby authentication
[ https://issues.apache.org/jira/browse/GERONIMO-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5689: -- Fix Version/s: 2.1.8 > User-defined derby connection user name and password should be honored when > enabling derby authentication > - > > Key: GERONIMO-5689 > URL: https://issues.apache.org/jira/browse/GERONIMO-5689 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.1.7, 2.2.1 > Environment: ubuntu 10.04.1 LTS > sun java 1.5.0_22 >Reporter: Forrest Xia >Assignee: Chi Runhua >Priority: Minor > Fix For: 2.1.8 > > Attachments: bank-ear-2.1.1.4.ear > > > Consider this scenario: > 1. User firstly disables derby authentication, then start the server and > deploy an application which is using embedded derby database. The datasource > deployment plan is like this: > > > > > javax.sql.DataSource > > BankPool >name="Driver">org.apache.derby.jdbc.EmbeddedDriver >name="UserName">app >name="Password">app >name="ConnectionURL">jdbc:derby:BankDB;create=true > > > > 10 > 0 > > > > > > > > In the plan, user specifies an username and password. > 2. Shutdown the server, enable derby authentication, and start the server > again > 3. Now the server cannot start successfullly, because this exception: > Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car > 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User > authentication failure (userName userPassword databaseName): app app BankDB > 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for handle: nullManagedConnectionInfo: > org.apache.geronimo.connector.outbound.ManagedConnectionInfo@123288b. mc: > null] > javax.resource.spi.ResourceAllocationException: Unable to obtain physical > connection to jdbc:derby:BankDB;create=true > ... > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to > start due to the following reasons: > The service > J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit > did not start because Connection authentication failure occurred. Reason: > Invalid authentication.. > I think this exception may cause by derby user is hard-coded in code to > acquire server connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5700) Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760
[ https://issues.apache.org/jira/browse/GERONIMO-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5700. --- Resolution: Fixed Fix Version/s: (was: Wish List) 2.1.8 > Active MQ Fixes in geronimo for AMQ-1779, AMQ-1431 and AMQ-1760 > --- > > Key: GERONIMO-5700 > URL: https://issues.apache.org/jira/browse/GERONIMO-5700 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.1.7 > Environment: geronimo tomcat assembly 2.1.6 >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.8 > > Attachments: AMQ-1431.patch, AMQ-1760.patch, AMQ-1779.patch > > > Some important fixes have gone to ActiveMQ via AMQ-1779, AMQ-1431 and > AMQ-1760. Apply these in already used patched version of activemq 4.1.2 in > geronimo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6164) Passing more db2 specific properties through db2 xa connector
[ https://issues.apache.org/jira/browse/GERONIMO-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6164. --- Resolution: Fixed Fix Version/s: 3.0-beta-1 3.0 2.1.8 > Passing more db2 specific properties through db2 xa connector > - > > Key: GERONIMO-6164 > URL: https://issues.apache.org/jira/browse/GERONIMO-6164 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.1.7 > Environment: db2 database >Reporter: ldxjava >Assignee: viola.lu > Fix For: 2.1.8, 3.0, 3.0-beta-1 > > > Use db2 xa connector to access db2 database. > We need to pass some db2 specific properties. for example > progressiveStreaming etc. > Currently we have no methods to do this when we use db2 xa connector. > We can only use the general connector (non-xa) to pass these properties > through URL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6234) Upgrade some components for 2.1.8 release
[ https://issues.apache.org/jira/browse/GERONIMO-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6234. --- Resolution: Fixed > Upgrade some components for 2.1.8 release > - > > Key: GERONIMO-6234 > URL: https://issues.apache.org/jira/browse/GERONIMO-6234 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.1.8 > > > Components upgrade for 2.1.8: > JAXB 2.0.5 -> 2.1.13 > OPENEJB 3.0.3 -> 3.0.4 > TOMCAT 6.0.33.1 -> 6.0.35.1 > ACTIVEMQ 4.1.2-G20100308 -> 4.1.2-G20110506 > MYFACES 1.2.8 -> 1.2.8-G2.1.8 > tranql-connector-db2-xa 1.6 -> 1.7 > tranql-connector-sqlserver2008-xa n/a -> 1.0 > tranql-connector-db2ISeries-xa 1.0 -> 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6234) Upgrade some components for 2.1.8 release
Upgrade some components for 2.1.8 release - Key: GERONIMO-6234 URL: https://issues.apache.org/jira/browse/GERONIMO-6234 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Forrest Xia Assignee: Forrest Xia Fix For: 2.1.8 Components upgrade for 2.1.8: JAXB 2.0.5 -> 2.1.13 OPENEJB 3.0.3 -> 3.0.4 TOMCAT 6.0.33.1 -> 6.0.35.1 ACTIVEMQ 4.1.2-G20100308 -> 4.1.2-G20110506 MYFACES 1.2.8 -> 1.2.8-G2.1.8 tranql-connector-db2-xa 1.6 -> 1.7 tranql-connector-sqlserver2008-xa n/a -> 1.0 tranql-connector-db2ISeries-xa 1.0 -> 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6171) Grails applications do not works correctly when deployed to ROOT folder
[ https://issues.apache.org/jira/browse/GERONIMO-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6171. --- Resolution: Fixed Fix Version/s: 3.0-beta-1 3.0 2.2.2 2.1.8 > Grails applications do not works correctly when deployed to ROOT folder > --- > > Key: GERONIMO-6171 > URL: https://issues.apache.org/jira/browse/GERONIMO-6171 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1.7 > Environment: Windows and Unix >Reporter: Radim Kolar > Labels: grails > Fix For: 2.1.8, 2.2.2, 3.0, 3.0-beta-1 > > Attachments: zero.zip > > > If you deploy grails 1.3.7 application to root of virtual server links are > not generated correctly. > Default URL mapping is /controller/action (works in other application > servers) but in G with tomcat you have to write link like > /controller/action.gsp which is invalid path in other application servers. > it works correctly in plain tomcat, jetty, glassfish 3.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.
[ https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reopened GERONIMO-5712: --- > Geronimo should remember the monitoring server enablement status. > -- > > Key: GERONIMO-5712 > URL: https://issues.apache.org/jira/browse/GERONIMO-5712 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.6, 2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shenghao Fang > Fix For: 2.1.8, 3.0 > > Attachments: G5712.patch, GERONIMO-5712-3.0.patch > > > Currently , when a monitor user can use the monitoring function only after a > admin user add/enable the server and enable query on the servers. > But after the server restart, the enable status become disable automatically > so the the admin user have to do the enablement again so that Monitor user > could continue use the monitoring console. > To resolve this, we should make the server and query thread enablement status > persistent. so that we could start the query thread once the server is > restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.
[ https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5712. - Resolution: Fixed > Geronimo should remember the monitoring server enablement status. > -- > > Key: GERONIMO-5712 > URL: https://issues.apache.org/jira/browse/GERONIMO-5712 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.6, 2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shenghao Fang > Fix For: 2.1.8, 3.0 > > Attachments: G5712.patch, GERONIMO-5712-3.0.patch > > > Currently , when a monitor user can use the monitoring function only after a > admin user add/enable the server and enable query on the servers. > But after the server restart, the enable status become disable automatically > so the the admin user have to do the enablement again so that Monitor user > could continue use the monitoring console. > To resolve this, we should make the server and query thread enablement status > persistent. so that we could start the query thread once the server is > restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.
[ https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5712: -- Fix Version/s: 2.1.8 > Geronimo should remember the monitoring server enablement status. > -- > > Key: GERONIMO-5712 > URL: https://issues.apache.org/jira/browse/GERONIMO-5712 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.6, 2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shenghao Fang > Fix For: 2.1.8, 3.0 > > Attachments: G5712.patch, GERONIMO-5712-3.0.patch > > > Currently , when a monitor user can use the monitoring function only after a > admin user add/enable the server and enable query on the servers. > But after the server restart, the enable status become disable automatically > so the the admin user have to do the enablement again so that Monitor user > could continue use the monitoring console. > To resolve this, we should make the server and query thread enablement status > persistent. so that we could start the query thread once the server is > restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release XBean 3.9
Have you verified that current xbean-blueprint (including my inclusion of necessary aries blueprint compendium.cm classes) works with the aries blueprint compatibility bundles (small bundles) with activemq? I'm not yet at a point to verify this in geronimo, although I hope to be able to shortly. thanks david jencks On Dec 16, 2011, at 6:31 AM, Hiram Chirino wrote: > Please vote for the geronimo xbean 3.9 release,. > > The components up for vote are: > https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-349/ > > tag is here: > https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/ > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > Here's my +1 > > Regards, > Hiram > > FuseSource > Web: http://fusesource.com/
Re: buildbot success in ASF Buildbot on geronimo-xbean-trunk
How to access buildbot system? so that we can configure CI build for necessary branches/trunk. On Fri, Dec 16, 2011 at 10:29 PM, wrote: > The Buildbot has detected a restored build on builder geronimo-xbean-trunk > while building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/geronimo-xbean-trunk/builds/37 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: isis_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch geronimo/xbean/trunk] 1215149 > Blamelist: chirino > > Build succeeded! > > sincerely, > -The Buildbot > > > > -- Thanks! Regards, Forrest
Re: [Proposition] - Collaboration between Karaf - Geronimo
On Dec 15, 2011, at 4:55 AM, Charles Moulliard wrote: > Hi, > > Within mailing list of Karaf, we have started a discussion about the > idea to have a KarafEE release. This idea is similar to the reflection > that OpenEJB team has had with TomEE but using Tomcat as Java > Application Server. As Geronimo uses Karaf as their kernel (which is > not the case for Glassfish, JBoss, Eclipse Virgo, ...) that makes a > lot of sense that we continue to promote karaf as platform not only > for Integration Server like ServiceMix but also for J2EE platform. > Since EJB3 spec and CDI, we see more and more projects interested to > have/use an EJB container on Karaf and use it as an alternative to > Spring (Dynamic Module/Blueprint). Developing a server, certify it, > cost a lot. > > As we we do not want to re-invent the wheel and due to number of > resources available, we prefer to capitalize on the work/efforts done. > This is why we come to you to discuss the idea about collaborating > together to improve existing geronimo-karaf platform to address points > mentioned in this thread > (http://karaf.922171.n3.nabble.com/Proposition-Apache-KarafEE-td3585332.html) > to be able to provide a KarafEE or Geronimo distro but using "features > mechanism" of Karaf to deploy OpenEJB, OpenJPA, new Karaf web console, > ... > > What do you think about that ? You may need to be more precise about what exact capabilities/features you are looking for… David Jencks has been working on some Karaf updates necessary for a more complete Karaf integration within Geronimo. We do have a general desire to move Geronimo from the current GBeans to an OSGi service-based infrastructure. If this is inline with your thinking, than I'd say there's a definite possibility for collaboration… Your thoughts, ideas, and contributions would be welcomed by the Geronimo community. --kevan
Re: [VOTE] Release XBean 3.9
just notice xbean-191, no more concern. tried building, seems ok for me. so my +1 On Fri, Dec 16, 2011 at 10:35 PM, Forrest Xia wrote: > What major changes in 3.9? > > > On Fri, Dec 16, 2011 at 10:31 PM, Hiram Chirino wrote: > >> Please vote for the geronimo xbean 3.9 release,. >> >> The components up for vote are: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip >> >> Staging repo is here: >> https://repository.apache.org/content/repositories/orgapachegeronimo-349/ >> >> tag is here: >> https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/ >> >> Vote open 72 hours >> >> [ ] +1 release this >> [ ] 0 don't care >> [ ] -1 don't release this (please explain) >> >> Here's my +1 >> >> Regards, >> Hiram >> >> FuseSource >> Web: http://fusesource.com/ >> > > > > -- > Thanks! > > Regards, Forrest > > -- Thanks! Regards, Forrest
Re: [VOTE] Release XBean 3.9
What major changes in 3.9? On Fri, Dec 16, 2011 at 10:31 PM, Hiram Chirino wrote: > Please vote for the geronimo xbean 3.9 release,. > > The components up for vote are: > > https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-349/ > > tag is here: > https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/ > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > Here's my +1 > > Regards, > Hiram > > FuseSource > Web: http://fusesource.com/ > -- Thanks! Regards, Forrest
[VOTE] Release XBean 3.9
Please vote for the geronimo xbean 3.9 release,. The components up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-349/ tag is here: https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/ Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) Here's my +1 Regards, Hiram FuseSource Web: http://fusesource.com/
[jira] [Resolved] (GERONIMO-5900) NullPointerException on JavaBeanDispatcher class when debug logging enabled
[
https://issues.apache.org/jira/browse/GERONIMO-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia resolved GERONIMO-5900.
---
Resolution: Won't Fix
Fix Version/s: (was: 2.1.8)
> NullPointerException on JavaBeanDispatcher class when debug logging enabled
> ---
>
> Key: GERONIMO-5900
> URL: https://issues.apache.org/jira/browse/GERONIMO-5900
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
>Affects Versions: 2.1.7
> Environment: Windows XP SP3
> Apache Geronimo 2.1.7
>Reporter: Ashok Poralu
>
> Getting a NPE
> Caused by:
> java.lang.NullPointerException
> at
> org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.invoke(JavaBeanDispatcher.java:95)
> at
> org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:172)
> ... 30 more
> The debug logging code from JavaBeanDispatcher getting serviceInstance as
> null from EJBServiceDispatcher. Following the code snippet,
> if (log.isDebugEnabled()) {
> log.debug("Exception invoking a method of " +
> serviceImplClass.toString() + " of instance " +
> serviceInstance.toString());
> It seems, Geronimo uses the custom version of AXIS2 1.3-G20090406 codebase.
> The temporary workaround for the issue to disable logging of the class
> JavaBeanDispatcher
> log4j.logger.org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher=INFO
> To fix this, we can change the
> log.debug("Exception invoking a method of " +
> (serviceImplClass == null : null ?
> serviceImplClass.toString() ) + " of instance " + (serviceInstance == null :
> null ? serviceInstance.toString()));
> Your comments please...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6161) Support MSSQL Server 2008 XA Datasource Creation
[ https://issues.apache.org/jira/browse/GERONIMO-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-6161. - Resolution: Fixed > Support MSSQL Server 2008 XA Datasource Creation > - > > Key: GERONIMO-6161 > URL: https://issues.apache.org/jira/browse/GERONIMO-6161 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector >Affects Versions: 2.1 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 2.1.8, 3.0.1 > > > Add MSSQL Server 2008 XA Datasource Creation support. > Now prepared-statement-cache is not set when creating MS SQL Server XA > Datasource, add this configuration also. > patch is available at jra.ciodehaus.org/browse/TQL-28 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6105) [Wish List] RMI Object LoadBalance
[ https://issues.apache.org/jira/browse/GERONIMO-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6105: -- Fix Version/s: (was: 2.1.8) (was: 2.2.2) Wish List > [Wish List] RMI Object LoadBalance > -- > > Key: GERONIMO-6105 > URL: https://issues.apache.org/jira/browse/GERONIMO-6105 > Project: Geronimo > Issue Type: Wish > Security Level: public(Regular issues) > Components: Wish List >Reporter: viola.lu >Priority: Minor > Fix For: Wish List > > > http://apache-geronimo.328035.n3.nabble.com/RMI-Object-Load-Balance-td3221106.html#a3222425 > Add it as a wish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Releasing XBean 3.9
Ok, I'm really going to start cutting a release candidate for XBean 3.9. I've got my fingers crossed that the release plugin is working smoothly! Regards, Hiram FuseSource Web: http://fusesource.com/ On Thu, Oct 27, 2011 at 12:57 PM, Kevan Miller wrote: > > On Oct 27, 2011, at 9:30 AM, Hiram Chirino wrote: > >> I've just added in a little feature which we really need in the next >> version of ActiveMQ. Details at: >> https://issues.apache.org/jira/browse/XBEAN-191 >> >> Are there any problems with doing a quick XBean 3.9 release soon? > > No problems from my perspective. > > --kevan >
[jira] [Assigned] (GERONIMO-5991) org.apache.myfaces.el.VariableResolverImpl throws java.lang.IllegalStateException when it unsets the scope as null
[ https://issues.apache.org/jira/browse/GERONIMO-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-5991: - Assignee: Forrest Xia > org.apache.myfaces.el.VariableResolverImpl throws > java.lang.IllegalStateException when it unsets the scope as null > -- > > Key: GERONIMO-5991 > URL: https://issues.apache.org/jira/browse/GERONIMO-5991 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: myfaces >Affects Versions: 2.1.7 > Environment: Linux > Apache Geronimo 2.1.7 >Reporter: Mohan Reddy >Assignee: Forrest Xia > Fix For: 2.1.8 > > > The following issue has been reported in MyFaces community under JIRA > MYFACES-3166. This Geronimo JIRA is created to track the fix integration into > geronimo. > I am running an application in Geronimo 2.1.7 that requires valid scope and > it fails with the following exception > Servlet.service() for servlet jsp threw exception > > java.lang.IllegalStateException: unknown scope defined: null > at > org.apache.myfaces.el.VariableResolverImpl.resolveVariable(VariableResol > verImpl.java:71) > at > org.apache.myfaces.el.convert.VariableResolverToELResolver.getValue(Vari > ableResolverToELResolver.java:93) > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > --- > --- > Servlet.service() for servlet jsp threw exception > > java.lang.NullPointerException > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.access$3 > 01(FacesCompositeELResolver.java:46) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver$4.invoke > (FacesCompositeELResolver.java:108) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.invoke(F > acesCompositeELResolver.java:148) > at > org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue > (FacesCompositeELResolver.java:104) > at > javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5355) ClassCastException while starting snapshot (Stat Query) in G 215 Monitoring portlet through java client
[
https://issues.apache.org/jira/browse/GERONIMO-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5355.
-
Resolution: Fixed
Close it since the fix is in the 2.1 branch.
> ClassCastException while starting snapshot (Stat Query) in G 215 Monitoring
> portlet through java client
> ---
>
> Key: GERONIMO-5355
> URL: https://issues.apache.org/jira/browse/GERONIMO-5355
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.5, 2.2.1
>Reporter: Amit Puri
>Assignee: Vamsavardhana Reddy
> Fix For: 2.1.8, 2.2.2
>
>
> In a java client where MBeanServerConnection is created and invoke
> startSnapshot method in Monitoring Portlet of G 215, Stat Query snapshot
> started but we can also find ClassCastException.
> ...
> ERROR [MasterRemoteControlJMX]
> org.tranql.connector.jdbc.TranqlDataSource$SelfReference incompatible with
> javax.sql.DataSource
> java.lang.ClassCastException:
> org.tranql.connector.jdbc.TranqlDataSource$SelfReference incompatible with
> javax.sql.DataSource
> at
> org.apache.geronimo.monitoring.MasterRemoteControlJMX.(MasterRemoteControlJMX.java:110)
> at
> org.apache.geronimo.monitoring.snapshot.SnapshotProcessor.getMRC(SnapshotProcessor.java:148)
> at
> org.apache.geronimo.monitoring.snapshot.SnapshotProcessor.takeSnapshot(SnapshotProcessor.java:59)
> at
> org.apache.geronimo.monitoring.snapshot.SnapshotThread.run(SnapshotThread.java:103)
> ...
> In G 214, this exception does not come while using same java client.
> These steps are followed in java client:
> 1.Creating MBeanServerConnection object
> ...
> MBeanServerConnection mbServerConn;
> JMXServiceURL serviceURL = new
> JMXServiceURL("service:jmx:rmi:///jndi/rmi://localhost/JMXConnector");
> Hashtable env = new Hashtable();
> String[] credentials = new String[2];
> credentials[0] = "system";
> credentials[1] = "manager";
> env.put(JMXConnector.CREDENTIALS, credentials);
>
> JMXConnector connector = JMXConnectorFactory.connect(serviceURL, env);
> mbServerConn = connector.getMBeanServerConnection();
> ..
> 2. Retrieving the mbean name to the agent-car-jmx plugin
> ..
> if(PATH == null) {
> Set mbeanNames = mbServerConn.queryNames(new
> ObjectName("*:name=MasterRemoteControlJMX,*"), null);
> for(Iterator it = mbeanNames.iterator(); it.hasNext(); ) {
> String mbeanName = ((ObjectName)it.next()).getCanonicalName();
> if(mbeanName.contains("agent-car-jmx") &&
> mbeanName.contains("MasterRemoteControlJMX") && mbeanName.contains("GBean")) {
> PATH = mbeanName;
> break;
> }}
> if(PATH == null) {
> throw new Exception("[ERROR] Required mbean not found: agent-car-jmx");
> }}
> ..
> Here I am getting mbean name as
> "geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1.5/car,j2eeType=GBean,name=MasterRemoteControlJMX"
> 3. Invoking startSnapshot
> ..
> long time = 30;
> int days = 2;
> mbServerConn.invoke(new ObjectName(PATH),"startSnapshot", new Object[] {
> time, days }, new String[] { "java.lang.Long", "java.lang.Integer" });
> ..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5749) Command Line utility to enable/disable Monitoring server and Stat query Snapshot thread for DefaultServer
[ https://issues.apache.org/jira/browse/GERONIMO-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5749. - Resolution: Fixed Fix will be in 2.1.8 release > Command Line utility to enable/disable Monitoring server and Stat query > Snapshot thread for DefaultServer > - > > Key: GERONIMO-5749 > URL: https://issues.apache.org/jira/browse/GERONIMO-5749 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.1.7 >Reporter: Vamsavardhana Reddy >Assignee: Shenghao Fang > Fix For: 2.1.8 > > Attachments: disable-monitoring.sql, enable-monitoring.sql, > runsql.bat, runsql.sh > > > Currently there is no command line utility to enable/disable Monitoring on > Default Server and start/stop of Stats Query snapshot thread. The only way > to do these operations is through Monitoring portlet in the admin console. > Enable/disable Monitoring is done by changing ENABLED column in SERVERS and > GRAPHS tables in MonitoringClientDB. SQL scripts can be provided for this to > execute from command line. > Start/Stop of snapshot thread is done by calling MasterRemoteControlJMX GBean > methods. Ideal place to provide support for this would be through a new > deployer command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5806) SharedLIb GBean should have priority set to PRIORITY_CLASSLOADER
[ https://issues.apache.org/jira/browse/GERONIMO-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5806. - Resolution: Fixed Fix Version/s: (was: 2.2.2) The fix was committed into 2.1 branch, and will be included in 2.1.8 release > SharedLIb GBean should have priority set to PRIORITY_CLASSLOADER > > > Key: GERONIMO-5806 > URL: https://issues.apache.org/jira/browse/GERONIMO-5806 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: kernel >Affects Versions: 2.1.7, 2.2.1 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: 2.1.8 > > Attachments: GERONIMO-5806.patch > > > When a SharedLib GBean is added to a configuration by updating config.xml, > the new classes and jars from the shared lib do not get into the > configuration's class loader until that GBean instance is created. This > results in ClassNotFoundExceptions if another GBean that uses these new > classes is loaded ahead of the SharedLib GBean. This can be avoided by > setting the priority of SharedLib GBean to GBeanInfo.PRIORITY_CLASSLOADER so > that the new classes and jars get added to the classloader and are available > immediately for all other GBeans in the configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5950) AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory
[ https://issues.apache.org/jira/browse/GERONIMO-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5950. --- Resolution: Fixed Close this jira because the fix has been added to G 2.1 branch, and will be included in G 2.1.8 release > AMQ-3121: Avoid connection creation while creating XAResource if the > connection factory is not an xa connection factory > --- > > Key: GERONIMO-5950 > URL: https://issues.apache.org/jira/browse/GERONIMO-5950 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.1.7 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: 2.1.8 > > > AMQ-3121: Avoid connection creation while creating XAResource if the > connection factory is not an xa connection factory > Avoid connection creation while creating XAResource if the connection factory > is not xa connection factory, also, if it is xa connection, I think that the > connection should not be closed as the new created xa resource holds > reference to connection. > --- > When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to > the following are noticed: > 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept > connection from /127.0.0.1:48012: java.io.IOException: The transport is not > running. > java.io.IOException: The transport is not running. > at org.apache.activemq.transport.TransportSupport.checkStarted > (TransportSupport.java:103) > at org.apache.activemq.transport.tcp.TcpTransport.oneway > (TcpTransport.java:117) > at org.apache.activemq.transport.InactivityMonitor.oneway > (InactivityMonitor.java:145) > at org.apache.activemq.transport.TransportFilter.oneway > (TransportFilter.java:80) > at org.apache.activemq.transport.WireFormatNegotiator.oneway > (WireFormatNegotiator.java:93) > at org.apache.activemq.transport.MutexTransport.oneway > (MutexTransport.java:47) > at org.apache.activemq.broker.TransportConnection.dispatch > (TransportConnection.java:1138) > at > org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805) > > at org.apache.activemq.broker.TransportConnection.start > (TransportConnection.java:885) > at org.apache.activemq.broker.TransportConnector$1.onAccept > (TransportConnector.java:148) > at org.apache.activemq.transport.tcp.TcpTransportServer.run > (TcpTransportServer.java:162) > at java.lang.Thread.run(Thread.java:736) > This is because the connection used to create xa resources is closed > immediately. A fix AMQ-3121-v412.patch > (https://issues.apache.org/jira/secure/attachment/12478376/AMQ-3121-v412.patch) > has been posted to AMQ JIRA. The issue is resolved by > (1) creating the connection only when the factory is XA and > (2) caching the connection used to create xa resources and closing it when > the resource adapter is stopped. > This Geronimo JIRA is created to merge AMQ-3121 into our private build of AMQ > and track the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
