[jira] [Updated] (GERONIMO-5858) Fail to parse servlet 3.0 annotations in WAB
[ https://issues.apache.org/jira/browse/GERONIMO-5858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5858: -- Attachment: NiHaoShiJie_ServletAnnotation_3.0.0.eba The original sample provided has programming/configuration issue. I attach a new sample to demo that G 3.0-beta branch code support servlet 3.0 in WAB/EBA programming model. Fail to parse servlet 3.0 annotations in WAB Key: GERONIMO-5858 URL: https://issues.apache.org/jira/browse/GERONIMO-5858 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: osgi, web Affects Versions: 3.0 Environment: OS:win Reporter: viola.lu Assignee: Forrest Xia Fix For: 3.0, 3.0-beta-1 Attachments: NiHaoShiJie_ServletAnnotation_3.0.0.eba, ds-eba-3.0-SNAPSHOT.eba 1.Create an eba including a WAB, which has one servlet using @WebServlet annotation 2.Deploy it, but this annotation isn't resolved. Have to declare it in descriptor web.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] [Updated] (GERONIMO-5802) Server startup failure if one of the application modules fails to start
[ https://issues.apache.org/jira/browse/GERONIMO-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5802: -- Component/s: startup/shutdown Affects Version/s: 2.1.8 2.2.1 Assignee: Forrest Xia This issue is common to other Geronimo releases. Server startup failure if one of the application modules fails to start --- Key: GERONIMO-5802 URL: https://issues.apache.org/jira/browse/GERONIMO-5802 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: general, startup/shutdown Affects Versions: 2.1.8, 2.2.1, 3.0 Reporter: Jarek Gawor Assignee: Forrest Xia The server startup will fail if one of the application modules fails to start. This might not be a desirable behavior in all cases. For example, when using IDE one would like to start the server and debug the broken application and later redeploy the application with a fix. Right now, that's not quite possible. -- 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-5560) Running Geronimo as a Windows service (geronimosrvw.exe) gives Java PermGen space out of memory error
[ https://issues.apache.org/jira/browse/GERONIMO-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5560: -- Attachment: service_pr.bat Hi Guillaume, Please try the updated service_pr.bat in your G 3.0-beta-1 and see if the problem is fixed. Steps to use this new file: 1. Replace the same file in geronimoHome\bin folder 2. Remove the service and then reinstall it service_pr.bat remove service_pr.bat install 3. Start the service and see if the problem is fixed. Running Geronimo as a Windows service (geronimosrvw.exe) gives Java PermGen space out of memory error - Key: GERONIMO-5560 URL: https://issues.apache.org/jira/browse/GERONIMO-5560 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: Windows 2008R2 server Reporter: Albert T. Wong Priority: Critical Attachments: service_pr.bat Followed the instructions at https://cwiki.apache.org/GMOxDOC22/running-geronimo-as-a-windows-service.html. No problem installing the Windows Service Wrapper. When you start up the service and hit Geronimo, after login, throws PermGen space out of memory error. I also tried geronimosrvw.exe and modifying the command line startup (added -Xmx256m -XX:MaxPermSize=128m in the startup - arguments) and still geronimosrvw.exe gives me the same error. type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:862) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:791) jsp.WEB_002dINF.themes.navigation_jsp._jspService(navigation_jsp.java:296) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968) jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:116) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:151) javax.servlet.http.HttpServlet.service(HttpServlet.java:693) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48) org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) root cause java.lang.OutOfMemoryError: PermGen space java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) java.lang.ClassLoader.defineClass(ClassLoader.java:616) java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:52) org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:302) java.security.AccessController.doPrivileged(Native Method) org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:254) org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:416) org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256) java.lang.ClassLoader.loadClass(ClassLoader.java:248) java.lang.Class.forName0(Native Method) java.lang.Class.forName(Class.java:169) org.apache.taglibs.standard.lang.support.ExpressionEvaluatorManager.getEvaluatorByName(ExpressionEvaluatorManager.java:125) org.apache.taglibs.standard.lang.support.ExpressionEvaluatorManager.evaluate(ExpressionEvaluatorManager.java:81) org.apache.taglibs.standard.tag.el.core.ForEachTag.evaluateExpressions(ForEachTag.java:164) org.apache.taglibs.standard.tag.el.core.ForEachTag.doStartTag(ForEachTag.java:75) jsp.WEB_002dINF.themes.navigation_jsp._jspService(navigation_jsp.java:116) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
[jira] [Updated] (GERONIMO-6285) Application also deployed into the default server instance if deploying it in a new instance
[ https://issues.apache.org/jira/browse/GERONIMO-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6285: -- Attachment: cviewer-3.0.0.0.war Application also deployed into the default server instance if deploying it in a new instance Key: GERONIMO-6285 URL: https://issues.apache.org/jira/browse/GERONIMO-6285 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: cviewer-3.0.0.0.war Steps to reproduce: 1. Create a new server instance by following the doc[1] 2. Deploy the attached sample in the new instance via command like this: $ ./bin/deploy --port 1109 deploy attachedsample.war 3. Then you will see it running in the default instance on port 8080 as well 4. While it won't if deploying it from the default server instance [1] https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html -- 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-6274) Cannot save some of tomcat web connector parameters via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6274: -- Summary: Cannot save some of tomcat web connector parameters via admin console (was: Cannot save tomcat web connector parameters via admin console) Cannot save some of tomcat web connector parameters via admin console - Key: GERONIMO-6274 URL: https://issues.apache.org/jira/browse/GERONIMO-6274 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0-beta-2 Reporter: Forrest Xia Assignee: Forrest Xia 1. Start the server 2. login admin console 3. Edit a web connector 4. Click save 5. Return to edit again, you will see the value is not changed. -- 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] (GERONIMODEVTOOLS-784) EBA Auto-redeployment failed if not enabling hot swap
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMODEVTOOLS-784: - Summary: EBA Auto-redeployment failed if not enabling hot swap (was: Auto-redeployment failed if not enabling hot swap) EBA Auto-redeployment failed if not enabling hot swap - Key: GERONIMODEVTOOLS-784 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-2 Environment: Eclipse indigo sr1 sun java 6 Geronimo 3.0-beta-2-snapshot GEP trunk Reporter: Forrest Xia Priority: Critical Steps to reproduce this issue: 1. Having these stuffs installed: eclipse indigo sr1, geronimo web profile assembly 3.0-beta-2-snapshot build, GEP trunk build, IBM OSGi free tool 2. Import the attached EBA application into eclipse 3. Deploy this application into the server 4. Update the wab module to add a new jsp file 5. An auto-redeployment will happen to redeploy the changed project into the server, however, an error message shows as following: Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.getConfigID(Deployer.java:320) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) 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:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) ... If checked all options in Publish Advanced tab, then no such exception. -- 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] (GERONIMODEVTOOLS-784) EBA Auto-redeployment failed if not enabling hot swap
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMODEVTOOLS-784: - Attachment: org.apache.aries.samples.blueprint.helloworld.assembly_3.0.0.0.eba EBA Auto-redeployment failed if not enabling hot swap - Key: GERONIMODEVTOOLS-784 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-784 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-2 Environment: Eclipse indigo sr1 sun java 6 Geronimo 3.0-beta-2-snapshot GEP trunk Reporter: Forrest Xia Priority: Critical Attachments: org.apache.aries.samples.blueprint.helloworld.assembly_3.0.0.0.eba Steps to reproduce this issue: 1. Having these stuffs installed: eclipse indigo sr1, geronimo web profile assembly 3.0-beta-2-snapshot build, GEP trunk build, IBM OSGi free tool 2. Import the attached EBA application into eclipse 3. Deploy this application into the server 4. Update the wab module to add a new jsp file 5. An auto-redeployment will happen to redeploy the changed project into the server, however, an error message shows as following: Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module application/org.apache.aries.samples.blueprint.helloworld.assembly/3.0.0-0/eba already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.getConfigID(Deployer.java:320) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) 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:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) ... If checked all options in Publish Advanced tab, then no such exception. -- 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] (GERONIMODEVTOOLS-786) Failed deployment of EAR causes consistent error messages in eclipse following on
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMODEVTOOLS-786: - Attachment: DataCDInfo-JTA-ear-3.0.0.0.ear Failed deployment of EAR causes consistent error messages in eclipse following on - Key: GERONIMODEVTOOLS-786 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-786 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: Eclipse indigo SR1 x64 Sun JDK 1.6.0_29 Ubuntu 10.04 Reporter: Forrest Xia Attachments: DataCDInfo-JTA-ear-3.0.0.0.ear If you deployed the attached ear file into server via GEP, you will hit consistent error messages when doing other deployment work. -- 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-6267) Enable JSF 2.1 support for 3.0-beta and trunk
[ https://issues.apache.org/jira/browse/GERONIMO-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6267: -- Attachment: GERONIMO-6267_20120203.patch With patch GERONIMO-6267_20120203.patch, the server can compile and run, but fail lots of jcdi tck cases. Enable JSF 2.1 support for 3.0-beta and trunk - Key: GERONIMO-6267 URL: https://issues.apache.org/jira/browse/GERONIMO-6267 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: myfaces Affects Versions: 3.0, 3.0-beta-2 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Attachments: GERONIMO-6267_20120203.patch JSF 2.0 does not officially support Java 7, we might want to upgrade JSF to 2.1 to enable Java 7 support. Draft idea as following: 1. Use myfaces-bundle-2.1.5.jar directly 2. Upgrade GeronimoFactoryFinderProvider to support a new factory class FaceletCacheFactory 3. Run tck to see if any problem. -- 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-6267) Enable JSF 2.1 support for 3.0-beta and trunk
[ https://issues.apache.org/jira/browse/GERONIMO-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6267: -- Attachment: results.zip The attached results.zip is the jcdi tck results, totally there are 25 failures. Enable JSF 2.1 support for 3.0-beta and trunk - Key: GERONIMO-6267 URL: https://issues.apache.org/jira/browse/GERONIMO-6267 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: myfaces Affects Versions: 3.0, 3.0-beta-2 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Attachments: GERONIMO-6267_20120203.patch, results.zip JSF 2.0 does not officially support Java 7, we might want to upgrade JSF to 2.1 to enable Java 7 support. Draft idea as following: 1. Use myfaces-bundle-2.1.5.jar directly 2. Upgrade GeronimoFactoryFinderProvider to support a new factory class FaceletCacheFactory 3. Run tck to see if any problem. -- 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-5651) Add a own authenticator for Spnego login
[ https://issues.apache.org/jira/browse/GERONIMO-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5651: -- Affects Version/s: (was: 2.2.1) Add a own authenticator for Spnego login Key: GERONIMO-5651 URL: https://issues.apache.org/jira/browse/GERONIMO-5651 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Ashish Jain Assignee: Shenghao Fang Fix For: 3.0 Attachments: GERONIMO-5651.patch Continuation of GERONIMO-5196 for 2.2 and 3.0. -- 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-6258) HttpClient classloading problem while deploying ejb application
[ https://issues.apache.org/jira/browse/GERONIMO-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6258: -- Affects Version/s: (was: 3.0-M1) 3.0-beta-1 I modify the affected version to 3.0-beta-1 to reflect the truth. However, thank you for reporting this issue! HttpClient classloading problem while deploying ejb application --- Key: GERONIMO-6258 URL: https://issues.apache.org/jira/browse/GERONIMO-6258 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0-beta-1 Environment: Windows 64 bit and 32 bit Reporter: Michel Jonker Attachments: testForClassLoading.zip When I create ejb (or web) applications that contain the latest http client (4.1.2) I cannot make the application run succesfully on WAS CE 3.0 Deployment from Eclipse or through the Browser result in the same behaviour. I have added the jars through to the repository (The eclipse plugin recognizes them as such). More details can be found here http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14775203 I will also upload a sample eclipse project -- 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-6184) Upgrade PAX Logging
[ https://issues.apache.org/jira/browse/GERONIMO-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6184: -- Affects Version/s: 3.0-beta-1 Fix Version/s: 3.0-beta-2 3.0 Upgrade PAX Logging --- Key: GERONIMO-6184 URL: https://issues.apache.org/jira/browse/GERONIMO-6184 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Logging Affects Versions: 3.0, 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0, 3.0-beta-2 Upgrade to some recent version of PAX Logging to pick up latest changes and fixes. -- 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-6253) Improve parameter handling patch from tomcat community for G 2.2.1 release
[ https://issues.apache.org/jira/browse/GERONIMO-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6253: -- Description: We need a fix for Geronimo 2.2.1 release for the parameter handling issue from Tomcat community. (was: We need a fix for Geronimo 2.2.x release for the tomcat security patch of CVE-2011-4084.) Summary: Improve parameter handling patch from tomcat community for G 2.2.1 release (was: Tomcat security patch of CVE-2011-4084 for G 2.2.1 release) Improve parameter handling patch from tomcat community for G 2.2.1 release -- Key: GERONIMO-6253 URL: https://issues.apache.org/jira/browse/GERONIMO-6253 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.2, 2.2.1 Reporter: Forrest Xia We need a fix for Geronimo 2.2.1 release for the parameter handling issue from Tomcat community. -- 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-6242) Fork tomcat comet sample Chat to geronimo samples
[ https://issues.apache.org/jira/browse/GERONIMO-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6242: -- Affects Version/s: 3.0-beta-1 Fix Version/s: 3.0-beta-2 3.0 2.2.2 2.1.8 Fork tomcat comet sample Chat to geronimo samples --- Key: GERONIMO-6242 URL: https://issues.apache.org/jira/browse/GERONIMO-6242 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1, 2.2, 3.0, 3.0-beta-1 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 2.1.8, 2.2.2, 3.0, 3.0-beta-2 Fork tomcat example - Chat to geronimo samples to demonstrate Comet API Code source - http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/examples/ -- 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
[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
[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: resourceadapter outbound-resourceadapter connection-definition connectionfactory-interfacejavax.sql.DataSource/connectionfactory-interface connectiondefinition-instance nameBankPool/name config-property-setting name=Driverorg.apache.derby.jdbc.EmbeddedDriver/config-property-setting config-property-setting name=UserNameapp/config-property-setting config-property-setting name=Passwordapp/config-property-setting config-property-setting name=ConnectionURLjdbc:derby:BankDB;create=true/config-property-setting connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager /connectiondefinition-instance /connection-definition /outbound-resourceadapter /resourceadapter 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] [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-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. plugin groupIdorg.apache.rat/groupId artifactIdapache-rat-plugin/artifactId version0.7/version configuration includes includesrc/**/*/include includepom.xml/include /includes excludes exclude**/*/emptyfile1/exclude exclude**/*/goals.txt/exclude exclude**/*/hello.txt/exclude exclude**/*/RELEASE_NOTES-*.txt/exclude exclude**/*/MANIFEST.MF/exclude exclude.git/exclude exclude.gitignore/exclude /excludes /configuration executions execution phaseverify/phase goals goalcheck/goal /goals /execution /executions /plugin -- 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-6225) IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries
[ https://issues.apache.org/jira/browse/GERONIMO-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6225: -- Attachment: DonateEAR.ear JMSResources-plan_3.0.xml DonatePool-plan_3.0.xml VacationPool-plan_3.0.xml IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries -- Key: GERONIMO-6225 URL: https://issues.apache.org/jira/browse/GERONIMO-6225 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat, web Affects Versions: 3.0-beta-1 Reporter: Forrest Xia Labels: tomcat,deployment, web2.0, Attachments: DonateEAR.ear, DonatePool-plan_3.0.xml, JMSResources-plan_3.0.xml, VacationPool-plan_3.0.xml 1. Start geronimo server, 2. Deploy two derby net XA data sources with attached plan files VacationPool-plan_3.0.xml and DonatePool-plan_3.0.xml, 3. Deploy the JMS resources with geronimo-activemq-ra-version.rar and the attached plan file JMSResources-plan_3.0.xml, 4. Deploy the attached EAR, then you will see an exception in the admin console: The application was not deployed.The application was not deployed. java.lang.IllegalArgumentException org.apache.geronimo.common.DeploymentException: java.lang.IllegalArgumentException at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:279) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) Caused by: java.lang.IllegalArgumentException at java.net.URI.create(URI.java:853) at java.net.URI.resolve(URI.java:1039) at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) ... 12 more Caused by: java.net.URISyntaxException: Illegal character in path at index 39: dojox/data/demos/geography/Commonwealth of Australia/ at java.net.URI$Parser.fail(URI.java:2820) at java.net.URI$Parser.checkChars(URI.java:2993) at java.net.URI$Parser.parseHierarchical(URI.java:3077) at java.net.URI$Parser.parse(URI.java:3035) at java.net.URI.(URI.java:589) at java.net.URI.create(URI.java:851) ... 18 more -- 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-6225) IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries
[ https://issues.apache.org/jira/browse/GERONIMO-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6225: -- Attachment: cviewer-3.0.0.0_mod.war A simple app to reproduce this issue easily IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries -- Key: GERONIMO-6225 URL: https://issues.apache.org/jira/browse/GERONIMO-6225 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat, web Affects Versions: 3.0-beta-1 Reporter: Forrest Xia Labels: deployment,, tomcat,, web2.0, Attachments: DonateEAR.ear, DonatePool-plan_3.0.xml, JMSResources-plan_3.0.xml, VacationPool-plan_3.0.xml, cviewer-3.0.0.0_mod.war 1. Start geronimo server, 2. Deploy two derby net XA data sources with attached plan files VacationPool-plan_3.0.xml and DonatePool-plan_3.0.xml, 3. Deploy the JMS resources with geronimo-activemq-ra-version.rar and the attached plan file JMSResources-plan_3.0.xml, 4. Deploy the attached EAR, then you will see an exception in the admin console: The application was not deployed.The application was not deployed. java.lang.IllegalArgumentException org.apache.geronimo.common.DeploymentException: java.lang.IllegalArgumentException at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:279) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) Caused by: java.lang.IllegalArgumentException at java.net.URI.create(URI.java:853) at java.net.URI.resolve(URI.java:1039) at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) ... 12 more Caused by: java.net.URISyntaxException: Illegal character in path at index 39: dojox/data/demos/geography/Commonwealth of Australia/ at java.net.URI$Parser.fail(URI.java:2820) at java.net.URI$Parser.checkChars(URI.java:2993) at java.net.URI$Parser.parseHierarchical(URI.java:3077) at java.net.URI$Parser.parse(URI.java:3035) at java.net.URI.(URI.java:589) at java.net.URI.create(URI.java:851) ... 18 more -- 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-6220) Doc JBoss to Geronimo - Hibernate Migration for 3.0 needs update with JBoss v7
[ https://issues.apache.org/jira/browse/GERONIMO-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6220: -- Description: This doc: https://cwiki.apache.org/GMOxDOC30/jboss-to-geronimo-hibernate-migration.html It's better to update it with JBoss v7 to G 3.0. was: This doc: https://cwiki.apache.org/GMOxDOC30/jboss-to-geronimo-hibernate-migration.html It's better to update it with JBoss v7 to CE 3.0. Doc JBoss to Geronimo - Hibernate Migration for 3.0 needs update with JBoss v7 Key: GERONIMO-6220 URL: https://issues.apache.org/jira/browse/GERONIMO-6220 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0 Reporter: Forrest Xia Priority: Minor This doc: https://cwiki.apache.org/GMOxDOC30/jboss-to-geronimo-hibernate-migration.html It's better to update it with JBoss v7 to G 3.0. -- 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-6200) NPE when using Plan Creator to create a plan for daytrader.ear
[ https://issues.apache.org/jira/browse/GERONIMO-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6200: -- Attachment: daytrader-ear-3.0.0.0.ear NPE when using Plan Creator to create a plan for daytrader.ear Key: GERONIMO-6200 URL: https://issues.apache.org/jira/browse/GERONIMO-6200 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: windows 7 x86-32 oracle jdk 6 Reporter: Forrest Xia Priority: Minor Attachments: daytrader-ear-3.0.0.0.ear Steps: 1. Start server and login admin console 2. Click plan creator and select the attached daytrader app, then click next An NullPointerException throws out as following: javax.el.ELException: Error reading 'deploymentPlan' on type org.apache.geronimo.console.configcreator.configData.EARConfigData at javax.el.BeanELResolver.getValue(BeanELResolver.java:68) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:58) at org.apache.el.parser.AstValue.getValue(AstValue.java:169) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:189) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:985) at jsp.WEB_002dINF.view.configcreator.enterpriseApp_jsp._jspService(enterpriseApp_jsp.java:203) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530) at org.apache.pluto.container.impl.PortletRequestDispatcherImpl.doDispatch(PortletRequestDispatcherImpl.java:174) at org.apache.pluto.container.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:227) at org.apache.geronimo.console.MultiPagePortlet.doView(MultiPagePortlet.java:151) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340) at org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117) at org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:108) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
[jira] [Updated] (GERONIMO-6201) Bundle cannot be resolved when starting a custom server assembly
[ https://issues.apache.org/jira/browse/GERONIMO-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6201: -- Attachment: cviewer-3.0.0.0.war Bundle cannot be resolved when starting a custom server assembly Key: GERONIMO-6201 URL: https://issues.apache.org/jira/browse/GERONIMO-6201 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0-beta-1 Environment: Windows 7 oracle jdk 6 32bit Reporter: Forrest Xia Assignee: Saphen Qiu Priority: Minor Attachments: cviewer-3.0.0.0.war Steps: 1. Start server and login admin console 2. deploy the attached sample app 3. Use Plugins portlet to assemble a server 4. Start the custom server 5. Server started with an exception like this: Module 17/19 org.apache.geronimo.configs/webservices-common/3.0-w20110721/car 2011-10-21 17:34:17,688 WARN [DependencyManager] Could not start bundle: or g.apache.geronimo.bundles.axis2-saaj_1.6.1.w20110801_1 [202] org.osgi.framework.BundleException: The bundle org.apache.geronimo.bundles.axis 2-saaj_1.6.1.w20110801_1 [202] could not be resolved. Reason: Missing Constrain t: Import-Package: org.apache.axis2; version=1.6.0 at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverEr ror(AbstractBundle.java:1327) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolution FailureException(AbstractBundle.java:1311) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:299) at org.apache.geronimo.system.configuration.DependencyManager.starting(D ependencyManager.java:487) at org.apache.geronimo.system.configuration.DependencyManager.bundleChan ged(DependencyManager.java:116) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEv ent(BundleContextImpl.java:847) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventM anager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchr onous(ListenerQueue.java:148) at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent Privileged(Framework.java:1523) at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent (Framework.java:1459) at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent (Framework.java:1454) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:367) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:299) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf iguration(SimpleConfigurationManager.java:311) at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaem on.java:209) at org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon .java:93) at org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator .java:107) at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:67) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) 2011-10-21 17:34:17,734 WARN [DependencyManager] Could not start bundle: org.ap ache.geronimo.bundles.axis2_1.6.1.w20110801_1 [203] org.osgi.framework.BundleException: The bundle org.apache.geronimo.bundles.axis 2_1.6.1.w20110801_1 [203] could not be resolved. Reason: Missing Constraint: Im port-Package: org.apache.commons.fileupload; version=0.0.0, Missing Constraint : Import-Package: org.apache.axis2.saaj; version=0.0.0 at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverEr ror(AbstractBundle.java:1327) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolution FailureException(AbstractBundle.java:1311) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac tBundle.java:299) at org.apache.geronimo.system.configuration.DependencyManager.starting(D ependencyManager.java:487) at org.apache.geronimo.system.configuration.DependencyManager.bundleChan ged(DependencyManager.java:116) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEv ent(BundleContextImpl.java:847) at
