[jira] Assigned: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central
[ https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom reassigned GERONIMO-5309: --- Assignee: Matt Hogstrom Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central - Key: GERONIMO-5309 URL: https://issues.apache.org/jira/browse/GERONIMO-5309 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Anders Hammar Assignee: Matt Hogstrom The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven. Suggested action: 1. Verify the pom at the Apache repo (against the one in svn) 2. Resign and deploy to the Apache repo 3. It should now be synced to central You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central
[ https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12869682#action_12869682 ] Matt Hogstrom commented on GERONIMO-5309: - Here are the list of artifacts in quesition: genesis-1.2-site.xml 31-Jul-2007 22:24 757 genesis-1.2-site.xml.md5 31-Jul-2007 22:24 32 genesis-1.2-site.xml.sha1 31-Jul-2007 22:24 40 genesis-1.2.pom31-Jul-2007 22:16 11097 genesis-1.2.pom.asc31-Jul-2007 22:24 186 genesis-1.2.pom.asc.asc31-Jul-2007 22:24 186 genesis-1.2.pom.asc.asc.md531-Jul-2007 22:24 32 genesis-1.2.pom.asc.asc.sha1 31-Jul-2007 22:24 40 genesis-1.2.pom.asc.md531-Jul-2007 22:24 32 genesis-1.2.pom.asc.sha1 31-Jul-2007 22:24 40 genesis-1.2.pom.md531-Jul-2007 22:16 32 genesis-1.2.pom.sha1 31-Jul-2007 22:16 40 It looks like the tool used to generate the signatures ran a little awry and signed signatures and basically didn't work correctly. Also, I don't think these artifacts need to be signed. I'll drop a note to Brian to ask for them to be removed. Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central - Key: GERONIMO-5309 URL: https://issues.apache.org/jira/browse/GERONIMO-5309 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Anders Hammar Assignee: Matt Hogstrom The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven. Suggested action: 1. Verify the pom at the Apache repo (against the one in svn) 2. Resign and deploy to the Apache repo 3. It should now be synced to central You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4558) Update to latest TranQL DB2 driver
[ https://issues.apache.org/jira/browse/GERONIMO-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680291#action_12680291 ] Matt Hogstrom commented on GERONIMO-4558: - David, Is this the error you refer to above: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: MKACTIVITY of '/tranql/!svn/act/267144dd-85be-49fe-bb85-b9e2d45ea60b': authorization failed (https://svn.codehaus.org) If so, please feel free to release it although I'd like to know if there is a way to fix it. Thanks. Update to latest TranQL DB2 driver -- Key: GERONIMO-4558 URL: https://issues.apache.org/jira/browse/GERONIMO-4558 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Fix For: 2.1.4, 2.2 Matt has pushed out a new TranQL driver for DB2 XA. We should pick it up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3718) ResourceRef lookups are now really slow
[ https://issues.apache.org/jira/browse/GERONIMO-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554318 ] Matt Hogstrom commented on GERONIMO-3718: - I'll give it a spin. ResourceRef lookups are now really slow --- Key: GERONIMO-3718 URL: https://issues.apache.org/jira/browse/GERONIMO-3718 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector, naming Affects Versions: 2.0.x, 2.1 Reporter: David Jencks Assignee: Matt Hogstrom Fix For: 2.1 Attachments: GERONIMO-3718-1.patch, GERONIMO-3718-2.patch, GERONIMO-3718-3.patch We had to turn off jndi reference lookup result caching since the tck is now testing that e.g. datasource lookups give you a different object each time. Some of Matt's performance tests indicate that finding the MCFWrapper gbean takes an inordinate amount of time. One possibility is to, instead of caching the lookup result, look up the gbean when the jndi tree is set up for the javaee component. Calling e.g. $getResource() is then as fast as the resource adapter makes it to get a new connection factory. This needs a few changes in both naming and connector and connector-builder. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3520) missing jsr-77 stats for JTA
[ https://issues.apache.org/jira/browse/GERONIMO-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533925 ] Matt Hogstrom commented on GERONIMO-3520: - Viet, for the txmanager patch I think there may be an issue with the use of the static long. Since the access is not synchronized there exists a strong possibility of lost updates in a heavily concurrent system which would lead to inaccurate values. volatile is one way to address this problem but I don't think it is perfect on all VMs so I think the better solution would be the use of java.util.concurrent.atomic.AtomicLong .getAndIncrement() which should do the trick. Not sure of other folks have suggestions. missing jsr-77 stats for JTA Key: GERONIMO-3520 URL: https://issues.apache.org/jira/browse/GERONIMO-3520 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring, transaction manager Affects Versions: 2.0.2, 2.1 Environment: linux Reporter: Viet Hung Nguyen Attachments: geronimo-3520.patch, jms-mdb-sample-ear-2.0-SNAPSHOT.ear, txmanagerStats.patch we need to surface transaction statistics defined by the JSR 77 spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAYTRADER-57) Enhance Configuration by pre-populating the Max Users and Max Quotes based on database cardinality
Enhance Configuration by pre-populating the Max Users and Max Quotes based on database cardinality -- Key: DAYTRADER-57 URL: https://issues.apache.org/jira/browse/DAYTRADER-57 Project: DayTrader Issue Type: Improvement Affects Versions: 2.0 Environment: All Reporter: Matt Hogstrom Priority: Trivial Fix For: 2.0 Currently DayTrader defaults to a maximum number of users of 200 and maximum quotes of 400. If these values are changed and the server is restarted then the changes are lost. Many primitives rely on this information for performance testing. To simplify the testers life the configuration system will query the database for the cardinality of the current user and quote population. This value will become the default. If the database is not populated then the default will be set to 500 / 1000 and a warning message will be issued on the configuration panel. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3465) Default log level needs to be tweaked to provide more useful information to users
[ https://issues.apache.org/jira/browse/GERONIMO-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526496 ] Matt Hogstrom commented on GERONIMO-3465: - Donald, personally I don't like lots of gorp coming out so I expect whatever we choose someone will be unhappy. I'd suggest a vote to gather community consensus and let's make that the default going forward. Would you like to do this ? Default log level needs to be tweaked to provide more useful information to users - Key: GERONIMO-3465 URL: https://issues.apache.org/jira/browse/GERONIMO-3465 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.1 Reporter: Kevan Miller Priority: Critical Fix For: 2.0.2, 2.1 default log level is currently ERROR. This is too strict for many users. We should default to being more verbose and provide useful information to new Geronimo users/developers. Users who want less verbose output can tune their server-log4j properties accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3389) console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector
[ https://issues.apache.org/jira/browse/GERONIMO-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520317 ] Matt Hogstrom commented on GERONIMO-3389: - Perhaps this should be relabeled enhancement and we can catch this exception and put out a note saying the libraries can't be found rather than the stack trace :) console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector - Key: GERONIMO-3389 URL: https://issues.apache.org/jira/browse/GERONIMO-3389 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation, Tomcat Affects Versions: 2.0, 2.0.x, 2.1 Environment: Windows xp sp2, IE, Firefox Reporter: Song Fix For: 2.0.x Click on Save button after entering all necessary parameters for creating a new Tomcat APR HTTP Connector test_APR_HTTP, it returned to the Network Listeners list page. However,the Protocol for test_APR_HTTP is empty, State is failed. And java.lang.UnsatisfiedLinkError is thrown from the server started console and server.log. Same error to creating Tomcat APR HTTPS Connetor. Detailed error as below: -- 13:33:46,515 WARN [ConnectorGBean] test_APR_HTTP connector failed 13:33:46,515 ERROR [Connector] Coyote connector has not been started 13:33:46,515 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car,j2eeType=GBean,name=test_APR_HTTP java.lang.UnsatisfiedLinkError: org/apache/tomcat/jni/Pool.create(J)J at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:579) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) at org.apache.catalina.connector.Connector.initialize(Connector.java:1059) at org.apache.catalina.core.StandardService.addConnector(StandardService.java:267) at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:327) at org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:383) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$fa3733e1.addConnector(generated) at org.apache.geronimo.tomcat.connector.ConnectorGBean.doStart(ConnectorGBean.java:95) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.connector.Http11APRProtocol$$EnhancerByCGLIB$$abc46ac2.startRecursive(generated) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:146) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at
[jira] Updated: (GERONIMO-3389) console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector
[ https://issues.apache.org/jira/browse/GERONIMO-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-3389: Issue Type: Improvement (was: Bug) We should catch this since we know what it is and give a human readable explanation. console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector - Key: GERONIMO-3389 URL: https://issues.apache.org/jira/browse/GERONIMO-3389 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: documentation, Tomcat Affects Versions: 2.0, 2.0.x, 2.1 Environment: Windows xp sp2, IE, Firefox Reporter: Song Fix For: 2.0.x Click on Save button after entering all necessary parameters for creating a new Tomcat APR HTTP Connector test_APR_HTTP, it returned to the Network Listeners list page. However,the Protocol for test_APR_HTTP is empty, State is failed. And java.lang.UnsatisfiedLinkError is thrown from the server started console and server.log. Same error to creating Tomcat APR HTTPS Connetor. Detailed error as below: -- 13:33:46,515 WARN [ConnectorGBean] test_APR_HTTP connector failed 13:33:46,515 ERROR [Connector] Coyote connector has not been started 13:33:46,515 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car,j2eeType=GBean,name=test_APR_HTTP java.lang.UnsatisfiedLinkError: org/apache/tomcat/jni/Pool.create(J)J at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:579) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) at org.apache.catalina.connector.Connector.initialize(Connector.java:1059) at org.apache.catalina.core.StandardService.addConnector(StandardService.java:267) at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:327) at org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:383) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$fa3733e1.addConnector(generated) at org.apache.geronimo.tomcat.connector.ConnectorGBean.doStart(ConnectorGBean.java:95) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.connector.Http11APRProtocol$$EnhancerByCGLIB$$abc46ac2.startRecursive(generated) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:146) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at
[jira] Updated: (GERONIMO-3401) Stop of module from System Modules in console should warn user of destructive action
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom updated GERONIMO-3401:
Issue Type: Improvement (was: Bug)
Summary: Stop of module from System Modules in console should warn
user of destructive action (was: Stop of module from System Modules in
console fails)
Stop of module from System Modules in console should warn user of
destructive action
--
Key: GERONIMO-3401
URL: https://issues.apache.org/jira/browse/GERONIMO-3401
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Affects Versions: 2.0, 2.0.x
Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
likely affects others as well
Reporter: Matt Hogstrom
Fix For: 2.0.x
When using the Geronimo Console to stop of a module a 404 is received in the
console. In this case an attempt to stop OpenEJB. The console then becomes
unusable and also does not survive a restart. It appears the console needs
to be re-installed.
{panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
HTTP Status 404 -
/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
type Status report
message
/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
description The requested resource
(/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
is not available.
{panel}
{panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
[] received stop signal
00:59:03,833 ERROR [Servlet] Exception caught:
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
to gbean:
org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit(generated)
at
org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
at
org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
at
org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
at
org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
at
org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
at
org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
at
org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
at
org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
at
org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
[jira] Created: (GERONIMO-3401) Stop of module from System Modules in console fails
Stop of module from System Modules in console fails
-
Key: GERONIMO-3401
URL: https://issues.apache.org/jira/browse/GERONIMO-3401
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0, 2.0.x
Environment: Geronimo 2.0.1-SNAPSHOT using Tomcat JEE assembly. Most
likely affects others as well
Reporter: Matt Hogstrom
Fix For: 2.0.x
When using the Geronimo Console to stop of a module a 404 is received in the
console. In this case an attempt to stop OpenEJB. The console then becomes
unusable and also does not survive a restart. It appears the console needs to
be re-installed.
{panel:title=Error reported to Browser| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
HTTP Status 404 -
/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
type Status report
message
/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view
description The requested resource
(/console/portal/apps/apps_system/_st_apps_system_row1_col1_p1/normal/_rp_apps_system_row1_col1_p1_message/1_/_pid/apps_system_row1_col1_p1/_md_apps_system_row1_col1_p1/view)
is not available.
{panel}
{panel:title=Exception LoggedMy Title| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
[] received stop signal
00:59:03,833 ERROR [Servlet] Exception caught:
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
to gbean:
org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction/2.0.1-SNAPSHOT/car,j2eeType=JCAConnectionTracker,name=ConnectionTracker
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$4301e6fc.exit(generated)
at
org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.after(InstanceContextBeforeAfter.java:73)
at
org.apache.geronimo.tomcat.interceptor.ComponentContextBeforeAfter.after(ComponentContextBeforeAfter.java:46)
at
org.apache.geronimo.tomcat.interceptor.PolicyContextBeforeAfter.after(PolicyContextBeforeAfter.java:70)
at
org.apache.geronimo.tomcat.interceptor.UserTransactionBeforeAfter.after(UserTransactionBeforeAfter.java:47)
at
org.apache.geronimo.tomcat.listener.DispatchListener.afterDispatch(DispatchListener.java:86)
at
org.apache.geronimo.tomcat.listener.DispatchListener.instanceEvent(DispatchListener.java:59)
at
org.apache.catalina.util.InstanceSupport.fireInstanceEvent(InstanceSupport.java:275)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:682)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
at
org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
at
org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
at
org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
[jira] Closed: (GERONIMO-3368) Axis2ClientConfigurationFactory not always being used in certain platforms
[ https://issues.apache.org/jira/browse/GERONIMO-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3368. --- Closing as it has been resolved and committed. Axis2ClientConfigurationFactory not always being used in certain platforms -- Key: GERONIMO-3368 URL: https://issues.apache.org/jira/browse/GERONIMO-3368 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0 Reporter: Lin Sun Assignee: Jarek Gawor Fix For: 2.0 Attachments: G-3368.patch On Windows 2003 Linux, GBean TomcatWebAppContext will be started before Axis2ConfigGBean. Class org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl will be loaded when the geronimo kernel starts TomcatWebAppContext, look at the following codes in DescriptionFactoryImpl: private static ClientConfigurationFactory clientConfigFactory = ClientConfigurationFactory.newInstance(); This will make class DescriptionFactoryImpl can not load Axis2ClientConfigurationFactory which is registered into MetadataFactoryRegistry in Axis2ConfigGBean. So DescriptionFactoryImpl still use the old ClientConfigurationFactory, not Axis2ClientConfigurationFactory. On Windows XP, GBean TomcatWebAppContext will be started after Axis2ConfigGBean so the client configurationcontext is working as expected. GBean TomcatWebAppContext and Axis2ConfigGBean have the same priority, it's not mandatory for geronimo kernel to start Axis2ConfigGBean firstly. The patch will set priority of Axis2ConfigGBean as GBeanInfo.PRIORITY_CLASSLOADER. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3365) config.xml condition vs. load attribute issues
[
https://issues.apache.org/jira/browse/GERONIMO-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom closed GERONIMO-3365.
---
Assignee: Jarek Gawor
Closing as it has been resolved and committed.
config.xml condition vs. load attribute issues
--
Key: GERONIMO-3365
URL: https://issues.apache.org/jira/browse/GERONIMO-3365
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M7
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Priority: Critical
Fix For: 2.0
The initial config.xml contains the following condition:
module condition=props.getProperty('org.apache.geronimo.jaxws.provider',
'axis2') == 'axis2'
name=org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car
But after the server is started and stopped for the first time this entry is
rewritten as:
module condition=props.getProperty('org.apache.geronimo.jaxws.provider',
'axis2') == 'axis2' load=false
name=org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car
The 'load' attribute is added which invalidates the specified condition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3352) Upgrade to Jetty 6.1.5 (just released) for Geronimo 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3352. --- Closing as it has been resolved and committed. Upgrade to Jetty 6.1.5 (just released) for Geronimo 2.0 --- Key: GERONIMO-3352 URL: https://issues.apache.org/jira/browse/GERONIMO-3352 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.0 There are some problems that are fixed in Jetty 6.1.5 that are needed for Geronimo and we need a stable release for our Geronimo 2.0 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3332) POJO Web-services under Geronimo fail with arrays as method call arguments
[
https://issues.apache.org/jira/browse/GERONIMO-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom closed GERONIMO-3332.
---
Closing as the problem could not be recreated.
POJO Web-services under Geronimo fail with arrays as method call arguments
--
Key: GERONIMO-3332
URL: https://issues.apache.org/jira/browse/GERONIMO-3332
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: webservices
Affects Versions: 2.0-M6
Environment: Windows XP Pro SP2, Sun JSDK 1.5._07,
geronimo-tomcat6-jee5-2.0-M6-rc1
Reporter: Alexei Kozich
Assignee: Jarek Gawor
Fix For: 2.0
We created POJO web sevice like following:
@WebService
@SOAPBinding(style = Style.RPC, use = Use.LITERAL)
public interface PartInventoryWs {
@WebMethod
public Integer completeReplenishOrders(
@WebParam(name = orderIds)
ListString orderIds);
}
in web.xml we defined servlet mapping in order to call this web-service like
following:
servlet-mapping
servlet-namePartInventoryWs/servlet-name
url-pattern/partinventory/url-pattern
/servlet-mapping
servlet
servlet-namePartInventoryWs/servlet-name
servlet-classdemocrm.webservice.shop.PartInventoryWsImpl/servlet-class
/servlet
So everything is deployed fine and we can access wsdl document by opening
URL: http://localhost:8080/.../partinventory?wsdl.
But this webservice fails when I try to invoke method and pass to it array of
Strings (I generated client classes by
the Apache Axis 1.3 Oct 05, 2005 (05:23:37 EDT) WSDL2Java emitter) :
(see string HTTP/1.1 500 Internal Server Error in the below debug log).
2007-07-18 14:53:16,812 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(engineFactory)
2007-07-18 14:53:16,812 DEBUG
org.apache.axis.configuration.EngineConfigurationFactoryFinder Got
EngineFactory: org.apache.axis.configuration.EngineConfigurationFactoryDefault
2007-07-18 14:53:16,812 DEBUG org.apache.axis.AxisEngine Enter:
AxisEngine::init
2007-07-18 14:53:17,031 DEBUG org.apache.axis.AxisEngine Exit:
AxisEngine::init
2007-07-18 14:53:17,031 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(transport00)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call Transport is
[EMAIL PROTECTED]
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call Enter:
Call::invoke(ns, meth, args)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call
operation=name:completeReplenishOrders
returnQName: null
returnType: {http://xml.apache.org/axis/}Void
returnClass: null
elementQName:null
soapAction: null
style: rpc
use: literal
numInParams: 1
method:null
ParameterDesc[0]:
name: orderIds
typeEntry: null
mode: IN
position: 0
isReturn: false
typeQName: {http://jaxb.dev.java.net/array}stringArray
javaType: class [Ljava.lang.String;
inHeader: false
outHeader: false
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call
operation.getNumParams()=1
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call getParamList
number of params: 1
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call Enter:
Call::invoke(RPCElement)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.SOAPPart Enter: SOAPPart
ctor(FORM_SOAPENVELOPE)
2007-07-18 14:53:17,031 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(setMsgForm)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.SOAPPart Setting current
message form to: FORM_SOAPENVELOPE (currentMessage is now
org.apache.axis.message.SOAPEnvelope)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.SOAPPart Exit: SOAPPart
ctor()
2007-07-18 14:53:17,031 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(addBody00)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.message.SOAPBody Adding
body element to message...
2007-07-18 14:53:17,031 DEBUG org.apache.axis.client.Call Enter:
Call::invoke()
2007-07-18 14:53:17,031 DEBUG org.apache.axis.MessageContext
MessageContext: setTargetService(PartInventoryWsImplPort)
2007-07-18 14:53:17,031 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(noService10)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.SOAPPart Enter:
SOAPPart::getAsSOAPEnvelope()
2007-07-18 14:53:17,031 DEBUG
org.apache.axis.i18n.ProjectResourceBundle
org.apache.axis.i18n.resource::handleGetObject(currForm)
2007-07-18 14:53:17,031 DEBUG org.apache.axis.SOAPPart current form is
FORM_SOAPENVELOPE
[jira] Closed: (GERONIMO-3196) ConcurrentModificationException in ?wsdl processing
[ https://issues.apache.org/jira/browse/GERONIMO-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3196. --- Closing per Jarek's comments. ConcurrentModificationException in ?wsdl processing --- Key: GERONIMO-3196 URL: https://issues.apache.org/jira/browse/GERONIMO-3196 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.0 java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841) at java.util.HashMap$EntryIterator.next(HashMap.java:883) at java.util.HashMap$EntryIterator.next(HashMap.java:881) at org.apache.geronimo.cxf.GeronimoQueryHandler.updatePorts(GeronimoQueryHandler.java:93) at org.apache.geronimo.cxf.GeronimoQueryHandler.updateServices(GeronimoQueryHandler.java:73) at org.apache.geronimo.cxf.GeronimoQueryHandler.updateDefinition(GeronimoQueryHandler.java:55) at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:130) at org.apache.geronimo.cxf.CXFWebServiceContainer.getWsdl(CXFWebServiceContainer.java:118) at org.apache.geronimo.webservices.WebServiceContainerInvoker.service(WebServiceContainerInvoker.java:74) at org.apache.geronimo.webservices.POJOWebServiceServlet.service(POJOWebServiceServlet.java:79) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098) at com.sun.ts.tests.jaxws.wsi.w2j.document.literal.swatest.CheckHttpMimeHeadersFilter.doFilter(CheckHttpMimeHeadersFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58) at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:510) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3305) Out Of Memory Error when Running DayTrader in WebServices Mode
[
https://issues.apache.org/jira/browse/GERONIMO-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom closed GERONIMO-3305.
---
Close pending Jarek's comments and changes.
Out Of Memory Error when Running DayTrader in WebServices Mode
--
Key: GERONIMO-3305
URL: https://issues.apache.org/jira/browse/GERONIMO-3305
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: Jarek Gawor
Fix For: 2.0
I deployed DayTrader 2.0 on the latest SVN rev 554753 of trunk.
I deploy daytrader-ear-2.0-SNAPSHOT.ear (using the
daytrader-g-2.0-SNAPSHOT-plan.xml in ${DT}/trunk/plans
Create the tables and populate them in the config section.
Switch to WebServices mode
Log in and do portfolio, quotes, buy and sell a few stocks and then logoff.
Try to log in again and I get:
10:34:34,089 ERROR [Log] Error: JSR 109 lookup failed .. defaulting to JSR 101
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:65)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getPortFromFactory(TradeWebSoapProxy.java:67)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getTrade(TradeWebSoapProxy.java:47)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getAccountData(TradeWebSoapProxy.java:122)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doHome(TradeServletAction.java:277)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doLogin(TradeServletAction.java:372)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.performTask(TradeAppServlet.java:126)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.doPost(TradeAppServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.geronimo.samples.daytrader.web.OrdersAlertFilter.doFilter(OrdersAlertFilter.java:91)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
at
[jira] Closed: (GERONIMO-3353) Adjust server log4j files to use a default logging level of error instead of info before releasing.
[ https://issues.apache.org/jira/browse/GERONIMO-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3353. --- Resolution: Fixed Changed default to: Committed revision 563399. Adjust server log4j files to use a default logging level of error instead of info before releasing. --- Key: GERONIMO-3353 URL: https://issues.apache.org/jira/browse/GERONIMO-3353 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Reporter: Matt Hogstrom Assignee: Matt Hogstrom Fix For: 2.0 The title says it all. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2581) Update Version Numbers of Dependent Projects for Geronimo Version 2.0
[ https://issues.apache.org/jira/browse/GERONIMO-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2581. --- Resolution: Fixed Version changes complete for 2.0. Update Version Numbers of Dependent Projects for Geronimo Version 2.0 - Key: GERONIMO-2581 URL: https://issues.apache.org/jira/browse/GERONIMO-2581 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 2.0-M5 Environment: All Reporter: Matt Hogstrom Assignee: Matt Hogstrom Fix For: 2.0 This is a master record for dependent JIRAs for updating various version numbers of supporting project of o.a.g. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1567) Plan XML files aren't included in Geronimo distributions (was included in M5 release)
[ https://issues.apache.org/jira/browse/GERONIMO-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-1567: Fix Version/s: (was: 2.0) 2.0.x Moving to 2.0.x Plan XML files aren't included in Geronimo distributions (was included in M5 release) - Key: GERONIMO-1567 URL: https://issues.apache.org/jira/browse/GERONIMO-1567 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 1.0 Reporter: John Sisson Assignee: Jason Dillon Fix For: 2.0.x It was a combination of an oversight and the idea that being able to add gbeans using config.xml could replace the need to modify and redeploy the plans we supply. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-807) Better handling for system log viewer portlet render requests
[ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-807. -- Resolution: Fixed Applied patch and tested and it works. The text for criteria is still wiped out when navigating to different portlets. Given the longevity of this issue I'm going to close it and open a separate issue to be tracked independently. Thanks Rakesh! Better handling for system log viewer portlet render requests - Key: GERONIMO-807 URL: https://issues.apache.org/jira/browse/GERONIMO-807 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, usability Affects Versions: 1.0-M5 Reporter: Aaron Mulder Assignee: Rakesh Midha Priority: Minor Fix For: 2.0 Attachments: jira807.patch If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings. It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2025) Undeploy and redeploy with no version leaves dangling entries in config.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2025: Fix Version/s: (was: 2.0) 2.0.x Moving to 2.0.x Undeploy and redeploy with no version leaves dangling entries in config.xml --- Key: GERONIMO-2025 URL: https://issues.apache.org/jira/browse/GERONIMO-2025 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, kernel Affects Versions: 1.1 Reporter: Aaron Mulder Assignee: Rakesh Midha Fix For: 2.0.x Attachments: removeunwantedconfig.patch If you deploy an application with no version and then undeploy it, we leave an entry for it (with a timestamp version number) in config.xml, just marked as load=false. If you later deploy the application again, you get a new timestamp version number and a new entry is written into config.xml. Do this (undeploy/deploy) a few times and config.xml gets kind of messy. It would be be good to delete entries from config.xml on undeploy if they have no actual settings. It would be good to detect that a previous version is in conifg.xml but not in the repository and delete the settings from config.xml if the artifact has no version number and a newer copy is deployed. This is not a huge priority since nothing breaks, it just makes config.xml kind of crufty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1907) Deploy command should redeploy if the app is already deployed
[ https://issues.apache.org/jira/browse/GERONIMO-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-1907: Fix Version/s: (was: 1.x) (was: 2.0) 2.0.x Moving to 2.0.x Deploy command should redeploy if the app is already deployed - Key: GERONIMO-1907 URL: https://issues.apache.org/jira/browse/GERONIMO-1907 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment, usability Affects Versions: 1.1 Reporter: Aaron Mulder Assignee: Rakesh Midha Priority: Critical Fix For: 2.0.x Attachments: redeploy.patch Attached patch, and changing fix version to 1.2. Also unassigning so that committers can review and update. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2884) JNDI Name Not Correct
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2884: Fix Version/s: (was: 2.0) 2.0.x JNDI Name Not Correct - Key: GERONIMO-2884 URL: https://issues.apache.org/jira/browse/GERONIMO-2884 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Environment: Linux Reporter: Tom Purcell Assignee: David Blevins Fix For: 2.0.x I was asked to open this issue by David Blevins following this Nabble exchange: http://www.nabble.com/InitialContext-JNDI-Lookup-tf3273209s2756.html The issue is that the JNDI entry under which an ejb's remote business interface is registered is constructed as: deploymentId/BeanNameBussinessRemote instead of ejb.jar file name/BeanNameBussinessRemote this results in an entry that looks like this: geronimo-deploymentUtil5840.tmpdir/ConferenceCallSchedulerBeanBusinessRemote The main problem with this is that the number part of the deployment id (5840 in the above) will be different on each redeploy making it difficult for a client app to find. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3059) CLIs refactoring - options and arguments parsing should be done prior the boot of a Kernel to provide a quicker feedback to users if they are invalid
[ https://issues.apache.org/jira/browse/GERONIMO-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3059. --- Resolution: Fixed Looks like this has been fixed. CLIs refactoring - options and arguments parsing should be done prior the boot of a Kernel to provide a quicker feedback to users if they are invalid - Key: GERONIMO-3059 URL: https://issues.apache.org/jira/browse/GERONIMO-3059 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: usability Affects Versions: 2.0-M4 Reporter: Gianny Damour Assignee: Gianny Damour Fix For: 2.0 Attachments: GERONIMO-3059.patch CLIs options and arguments are parsed after the boot of a Kernel. As the boot of a Kernel, and especially the loading of configurations, are time expensive, users have to wait an unacceptable time to receive a feedback from CLs if these options or arguments are invalid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3089) geronimo-activemq-ra's ra.xml is missing several config-property elements
[ https://issues.apache.org/jira/browse/GERONIMO-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-3089: Fix Version/s: (was: 1.2) (was: 2.0) 2.0.x Good candidate for a 2.0.1. geronimo-activemq-ra's ra.xml is missing several config-property elements - Key: GERONIMO-3089 URL: https://issues.apache.org/jira/browse/GERONIMO-3089 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 2.0.x Several configuration properties which are listed ( http://activemq.apache.org/resource-adapter-properties.html ) are not actually configurable in the normal J2EE/JavaEE ra way as the ra.xml is missing config-property elements to define them as configurable. Specifically these documented properties are missing: * AllPrefetchValues * DurableTopicPrefetch * QueuePrefetch * InputStreamPrefetch * TopicPrefetch * InitialRedeliveryDelay * MaximumRedeliveries * RedeliveryBackOffMultiplier * RedeliveryUseExponentialBackOff Should also double check the org.apache.activemq.ra.ActiveMQResourceAdapter class for any other properties which may be missing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3324) Could not scan module for TLD files: illegal char (space)
[ https://issues.apache.org/jira/browse/GERONIMO-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-3324: Fix Version/s: (was: 2.0) 2.0.x Moving to 2.0.x as there are other small bugs that need to be fixed. Could not scan module for TLD files: illegal char (space) - Key: GERONIMO-3324 URL: https://issues.apache.org/jira/browse/GERONIMO-3324 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M6 Environment: Little-G on WinXP with Java 1.5.0_11 Reporter: Jens Nicolay Assignee: Tim McConnell Priority: Blocker Fix For: 2.0.x Attachments: WAR.war 16:25:24,033 ERROR [Deployer] Deployment failed due to org.apache.geronimo.common.DeploymentException: Could not scan module for TLD files: default/WAR/1.0/car Illegal character in path at index 16: WEB-INF/lib/Easy Service.jar at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.scanModule(JspModuleBuilderExtension.java:298) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getTldFiles(JspModuleBuilderExtension.java:236) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.createJspClassFinder(JspModuleBuilderExtension.java:179) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGBeans(JspModuleBuilderExtension.java:149) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension$$FastClassByCGLIB$$1f60ab3b.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:828) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilderExtension$$EnhancerByCGLIB$$cd133fa9.addGBeans(generated) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:484) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder$$FastClassByCGLIB$$1a00be84.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:828) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$57321d6a.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:828) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$57321d6a.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:616) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at
[jira] Closed: (GERONIMO-3337) Deploy of servlet-examples-tomcat-2.0-SNAPSHOT.car fails due to existing config.ser
[ https://issues.apache.org/jira/browse/GERONIMO-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3337. --- Resolution: Invalid cars need to be installed as plugins as such deploy is invalid. Deploy of servlet-examples-tomcat-2.0-SNAPSHOT.car fails due to existing config.ser --- Key: GERONIMO-3337 URL: https://issues.apache.org/jira/browse/GERONIMO-3337 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M7 Environment: WinXP, Sun 1.5.0_11 Reporter: Donald Woods Assignee: Donald Woods Priority: Blocker Fix For: 2.0 The following fails on the Tomcat JEE5 assembly - deploy deploy servlet-examples-tomcat-2.0-SNAPSHOT.car The deployer returns the following, even though it has not been deployed before - Error: Unable to distribute servlet-examples-tomcat-2.0-SNAPSHOT.car: java.io.IOException: Sum file already exists Sum file already exists Console window shows - 12:16:23,859 ERROR [Deployer] Deployment failed due to java.io.IOException: Sum file already exists at org.apache.geronimo.system.configuration.ConfigurationStoreUtil.write ChecksumFor(ConfigurationStoreUtil.java:46) at org.apache.geronimo.system.configuration.ExecutableConfigurationUtil. writeConfiguration(ExecutableConfigurationUtil.java:162) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore .install(RepositoryConfigurationStore.java:323) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:332) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.i nvoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.in voke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBrid ge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp l.java:231) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM BeanServerInterceptor.java:833) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802 ) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti onImpl.java:1423) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio nImpl.java:96) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run (RMIConnectionImpl.java:1260) at java.security.AccessController.doPrivileged(AccessController.java:275 ) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R MIConnectionImpl.java:1363) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp l.java:797) at sun.reflect.GeneratedMethodAccessor172.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:309) at sun.rmi.transport.Transport$1.run(Transport.java:168) at java.security.AccessController.doPrivileged(AccessController.java:275 ) at sun.rmi.transport.Transport.serviceCall(Transport.java:164) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:5 06) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TC PTransport.java:838) at
[jira] Created: (GERONIMO-3353) Adjust server log4j files to use a default logging level of error instead of info before releasing.
Adjust server log4j files to use a default logging level of error instead of info before releasing. --- Key: GERONIMO-3353 URL: https://issues.apache.org/jira/browse/GERONIMO-3353 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Reporter: Matt Hogstrom Assignee: Matt Hogstrom Fix For: 2.0 The title says it all. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3343) Out Of Memory Error when deploying and undeploying applications
Out Of Memory Error when deploying and undeploying applications --- Key: GERONIMO-3343 URL: https://issues.apache.org/jira/browse/GERONIMO-3343 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Matt Hogstrom Fix For: 2.0 Using DayTrader 2.0 if you deploy the app. Create the tables and populate them Log in and do a few trans Undeploy the app Deploy the app We get an out of memory error in permgen space. Here is the app and plan used to re-create this problem: http://people.apache.org/~hogstrom/daytrader-2.0-SNAPSHOT/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3305) Out Of Memory Error when Running DayTrader in WebServices Mode
Out Of Memory Error when Running DayTrader in WebServices Mode
--
Key: GERONIMO-3305
URL: https://issues.apache.org/jira/browse/GERONIMO-3305
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: Kevan Miller
I deployed DayTrader 2.0 on the latest SVN rev 554753 of trunk.
I deploy daytrader-ear-2.0-SNAPSHOT.ear (using the
daytrader-g-2.0-SNAPSHOT-plan.xml in ${DT}/trunk/plans
Create the tables and populate them in the config section.
Switch to WebServices mode
Log in and do portfolio, quotes, buy and sell a few stocks and then logoff.
Try to log in again and I get:
10:34:34,089 ERROR [Log] Error: JSR 109 lookup failed .. defaulting to JSR 101
javax.naming.NamingException: Could not look up : service/Trade [Root
exception is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
javax.naming.NamingException: Could not look up : service/Trade [Root exception
is net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null]
at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:65)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getPortFromFactory(TradeWebSoapProxy.java:67)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getTrade(TradeWebSoapProxy.java:47)
at
org.apache.geronimo.samples.daytrader.soap.TradeWebSoapProxy.getAccountData(TradeWebSoapProxy.java:122)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doHome(TradeServletAction.java:277)
at
org.apache.geronimo.samples.daytrader.web.TradeServletAction.doLogin(TradeServletAction.java:372)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.performTask(TradeAppServlet.java:126)
at
org.apache.geronimo.samples.daytrader.web.TradeAppServlet.doPost(TradeAppServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.geronimo.samples.daytrader.web.OrdersAlertFilter.doFilter(OrdersAlertFilter.java:91)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:613)
Caused by: net.sf.cglib.core.CodeGenerationException:
java.lang.reflect.InvocationTargetException--null
at
net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:237)
at
[jira] Created: (GERONIMO-3306) JMS Objects being bound at an incorrect spot in the JNDI tree.
JMS Objects being bound at an incorrect spot in the JNDI tree.
--
Key: GERONIMO-3306
URL: https://issues.apache.org/jira/browse/GERONIMO-3306
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M7
Environment: All
Reporter: Matt Hogstrom
Assignee: Tim McConnell
DayTrader 2.0 uses a Session Bean that acts as a focal point for many
application operations. This bean does a lookup of several resources in the
setSessionContext method. This method looks up the following resources. The
first line is line 1034 from TradeBean.java. Note that the jms/ resource are
successfully looked up but that the items on line 1056 and 1057 needs to have
geronimo inserted into the name in order for the resolution to be successful.
{code}
*1034* public void ejbCreate() throws CreateException {
*1035* try {
*1036*
*1037* if (Log.doTrace())
*1038* Log.trace(TradeBean:ejbCreate -- JNDI lookups
of EJB and JMS resources);
*1039*
*1040* InitialContext ic = new InitialContext();
*1041* quoteHome = (LocalQuoteHome)
ic.lookup(java:comp/env/ejb/Quote);
*1042* accountHome = (LocalAccountHome)
ic.lookup(java:comp/env/ejb/Account);
*1043* profileHome = (LocalAccountProfileHome)
ic.lookup(java:comp/env/ejb/AccountProfile);
*1044* holdingHome = (LocalHoldingHome)
ic.lookup(java:comp/env/ejb/Holding);
*1045* orderHome = (LocalOrderHome)
ic.lookup(java:comp/env/ejb/Order);
*1046* keySequenceHome = (LocalKeySequenceHome)
ic.lookup(java:comp/env/ejb/KeySequence);
*1047*
*1048* orderBySQLSupported = ( (Boolean)
ic.lookup(java:comp/env/orderBySQLSupported) ).booleanValue();
*1049* updateQuotePrices = ( (Boolean)
ic.lookup(java:comp/env/updateQuotePrices) ).booleanValue();
*1050* TradeConfig.setUpdateQuotePrices(updateQuotePrices);
*1051*
*1052* try
*1053* {
*1054* qConnFactory = (ConnectionFactory)
ic.lookup(java:comp/env/jms/QueueConnectionFactory);
*1055* tConnFactory = (ConnectionFactory)
ic.lookup(java:comp/env/jms/TopicConnectionFactory);
*1056* streamerTopic = (Topic)
ic.lookup(java:comp/geronimo/env/jms/TradeStreamerTopic);
*1057*brokerQueue = (Queue)
ic.lookup(java:comp/geronimo/env/jms/TradeBrokerQueue);
{code}
Now, looking at the streamerTopic and brokerQueue definitions we also have
annotations which have the desired (correct?) names defined. However, when
the bean is initialized we receive the following warnings:
{code}
*46*@Resource(name = jms/TradeBrokerQueue)
*47*private Queue brokerQueue = null;
*48*
*49*private ConnectionFactory tConnFactory = null;
*50*
*51*@Resource(name = jms/TradeStreamerTopic)
*52*private Topic streamerTopic = null;
{code}
12:24:37,117 WARN [OpenEJB] Injection data not found in enc:
jndiName='jms/TradeBrokerQueue', target=class
org.apache.geronimo.samples.daytrader.ejb.TradeBean/brokerQueue
12:24:37,118 WARN [OpenEJB] Injection data not found in enc:
jndiName='jms/TradeStreamerTopic', target=class
org.apache.geronimo.samples.daytrader.ejb.TradeBean/streamerTopic
So, the other resources outlined above (like the ConnectionFactories) seem to
be bound correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3304) ability to update openejb-jar.xml by examining annotations
[ https://issues.apache.org/jira/browse/GERONIMO-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511497 ] Matt Hogstrom commented on GERONIMO-3304: - You might look at DayTrader as it has jboss DDs in it. Look here for the current DT source: https://svn.apache.org/repos/asf/geronimo/daytrader/trunk ability to update openejb-jar.xml by examining annotations -- Key: GERONIMO-3304 URL: https://issues.apache.org/jira/browse/GERONIMO-3304 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: J2G Environment: windows xp, linux Reporter: Viet Hung Nguyen Attachments: geronimo-3304.patch As of now, when there is a jboss.xml in a JBoss project, the geronimo equivalent is written to openejb-jar.xml. However, that only covers EJB 2.1's features. We need a way to update the openejb-jar.xml by looking at the annotations because there is still some configuring left to do. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3265) Spring stale version in 2.0-M6-rc1
[ https://issues.apache.org/jira/browse/GERONIMO-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509329 ] Matt Hogstrom commented on GERONIMO-3265: - I agree with the approach Paul. Suggestions on solving this ? Spring stale version in 2.0-M6-rc1 -- Key: GERONIMO-3265 URL: https://issues.apache.org/jira/browse/GERONIMO-3265 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0-M6 Environment: Windows XP SP2, Sun JSDK 1.5.07, Geronimo (2.0-M6-rc1) obtained from: http://people.apache.org/~hogstrom/2.0-M6-rc1/geronimo-tomcat6-jee5-2.0-M6-rc1-bin.zip (2.0-M6-rc1) Reporter: Alexei Kozich 1. This Geronimo build includes spring-beans.jar, spring-context.jar and spring-core.jar of version 2.0. So as far as we know, version 2.0 does not fully support integration with JPA implementations. 2. We developed an enterprise application (ear) which utilizes Spring 2.0.2 and OpenJPA. OpenJPA comes with Geronimo. Deployment and start of this application fails, because of different versions of Spring (our application expects spring-beans.jar, spring-context.jar and spring-core.jar to be at least of version 2.0.2 but Geronimo contains libs of version 2.0 (the lack of some methods in version 2.0 is the problem here). 3. If we try to use inverse-classloading or hidden classes (org.springframework) in geronimo-web.xml and include all necesary libs in WEB-INF/lib following Exception is thrown during deployment and start of the application (see below). 4. We found temporary workaround: to replace spring-beans.jar, spring-context.jar and spring-core.jar of version 2.0 with jars of version 2.0.2 in Geronimo repository without using of inverse-classloading and hidden classes and everything looks fine. 5. So as far as I understand this out-of-the-box Geronimo build could not be used as Server for Spring-OpenJPA appications. At least Spring libs upgrade could solve this problem. 6. Another problem is following Exception when using hidden classes or inverse-classloading to load application jars first. ERROR [ContextLoader] Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/springAppContext.xml]; nested exception is java.lang.IllegalArgumentException: Class [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the NamespaceHandler interface Caused by: java.lang.IllegalArgumentException: Class [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the NamespaceHandler interface at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandlerMappings(DefaultNamespaceHandlerResolver.java:119) at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.init(DefaultNamespaceHandlerResolver.java:96) at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.init(DefaultNamespaceHandlerResolver.java:82) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNamespaceHandlerResolver(XmlBeanDefinitionReader.java:526) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContext(XmlBeanDefinitionReader.java:515) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:495) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:340) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:317) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:125) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:141) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:123) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:91) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:292) at
[jira] Created: (GERONIMO-3267) Naming lookup fails. Reported error for a different name than requested
Naming lookup fails. Reported error for a different name than requested
Key: GERONIMO-3267
URL: https://issues.apache.org/jira/browse/GERONIMO-3267
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Environment: All
Reporter: Matt Hogstrom
Assignee: Dain Sundstrom
Fix For: 2.0-M7
DayTrader 1.2 deploy's correctly on 2.0 but when an attempt to execute a
SessionBean is tried a JNDI lookup fails. Here is the code from TradeBean.java
InitialContext ic = new
InitialContext();
*this is line 1041 ---*qConnFactory = (ConnectionFactory)
ic.lookup(*java:comp/env/jms/QueueConnectionFactory*);
{panel:title=Name Not Found Exception| borderStyle=dashed| borderColor=#ccc|
titleBGColor=#F7D6C1| bgColor=#CE}
The lookup fails with a name not found exception. What is odd is that the
exception says:
javax.naming.NameNotFoundException: Name
*java:openejb/Resource/jms/TradeBrokerQCF* not found.
at
org.apache.openejb.core.ivm.naming.IvmContext.federate(IvmContext.java:172)
at
org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:129)
at
org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(IntraVmJndiReference.java:38)
at
org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40)
at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152)
at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
*at
org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1041)*
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:146)
at
org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:129)
at
org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
at
org.apache.openejb.core.stateless.StatelessInstanceManager.getInstance(StatelessInstanceManager.java:177)
at
org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:156)
at
org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:211)
at
org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:65)
at
org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:230)
at
org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
at $Proxy25.resetTrade(Unknown Source)
at
org.apache.geronimo.samples.daytrader.TradeAction.resetTrade(TradeAction.java:510)
at
org.apache.geronimo.samples.daytrader.web.TradeConfigServlet.doResetTrade(TradeConfigServlet.java:73)
at
org.apache.geronimo.samples.daytrader.web.TradeConfigServlet.service(TradeConfigServlet.java:362)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
[jira] Commented: (GERONIMO-3240) Unable to obtain physical connection to jdbc:derby:
[ https://issues.apache.org/jira/browse/GERONIMO-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508708 ] Matt Hogstrom commented on GERONIMO-3240: - What do you mean the driver works properly? sounds like a bad dependency IIUC. Unable to obtain physical connection to jdbc:derby: --- Key: GERONIMO-3240 URL: https://issues.apache.org/jira/browse/GERONIMO-3240 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 2.0-M6 Environment: Geronimo v2.0-M6-rc3 Reporter: Hernan Cunico Attachments: geronimo-3240.patch Created a sample db on the embedded Derby database using the admin console. Created a connection pool to that database with the wizard, the Test Connection works fine during pool creation. When I try to access that pool from an application I get an error as if the database wouldn't exists. 13:28:24,218 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for [EMAIL PROTECTED] javax.resource.spi.ResourceAllocationException: Unable to obtain physical connection to jdbc:derby:sample at org.tranql.connector.jdbc.JDBCDriverMCF.getPhysicalConnection(JDBCDriverMCF.java:98) at org.tranql.connector.jdbc.JDBCDriverMCF.createManagedConnection(JDBCDriverMCF.java:73) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.LocalXAResourceInsertionInterceptor.getConnection(LocalXAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:78) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:95) at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(ConnectionHandleInterceptor.java:43) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(ConnectionTrackingInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:61) at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56) at org.apache.geronimo.samples.dbtester.beans.DBManagerBean.getTableList(DBManagerBean.java:76) at org.apache.geronimo.samples.dbtester.web.ListTablesServlet.listTables(ListTablesServlet.java:32) at org.apache.geronimo.samples.dbtester.web.ListTablesServlet.doGet(ListTablesServlet.java:17) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:358) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at
[jira] Created: (GERONIMO-3207) Created 2.0-M6 Branch
Created 2.0-M6 Branch - Key: GERONIMO-3207 URL: https://issues.apache.org/jira/browse/GERONIMO-3207 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Affects Versions: 2.0-M6 Environment: All Reporter: Matt Hogstrom Assignee: Matt Hogstrom Fix For: 2.0-M6 Created new 2.0-M6 branch. svn cp https://svn.apache.org/repos/asf/geronimo/server/trunk https://svn.apache.org/repos/asf/geronimo/server/branches/2.0-M6 Committed revision 543874. hogstrom-2:~ hogstrom$ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3060) Add a separate tree branch for persistence units into the JMX viewer
[ https://issues.apache.org/jira/browse/GERONIMO-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom reassigned GERONIMO-3060: --- Assignee: Matt Hogstrom (was: Jay D. McHugh) Add a separate tree branch for persistence units into the JMX viewer Key: GERONIMO-3060 URL: https://issues.apache.org/jira/browse/GERONIMO-3060 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console, persistence Affects Versions: 2.0-M5 Reporter: Jay D. McHugh Assigned To: Matt Hogstrom Priority: Minor Attachments: geronimo-3060.patch Added a branch under J2EE Managed Objects that show the persistence unit gbeans. Note: persistence unit gbeans still appear under All MBeans/geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3060) Add a separate tree branch for persistence units into the JMX viewer
[ https://issues.apache.org/jira/browse/GERONIMO-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-3060: Affects Version/s: (was: 2.0-M6) 2.0-M5 Will apply this patch for 2.0-M5 Add a separate tree branch for persistence units into the JMX viewer Key: GERONIMO-3060 URL: https://issues.apache.org/jira/browse/GERONIMO-3060 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console, persistence Affects Versions: 2.0-M5 Reporter: Jay D. McHugh Assigned To: Matt Hogstrom Priority: Minor Attachments: geronimo-3060.patch Added a branch under J2EE Managed Objects that show the persistence unit gbeans. Note: persistence unit gbeans still appear under All MBeans/geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3107) PersistenceUnits getting processed more than once
[ https://issues.apache.org/jira/browse/GERONIMO-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-3107: Assignee: Matt Hogstrom (was: David Jencks) PersistenceUnits getting processed more than once - Key: GERONIMO-3107 URL: https://issues.apache.org/jira/browse/GERONIMO-3107 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0-M5 Reporter: David Jencks Assigned To: Matt Hogstrom Fix For: 2.0-M5 Attachments: GERONIMO-3107.patch A persistence.xml is getting processed multiple times, e.g. the daytrader one. This is causing problems finding it from a pcr. A dumb solution is to keep a list of known urls and not process them again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3107) PersistenceUnits getting processed more than once
[ https://issues.apache.org/jira/browse/GERONIMO-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3107. --- Resolution: Fixed Applied the patch. Swizzled the patch a little to only add a PU to the knownPersistenceUnits only after the unit was successfully created. Fixed the original problem. PersistenceUnits getting processed more than once - Key: GERONIMO-3107 URL: https://issues.apache.org/jira/browse/GERONIMO-3107 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0-M5 Reporter: David Jencks Assigned To: Matt Hogstrom Fix For: 2.0-M5 Attachments: GERONIMO-3107.patch A persistence.xml is getting processed multiple times, e.g. the daytrader one. This is causing problems finding it from a pcr. A dumb solution is to keep a list of known urls and not process them again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3101) Role Based J2EE security model for DayTrader Benchmark
[ https://issues.apache.org/jira/browse/GERONIMO-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489171 ] Matt Hogstrom commented on GERONIMO-3101: - This would be excellent. What are the touch points for manipulating the configuration? I expect its a server startup issue as well as application configuration ? Role Based J2EE security model for DayTrader Benchmark -- Key: GERONIMO-3101 URL: https://issues.apache.org/jira/browse/GERONIMO-3101 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: Surya V Duggirala To characterize and assess the performance of Security runtime for J2EE role based security and Java 2 Security, we need a secured version of DayTrader. This can be useful for Web Authenticatin and Authorization and EJB Authentication and Authorization etc., Currently I am working on assessing the security performance using DayTrader and wondering whether anyone has done similar studies with DayTrader. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2651) Servlet annotations are not supported
[ https://issues.apache.org/jira/browse/GERONIMO-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2651. --- Resolution: Fixed Recent work on DT shows that @Resource is working properly. If this is an issue please re-open. Servlet annotations are not supported - Key: GERONIMO-2651 URL: https://issues.apache.org/jira/browse/GERONIMO-2651 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: web Affects Versions: 2.0-M1, 2.0-M2, 2.0-M5 Reporter: Krishnakumar B Assigned To: Tim McConnell Fix For: 2.0-M3 Servlet JEE5 annotations are not supported. ( I have tried @Resource in servlet to get reference to a datasource.) Not sure which release this is targetted at so adding it to 2.0-M1 2.0-M2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2855) Missing persistence-context-ref while deploying DayTrader on 2.0-trunk
[
https://issues.apache.org/jira/browse/GERONIMO-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom closed GERONIMO-2855.
---
Resolution: Fixed
Fixed and verified.
Missing persistence-context-ref while deploying DayTrader on 2.0-trunk
--
Key: GERONIMO-2855
URL: https://issues.apache.org/jira/browse/GERONIMO-2855
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-M3
Environment: All
Reporter: Matt Hogstrom
Assigned To: Dain Sundstrom
Fix For: 2.0-M3
Daytrader is currently at a point where it is almost deployable. During
deployment we are getting errors
Deployment start: Tue Feb 20 09:35:11 EST 2007
Deployment end: Tue Feb 20 09:35:59 EST 2007
Overall deployment time was 48 seconds...not sure if this is good or bad.
The ear and plan are located at
http://people.apache.org/~hogstrom/daytrader-01/
{panel:title=Missing persistence-context-ref while deploying DayTrader}
Persistence unit cmp for persistence-context-ref openejb/cmp not found
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:433)
at
org.apache.openejb.assembler.classic.Assembler.createEjbJar(Assembler.java:303)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean.createEjbJar(OpenEjbSystemGBean.java:184)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean$$FastClassByCGLIB$$5005cdd0.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.openejb.OpenEjbSystem$$EnhancerByCGLIB$$3c720d3c.createEjbJar(generated)
at
org.apache.geronimo.openejb.EjbModuleImpl.start(EjbModuleImpl.java:123)
at
org.apache.geronimo.openejb.EjbModuleImplGBean.doStart(EjbModuleImplGBean.java:39)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:529)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:543)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:434)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:188)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
[jira] Closed: (GERONIMO-2970) Can not deploy daytrader in geronimo m2
[ https://issues.apache.org/jira/browse/GERONIMO-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2970. --- Resolution: Fixed Assignee: Matt Hogstrom Closing as G and DayTrader have moved past this error. Can not deploy daytrader in geronimo m2 --- Key: GERONIMO-2970 URL: https://issues.apache.org/jira/browse/GERONIMO-2970 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M3 Reporter: Frank G Assigned To: Matt Hogstrom Fix For: 2.0-M3 I checked out the source codes of daytrader from https://svn.apache.org/repos/asf/geronimo/daytrader/trunk and built it successful. But I encountered the following error when I deployed it: Error: Unable to distribute daytrader-ear-2.0-SNAPSHOT.ear: Could not load service class org.apache.geronimo.samples.daytrader.client.ws.Trade org.apache.geronimo.samples.daytrader.client.ws.Trade in classloader geronimo/daytrader-derby-tomcat_web.war/1.1.1/car I posted this on the dev maillist and David Jencks's comments are below: I assume you are working with geronimo trunk from svn? Can you please file a jira? I recently changed where appclient files go and that caused this problem. What daytrader is doing here is a bit odd (including client side jars in the server using manifest classpath) and I'd like to think a bit about what the best solution is. It might be to change daytrader and it might be to put the client jar in two places. thanks david jencks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2111) Change Default WebContainer behaviour to disable AccessLogging
[ https://issues.apache.org/jira/browse/GERONIMO-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2111. --- Resolution: Fixed Fix Version/s: (was: 2.0-M4) 1.2 Closing as this was incorrectly tagged for Geronimo 2.0. Change Default WebContainer behaviour to disable AccessLogging -- Key: GERONIMO-2111 URL: https://issues.apache.org/jira/browse/GERONIMO-2111 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 1.2 Currently Tomcat and Jetty have access logging enabled by default. This should be changed to have it disabled by default for all geronimo assemblies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3046) When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started
[ https://issues.apache.org/jira/browse/GERONIMO-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-3046. --- Resolution: Fixed Fix Version/s: (was: 2.0-M4) 2.0-M5 Tested latest changes...either the race condition has changed or this is fixed :) Thanks Dain When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started - Key: GERONIMO-3046 URL: https://issues.apache.org/jira/browse/GERONIMO-3046 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0-M4, 2.0-M5 Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 2.0-M5 Testing deployment of Daytrader on Geronimo 2.0 - M4 (as well as trunk) the dt-ejb.jar is started before the messaging component it depends on. As a consequence, startup of the application fails as a dependent resource (a messaging queue) is not found. Talked to Dain about this and he thinks he knows where this needs to be addressed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3054) org.apache.geronimo.util.jce.X509V1CertificateGenerator appears to be deprecated with no replacement
[ https://issues.apache.org/jira/browse/GERONIMO-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486338 ] Matt Hogstrom commented on GERONIMO-3054: - Many of these files came from Bouncy Castle. We had to break them apart as there was an issue with the Bouncy Castle jars shipping a ptented algorithm. If you simply need the file you can go to www.bouncycastle.org. If not, is there some function that is not working as intended in Geornimo? org.apache.geronimo.util.jce.X509V1CertificateGenerator appears to be deprecated with no replacement Key: GERONIMO-3054 URL: https://issues.apache.org/jira/browse/GERONIMO-3054 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.1.1 Environment: All Reporter: Ken Priority: Minor Hello, all. I am looking at the source code for several files, and one of them, org.apache.geronimo.util.jce.X509V1CertificateGenerator has the following tag notice: /** * class to produce an X.509 Version 1 certificate. * * @deprecated use the equivalent class in org.apache.geronimo.util.x509 */ I (think I) have looked everywhere for a package named x509 under util, or even a reference to when/how/why/to what it was changed, but can't seem to find one. Where is this replacement class that is mentioned in the deprecation? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3046) When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started
[ https://issues.apache.org/jira/browse/GERONIMO-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485919 ] Matt Hogstrom commented on GERONIMO-3046: - Still having the same problem with this fix applied. When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started - Key: GERONIMO-3046 URL: https://issues.apache.org/jira/browse/GERONIMO-3046 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0-M4, 2.0-M5 Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 2.0-M4 Testing deployment of Daytrader on Geronimo 2.0 - M4 (as well as trunk) the dt-ejb.jar is started before the messaging component it depends on. As a consequence, startup of the application fails as a dependent resource (a messaging queue) is not found. Talked to Dain about this and he thinks he knows where this needs to be addressed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3046) When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started
When starting Daytrader after deploy on 2.0-SNAPSHOT ejb-jar is started before its dependencies have been started - Key: GERONIMO-3046 URL: https://issues.apache.org/jira/browse/GERONIMO-3046 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.0-M4, 2.0-M5 Reporter: Matt Hogstrom Assigned To: Dain Sundstrom Fix For: 2.0-M4 Testing deployment of Daytrader on Geronimo 2.0 - M4 (as well as trunk) the dt-ejb.jar is started before the messaging component it depends on. As a consequence, startup of the application fails as a dependent resource (a messaging queue) is not found. Talked to Dain about this and he thinks he knows where this needs to be addressed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1945) Console's web application list does not show WARs that are deployed inside EARs
[ https://issues.apache.org/jira/browse/GERONIMO-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-1945: Affects Version/s: 2.0-M2 2.0-M3 Fix Version/s: (was: 2.0-M1) 2.0-M5 Update for review time before M5 Console's web application list does not show WARs that are deployed inside EARs --- Key: GERONIMO-1945 URL: https://issues.apache.org/jira/browse/GERONIMO-1945 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.0, 2.0-M1, 2.0-M2, 2.0-M3 Reporter: Erin Mulder Fix For: 2.0-M5 Attachments: jira1945.patch In the console, click on Applications - Web App WARs. The resulting list of web applications does not include any web application that is packaged as part of an EAR. (The list is populated inside ConfigManagerPortlet.doView) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2946) Add StAX specs into Geronimo Specs project
Add StAX specs into Geronimo Specs project -- Key: GERONIMO-2946 URL: https://issues.apache.org/jira/browse/GERONIMO-2946 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: specs Affects Versions: 2.0-beta1 Environment: All Reporter: Matt Hogstrom Assigned To: Matt Hogstrom The StAX API 1.0.1 at Codehaus has introduced a fix for a problem on javax.xml.stream.XMLOutputFactory. The fix in the API is not compatible with the RI and was introduced in an attempt to fix this problem as outlined in JSR 173 MR1. This MR was rejected by Sun and as such the recently released API is no longer compatible with the Java EE 5 RI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2881) Client-Transaction explicit-versions.properties does not include all dependencies.
Client-Transaction explicit-versions.properties does not include all
dependencies.
--
Key: GERONIMO-2881
URL: https://issues.apache.org/jira/browse/GERONIMO-2881
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Maven Plugins for G
Affects Versions: 2.0-beta1
Environment: All (I think)
Reporter: Matt Hogstrom
Assigned To: Jason Dillon
Fix For: 2.0-beta1
When working on the branch I ran into a problem in configs/client-transaction
where the build failed because geronimo-ejb_3.0_specs//car could not be
resolved. In looking at the generated explicit-versions.properties this entry
was missing. I looked at the Maven dependencies for that module and found that
all dependencies under geronimo-transaction were missing in the explicit
versions.
Here are the Maven dependencies:
[INFO] org.apache.geronimo.configs:client-transaction:car {
version=2.0-M3-SNAPSHOT, scope=null }
[INFO] junit:junit:jar { version=3.8.1, scope=test }
[INFO] org.apache.geronimo.genesis.config:logging-config:jar { version=1.1,
scope=test }
[INFO] org.apache.geronimo.modules:geronimo-transaction:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
These are not included in the explicit-version.properties file that is
generated:
[INFO] org.apache.geronimo.modules:geronimo-core:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-j2ee:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar {
version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar {
version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-j2ee-connector_1.5_spec:jar {
version=1.1, scope=compile }
[INFO] backport-util-concurrent:backport-util-concurrent:jar {
version=2.2, scope=compile }
[INFO] org.objectweb.howl:howl:jar { version=1.0.1-1, scope=compile }
Resume included dependencies:
[INFO] org.apache.geronimo.configs:client:car { version=2.0-M3-SNAPSHOT,
scope=compile }
[INFO] org.apache.geronimo.configs:client-system:car {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.configs:jee-specs:car {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar {
version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-el_1.0_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jacc_1.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar
{ version=1.0-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.javamail:geronimo-javamail_1.4_provider:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar
{ version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jaxr_1.0_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jsp_2.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-saaj_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar {
version=1.1-SNAPSHOT, scope=compile }
[INFO] stax:stax-api:jar { version=1.0.1, scope=compile }
[INFO] javax.xml.bind:jaxb-api:jar { version=2.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar
{ version=1.1-SNAPSHOT, scope=compile }
[INFO] javax.xml.ws:jaxws-api:jar { version=2.0, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-activation:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-interceptor:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-naming:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.xbean:xbean-naming:jar { version=2.8,
scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-management:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO]
[jira] Commented: (GERONIMO-2881) Client-Transaction explicit-versions.properties does not include all dependencies.
[
https://issues.apache.org/jira/browse/GERONIMO-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475566
]
Matt Hogstrom commented on GERONIMO-2881:
-
The type is mine... things are fine in trunk...perhaps I missed some bits in
the branch but they're not jumping out at me.
Client-Transaction explicit-versions.properties does not include all
dependencies.
--
Key: GERONIMO-2881
URL: https://issues.apache.org/jira/browse/GERONIMO-2881
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Maven Plugins for G
Affects Versions: 2.0-beta1
Environment: All (I think)
Reporter: Matt Hogstrom
Assigned To: Jason Dillon
Fix For: 2.0-beta1
When working on the branch I ran into a problem in configs/client-transaction
where the build failed because geronimo-ejb_3.0_specs//car could not be
resolved. In looking at the generated explicit-versions.properties this
entry was missing. I looked at the Maven dependencies for that module and
found that all dependencies under geronimo-transaction were missing in the
explicit versions.
Here are the Maven dependencies:
{noformat}
[INFO] org.apache.geronimo.configs:client-transaction:car {
version=2.0-M3-SNAPSHOT, scope=null }
[INFO] junit:junit:jar { version=3.8.1, scope=test }
[INFO] org.apache.geronimo.genesis.config:logging-config:jar {
version=1.1, scope=test }
[INFO] org.apache.geronimo.modules:geronimo-transaction:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
{noformat}
These are not included in the explicit-version.properties file that is
generated:
{noformat}
[INFO] org.apache.geronimo.modules:geronimo-core:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-j2ee:jar {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar {
version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-ejb_3.0_spec:jar {
version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-j2ee-connector_1.5_spec:jar
{ version=1.1, scope=compile }
[INFO] backport-util-concurrent:backport-util-concurrent:jar {
version=2.2, scope=compile }
[INFO] org.objectweb.howl:howl:jar { version=1.0.1-1, scope=compile }
{noformat}
Resume included dependencies:
{noformat}
[INFO] org.apache.geronimo.configs:client:car { version=2.0-M3-SNAPSHOT,
scope=compile }
[INFO] org.apache.geronimo.configs:client-system:car {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.configs:jee-specs:car {
version=2.0-M3-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar
{ version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar
{ version=1.0, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-el_1.0_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jacc_1.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.javamail:geronimo-javamail_1.4_mail:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.javamail:geronimo-javamail_1.4_provider:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO]
org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jaxr_1.0_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-jsp_2.1_spec:jar {
version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-saaj_1.1_spec:jar {
version=1.1, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar {
version=1.1-SNAPSHOT, scope=compile }
[INFO] stax:stax-api:jar { version=1.0.1, scope=compile }
[INFO] javax.xml.bind:jaxb-api:jar { version=2.0, scope=compile }
[INFO]
org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar {
version=1.1-SNAPSHOT, scope=compile }
[INFO] javax.xml.ws:jaxws-api:jar { version=2.0, scope=compile }
[INFO]
[jira] Created: (GERONIMO-2855) Error deploying DayTrader CMP 2.1 beans on Geornimo 2.0-trunk
Error deploying DayTrader CMP 2.1 beans on Geornimo 2.0-trunk
-
Key: GERONIMO-2855
URL: https://issues.apache.org/jira/browse/GERONIMO-2855
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-beta1
Environment: All
Reporter: Matt Hogstrom
Assigned To: Dain Sundstrom
Fix For: 2.0-beta1
Daytrader is currently at a point where it is almost deployable. During
deployment we are getting errors
Deployment start: Tue Feb 20 09:35:11 EST 2007
Deployment end: Tue Feb 20 09:35:59 EST 2007
Overall deployment time was 48 seconds...not sure if this is good or bad.
The ear and plan are located at http://people.apache.org/~hogstrom/daytrader-01/
{panel:title=Missing persistence-context-ref while deploying DayTrader}
Persistence unit cmp for persistence-context-ref openejb/cmp not found
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:433)
at
org.apache.openejb.assembler.classic.Assembler.createEjbJar(Assembler.java:303)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean.createEjbJar(OpenEjbSystemGBean.java:184)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean$$FastClassByCGLIB$$5005cdd0.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.openejb.OpenEjbSystem$$EnhancerByCGLIB$$3c720d3c.createEjbJar(generated)
at
org.apache.geronimo.openejb.EjbModuleImpl.start(EjbModuleImpl.java:123)
at
org.apache.geronimo.openejb.EjbModuleImplGBean.doStart(EjbModuleImplGBean.java:39)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:529)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:543)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:434)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:188)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:855)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at
[jira] Updated: (GERONIMO-2855) Missing persistence-context-ref while deploying DayTrader on 2.0-trunk
[
https://issues.apache.org/jira/browse/GERONIMO-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom updated GERONIMO-2855:
Summary: Missing persistence-context-ref while deploying DayTrader on
2.0-trunk (was: Error deploying DayTrader CMP 2.1 beans on Geornimo 2.0-trunk)
Missing persistence-context-ref while deploying DayTrader on 2.0-trunk
--
Key: GERONIMO-2855
URL: https://issues.apache.org/jira/browse/GERONIMO-2855
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.0-beta1
Environment: All
Reporter: Matt Hogstrom
Assigned To: Dain Sundstrom
Fix For: 2.0-beta1
Daytrader is currently at a point where it is almost deployable. During
deployment we are getting errors
Deployment start: Tue Feb 20 09:35:11 EST 2007
Deployment end: Tue Feb 20 09:35:59 EST 2007
Overall deployment time was 48 seconds...not sure if this is good or bad.
The ear and plan are located at
http://people.apache.org/~hogstrom/daytrader-01/
{panel:title=Missing persistence-context-ref while deploying DayTrader}
Persistence unit cmp for persistence-context-ref openejb/cmp not found
at
org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:433)
at
org.apache.openejb.assembler.classic.Assembler.createEjbJar(Assembler.java:303)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean.createEjbJar(OpenEjbSystemGBean.java:184)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean$$FastClassByCGLIB$$5005cdd0.invoke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.openejb.OpenEjbSystem$$EnhancerByCGLIB$$3c720d3c.createEjbJar(generated)
at
org.apache.geronimo.openejb.EjbModuleImpl.start(EjbModuleImpl.java:123)
at
org.apache.geronimo.openejb.EjbModuleImplGBean.doStart(EjbModuleImplGBean.java:39)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:986)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:529)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:543)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:434)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:188)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(generated)
at
[jira] Closed: (GERONIMO-2600) Upgrade to Derby 10.2.2.0
[ https://issues.apache.org/jira/browse/GERONIMO-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2600. --- Assignee: Matt Hogstrom (was: Kevan Miller) Updated to 10.2.2.0 as well as corresponding fixes in TranQL due to DataSource changes made in Derby. Upgrade to Derby 10.2.2.0 - Key: GERONIMO-2600 URL: https://issues.apache.org/jira/browse/GERONIMO-2600 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: databases, dependencies Affects Versions: 2.0 Reporter: Donald Woods Assigned To: Matt Hogstrom Fix For: 2.0-M2 Attachments: G2600.patch Derby 10.2.1.6 was released on Oct. 6, 2006 - http://mail-archives.apache.org/mod_mbox/db-derby-user/200610.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2661) Make geronimo schema files more human readable
[ https://issues.apache.org/jira/browse/GERONIMO-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom reassigned GERONIMO-2661: --- Assignee: Matt Hogstrom Make geronimo schema files more human readable -- Key: GERONIMO-2661 URL: https://issues.apache.org/jira/browse/GERONIMO-2661 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: documentation Affects Versions: 2.0 Environment: Any Reporter: Rakesh Midha Assigned To: Matt Hogstrom Priority: Minor Fix For: 2.0 Attachments: alldoc.patch, appclientdoc.patch, appdoc.patch, attributedoc.patch, connectordoc.patch, jettyconfigdoc.patch, jettydoc.patch, logindoc.patch, moduledoc.patch, namingdoc.patch, plugindoc.patch, securitydoc.patch, tomcatconfigdoc.patch, tomcatdoc.patch, webdoc.patch Geronimo schema files are the files which are basically exposed to all the user's to follow the guidelines while developing there plan files. These schema files should have lot of documentation just like j2ee descriptor's schema's. All the fields should be described. Schema formatting provides a nice option to do this by specifying xs:annotation xs:documentation lang=endocumentation for each element goes here/xs:documentation /xs:annotation for each and every element in schema files. I think this will make it more human readable, i believe that every file which is openly exposed to user's should have lot of documentation for readbility. What do you think? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2661) Make geronimo schema files more human readable
[ https://issues.apache.org/jira/browse/GERONIMO-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470808 ] Matt Hogstrom commented on GERONIMO-2661: - Rakesh...looks like you've been quite busy. I'll take a look through the patches and give them a go. Looks good from my quick peek. Thanks! Make geronimo schema files more human readable -- Key: GERONIMO-2661 URL: https://issues.apache.org/jira/browse/GERONIMO-2661 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: documentation Affects Versions: 2.0 Environment: Any Reporter: Rakesh Midha Assigned To: Matt Hogstrom Priority: Minor Fix For: 2.0 Attachments: alldoc.patch, appclientdoc.patch, appdoc.patch, attributedoc.patch, connectordoc.patch, jettyconfigdoc.patch, jettydoc.patch, logindoc.patch, moduledoc.patch, namingdoc.patch, plugindoc.patch, securitydoc.patch, tomcatconfigdoc.patch, tomcatdoc.patch, webdoc.patch Geronimo schema files are the files which are basically exposed to all the user's to follow the guidelines while developing there plan files. These schema files should have lot of documentation just like j2ee descriptor's schema's. All the fields should be described. Schema formatting provides a nice option to do this by specifying xs:annotation xs:documentation lang=endocumentation for each element goes here/xs:documentation /xs:annotation for each and every element in schema files. I think this will make it more human readable, i believe that every file which is openly exposed to user's should have lot of documentation for readbility. What do you think? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2638) Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of JarFile
[ https://issues.apache.org/jira/browse/GERONIMO-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2638: Fix Version/s: (was: 2.0-M2) 2.0-beta1 Deferred to beta-1 due to size. Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of JarFile --- Key: GERONIMO-2638 URL: https://issues.apache.org/jira/browse/GERONIMO-2638 Project: Geronimo Issue Type: RTC Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M1 Reporter: Sachin Patel Assigned To: Sachin Patel Fix For: 2.0-beta1 Attachments: GERONIMO-1526-v1.2.patch, GERONIMO-1526-v1.2.patch2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2607) GoperationInfo should include the return type for the operation
[ https://issues.apache.org/jira/browse/GERONIMO-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2607: Affects Version/s: (was: 2.0) 2.0-M2 Applied kernel patch for Anita and deployed a new SNAPSHOT. Anita, please close if your satisfied. GoperationInfo should include the return type for the operation --- Key: GERONIMO-2607 URL: https://issues.apache.org/jira/browse/GERONIMO-2607 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 2.0-M2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Anita Kulshreshtha Attachments: kernel.diff, kernel.diff, modules.diff, operations.jpg When the operations are viewed by jconsole the return type is not avaialble. GOpeartionInfo should keep the retrunType information. This will break backward compatibility of GBeanInfo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2640) Expose development and modificationTestInterval attributes in Jasper as configuration attributes for webcontainer
[ https://issues.apache.org/jira/browse/GERONIMO-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2640: Fix Version/s: (was: 2.0-M2) 2.0 Expose development and modificationTestInterval attributes in Jasper as configuration attributes for webcontainer - Key: GERONIMO-2640 URL: https://issues.apache.org/jira/browse/GERONIMO-2640 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0 Reporter: Sachin Patel Assigned To: Sachin Patel Fix For: 2.0 The Geronimo WebContainer should allow the attributes development and modificationTestInterval to be configurable. In a development enviorment this should be set to true in the test enviorment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2684) Upgrade server trunk (2.0) to use the latest released geronimo-spec versions
[ https://issues.apache.org/jira/browse/GERONIMO-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2684: Affects Version/s: (was: 2.0-M2) 2.0-beta1 Upgrade server trunk (2.0) to use the latest released geronimo-spec versions Key: GERONIMO-2684 URL: https://issues.apache.org/jira/browse/GERONIMO-2684 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Affects Versions: 2.0-beta1 Reporter: Donald Woods Assigned To: Donald Woods Fix For: 2.0-M2 Several spec modules were released in the past week and 2.0 should be using them instead of the previous SNAPSHOT versions. geronimo-annotation_1.0_spec-1.0 geronimo-jpa_3.0_spec-1.0 The following specs also are newer versions of ones currently being used in 2.0 - geronimo-ejb_2.1_spec-1.1 geronimo-j2ee-connector_1.5_spec-1.1 geronimo-j2ee-deployment_1.1_spec-1.1 geronimo-jaxr_1.0_spec-1.1 geronimo-jaxrpc_1.1_spec-1.1 geronimo-jms_1.1_spec-1.1 geronimo-jsp_2.0_spec-1.1 geronimo-jta_1.1_spec-1.0 geronimo-qname_1.1_spec-1.1 geronimo-saaj_1.1_spec-1.1 geronimo-servlet_2.4_spec-1.1 Should the following new specs be included in the top-level pom? geronimo-interceptor_3.0_spec-1.0 geronimo-el_1.0_spec-1.0-SNAPSHOT geronimo-jsp_2.1_spec-1.0-SNAPSHOT -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-438) Deployer.deploy arguments inconsistent
[ https://issues.apache.org/jira/browse/GERONIMO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-438: --- Fix Version/s: (was: 2.0-M2) 2.0-beta1 Deployer.deploy arguments inconsistent -- Key: GERONIMO-438 URL: https://issues.apache.org/jira/browse/GERONIMO-438 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M2 Reporter: Aaron Mulder Fix For: 2.0-beta1 Attachments: g-438-11x-option2.patch, g-438-option1.patch, g-438-option2.patch One deploy method starts with the arguments: File module, File plan Another overloaded deploy method starts with the arguments: File plan, File module These should not be reversed, but we need to carefully hunt down usages since the types alone won't cause the usages to be flagged if one is switched. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2664) Servlet Filter Error
[ https://issues.apache.org/jira/browse/GERONIMO-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2664: Fix Version/s: (was: 2.0-M2) (was: 2.0) 2.0-beta1 Servlet Filter Error Key: GERONIMO-2664 URL: https://issues.apache.org/jira/browse/GERONIMO-2664 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty, Tomcat Affects Versions: 2.0-M1, 2.0-M2, 2.0 Reporter: Krishnakumar B Assigned To: Joe Bohn Fix For: 2.0-beta1 Trying out servlet name with a wild card ( * ) in Filter throws exception in Jetty. In tomcat the filter is not called at all filter-mapping filter-nameSample Filter/filter-name servlet-name*/servlet-name /filter-mapping instead of filter-nameSample Filter/filter-name !--servlet-name*/servlet-name -- servlet-nameSampleServlet/servlet-name servlet-nameAnotherSampleServlet/servlet-name Jetty 14:21:50,780 ERROR [Deployer] Deployment failed due to java.lang.AssertionError: javax.management.MalformedObjectNameException: Invalid character `*' in value at org.apache.geronimo.kernel.Jsr77Naming.createObjectName(Jsr77Naming.java:112) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:80) at org.apache.geronimo.kernel.Jsr77Naming.createChildName(Jsr77Naming.java:54) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addFilterMappingsGBeans(JettyModuleBuilder.java:614) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:483) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder$$FastClassByCGLIB$$1a00be84.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$8c79360e.addGBeans(generated) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:572) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$c3a6b023.buildConfiguration(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:302) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at
[jira] Updated: (GERONIMO-2651) Servlet annotations are not supported
[ https://issues.apache.org/jira/browse/GERONIMO-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2651: Fix Version/s: (was: 2.0-M2) (was: 2.0) 2.0-beta1 Servlet annotations are not supported - Key: GERONIMO-2651 URL: https://issues.apache.org/jira/browse/GERONIMO-2651 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: web Affects Versions: 2.0-M1, 2.0-M2, 2.0 Reporter: Krishnakumar B Assigned To: Paul McMahan Fix For: 2.0-beta1 Servlet JEE5 annotations are not supported. ( I have tried @Resource in servlet to get reference to a datasource.) Not sure which release this is targetted at so adding it to 2.0-M1 2.0-M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2711) specs/trunk fails to build
[ https://issues.apache.org/jira/browse/GERONIMO-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom closed GERONIMO-2711. --- Resolution: Fixed Updated spec pom to remove ejb-3.0 specs/trunk fails to build -- Key: GERONIMO-2711 URL: https://issues.apache.org/jira/browse/GERONIMO-2711 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Affects Versions: 2.0-M2 Reporter: Donald Woods Assigned To: Donald Woods Fix For: 2.0-M2 geronimo-ejb_3.0_spec was released, but not removed from specs/trunk/pom.xml geronimo-commonj_1.1_spec fails to build, because it is trying to use org.apache.geronimo.specs.specs version=1.2-SNAPSHOT instead of 1.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2111) Change Default WebContainer behaviour to disable AccessLogging
[ https://issues.apache.org/jira/browse/GERONIMO-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2111: Fix Version/s: (was: 2.0-M2) 2.0-beta2 Change Default WebContainer behaviour to disable AccessLogging -- Key: GERONIMO-2111 URL: https://issues.apache.org/jira/browse/GERONIMO-2111 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 2.0-beta2 Currently Tomcat and Jetty have access logging enabled by default. This should be changed to have it disabled by default for all geronimo assemblies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2643) Stack trace (due to amq) while shutting down Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2643: Fix Version/s: (was: 2.0-M2) 2.0-beta1 Stack trace (due to amq) while shutting down Geronimo - Key: GERONIMO-2643 URL: https://issues.apache.org/jira/browse/GERONIMO-2643 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.0-M1 Reporter: Prasad Kashyap Assigned To: Anita Kulshreshtha Fix For: 2.0-beta1 Long stacktrace when the Geronimo server is shut down. http://www.nabble.com/forum/ViewPost.jtp?post=7735287framed=y Creating this JIRA just as a placeholder so that we may track it. Anita, I took the liberty of assigning this to you since you said on the devlist that you were investigating it. Please fee free to reassign it if you think otherwise. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2684) Upgrade server trunk (2.0) to use the latest released geronimo-spec versions
[ https://issues.apache.org/jira/browse/GERONIMO-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2684: Fix Version/s: (was: 2.0-M2) 2.0-beta1 Upgrade server trunk (2.0) to use the latest released geronimo-spec versions Key: GERONIMO-2684 URL: https://issues.apache.org/jira/browse/GERONIMO-2684 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Affects Versions: 2.0-beta1 Reporter: Donald Woods Assigned To: Donald Woods Fix For: 2.0-beta1 Several spec modules were released in the past week and 2.0 should be using them instead of the previous SNAPSHOT versions. geronimo-annotation_1.0_spec-1.0 geronimo-jpa_3.0_spec-1.0 The following specs also are newer versions of ones currently being used in 2.0 - geronimo-ejb_2.1_spec-1.1 geronimo-j2ee-connector_1.5_spec-1.1 geronimo-j2ee-deployment_1.1_spec-1.1 geronimo-jaxr_1.0_spec-1.1 geronimo-jaxrpc_1.1_spec-1.1 geronimo-jms_1.1_spec-1.1 geronimo-jsp_2.0_spec-1.1 geronimo-jta_1.1_spec-1.0 geronimo-qname_1.1_spec-1.1 geronimo-saaj_1.1_spec-1.1 geronimo-servlet_2.4_spec-1.1 Should the following new specs be included in the top-level pom? geronimo-interceptor_3.0_spec-1.0 geronimo-el_1.0_spec-1.0-SNAPSHOT geronimo-jsp_2.1_spec-1.0-SNAPSHOT -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2694) STATUS file sent out as the Geronimo Weekly Status email needs updating
[ https://issues.apache.org/jira/browse/GERONIMO-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2694: Fix Version/s: (was: 2.0-M2) Wish List STATUS file sent out as the Geronimo Weekly Status email needs updating --- Key: GERONIMO-2694 URL: https://issues.apache.org/jira/browse/GERONIMO-2694 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 1.2, 2.0-M2 Reporter: Donald Woods Priority: Trivial Fix For: Wish List Attachments: G2694-server-trunk.patch The geronimo/server/trunk/STATUS file needs to be updated to mention trunk is now 2.0, where the 1.2 branch is located and the fact that 1.2-Beta and 2.0-M1 were released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2650) JSP 2.1 error in Jetty/Tomcat
[
https://issues.apache.org/jira/browse/GERONIMO-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Hogstrom updated GERONIMO-2650:
Fix Version/s: (was: 2.0-M2)
(was: 2.0)
2.0-beta1
JSP 2.1 error in Jetty/Tomcat
-
Key: GERONIMO-2650
URL: https://issues.apache.org/jira/browse/GERONIMO-2650
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: web
Affects Versions: 2.0-M1, 2.0-M2, 2.0
Reporter: Krishnakumar B
Assigned To: Joe Bohn
Fix For: 2.0-beta1
Attachments: SampleJSP.war
Deploying a web application with JSP 2.1 features throws error in Jetty and
Tomcat
On Tomcat 6:
---
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
org.apache.jasper.compiler.Node$Root.accept (Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
org.apache.jasper.JspCompilationContext.compile
(JspCompilationContext.java:566)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service (JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
On Jetty 6.0:
org.apache.jasper.JasperException: /SampleJSP.jsp(12,35) #{..} is not allowed
in template text
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch
(ErrorDispatcher.java:406)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:101)
at
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:710)
at org.apache.jasper.compiler.Node$ELExpression.accept (Node.java:935)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
at org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
at org.apache.jasper.compiler.Validator.validate(Validator.java:1679)
at org.apache.jasper.compiler.Compiler.generateJava (Compiler.java:178)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java :273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:314)
at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java :459)
at
org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.apache.geronimo.jetty6.JettyServletHandler.doHandle
(JettyServletHandler.java:55)
at
org.apache.geronimo.jetty6.JettyServletHandler$ActualJettyServletHandler.handle(JettyServletHandler.java:62)
at org.apache.geronimo.jetty6.JettyServletHandler$NoOpChainedHandler.handle
(JettyServletHandler.java:70)
at
org.apache.geronimo.jetty6.JettyServletHandler.handle(JettyServletHandler.java:47)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
(ThreadClassloaderHandler.java:46)
at
[jira] Updated: (GERONIMO-2723) The j2ee-builder module should use geronimo-schema-jee_5 jar
[ https://issues.apache.org/jira/browse/GERONIMO-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2723: Affects Version/s: (was: 2.0-M2) 2.0-beta1 The j2ee-builder module should use geronimo-schema-jee_5 jar - Key: GERONIMO-2723 URL: https://issues.apache.org/jira/browse/GERONIMO-2723 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Anita Kulshreshtha Fix For: 2.0-beta1 Attachments: configs.diff, modules.diff, modules.diff The j2ee-builder should use classes from geronimo-schema-jee_5 (see http://www.nabble.com/Web-Builders-p8230881.html) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2723) The j2ee-builder module should use geronimo-schema-jee_5 jar
[ https://issues.apache.org/jira/browse/GERONIMO-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Hogstrom updated GERONIMO-2723: Affects Version/s: (was: 2.0-beta1) 2.0-M2 Fix Version/s: (was: 2.0-M2) 2.0-beta1 The j2ee-builder module should use geronimo-schema-jee_5 jar - Key: GERONIMO-2723 URL: https://issues.apache.org/jira/browse/GERONIMO-2723 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Anita Kulshreshtha Fix For: 2.0-beta1 Attachments: configs.diff, modules.diff, modules.diff The j2ee-builder should use classes from geronimo-schema-jee_5 (see http://www.nabble.com/Web-Builders-p8230881.html) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2665) CLONE -Invalid module path or references in plan should result in failed deployment or warning
[ http://issues.apache.org/jira/browse/GERONIMO-2665?page=all ] Matt Hogstrom closed GERONIMO-2665. --- Resolution: Fixed Closed at Rakesh's request. CLONE -Invalid module path or references in plan should result in failed deployment or warning -- Key: GERONIMO-2665 URL: http://issues.apache.org/jira/browse/GERONIMO-2665 Project: Geronimo Issue Type: Bug Components: deployment Reporter: Rakesh Midha Priority: Critical Fix For: Wish List If an EAR deployment plan contains a entry for a module but the path does not match that of a module in the application.xml then an error or warning should be issued at deployment time. A likely reason for this is that a developer copied the plan from another but forgot to change the uri entry for the submodule; or it could just be a simple typo. In either way, the plan won't match the intended module from the application.xml resulting in erroroneous behaviour. (added) In addition, elements in a plan that do not correspond to elements in the deployment descriptor should result in a warning or error. Examples would be an ejb listed in the openejb plan that does not correspond to an ejb in the ejb-jar.xml, or a resource-ref in the ejb that does not correspond to a resource-ref in the ejb-jar.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2661) Make geronimo schema files more human readable
[ http://issues.apache.org/jira/browse/GERONIMO-2661?page=all ] Matt Hogstrom updated GERONIMO-2661: Fix Version/s: Wish List (was: 2.0) Rakesh...this would be awesome. The comments are specifically missing as the content in the Sun XSDs are copyrighted information. If you would like to add similar comments that would be great. Bear in mind that you cannot copy what Sun has done but you can phrase in your own words what each of the various elements are. I'm moving this to wishlist. If you are interested in working on this please feel free to move this back to 2.0. Make geronimo schema files more human readable -- Key: GERONIMO-2661 URL: http://issues.apache.org/jira/browse/GERONIMO-2661 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: documentation Affects Versions: 2.0 Environment: Any Reporter: Rakesh Midha Priority: Minor Fix For: Wish List Geronimo schema files are the files which are basically exposed to all the user's to follow the guidelines while developing there plan files. These schema files should have lot of documentation just like j2ee descriptor's schema's. All the fields should be described. Schema formatting provides a nice option to do this by specifying xs:annotation xs:documentation lang=endocumentation for each element goes here/xs:documentation /xs:annotation for each and every element in schema files. I think this will make it more human readable, i believe that every file which is openly exposed to user's should have lot of documentation for readbility. What do you think? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2411) Add NOTICE and LICENSE files to CAR, WAR and EAR artifacts
[ http://issues.apache.org/jira/browse/GERONIMO-2411?page=comments#action_12458006 ] Matt Hogstrom commented on GERONIMO-2411: - Does this apply to trunk as well ? Add NOTICE and LICENSE files to CAR, WAR and EAR artifacts -- Key: GERONIMO-2411 URL: http://issues.apache.org/jira/browse/GERONIMO-2411 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 1.0, 1.2, 1.x, 1.1, 1.1.1, 1.1.x, 1.1.2 Reporter: Matt Hogstrom Assigned To: Dain Sundstrom Priority: Blocker Fix For: 1.2 For release of these artifacts they need to include the LICENSE and NOTICE files. Currently the build does not automatically include them. The M2 build needs to be updated to include these artifacts in the build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2111) Change Default WebContainer behaviour to disable AccessLogging
[ http://issues.apache.org/jira/browse/GERONIMO-2111?page=all ] Matt Hogstrom updated GERONIMO-2111: Fix Version/s: 2.0-M1 (was: 1.2) Change Default WebContainer behaviour to disable AccessLogging -- Key: GERONIMO-2111 URL: http://issues.apache.org/jira/browse/GERONIMO-2111 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 2.0-M1 Currently Tomcat and Jetty have access logging enabled by default. This should be changed to have it disabled by default for all geronimo assemblies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2129) Allow user to specify the pool size for Stateless Session beans
[ http://issues.apache.org/jira/browse/GERONIMO-2129?page=all ] Matt Hogstrom closed GERONIMO-2129. --- Resolution: Fixed Committed to Open EJB Allow user to specify the pool size for Stateless Session beans --- Key: GERONIMO-2129 URL: http://issues.apache.org/jira/browse/GERONIMO-2129 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Reporter: Matt Hogstrom Assigned To: Matt Hogstrom Fix For: 1.2 OpenEJB has code implemented to Pool Stateless session beans. This support is currently hardcoded to a cache size of one which eliminates any performance benefit of caching. A new attribute will be added to the OpenEJB XSD that will allow the user to specify the pool size to be used for a deployed stateless session bean. The attribute will be poolsize and will take an integer value as its argument. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-26) Cannot switch between EJB mode and Session Direct mode
[ http://issues.apache.org/jira/browse/DAYTRADER-26?page=all ] Matt Hogstrom closed DAYTRADER-26. -- Fix Version/s: 1.2 2.0 Resolution: Fixed Trunk Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/TradeAction.java Transmitting file data . Committed revision 482210. branches/1.2 Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/TradeAction.java Transmitting file data . Committed revision 482211 Cannot switch between EJB mode and Session Direct mode -- Key: DAYTRADER-26 URL: http://issues.apache.org/jira/browse/DAYTRADER-26 Project: DayTrader Issue Type: Bug Affects Versions: 1.2 Reporter: Christopher James Blythe Fix For: 1.2, 2.0 Attachments: daytrader-26.patch Found a small typo that went in with the changes for Stateless Session to JDBC mode that causes an exception when switching between EJB and SessionDirect mode. Will attach the 1-line patch shortly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-14) Include sql script in the ear and use a gbean to create tables etc
[ http://issues.apache.org/jira/browse/DAYTRADER-14?page=all ] Matt Hogstrom closed DAYTRADER-14. -- Fix Version/s: 1.2 2.0 Resolution: Fixed Assignee: Matt Hogstrom trunk/ Sending trunk/modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/direct/TradeDirect.java Sending trunk/modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/TradeBuildDB.java Sending trunk/modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/TradeConfigServlet.java Sendingtrunk/modules/web/src/main/webapp/configure.html Adding trunk/modules/web/src/main/webapp/dbscripts Adding trunk/modules/web/src/main/webapp/dbscripts/db2 Adding trunk/modules/web/src/main/webapp/dbscripts/db2/Table.ddl Adding trunk/modules/web/src/main/webapp/dbscripts/derby Adding trunk/modules/web/src/main/webapp/dbscripts/derby/Table.ddl Adding trunk/modules/web/src/main/webapp/dbscripts/oracle Adding trunk/modules/web/src/main/webapp/dbscripts/oracle/Table.ddl Transmitting file data ... Committed revision 482366. branches/1.2 Sending 1.2/modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/direct/TradeDirect.java Sending 1.2/modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/TradeBuildDB.java Sending 1.2/modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/TradeConfigServlet.java Sending1.2/modules/web/src/main/webapp/configure.html Adding 1.2/modules/web/src/main/webapp/dbscripts Adding 1.2/modules/web/src/main/webapp/dbscripts/db2 Adding 1.2/modules/web/src/main/webapp/dbscripts/db2/Table.ddl Adding 1.2/modules/web/src/main/webapp/dbscripts/derby Adding 1.2/modules/web/src/main/webapp/dbscripts/derby/Table.ddl Adding 1.2/modules/web/src/main/webapp/dbscripts/oracle Adding 1.2/modules/web/src/main/webapp/dbscripts/oracle/Table.ddl Transmitting file data ... Committed revision 482359. Include sql script in the ear and use a gbean to create tables etc -- Key: DAYTRADER-14 URL: http://issues.apache.org/jira/browse/DAYTRADER-14 Project: DayTrader Issue Type: Improvement Components: EJB Tier Affects Versions: 1.2 Reporter: David Jencks Assigned To: Matt Hogstrom Fix For: 1.2, 2.0 Attachments: d-j-plan.xml, DAYTRADER-14.patch, daytrader-14.patch.1019, daytrader-14.patch.11152006, daytrader-14.patch.11202006, daytrader-14.patch.11202006 You can use the DatabaseIntitializationGBean (GERONIMO-2396) in a g. plan and include the sql script in the ejb module so the database will get created if not already present. This is way better than the previous hack of including a pre-built database in the car file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-24) Clean up plan files in 1.2 branch
[ http://issues.apache.org/jira/browse/DAYTRADER-24?page=all ] Matt Hogstrom closed DAYTRADER-24. -- Fix Version/s: 1.2 2.0 Resolution: Fixed Assignee: Matt Hogstrom branches/1.2 Sending1.2/plans/dayTrader-db2-plan.xml Sending1.2/plans/dayTrader-plan.xml Sending1.2/plans/db2-resource-plan.xml Adding 1.2/plans/jetty-plan.xml Sending1.2/plans/jms-resource-plan.xml Adding 1.2/plans/tomcat-plan.xml Transmitting file data .. Committed revision 482372. trunk/ Sendingtrunk/plans/dayTrader-db2-plan.xml Sendingtrunk/plans/dayTrader-plan.xml Sendingtrunk/plans/db2-resource-plan.xml Sendingtrunk/plans/jms-resource-plan.xml Transmitting file data Committed revision 482373. Clean up plan files in 1.2 branch - Key: DAYTRADER-24 URL: http://issues.apache.org/jira/browse/DAYTRADER-24 Project: DayTrader Issue Type: Bug Affects Versions: 1.2 Reporter: Christopher James Blythe Assigned To: Matt Hogstrom Priority: Minor Fix For: 1.2, 2.0 Attachments: daytrader-24.1120.patch, daytrader-24.patch The plan files in the 1.2 branch are are based on Geronimo 1.0 and need to be updated (similar to what is in the Daytrader 1.1 branch). It would also be nice if we could add plan files for Oracle and DB2 data sources. However, it looks like we do not include the necessary Tranql rars in Geronimo to support this out of the box. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-6) Longer version (1.1.1) causes build failures on Windows in daytrader-jetty config
[ http://issues.apache.org/jira/browse/DAYTRADER-6?page=all ] Matt Hogstrom closed DAYTRADER-6. - Resolution: Won't Fix Assignee: Matt Hogstrom This problem occurred while building configurations for DayTrader in Geronimo. This is no longer the case. Longer version (1.1.1) causes build failures on Windows in daytrader-jetty config - Key: DAYTRADER-6 URL: http://issues.apache.org/jira/browse/DAYTRADER-6 Project: DayTrader Issue Type: Bug Components: buildsystem Affects Versions: 1.1.1 Reporter: John Sisson Assigned To: Matt Hogstrom Whilst developing Geronimo 1.1 for the 1.1 release I was able to build ok from a windows path C:\dev\geronimo\br\1.1 . Now that the versions have been bumped up to 1.1.1 I am now getting build failures due to the max windows file path being exceeded. An example of a path that has a problem is the following (which is 261 bytes long) C:\dev\geronimo\br\1.1\configs\daytrader-jetty\target\repository\geronimo\daytrader-derby-jetty\1.1.1-SNAPSHOT\daytrader-derby-jetty-1.1.1-SNAPSHOT.car\web.war\WEB-INF\classes\org\apache\geronimo\samples\daytrader\web\prims\PingServlet2Session2CMROne2Many.class It looks like we need to do some further trimming of file names (e.g. like in the patch attached to GERONIMO-1790). The following is the build output: + | configurations Daytrader using derby deployed on jetty | Memory: 55M/69M + DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml build:end: Attempting to download geronimo-daytrader-derby-db-1.1.1-SNAPSHOT.jar. Artifact /geronimo/jars/geronimo-daytrader-derby-db-1.1.1-SNAPSHOT.jar doesn't exist in remote repository, but it exists locally. Attempting to download daytrader-ear-1.1.ear. 983K downloaded Attempting to download openejb-1.1.1-SNAPSHOT.car. Artifact /geronimo/cars/openejb-1.1.1-SNAPSHOT.car doesn't exist in remote repository, but it exists locally. build:start: multiproject:install-callback: [echo] Running car:install for Daytrader using derby deployed on jetty car:prepare-plan: car:package: [delete] Deleting directory C:\dev\geronimo\br\1.1\configs\daytrader-jetty\target\repository [mkdir] Created dir: C:\dev\geronimo\br\1.1\configs\daytrader-jetty\target\repository Packaging configuration C:\dev\geronimo\br\1.1\configs\daytrader-jetty\target\plan\plan.xml Retrieving document at 'WEB-INF/wsdl/TradeServices.wsdl'. Retrieving document at 'WEB-INF/wsdl/TradeServices.wsdl'. 16:51:12,169 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geronimo .apache.org 16:51:12,607 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geroni mo.apache.org 16:51:12,654 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geronimo .apache.org 16:51:12,669 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geronimo .apache.org 16:51:12,669 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geroni mo.apache.org 16:51:12,685 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.geronimo .apache.org 16:51:12,685 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.g eronimo.apache.org 16:51:12,701 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples.g eronimo.apache.org 16:51:12,701 WARN [HeavyweightTypeInfoBuilder] No soap array info for schematype: [EMAIL PROTECTED]://daytrader.samples .geronimo.apache.org 16:51:13,076 ERROR [PackageBuilder] org.apache.geronimo.common.DeploymentException: Could not load servlet class org.apache.geronimo .samples.daytrader.web.prims.PingServlet2Session2CMROne2Many org.apache.geronimo.common.DeploymentException: Could not load servlet class org.apache.geronimo.samples.daytrader.web.prims.PingSer vlet2Session2CMROne2Many at org.apache.geronimo.jetty.deployment.JettyModuleBuilder.addServlet(JettyModuleBuilder.java:837) at org.apache.geronimo.jetty.deployment.JettyModuleBuilder.addServlets(JettyModuleBuilder.java:797) at org.apache.geronimo.jetty.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:704) at
[jira] Closed: (DAYTRADER-15) Stateless Session Bean to JDBC mode
[ http://issues.apache.org/jira/browse/DAYTRADER-15?page=all ] Matt Hogstrom closed DAYTRADER-15. -- Resolution: Fixed Assignee: Matt Hogstrom Applied to 1.2 and trunk This is from trunk...1.2 was done a while ago Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/TradeAction.java Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/TradeConfig.java Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/direct/KeySequenceDirect.java Sending modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/direct/TradeDirect.java Adding modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/session Adding modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/session/TradeJDBC.java Adding modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/session/TradeJDBCBean.java Adding modules/ejb/src/main/java/org/apache/geronimo/samples/daytrader/session/TradeJDBCHome.java Sendingmodules/ejb/src/main/resources/META-INF/ejb-jar.xml Adding modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/prims/PingServlet2Session2JDBC.java Adding modules/web/src/main/java/org/apache/geronimo/samples/daytrader/web/prims/PingServlet2Session2JDBCCollection.java Sendingmodules/web/src/main/webapp/WEB-INF/web.xml Sendingmodules/web/src/main/webapp/web_prmtv.html Transmitting file data Committed revision 481268. Stateless Session Bean to JDBC mode --- Key: DAYTRADER-15 URL: http://issues.apache.org/jira/browse/DAYTRADER-15 Project: DayTrader Issue Type: New Feature Affects Versions: 1.2 Reporter: Christopher James Blythe Assigned To: Matt Hogstrom Attachments: session_jdbc.patch One of the more common architectures encountered in customer environments involves stateless session beans performing JDBC statements against the database. In this environment, the stateless session bean is responsible for handling the transaction commits/rollbacks. Currently, DayTrader supports direct JDBC and SSB to Enitity bean scenarios, but does not cover the SSB to JDBC scenario. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-19) Fix various HTML syntax issues and remove un-needed import statements
[ http://issues.apache.org/jira/browse/DAYTRADER-19?page=all ] Matt Hogstrom closed DAYTRADER-19. -- Fix Version/s: 1.2 2.0 Resolution: Fixed Assignee: Matt Hogstrom Applied to trunk and branches/1.2. Fix various HTML syntax issues and remove un-needed import statements - Key: DAYTRADER-19 URL: http://issues.apache.org/jira/browse/DAYTRADER-19 Project: DayTrader Issue Type: Bug Components: Web Tier Affects Versions: 1.2 Reporter: Christopher James Blythe Assigned To: Matt Hogstrom Priority: Trivial Fix For: 1.2, 2.0 Attachments: daytrader-19.patch Just a few minor changes to the html and jsp files to fix any HTML syntax issues that are raised during eclipse validation. I have also removed a few un-needed import statement from some of the jsps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DAYTRADER-12) G2361 - unclosed statement found during trade direct test
[ http://issues.apache.org/jira/browse/DAYTRADER-12?page=all ] Matt Hogstrom closed DAYTRADER-12. -- Fix Version/s: 2.0 Resolution: Fixed Assignee: Matt Hogstrom This fix was manually applied to trunk/ branches/1.1 and branches/1.2 In the future please keep the patch to only the lines that are relevant to the change. In this case the patch file was 2200+ lines and the actual change was limited to the addition of one line. G2361 - unclosed statement found during trade direct test - Key: DAYTRADER-12 URL: http://issues.apache.org/jira/browse/DAYTRADER-12 Project: DayTrader Issue Type: Bug Affects Versions: 1.1, 1.1.1 Environment: Performance testing with DB2 XA Reporter: Donald Woods Assigned To: Matt Hogstrom Fix For: 1.1.1, 1.2, 2.0 Attachments: Daytrader-12.patch After 8 hours of stress testing with 25 users, we were receiveing OutOfMemory errors and the DB2 server was at 100% load. Discovered that there was a stmt.close() missing from TradeDirect.login(). Attaching patch that allowed us to run stess testing of 48 hours with 25 users against DB2 XA driver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2537) All Geronimo source files must be brought in line with the new ASF source header and copyright notice policy
[ http://issues.apache.org/jira/browse/GERONIMO-2537?page=comments#action_12450417 ] Matt Hogstrom commented on GERONIMO-2537: - Is this complete? I saw flurries of commits earlier. All Geronimo source files must be brought in line with the new ASF source header and copyright notice policy Key: GERONIMO-2537 URL: http://issues.apache.org/jira/browse/GERONIMO-2537 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 1.2, 1.1.2 Reporter: Kevan Miller Assigned To: Jacek Laskowski Priority: Blocker Fix For: 1.2, 1.1.2 The ASF has new requirements for Source headers and copyright notices. See http://www.apache.org/legal/src-headers.html for details. All releases after November 1, 2006 must comply with this policy. It seems that 1.2 will be post November 1... :-) All Geronimo source files in trunk must be brought in line with this new policy... If we create a 1.1.2 release, we need to insure that all src files in branches/1.1 are brought inline with this new policy, also. There seem to be some scripts that will aid with these updates (see the FAQ in the above url). However, I can't access them at the moment... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-348) Invalid module path or references in plan should result in failed deployment or warning
[ http://issues.apache.org/jira/browse/GERONIMO-348?page=all ] Matt Hogstrom updated GERONIMO-348: --- Fix Version/s: Wish List (was: 1.2) Moving out for consideration for 2.0 Invalid module path or references in plan should result in failed deployment or warning --- Key: GERONIMO-348 URL: http://issues.apache.org/jira/browse/GERONIMO-348 Project: Geronimo Issue Type: Bug Components: deployment Reporter: Jeremy Boynes Priority: Critical Fix For: Wish List If an EAR deployment plan contains a entry for a module but the path does not match that of a module in the application.xml then an error or warning should be issued at deployment time. A likely reason for this is that a developer copied the plan from another but forgot to change the uri entry for the submodule; or it could just be a simple typo. In either way, the plan won't match the intended module from the application.xml resulting in erroroneous behaviour. (added) In addition, elements in a plan that do not correspond to elements in the deployment descriptor should result in a warning or error. Examples would be an ejb listed in the openejb plan that does not correspond to an ejb in the ejb-jar.xml, or a resource-ref in the ejb that does not correspond to a resource-ref in the ejb-jar.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-734) Adding CORBA settings to local-only EJB appears to give NPE
[ http://issues.apache.org/jira/browse/GERONIMO-734?page=all ] Matt Hogstrom updated GERONIMO-734: --- Fix Version/s: Wish List (was: 1.2) Adding CORBA settings to local-only EJB appears to give NPE --- Key: GERONIMO-734 URL: http://issues.apache.org/jira/browse/GERONIMO-734 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M3 Reporter: Aaron Mulder Priority: Critical Fix For: Wish List I added a tss-link to an EJB with only local and local-home interfaces. I suspect the problem is the lack of remote interfaces, in which case this should result in a deployment error. What actually happened was: org.openejb.corba.CORBAException: java.lang.NullPointerException at org.openejb.corba.Adapter.init(Adapter.java:127) at org.openejb.corba.AdapterEntity.init(AdapterEntity.java:85) at org.openejb.corba.AdapterWrapper.start(AdapterWrapper.java:87) at org.openejb.corba.TSSBean.registerContainer(TSSBean.java:207) at org.openejb.corba.TSSBean$$FastClassByCGLIB$$57d49a76.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:719) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:94) at org.openejb.corba.TSSBean$$EnhancerByCGLIB$$7369adf9.registerContainer(generated) at org.openejb.GenericEJBContainer.doStart(GenericEJBContainer.java:396) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:850) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:328) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:111) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:133) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:503) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:207) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:141) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:503) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:207) at org.apache.geronimo.kernel.KernelGBean.startRecursiveGBean(KernelGBean.java:72) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:754) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:177) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at
[jira] Commented: (GERONIMO-803) Deploy failure during redeploy leaves app undeployed
[ http://issues.apache.org/jira/browse/GERONIMO-803?page=comments#action_12450419 ] Matt Hogstrom commented on GERONIMO-803: Aaron, can you confirm this is fixed? Deploy failure during redeploy leaves app undeployed Key: GERONIMO-803 URL: http://issues.apache.org/jira/browse/GERONIMO-803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.0-M3 Reporter: Aaron Mulder Priority: Critical Fix For: 1.2 Ouch, this is a nasty one. If you deploy app Foo, then change it to be broken (invalid DD, whatever) and redeploy it, it goes like this: 1) undeploy old one 2) try to deploy new one 3) fail The result is that the old one has been undeployed but the new one hasn't been deployed. It would be ideal if we could try the deploy operation first, and only if it appears valid, undeploy the old version and start the new version. I'm not sure how that could be done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1410) Configuration geronimo/jetty/1.0-SNAPSHOT/car defines Spring Framework - Hibernate based Web-app do not work
[ http://issues.apache.org/jira/browse/GERONIMO-1410?page=all ] Matt Hogstrom updated GERONIMO-1410: Fix Version/s: Wish List (was: 1.2) Configuration geronimo/jetty/1.0-SNAPSHOT/car defines Spring Framework - Hibernate based Web-app do not work Key: GERONIMO-1410 URL: http://issues.apache.org/jira/browse/GERONIMO-1410 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Clustering Affects Versions: 1.0 Reporter: Gianny Damour Priority: Critical Fix For: Wish List Spring Framework is defined by the base configuration geronimo/jetty/1.0-SNAPSHOT/car. This is an issue as Web-app leveraging the Hibernate integration provide by Spring cannot be deployed. Basically, Hibernate classes cannot be loaded from the configuration CL of geronimo/jetty/1.0-SNAPSHOT/car. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1873) Deployment must handle dynamically-registered module builders
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=all ] Matt Hogstrom updated GERONIMO-1873: Fix Version/s: Wish List (was: 1.2) Deployment must handle dynamically-registered module builders - Key: GERONIMO-1873 URL: http://issues.apache.org/jira/browse/GERONIMO-1873 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.1 Reporter: Aaron Mulder Priority: Critical Fix For: Wish List Currently the deployment infrastructure does some things specific to different module types -- like identifying the embedded deployment plan in a xAR so it can look up the config ID, and searching for child modules of an EAR. This is currently hardcoded to the specific set of module types supported by Geronimo by default. It should be able to handle builders deployed later (e.g. Spring, ServiceMix, whatever), which probably means it needs to be able to ask something on the server-side what modules are available, what their nested plan files are called, and what their j2eeType would be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1884) Samples not installed properly in G1.1 - several issues
[ http://issues.apache.org/jira/browse/GERONIMO-1884?page=all ] Matt Hogstrom updated GERONIMO-1884: Fix Version/s: Wish List (was: 1.2) Samples not installed properly in G1.1 - several issues --- Key: GERONIMO-1884 URL: http://issues.apache.org/jira/browse/GERONIMO-1884 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.1 Reporter: Dave Colasurdo Priority: Critical Fix For: Wish List IT appears that the Geronimo samples have recently been removed from the default distributions and replaced with the ability to download them through the admin console. There are several issues that need to be addressed: 1) The Sample links on the Geronimo welcome page are dead.. This needs to be updated with instructions on how to download, start and access the samples.. 2) Assuming that the admin console plugins is the correct spot to download the samples.. 2a) The initial panel presented to the user is a bit confusing and is missing the ldap-demo.. 2b) After downloading the jsp or servlet examples.. The user is presented with a start examples box.. Selecting this does not work and results in an exception (attached below) 2c) start examples box does not return any status 2d) Manually starting the example via the command line also does not work. and results in an exception... Exception for 2b Geronimo Application Server started # Installed configuration # id = geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car # location = /home/davecola/geronimo-1.1-041906/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/repository/geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/jsp-examples-tomcat-1.1-SNAPSHOT.car 14:12:04,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car?configurationName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car java.lang.ClassCastException at org.apache.geronimo.kernel.config.Configuration.buildClassPath(Configuration.java:380) at org.apache.geronimo.kernel.config.Configuration.createConfigurationClasssLoader(Configuration.java:322) at org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:267) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:932) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:376) at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:143) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:267) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:210) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:111) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at
[jira] Updated: (GERONIMO-1922) Plugin Export should check for shared libs
[ http://issues.apache.org/jira/browse/GERONIMO-1922?page=all ] Matt Hogstrom updated GERONIMO-1922: Fix Version/s: Wish List (was: 1.2) (was: 1.1.x) Plugin Export should check for shared libs -- Key: GERONIMO-1922 URL: http://issues.apache.org/jira/browse/GERONIMO-1922 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, Plugins Affects Versions: 1.1.1, 1.1 Reporter: Aaron Mulder Priority: Critical Fix For: Wish List The export process should check configation.findGBeans(new AbstractNameQuery(SharedLib.class.getName()) The MavenAsGeronimoServlet should not list any plugins that use the shared lib GBean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1926) Changes to navigation break remote clients
[ http://issues.apache.org/jira/browse/GERONIMO-1926?page=all ]
Matt Hogstrom updated GERONIMO-1926:
Fix Version/s: Wish List
(was: 1.2)
Changes to navigation break remote clients
--
Key: GERONIMO-1926
URL: http://issues.apache.org/jira/browse/GERONIMO-1926
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: core
Affects Versions: 1.1
Reporter: Aaron Mulder
Priority: Critical
Fix For: Wish List
Attachments: peek-remote.jar, peek.jar
From an e-mail:
I have created a simple program that calls J2EEDomain.getServerInstances() on
J2EEDomain obtained from remote kernel. Detatch the two jars to bin
directory and run the program using the cmd java -jar peek.jar. Here is
the code in the main() method.
public static void main(String[] args) throws Exception {
String host = localhost;
String username = system;
String password = manager;
for(int i = 0; i args.length-1; ++i) {
if(--username.equalsIgnoreCase(args[i])) username = args[i+1];
if(--host.equalsIgnoreCase(args[i])) host = args[i+1];
if(--password.equalsIgnoreCase(args[i])) password = args[i+1];
}
System.out.println(Using host=+host+, username=+username+,
password=+password);
KernelManagementHelper mgr =
KernelManagementHelper.getRemoteKernelManager(host, username, password);
System.out.println(KernelManagementHelper = +mgr);
J2EEDomain domain = mgr.getDomains()[0];
System.out.println(J2EEDomain = +domain);
J2EEServer[] j2eeServers = domain.getServerInstances();
System.out.println(J2EEServer = +j2eeServers[0]);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2290) Percent complete goes over 100% when installing configurations
[ http://issues.apache.org/jira/browse/GERONIMO-2290?page=all ] Matt Hogstrom updated GERONIMO-2290: Fix Version/s: 2.0 (was: 1.2) Percent complete goes over 100% when installing configurations -- Key: GERONIMO-2290 URL: http://issues.apache.org/jira/browse/GERONIMO-2290 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core, console Affects Versions: 1.1 Reporter: Aaron Mulder Priority: Critical Fix For: 2.0 Looks like the UnpackArtifactTypeHandler counts the uncompressed bytes, whereas the % is based on the content size returned by the server for the download (the compressed byte count). Probably should use an InputStream between the download stream and the ZIP stream that performs the count on read(byte[],int,int) and them use that count instead of the uncompressed count. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2561) Uber geronimo-j2ee_1.4_spec was not updated and republished for 1.1.1 to include updated geronimo-j2ee-jacc_1.0_spec-1.1.1
[ http://issues.apache.org/jira/browse/GERONIMO-2561?page=all ] Matt Hogstrom updated GERONIMO-2561: Fix Version/s: 1.1.x (was: 1.2) Assignee: Matt Hogstrom I need to take care of this but it is independent of 1.2 Uber geronimo-j2ee_1.4_spec was not updated and republished for 1.1.1 to include updated geronimo-j2ee-jacc_1.0_spec-1.1.1 -- Key: GERONIMO-2561 URL: http://issues.apache.org/jira/browse/GERONIMO-2561 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.1.1, 1.1.2, 1.2 Reporter: Donald Woods Assigned To: Matt Hogstrom Priority: Critical Fix For: 1.1.2, 1.1.x geronimo-j2ee-jacc_1.0_spec was updated to version 1.1.1 for the Geronimo 1.1.1 release, but the uber geronimo-j2ee_1.4_spec was not rebuilt and republished to include the JACC updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2416) ProxyMethodInterceptor should work with classes that have start,stop methods
[ http://issues.apache.org/jira/browse/GERONIMO-2416?page=all ]
Matt Hogstrom updated GERONIMO-2416:
Fix Version/s: 2.0
(was: 1.2)
ProxyMethodInterceptor should work with classes that have start,stop methods
Key: GERONIMO-2416
URL: http://issues.apache.org/jira/browse/GERONIMO-2416
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: kernel
Affects Versions: 1.2
Reporter: David Jencks
Assigned To: Dain Sundstrom
Priority: Critical
Fix For: 2.0
jetty6 components usually have lifecycle methods start,stop, and possibly
others. If we write a gbean extending these objects ProxyMethodInterceptor
blows up with an ArrayIndexOutOfBoundsException (-1). I don't understand why
this happens, and there might be a different cause, but the gbeans that have
this problem all extend jetty objects with start methods.
A really bad workaround that lets the server start is this patch:
Index:
modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
===
---
modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
(revision 447903)
+++
modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/basic/ProxyMethodInterceptor.java
(working copy)
@@ -110,14 +110,29 @@
invokers[getSuperIndex(proxyType, proxyType.getMethod(equals,
new Class[]{Object.class}))] = new EqualsInvoke(kernel);
invokers[getSuperIndex(proxyType,
proxyType.getMethod(hashCode, null))] = new HashCodeInvoke();
invokers[getSuperIndex(proxyType,
proxyType.getMethod(toString, null))] = new
ToStringInvoke(proxyType.getName());
-if(GeronimoManagedBean.class.isAssignableFrom(proxyType)) {
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(getState, null))] = new GetStateInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(getStateInstance, null))] = new
GetStateInstanceInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(start, null))] = new StartInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(startRecursive, null))] = new
StartRecursiveInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(stop, null))] = new StopInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(getStartTime, null))] = new GetStartTimeInvoke(kernel);
-invokers[getSuperIndex(proxyType,
proxyType.getMethod(getObjectName, null))] = new
GetObjectNameInvoke(kernel);
+if (GeronimoManagedBean.class.isAssignableFrom(proxyType)) {
+int superIndex;
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(getState, null))) -1) {
+invokers[superIndex] = new GetStateInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(getStateInstance, null))) -1) {
+invokers[superIndex] = new
GetStateInstanceInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(start, null))) -1) {
+invokers[superIndex] = new StartInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(startRecursive, null))) -1) {
+invokers[superIndex] = new StartRecursiveInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(stop, null))) -1) {
+invokers[superIndex] = new StopInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(getStartTime, null))) -1) {
+invokers[superIndex] = new GetStartTimeInvoke(kernel);
+}
+if ((superIndex = getSuperIndex(proxyType,
proxyType.getMethod(getObjectName, null))) -1) {
+invokers[superIndex] = new GetObjectNameInvoke(kernel);
+}
}
} catch (Exception e) {
// this can not happen... all classes must implement equals,
hashCode and toString
Dain, do you have any clues why this is happening?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
[jira] Closed: (GERONIMO-2507) Starting the webconsole config is taking *way* too much time
[ http://issues.apache.org/jira/browse/GERONIMO-2507?page=all ] Matt Hogstrom closed GERONIMO-2507. --- Resolution: Fixed Fix recorded against GERONIMO-2571. Starting the webconsole config is taking *way* too much time Key: GERONIMO-2507 URL: http://issues.apache.org/jira/browse/GERONIMO-2507 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: Kevan Miller Priority: Critical Fix For: 1.2 Server startup time of 1.2 has more than doubled. The vast majority of time is being spent starting the webconsole config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-644) Serialized form of GBeans objects must each declare SUID
[ http://issues.apache.org/jira/browse/GERONIMO-644?page=all ] Matt Hogstrom closed GERONIMO-644. -- Resolution: Later This problem is a project issue and a development standard. We'll address this through documentation. Serialized form of GBeans objects must each declare SUID Key: GERONIMO-644 URL: http://issues.apache.org/jira/browse/GERONIMO-644 Project: Geronimo Issue Type: Bug Components: kernel Reporter: Tim Ellison Fix For: 1.2 Since Geronimo exchanges config information via serialized form of Java objects, its imperative that the serializable classes declare a serialVersionUID. If they don't then the serialized form is not necessarily compatible across Java implementations (or even Java compilers) [1]. The case in point is the wire format classes in ActiveMQ (e.g. org.codehaus.activemq.message.DefaultWireFormat) which are marked serializable and do not declare a static ID. I've tried raising this with ActiveMQ [2] but without success. I can provide the required SUID in each case, but it looks like I might need help to get it into the ActiveMQ code. [1] http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100 [2] http://article.gmane.org/gmane.comp.java.activemq.devel/486 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
