[jira] [Commented] (GERONIMO-6429) CLONE - Problem with attribute manager
[ https://issues.apache.org/jira/browse/GERONIMO-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13549399#comment-13549399 ] John Sisson commented on GERONIMO-6429: --- This was a very long time ago... Did a bit of googling for GERONIMO-2095 and found this: http://mail-archives.apache.org/mod_mbox/geronimo-scm/200606.mbox/%3c20060609052636.267f41a9...@eris.apache.org%3E The changes seem to be related to ensuring the file is properly closed when exceptions occur. Sorry, I don't have the time to investigate further. I haven't looked at the code, but might be worth investigating whether there could be anything else running on the system opening files that may cause it to be in use and prevent it from being renamed (e.g. antivirus, file indexer, backup). CLONE - Problem with attribute manager -- Key: GERONIMO-6429 URL: https://issues.apache.org/jira/browse/GERONIMO-6429 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Environment: http://people.apache.org/~hogstrom/20060607/geronimo-jetty-j2ee-1.1-20060607.tar.gz Windows XP, cygwin Command line: java -jar bin/server.jar Free disk space: 3 Gb Reporter: Amit S Assignee: John Sisson Priority: Critical gnodet@guillaumes /cygdrive/c/tmp/geronimo-1.1-20060607 $ java -jar bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_06)... Starting Geronimo Application Server v1.1-20060607 [** ] 30% 21s Starting geronimo/system-database...20:32:49,484 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [** ] 84% 39s Starting geronimo/webconsole-jett...20:33:07,890 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [**] 100% 45s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8009 0.0.0.0 Jetty Connector AJP13 8080 0.0.0.0 Jetty Connector HTTP 8443 0.0.0.0 Jetty Connector HTTPS 0.0.0.0 JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/webconsole-jetty/1.1-20060607/car RAR: geronimo/activemq/1.1-20060607/car RAR: geronimo/system-database/1.1-20060607/car WAR: geronimo/remote-deploy-jetty/1.1-20060607/car WAR: geronimo/welcome-jetty/1.1-20060607/car Web Applications: http://guillaumes:8080/ http://guillaumes:8080/console http://guillaumes:8080/console-standard http://guillaumes:8080/remote-deploy Geronimo Application Server started 20:33:18,718 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) -- This message is
[jira] Updated: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sisson updated GERONIMO-4475: -- Summary: Improve JMS portlet for AMQ 5.3 Broker configuration (was: Improve JMS portlet for AMQ 5.3 Borker configuration) Corrected description Improve JMS portlet for AMQ 5.3 Broker configuration Key: GERONIMO-4475 URL: https://issues.apache.org/jira/browse/GERONIMO-4475 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Assignee: Ivan Fix For: 2.2 Attachments: G4475-activemq-broker-00.patch, G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch, G4475-geronimo-activemq.patch, G4475-geronimo-management.patch Currently in the administrator console, the users could not add another embed broker. Also, they could not edit the broker through administrator console. I list the features that I could see : 1. While creating the broker, let the use upload a configuration file. 2. While editing the broker, show a text area, so that the user could edit the spring XML file in it. Shall we give the user a more friendly interface, so that they do not need the edit the XML file directly. I am not sure how it should look like. 3. Update the connector port let, so that while creating a new connector, the user could specify the broker that it belongs to. Please help to give some comments ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1786) JMS Listeners for protocols activeio, peer and openwire fail to start
[ http://issues.apache.org/jira/browse/GERONIMO-1786?page=all ] John Sisson updated GERONIMO-1786: -- Affects Version/s: 1.1.1 Updated version to include 1.1.1 ( problem still exists in 1.1.1-rc3). JMS Listeners for protocols activeio, peer and openwire fail to start - Key: GERONIMO-1786 URL: http://issues.apache.org/jira/browse/GERONIMO-1786 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, console Affects Versions: 1.0, 1.2, 1.1, 1.1.1 Environment: Geronimo 1.0.0 Reporter: Donald Woods Fix For: 1.2 Even though addition of JMS Listeners for activeio, peer and openwire protocols is successful, the listeners fail to start with the following exceptions. activeio --- java.lang.NoSuchMethodError: org.activeio.ChannelFactory: method bindAsynchChannel(Ljava/net/URI;)Lorg/activeio/AsynchChannelServer; not found openwire --- javax.jms.JMSException: Could not load protocol: openwire. Reason: java.lang.ClassNotFoundException: org.activemq.transport.openwire.OpenWireTransportServerChannelFactory peer --- javax.jms.JMSException: Could not load protocol: peer. Reason: java.lang.ClassNotFoundException: org.activemq.transport.peer.PeerTransportServerChannelFactory Stack trace of the same. 192: 14:17:49,499 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: objectName=geronimo.server:J2EEApplication=null,J2EEModule=geronimo/activemq-broker/1.0/car,J2EEServer=geronimo,br oker=ActiveMQ,j2eeType=JMSConnector,name=ActiveMQ.activeio.0.0.0.0.12340-aio 193: java.lang.NoSuchMethodError: org.activeio.ChannelFactory: method bindAsynchChannel(Ljava/net/URI;)Lorg/activeio/AsynchChannelServer; not found 194: at org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.createAsynchChannelServer(ActiveIOTranspo rtServerChannelFactory.java:60) 195: at org.activemq.transport.activeio.ActiveIOTransportServerChannelFactory.create(ActiveIOTransportServerChannelFact ory.java:49) 196: at org.activemq.transport.TransportServerChannelProvider.create(TransportServerChannelProvider.java:45) 197: at org.activemq.broker.impl.BrokerConnectorImpl.createTransportServerChannel(BrokerConnectorImpl.java:425) 198: at org.activemq.broker.impl.BrokerConnectorImpl.init(BrokerConnectorImpl.java:69) 199: at org.activemq.gbean.ActiveMQConnectorGBean.createBrokerConnector(ActiveMQConnectorGBean.java:161) 200: at org.activemq.gbean.ActiveMQConnectorGBean.doStart(ActiveMQConnectorGBean.java:129) 201: at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java(Compiled Code)) 202: at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) 203: at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) 204: at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132) 205: at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:537) 206: at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:208) 207: at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java :365) 208: at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) 209: at org.activemq.gbean.ActiveMQConnector$$EnhancerByCGLIB$$2b4c85ae.startRecursive(generated) 210: at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.processAction(JMSConnectorPortlet.java:79) 211: at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) 212: at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) 213: at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) 214: at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) 215: at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) 216: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 217: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 218: at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) 219: at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) 220: at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) 221: at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) 222: at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) 223: at
[jira] Commented: (GERONIMO-2332) RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a spec module so we don't need the schemas in svn at all
[
http://issues.apache.org/jira/browse/GERONIMO-2332?page=comments#action_12429261
]
John Sisson commented on GERONIMO-2332:
---
Agree with Alan's objection that it should be placed elsewhere.
I tested applying it to 1.1.1 and openejb/branches/v2_1_1/openejb2 and did a
build. I had to manually apply the changes to openejb's etc/project.properties
due to a conflict with the geronimo_dependency_plugin_version that is two lines
above the change.
Assuming Alan's argument is addressed *and* the new schema jar is fixed to
contain LICENSE.txt and NOTICE.txt files under META-INF, *then I'm +1*.
One other minor point is that if one builds the schema jar with just the
{{mvn}} command instead of {{mvn -o clean install -Pgenerate-source}} they will
get a BUILD SUCCESSFUL but the JAR won't contain any classes. The only other
hint of a problem is that there is the line {{[WARNING] JAR will be empty - no
content was marked for inclusion!}}. Is there something we can do to fail the
build?
RTC Put the generated xmlbeans files for the j2ee 1.4 schemas in svn in a
spec module so we don't need the schemas in svn at all
Key: GERONIMO-2332
URL: http://issues.apache.org/jira/browse/GERONIMO-2332
Project: Geronimo
Issue Type: RTC
Security Level: public(Regular issues)
Components: specs
Affects Versions: 1.2, 1.1.1, 1.1.2
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 1.2, 1.1.1, 1.1.2
Attachments: GERONIMO-2332-1.1.patch,
GERONIMO-2332-openejb-2.1.patch, GERONIMO-2332-trunk.patch,
geronimo-schema_1.4_spec-generated-src.zip, geronimo-schema_1.4_spec-src.zip
See GERONIMO-2307. It seems that the option with the least legal exposure is
to not distribute and sun schema files and not have any in our svn. This is
a proposed spec module that uses a m2 profile to pull the schemas from suns
website (where they are freely available), run xmlbeans on them, and remove
the copies of the schemas that xmlbeasn helpfully tries to include in the
output. We can then check this stuff into svn.
A normal non-profile build then just builds these sources into a jar. We can
replace the xmlbeans step in j2ee-schema with a geronimo dependency on this
new spec jar.
--
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-2307) Include appropriate license for the Sun j2ee schema files that are redistributed
[ http://issues.apache.org/jira/browse/GERONIMO-2307?page=comments#action_12428914 ] John Sisson commented on GERONIMO-2307: --- Where does it say that they are under the Berkley license? We should document the source of this information if this is the case. I just looked at j2ee-schema\src\resources\schemaorg_apache_xmlbeans\src\modules\j2ee-schema\src\j2ee_1_2dtd\application_1_2.dtd and it has similar wording to the schemas regarding written authorization. Include appropriate license for the Sun j2ee schema files that are redistributed Key: GERONIMO-2307 URL: http://issues.apache.org/jira/browse/GERONIMO-2307 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.0, 1.1 Reporter: John Sisson Assigned To: Geir Magnusson Jr Priority: Blocker Fix For: 1.1.1 Geronimo redistributes the Sun J2EE schema files for deployment descriptors etc but doesn't appear to include anything in the global license file about it. The following two statement in the copyright text in the schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ) concern me: * This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. * No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Considering the first point, we need to determine what license the files are under. Seems we need written authorization for the second point. The concern regarding copyrights for the schemas came to mind whilst testing the geronimo eclipse plugin, eclipse prompted me to acknowledge the Sun license at http://developers.sun.com/license/berkeley_license.html when caching the j2ee schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ). I can't find anything to confirm that the berkeley license displayed by eclipse is the correct license for the schemas. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/application-client_1_4.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/application_1_4.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/connector_1_5.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/ejb-jar_2_1.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/j2ee_1_4.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/j2ee_jaxrpc_mapping_1_1.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/j2ee_web_services_1_1.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/j2ee_web_services_client_1_1.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/jsp_2_0.xsd|| |(x)|(x)|(x)|./j2ee-schema/src/j2ee_1_4schema/web-app_2_4.xsd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_2dtd/application-client_1_2.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_2dtd/application_1_2.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_2dtd/ejb-jar_1_1.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_2dtd/web-app_2_2.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_2dtd/web-jsptaglibrary_1_1.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/application-client_1_3.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/application_1_3.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/connector_1_0.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/ejb-jar_2_0.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/web-app_2_3.dtd|| |(/)|(/)|(/)|./j2ee-schema/src/resources/schemaorg_apache_xmlbeans/src/modules/j2ee-schema/src/j2ee_1_3dtd/web-jsptaglibrary_1_2.dtd|| -- 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] Created: (GERONIMO-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file -- Key: GERONIMO-2308 URL: http://issues.apache.org/jira/browse/GERONIMO-2308 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 1.1, 1.0 Reporter: John Sisson Assigned To: John Sisson Priority: Blocker Fix For: 1.1.1 Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) applications\console-core (x) applications\console-ear (x) applications\console-framework (x) applications\console-standard (x) applications\daytrader (x) applications\demo (x) applications\ldap-realm-demo (x) applications\magicGball (x) applications\project.properties (x) applications\remote-deploy (x) applications\remote-deploy-lib (x) applications\uddi-db (x) applications\uddi-server (x) applications\welcome (x) modules\activation (x) modules\activemq-embedded-rar (x) modules\axis (x) modules\axis-builder (x) modules\client (x) modules\client-builder (x) modules\common (x) modules\connector (x) modules\connector-builder (x) modules\console-web (x) modules\converter (x) modules\core (x) modules\deploy-config (x) modules\deploy-jsr88 (x) modules\deploy-tool (x) modules\deployment (x) modules\derby (x) modules\directory (x) modules\hot-deploy (x) modules\installer-processing (x) modules\installer-support (x) modules\j2ee (x) modules\j2ee-builder (x) modules\j2ee-schema (x) modules\javamail-transport (x) modules\jetty (x) modules\jetty-builder (x) modules\jmx-remoting (x) modules\kernel (x) modules\mail (x) modules\management (x) modules\naming (x) modules\naming-builder (x) modules\project.properties (x) modules\scripts (x) modules\security (x) modules\security-builder (x) modules\service-builder (x) modules\system (x) modules\test-ddbean (x) modules\timer (x) modules\tomcat (x) modules\tomcat-builder (x) modules\transaction (x) modules\upgrade (x) modules\util (x) modules\web-builder (x) modules\webservices -- 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-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[
http://issues.apache.org/jira/browse/GERONIMO-2308?page=comments#action_12427183
]
John Sisson commented on GERONIMO-2308:
---
The issue in 1.1 ( I haven't checked trunk yet) is that although the files may
be there, only the NOTICE.txt file is included in the jar. It appears the
LICENSE.txt file is automatically included by the JAR plugin.
The NOTICE.txt file can be included in JARs by making the following changes to
the project.xml files:
{noformat}
+resources
+ resource
+directory${basedir}/directory
+ includes
+includeNOTICE.txt/include
+ /includes
+ targetPathMETA-INF/targetPath
+ /resource
+/resources
{noformat}
All Geronimo JARs should include a NOTICE.txt file in addition to the
LICENSE.txt file
--
Key: GERONIMO-2308
URL: http://issues.apache.org/jira/browse/GERONIMO-2308
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: buildsystem
Affects Versions: 1.0, 1.1
Reporter: John Sisson
Assigned To: John Sisson
Priority: Blocker
Fix For: 1.1.1
Currently Geronimo jars (e.g. the JARs for each application/module) do not
contain a NOTICE.txt file under the META-INF directory.
The NOTICE.txt files in modules needs to contain attributions that are
relevant for that module (not Geronimo as a whole). For example, if the
module has a dependency on a library that has a license requiring
attributions upon use of the library (e.g. it has wording Redistribution and
use of this software in the library license) then the module using the
library should contain the attribution in the NOTICE.txt file.
Whilst reviewing attributions, the LICENSE.txt files for the modules and
applications should also be updated to include the relevant licenses.
The following is a checklist to help track what has been done, in case
someone wants to help out :-)
(x) applications\console-core
(x) applications\console-ear
(x) applications\console-framework
(x) applications\console-standard
(x) applications\daytrader
(x) applications\demo
(x) applications\ldap-realm-demo
(x) applications\magicGball
(x) applications\project.properties
(x) applications\remote-deploy
(x) applications\remote-deploy-lib
(x) applications\uddi-db
(x) applications\uddi-server
(x) applications\welcome
(x) modules\activation
(x) modules\activemq-embedded-rar
(x) modules\axis
(x) modules\axis-builder
(x) modules\client
(x) modules\client-builder
(x) modules\common
(x) modules\connector
(x) modules\connector-builder
(x) modules\console-web
(x) modules\converter
(x) modules\core
(x) modules\deploy-config
(x) modules\deploy-jsr88
(x) modules\deploy-tool
(x) modules\deployment
(x) modules\derby
(x) modules\directory
(x) modules\hot-deploy
(x) modules\installer-processing
(x) modules\installer-support
(x) modules\j2ee
(x) modules\j2ee-builder
(x) modules\j2ee-schema
(x) modules\javamail-transport
(x) modules\jetty
(x) modules\jetty-builder
(x) modules\jmx-remoting
(x) modules\kernel
(x) modules\mail
(x) modules\management
(x) modules\naming
(x) modules\naming-builder
(x) modules\project.properties
(x) modules\scripts
(x) modules\security
(x) modules\security-builder
(x) modules\service-builder
(x) modules\system
(x) modules\test-ddbean
(x) modules\timer
(x) modules\tomcat
(x) modules\tomcat-builder
(x) modules\transaction
(x) modules\upgrade
(x) modules\util
(x) modules\web-builder
(x) modules\webservices
--
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-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=comments#action_12427184 ] John Sisson commented on GERONIMO-2308: --- Correction to previous comment... only the LICENCE.txt file is included in the jar. All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file -- Key: GERONIMO-2308 URL: http://issues.apache.org/jira/browse/GERONIMO-2308 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.0, 1.1 Reporter: John Sisson Assigned To: John Sisson Priority: Blocker Fix For: 1.1.1 Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) applications\console-core (x) applications\console-ear (x) applications\console-framework (x) applications\console-standard (x) applications\daytrader (x) applications\demo (x) applications\ldap-realm-demo (x) applications\magicGball (x) applications\project.properties (x) applications\remote-deploy (x) applications\remote-deploy-lib (x) applications\uddi-db (x) applications\uddi-server (x) applications\welcome (x) modules\activation (x) modules\activemq-embedded-rar (x) modules\axis (x) modules\axis-builder (x) modules\client (x) modules\client-builder (x) modules\common (x) modules\connector (x) modules\connector-builder (x) modules\console-web (x) modules\converter (x) modules\core (x) modules\deploy-config (x) modules\deploy-jsr88 (x) modules\deploy-tool (x) modules\deployment (x) modules\derby (x) modules\directory (x) modules\hot-deploy (x) modules\installer-processing (x) modules\installer-support (x) modules\j2ee (x) modules\j2ee-builder (x) modules\j2ee-schema (x) modules\javamail-transport (x) modules\jetty (x) modules\jetty-builder (x) modules\jmx-remoting (x) modules\kernel (x) modules\mail (x) modules\management (x) modules\naming (x) modules\naming-builder (x) modules\project.properties (x) modules\scripts (x) modules\security (x) modules\security-builder (x) modules\service-builder (x) modules\system (x) modules\test-ddbean (x) modules\timer (x) modules\tomcat (x) modules\tomcat-builder (x) modules\transaction (x) modules\upgrade (x) modules\util (x) modules\web-builder (x) modules\webservices -- 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-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=all ] John Sisson updated GERONIMO-2308: -- Description: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(x)|(x)|applications\console-core| | |(x)|(x)|(x)|applications\console-ear|Include concurrent license| |(x)|(x)|(x)|applications\console-framework| | |(x)|(x)|(x)|applications\console-standard| | |(x)|(x)|(x)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|(x)|modules\axis| | |(x)|(x)|(x)|modules\axis-builder| | |(x)|(x)|(x)|modules\client| | |(x)|(x)|(x)|modules\client-builder| | |(x)|(x)|(x)|modules\common| | |(x)|(x)|(x)|modules\connector| | |(x)|(x)|(x)|modules\connector-builder| | |(x)|(x)|(x)|modules\console-web| | |(x)|(x)|(x)|modules\converter| | |(x)|(x)|(x)|modules\core| | |(x)|(x)|(x)|modules\deploy-config| | |(x)|(x)|(x)|modules\deploy-jsr88| | |(x)|(x)|(x)|modules\deploy-tool| | |(x)|(x)|(x)|modules\deployment| | |(x)|(x)|(x)|modules\derby| | |(x)|(x)|(x)|modules\directory| | |(x)|(x)|(x)|modules\hot-deploy| | |(x)|(x)|(x)|modules\installer-processing| | |(x)|(x)|(x)|modules\installer-support| | |(x)|(x)|(x)|modules\j2ee| | |(x)|(x)|(x)|modules\j2ee-builder| | |(x)|(x)|(x)|modules\j2ee-schema| | |(x)|(x)|(x)|modules\javamail-transport| | |(x)|(x)|(x)|modules\jetty| | |(x)|(x)|(x)|modules\jetty-builder| | |(x)|(x)|(x)|modules\jmx-remoting| | |(x)|(x)|(x)|modules\kernel| | |(x)|(x)|(x)|modules\mail| | |(x)|(x)|(x)|modules\management| | |(x)|(x)|(x)|modules\naming| | |(x)|(x)|(x)|modules\naming-builder| | |(x)|(x)|(x)|modules\project.properties| | |(x)|(x)|(x)|modules\scripts| | |(x)|(x)|(x)|modules\security| | |(x)|(x)|(x)|modules\security-builder| | |(x)|(x)|(x)|modules\service-builder| | |(x)|(x)|(x)|modules\system| | |(x)|(x)|(x)|modules\test-ddbean| | |(x)|(x)|(x)|modules\timer| | |(x)|(x)|(x)|modules\tomcat| | |(x)|(x)|(x)|modules\tomcat-builder| | |(x)|(x)|(x)|modules\transaction| | |(x)|(x)|(x)|modules\upgrade| | |(x)|(x)|(x)|modules\util| | |(x)|(x)|(x)|modules\web-builder| | |(x)|(x)|(x)|modules\webservices| | was: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(x)|applications\console-core| | |(x)|(x)|applications\console-ear|Include concurrent license| |(x)|(x)|applications\console-framework| | |(x)|(x)|applications\console-standard| | |(x)|(x)|applications\daytrader| | |(x)|(x)|applications\demo| | |(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|applications\magicGball| | |(x)|(x)|applications\project.properties| | |(x)|(x)|applications\remote-deploy| | |(x)|(x)|applications\remote-deploy-lib| | |(x)|(x)|applications\uddi-db| | |(x)|(x)|applications\uddi-server| | |(x)|(x)|applications\welcome| | |(x)|(x)|modules\activation| | |(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|modules\axis| | |(x)|(x)|modules\axis-builder| | |(x)|(x)|modules\client| | |(x)|(x)|modules\client-builder| |
[jira] Updated: (GERONIMO-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=all ] John Sisson updated GERONIMO-2308: -- Description: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(/)|(/)|applications\console-core| | |(x)|(/)|(/)|applications\console-ear|Include concurrent license| |(x)|(x)|(x)|applications\console-framework| | |(x)|(x)|(x)|applications\console-standard| | |(x)|(x)|(x)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|(x)|modules\axis| | |(x)|(x)|(x)|modules\axis-builder| | |(x)|(x)|(x)|modules\client| | |(x)|(x)|(x)|modules\client-builder| | |(x)|(x)|(x)|modules\common| | |(x)|(x)|(x)|modules\connector| | |(x)|(x)|(x)|modules\connector-builder| | |(x)|(x)|(x)|modules\console-web| | |(x)|(x)|(x)|modules\converter| | |(x)|(x)|(x)|modules\core| | |(x)|(x)|(x)|modules\deploy-config| | |(x)|(x)|(x)|modules\deploy-jsr88| | |(x)|(x)|(x)|modules\deploy-tool| | |(x)|(x)|(x)|modules\deployment| | |(x)|(x)|(x)|modules\derby| | |(x)|(x)|(x)|modules\directory| | |(x)|(x)|(x)|modules\hot-deploy| | |(x)|(x)|(x)|modules\installer-processing| | |(x)|(x)|(x)|modules\installer-support| | |(x)|(x)|(x)|modules\j2ee| | |(x)|(x)|(x)|modules\j2ee-builder| | |(x)|(x)|(x)|modules\j2ee-schema| | |(x)|(x)|(x)|modules\javamail-transport| | |(x)|(x)|(x)|modules\jetty| | |(x)|(x)|(x)|modules\jetty-builder| | |(x)|(x)|(x)|modules\jmx-remoting| | |(x)|(x)|(x)|modules\kernel| | |(x)|(x)|(x)|modules\mail| | |(x)|(x)|(x)|modules\management| | |(x)|(x)|(x)|modules\naming| | |(x)|(x)|(x)|modules\naming-builder| | |(x)|(x)|(x)|modules\project.properties| | |(x)|(x)|(x)|modules\scripts| | |(x)|(x)|(x)|modules\security| | |(x)|(x)|(x)|modules\security-builder| | |(x)|(x)|(x)|modules\service-builder| | |(x)|(x)|(x)|modules\system| | |(x)|(x)|(x)|modules\test-ddbean| | |(x)|(x)|(x)|modules\timer| | |(x)|(x)|(x)|modules\tomcat| | |(x)|(x)|(x)|modules\tomcat-builder| | |(x)|(x)|(x)|modules\transaction| | |(x)|(x)|(x)|modules\upgrade| | |(x)|(x)|(x)|modules\util| | |(x)|(x)|(x)|modules\web-builder| | |(x)|(x)|(x)|modules\webservices| | was: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(x)|(x)|applications\console-core| | |(x)|(x)|(x)|applications\console-ear|Include concurrent license| |(x)|(x)|(x)|applications\console-framework| | |(x)|(x)|(x)|applications\console-standard| | |(x)|(x)|(x)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|(x)|modules\axis| |
[jira] Updated: (GERONIMO-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=all ] John Sisson updated GERONIMO-2308: -- Description: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(?)|(?)|applications\console-core| Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-ear|Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-framework|Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-standard|Notice needs IBM attribution| |(x)|(/)|(/)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|(x)|modules\axis| | |(x)|(x)|(x)|modules\axis-builder| | |(x)|(x)|(x)|modules\client| | |(x)|(x)|(x)|modules\client-builder| | |(x)|(x)|(x)|modules\common| | |(x)|(x)|(x)|modules\connector| | |(x)|(x)|(x)|modules\connector-builder| | |(x)|(x)|(x)|modules\console-web| | |(x)|(x)|(x)|modules\converter| | |(x)|(x)|(x)|modules\core| | |(x)|(x)|(x)|modules\deploy-config| | |(x)|(x)|(x)|modules\deploy-jsr88| | |(x)|(x)|(x)|modules\deploy-tool| | |(x)|(x)|(x)|modules\deployment| | |(x)|(x)|(x)|modules\derby| | |(x)|(x)|(x)|modules\directory| | |(x)|(x)|(x)|modules\hot-deploy| | |(x)|(x)|(x)|modules\installer-processing| | |(x)|(x)|(x)|modules\installer-support| | |(x)|(x)|(x)|modules\j2ee| | |(x)|(x)|(x)|modules\j2ee-builder| | |(x)|(x)|(x)|modules\j2ee-schema| | |(x)|(x)|(x)|modules\javamail-transport| | |(x)|(x)|(x)|modules\jetty| | |(x)|(x)|(x)|modules\jetty-builder| | |(x)|(x)|(x)|modules\jmx-remoting| | |(x)|(x)|(x)|modules\kernel| | |(x)|(x)|(x)|modules\mail| | |(x)|(x)|(x)|modules\management| | |(x)|(x)|(x)|modules\naming| | |(x)|(x)|(x)|modules\naming-builder| | |(x)|(x)|(x)|modules\project.properties| | |(x)|(x)|(x)|modules\scripts| | |(x)|(x)|(x)|modules\security| | |(x)|(x)|(x)|modules\security-builder| | |(x)|(x)|(x)|modules\service-builder| | |(x)|(x)|(x)|modules\system| | |(x)|(x)|(x)|modules\test-ddbean| | |(x)|(x)|(x)|modules\timer| | |(x)|(x)|(x)|modules\tomcat| | |(x)|(x)|(x)|modules\tomcat-builder| | |(x)|(x)|(x)|modules\transaction| | |(x)|(x)|(x)|modules\upgrade| | |(x)|(x)|(x)|modules\util| | |(x)|(x)|(x)|modules\web-builder| | |(x)|(x)|(x)|modules\webservices| | was: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(/)|(/)|applications\console-core| | |(x)|(/)|(/)|applications\console-ear|Include concurrent license| |(x)|(x)|(x)|applications\console-framework| | |(x)|(x)|(x)|applications\console-standard| | |(x)|(x)|(x)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| |
[jira] Updated: (GERONIMO-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=all ] John Sisson updated GERONIMO-2308: -- Description: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(?)|(?)|applications\console-core| Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-ear|Notice needs IBM attribution| |(x)|(x)|(x)|applications\console-framework|Notice needs IBM attribution| |(x)|(x)|(x)|applications\console-standard|Notice needs IBM attribution| |(x)|(/)|(/)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| | |(x)|(x)|(x)|applications\welcome| | |(x)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(x)|(x)|(x)|modules\axis| | |(x)|(x)|(x)|modules\axis-builder| | |(x)|(x)|(x)|modules\client| | |(x)|(x)|(x)|modules\client-builder| | |(x)|(x)|(x)|modules\common| | |(x)|(x)|(x)|modules\connector| | |(x)|(x)|(x)|modules\connector-builder| | |(x)|(x)|(x)|modules\console-web| | |(x)|(x)|(x)|modules\converter| | |(x)|(x)|(x)|modules\core| | |(x)|(x)|(x)|modules\deploy-config| | |(x)|(x)|(x)|modules\deploy-jsr88| | |(x)|(x)|(x)|modules\deploy-tool| | |(x)|(x)|(x)|modules\deployment| | |(x)|(x)|(x)|modules\derby| | |(x)|(x)|(x)|modules\directory| | |(x)|(x)|(x)|modules\hot-deploy| | |(x)|(x)|(x)|modules\installer-processing| | |(x)|(x)|(x)|modules\installer-support| | |(x)|(x)|(x)|modules\j2ee| | |(x)|(x)|(x)|modules\j2ee-builder| | |(x)|(x)|(x)|modules\j2ee-schema| | |(x)|(x)|(x)|modules\javamail-transport| | |(x)|(x)|(x)|modules\jetty| | |(x)|(x)|(x)|modules\jetty-builder| | |(x)|(x)|(x)|modules\jmx-remoting| | |(x)|(x)|(x)|modules\kernel| | |(x)|(x)|(x)|modules\mail| | |(x)|(x)|(x)|modules\management| | |(x)|(x)|(x)|modules\naming| | |(x)|(x)|(x)|modules\naming-builder| | |(x)|(x)|(x)|modules\project.properties| | |(x)|(x)|(x)|modules\scripts| | |(x)|(x)|(x)|modules\security| | |(x)|(x)|(x)|modules\security-builder| | |(x)|(x)|(x)|modules\service-builder| | |(x)|(x)|(x)|modules\system| | |(x)|(x)|(x)|modules\test-ddbean| | |(x)|(x)|(x)|modules\timer| | |(x)|(x)|(x)|modules\tomcat| | |(x)|(x)|(x)|modules\tomcat-builder| | |(x)|(x)|(x)|modules\transaction| | |(x)|(x)|(x)|modules\upgrade| | |(x)|(x)|(x)|modules\util| | |(x)|(x)|(x)|modules\web-builder| | |(x)|(x)|(x)|modules\webservices| | was: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(?)|(?)|applications\console-core| Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-ear|Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-framework|Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-standard|Notice needs IBM attribution| |(x)|(/)|(/)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| | |(x)|(x)|(x)|applications\uddi-server| |
[jira] Updated: (GERONIMO-2308) All Geronimo JARs should include a NOTICE.txt file in addition to the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2308?page=all ] John Sisson updated GERONIMO-2308: -- Description: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(/)|(/)|applications\console-core| Notice needs IBM attribution?| |(x)|(/)|(/)|applications\console-ear|Notice needs IBM attribution?| |(x)|(/)|(/)|applications\console-framework|Notice needs IBM attribution?| |(x)|(/)|(/)|applications\console-standard|Notice needs IBM attribution?| |(x)|(/)|(/)|applications\daytrader| | |(x)|(/)|(/)|applications\demo| | |(x)|(/)|(/)|applications\ldap-realm-demo| | |(x)|(/)|(/)|applications\magicGball| | |(x)|(/)|(/)|applications\project.properties| | |(x)|(/)|(/)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(/)|(/)|applications\uddi-db| | |(x)|(/)|(/)|applications\uddi-server| | |(x)|(/)|(/)|applications\welcome| | |(?)|(x)|(x)|modules\activation| | |(x)|(x)|(x)|modules\activemq-embedded-rar| | |(?)|(x)|(x)|modules\axis| | |(?)|(x)|(x)|modules\axis-builder| | |(?)|(x)|(x)|modules\client| | |(?)|(x)|(x)|modules\client-builder| | |(?)|(x)|(x)|modules\common| | |(?)|(x)|(x)|modules\connector| | |(?)|(x)|(x)|modules\connector-builder| | |(/)|(x)|(x)|modules\console-web| (Won't fix in trunk) | |(?)|(x)|(x)|modules\converter| | |(?)|(x)|(x)|modules\core| | |(?)|(x)|(x)|modules\deploy-config| | |(?)|(x)|(x)|modules\deploy-jsr88| | |(?)|(x)|(x)|modules\deploy-tool| | |(?)|(x)|(x)|modules\deployment| | |(?)|(x)|(x)|modules\derby| | |(?)|(x)|(x)|modules\directory| | |(?)|(x)|(x)|modules\hot-deploy| | |(?)|(x)|(x)|modules\installer-processing| | |(?)|(x)|(x)|modules\installer-support| | |(?)|(x)|(x)|modules\j2ee| | |(?)|(x)|(x)|modules\j2ee-builder| | |(?)|(x)|(x)|modules\j2ee-schema| | |(/)|(x)|(x)|modules\javamail-transport| (No longer in trunk) | |(?)|(x)|(x)|modules\jetty| | |(?)|(x)|(x)|modules\jetty-builder| | |(?)|(x)|(x)|modules\jmx-remoting| | |(?)|(x)|(x)|modules\kernel| | |(?)|(x)|(x)|modules\mail| | |(?)|(x)|(x)|modules\management| | |(?)|(x)|(x)|modules\naming| | |(?)|(x)|(x)|modules\naming-builder| | |(/)|(x)|(x)|modules\scripts| (Not distributed) | |(?)|(x)|(x)|modules\security| | |(?)|(x)|(x)|modules\security-builder| | |(?)|(x)|(x)|modules\service-builder| | |(?)|(x)|(x)|modules\system| | |(?)|(x)|(x)|modules\test-ddbean| | |(?)|(x)|(x)|modules\timer| | |(?)|(x)|(x)|modules\tomcat| | |(?)|(x)|(x)|modules\tomcat-builder| | |(?)|(x)|(x)|modules\transaction| | |(?)|(x)|(x)|modules\upgrade| | |(?)|(x)|(x)|modules\util| | |(?)|(x)|(x)|modules\web-builder| | |(?)|(x)|(x)|modules\webservices| | was: Currently Geronimo jars (e.g. the JARs for each application/module) do not contain a NOTICE.txt file under the META-INF directory. The NOTICE.txt files in modules needs to contain attributions that are relevant for that module (not Geronimo as a whole). For example, if the module has a dependency on a library that has a license requiring attributions upon use of the library (e.g. it has wording Redistribution and use of this software in the library license) then the module using the library should contain the attribution in the NOTICE.txt file. Whilst reviewing attributions, the LICENSE.txt files for the modules and applications should also be updated to include the relevant licenses. The following is a checklist to help track what has been done, in case someone wants to help out :-) (x) = not done (?) = partially done (/) = done ||trunk||1.1||1.1.1||Notes|| |(x)|(?)|(?)|applications\console-core| Notice needs IBM attribution| |(x)|(?)|(?)|applications\console-ear|Notice needs IBM attribution| |(x)|(x)|(x)|applications\console-framework|Notice needs IBM attribution| |(x)|(x)|(x)|applications\console-standard|Notice needs IBM attribution| |(x)|(/)|(/)|applications\daytrader| | |(x)|(x)|(x)|applications\demo| | |(x)|(x)|(x)|applications\ldap-realm-demo| | |(x)|(x)|(x)|applications\magicGball| | |(x)|(x)|(x)|applications\project.properties| | |(x)|(x)|(x)|applications\remote-deploy| | |(x)|(/)|(/)|applications\remote-deploy-lib| | |(x)|(x)|(x)|applications\uddi-db| |
[jira] Created: (GERONIMO-2307) Include appropriate license for the Sun j2ee schema files that are redistributed
Include appropriate license for the Sun j2ee schema files that are redistributed Key: GERONIMO-2307 URL: http://issues.apache.org/jira/browse/GERONIMO-2307 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 1.1, 1.0 Reporter: John Sisson Assigned To: John Sisson Priority: Blocker Fix For: 1.1.1 Geronimo redistributes the Sun J2EE schema files for deployment descriptors etc but doesn't appear to include anything in the global license file about it. The following two statement in the copyright text in the schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ) concern me: * This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. * No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Considering the first point, we need to determine what license the files are under. Seems we need written authorization for the second point. The concern regarding copyrights for the schemas came to mind whilst testing the geronimo eclipse plugin, eclipse prompted me to acknowledge the Sun license at http://developers.sun.com/license/berkeley_license.html when caching the j2ee schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ). I can't find anything to confirm that the berkeley license displayed by eclipse is the correct license for the schemas. -- 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] Assigned: (GERONIMO-2307) Include appropriate license for the Sun j2ee schema files that are redistributed
[ http://issues.apache.org/jira/browse/GERONIMO-2307?page=all ] John Sisson reassigned GERONIMO-2307: - Assignee: Geir Magnusson Jr (was: John Sisson) Geir said he will follow this up. Include appropriate license for the Sun j2ee schema files that are redistributed Key: GERONIMO-2307 URL: http://issues.apache.org/jira/browse/GERONIMO-2307 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 1.0, 1.1 Reporter: John Sisson Assigned To: Geir Magnusson Jr Priority: Blocker Fix For: 1.1.1 Geronimo redistributes the Sun J2EE schema files for deployment descriptors etc but doesn't appear to include anything in the global license file about it. The following two statement in the copyright text in the schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ) concern me: * This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. * No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Considering the first point, we need to determine what license the files are under. Seems we need written authorization for the second point. The concern regarding copyrights for the schemas came to mind whilst testing the geronimo eclipse plugin, eclipse prompted me to acknowledge the Sun license at http://developers.sun.com/license/berkeley_license.html when caching the j2ee schema files (e.g. http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd ). I can't find anything to confirm that the berkeley license displayed by eclipse is the correct license for the schemas. -- 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: (XBEAN-37) Compile error in QdoxMappingLoader introduced in XBEAN-27
[ http://issues.apache.org/jira/browse/XBEAN-37?page=all ] John Sisson closed XBEAN-37. Resolution: Fixed Compile error in QdoxMappingLoader introduced in XBEAN-27 - Key: XBEAN-37 URL: http://issues.apache.org/jira/browse/XBEAN-37 Project: XBean Issue Type: Bug Components: spring Reporter: John Sisson Assigned To: John Sisson Priority: Blocker Fix For: 2.6 Seems this compile error slipped through the RTC on the XBEAN-27 patch! C:\dev\geronimo\xbean\trunkmvn install SNIP [INFO] [INFO] Building XBean :: Spring :: Common [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 42 source files to C:\dev\geronimo\xbean\trunk\xbean-spring-common\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\dev\geronimo\xbean\trunk\xbean-spring-common\src\main\java\org\apache\xbean\spring\generator\QdoxMappingLoader.java:[507,29] repl ace(char,char) in java.lang.String cannot be applied to (java.lang.String,java.lang.String) -- 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] Created: (XBEAN-37) Compile error in QdoxMappingLoader introduced in XBEAN-27
Compile error in QdoxMappingLoader introduced in XBEAN-27 - Key: XBEAN-37 URL: http://issues.apache.org/jira/browse/XBEAN-37 Project: XBean Issue Type: Bug Components: spring Reporter: John Sisson Assigned To: John Sisson Priority: Blocker Fix For: 2.6 Seems this compile error slipped through the RTC on the XBEAN-27 patch! C:\dev\geronimo\xbean\trunkmvn install SNIP [INFO] [INFO] Building XBean :: Spring :: Common [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 42 source files to C:\dev\geronimo\xbean\trunk\xbean-spring-common\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\dev\geronimo\xbean\trunk\xbean-spring-common\src\main\java\org\apache\xbean\spring\generator\QdoxMappingLoader.java:[507,29] repl ace(char,char) in java.lang.String cannot be applied to (java.lang.String,java.lang.String) -- 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-1939) Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer
[ http://issues.apache.org/jira/browse/GERONIMO-1939?page=comments#action_12424762 ] John Sisson commented on GERONIMO-1939: --- Do the scripts available from Adobe help? http://www.adobe.com/svg/workflow/autoinstall.html The license for the script files says: // Copyright 2000 Adobe Systems Incorporated. All rights reserved. Permission // to use, modify, distribute, and publicly display this file is hereby // granted. This file is provided AS-IS with absolutely no warranties of any // kind. Portions (C) Netscape Communications 1999. // If you modify this file, please share your changes with Adobe and other SVG // developers at http://www.adobe.com/svg/. Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer - Key: GERONIMO-1939 URL: http://issues.apache.org/jira/browse/GERONIMO-1939 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Chris Cardona I've tested it to work on Firefox v1.5.0.2 but the graph doesn't show up on IE v6.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] Commented: (GERONIMO-1939) Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer
[ http://issues.apache.org/jira/browse/GERONIMO-1939?page=comments#action_12424766 ] John Sisson commented on GERONIMO-1939: --- I tried using FireFox 1.0.7 on windows (latest currently available) and if I click on the image click here to download plugin I get the Plugin finder service dialog box that just sits there seeming to do nothing. Do others have this problem? Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer - Key: GERONIMO-1939 URL: http://issues.apache.org/jira/browse/GERONIMO-1939 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Chris Cardona I've tested it to work on Firefox v1.5.0.2 but the graph doesn't show up on IE v6.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] Commented: (GERONIMO-1939) Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer
[ http://issues.apache.org/jira/browse/GERONIMO-1939?page=comments#action_12424778 ] John Sisson commented on GERONIMO-1939: --- Sorry, my comment about firefox 1.0.7 is incorrect. I just assumed that since that version said it had no updates available it was the latest. I confirmed that 1.5.0.5 works. Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer - Key: GERONIMO-1939 URL: http://issues.apache.org/jira/browse/GERONIMO-1939 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Chris Cardona Attachments: embedSVG.js I've tested it to work on Firefox v1.5.0.2 but the graph doesn't show up on IE v6.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] Closed: (GERONIMO-2136) Remove About icon and about page from console
[ http://issues.apache.org/jira/browse/GERONIMO-2136?page=all ] John Sisson closed GERONIMO-2136. - Fix Version/s: 1.2 Resolution: Fixed Remove About icon and about page from console - Key: GERONIMO-2136 URL: http://issues.apache.org/jira/browse/GERONIMO-2136 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: John Sisson Assigned To: John Sisson Priority: Trivial Fix For: 1.1.1, 1.2 h1. Problem The licenses displayed in the console in the about page ( http://localhost:8080/console/about.jsp ) are a subset of those in Geronimo's LICENSE.txt file and may be misleading. See mail thread. http://www.mail-archive.com/dev%40geronimo.apache.org/msg24852.html h1. Solution The about icon and about page will be removed from the Geronimo console. -- 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-1996) Serialization failure during deployment leaves a config.ser in the repository but doesn't write a config.info causing problems later.
[ http://issues.apache.org/jira/browse/GERONIMO-1996?page=all ]
John Sisson updated GERONIMO-1996:
--
Fix Version/s: 1.2
Description:
h1. Problem
If an Error (java.lang.Error and its subclasses) occurs during deployment and
the deployment operation fails it may not be possible to redeploy.
h1. Symptom
Example of exception during serialization phase of deployment:
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:534)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:520)
SNIP
at com.foo.server.ejb.Bar.clinit(FooBean.java:104)
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
SNIP
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:186)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.kernel.config.SerializedConfigurationMarshaler.writeConfigurationData(SerializedConfigurationMarshale
r.java:66)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.writeConfigurationData(ConfigurationUtil.java:163)
at
org.apache.geronimo.system.configuration.ExecutableConfigurationUtil.writeConfiguration(ExecutableConfigurationUtil.java:
149)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.install(RepositoryConfigurationStore.java:318)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:308)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
{code}
When restarting Geronimo after a deployment that failed during serialization
you may see the following exception:
{code}
ERROR [RepositoryConfigurationStore] Unable to load ConfigurationInfo for
com.acme.foo/foo-server-plus/3.4.060322-SNAPSHOT/ear
java.io.FileNotFoundException:
C:\test\geronimo-1.1-SNAPSHOT\repository\com\acme\foo\foo-server-plus\3.4.060322-SNAPSHOT\
foo-server-plus-3.4.060322-SNAPSHOT.ear\META-INF\config.info (The system cannot
find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:106)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.
java:401)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.jav
a:375)
{code}
Error if you attempt to undeploy the configuration you get:
{code}
11:04:27,699 ERROR [RepositoryConfigurationStore] Unable to load
ConfigurationInfo for com.acme.foo/foo-server-plus/3.4.0
60322-SNAPSHOT/ear
java.io.FileNotFoundException:
C:\test\geronimo-1.1-SNAPSHOT\repository\com\acme\foo\foo-server-plus\3.4.060322-SNAPSHOT\
foo-server-plus-3.4.060322-SNAPSHOT.ear\META-INF\config.info (The system cannot
find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:106)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.
java:401)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.jav
a:375)
at
[jira] Updated: (GERONIMO-1996) Error during deployment may result in files not being cleaned up properly
[ http://issues.apache.org/jira/browse/GERONIMO-1996?page=all ]
John Sisson updated GERONIMO-1996:
--
Summary: Error during deployment may result in files not being cleaned up
properly (was: Serialization failure during deployment leaves a config.ser in
the repository but doesn't write a config.info causing problems later.)
Error during deployment may result in files not being cleaned up properly
-
Key: GERONIMO-1996
URL: http://issues.apache.org/jira/browse/GERONIMO-1996
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.1
Reporter: John Sisson
Assigned To: John Sisson
Fix For: 1.2, 1.1.1
Attachments: jira-g-1996.zip
h1. Problem
If an Error (java.lang.Error and its subclasses) occurs during deployment and
the deployment operation fails it may not be possible to redeploy.
h1. Symptom
Example of exception during serialization phase of deployment:
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:534)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:520)
SNIP
at com.foo.server.ejb.Bar.clinit(FooBean.java:104)
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
SNIP
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:186)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.kernel.config.SerializedConfigurationMarshaler.writeConfigurationData(SerializedConfigurationMarshale
r.java:66)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.writeConfigurationData(ConfigurationUtil.java:163)
at
org.apache.geronimo.system.configuration.ExecutableConfigurationUtil.writeConfiguration(ExecutableConfigurationUtil.java:
149)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.install(RepositoryConfigurationStore.java:318)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:308)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
{code}
When restarting Geronimo after a deployment that failed during serialization
you may see the following exception:
{code}
ERROR [RepositoryConfigurationStore] Unable to load ConfigurationInfo for
com.acme.foo/foo-server-plus/3.4.060322-SNAPSHOT/ear
java.io.FileNotFoundException:
C:\test\geronimo-1.1-SNAPSHOT\repository\com\acme\foo\foo-server-plus\3.4.060322-SNAPSHOT\
foo-server-plus-3.4.060322-SNAPSHOT.ear\META-INF\config.info (The system
cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:106)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.
java:401)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.jav
a:375)
{code}
Error if you attempt to undeploy the configuration you get:
{code}
11:04:27,699
[jira] Closed: (GERONIMO-1996) Error during deployment may result in files not being cleaned up properly
[ http://issues.apache.org/jira/browse/GERONIMO-1996?page=all ]
John Sisson closed GERONIMO-1996.
-
Resolution: Fixed
Error during deployment may result in files not being cleaned up properly
-
Key: GERONIMO-1996
URL: http://issues.apache.org/jira/browse/GERONIMO-1996
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.1
Reporter: John Sisson
Assigned To: John Sisson
Fix For: 1.1.1, 1.2
Attachments: jira-g-1996.zip
h1. Problem
If an Error (java.lang.Error and its subclasses) occurs during deployment and
the deployment operation fails it may not be possible to redeploy.
h1. Symptom
Example of exception during serialization phase of deployment:
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:534)
at com.foo.common.xml.XMLNode.loadXML(XMLNode.java:520)
SNIP
at com.foo.server.ejb.Bar.clinit(FooBean.java:104)
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
SNIP
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:186)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.kernel.config.SerializedConfigurationMarshaler.writeConfigurationData(SerializedConfigurationMarshale
r.java:66)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.writeConfigurationData(ConfigurationUtil.java:163)
at
org.apache.geronimo.system.configuration.ExecutableConfigurationUtil.writeConfiguration(ExecutableConfigurationUtil.java:
149)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.install(RepositoryConfigurationStore.java:318)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:308)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:119)
{code}
When restarting Geronimo after a deployment that failed during serialization
you may see the following exception:
{code}
ERROR [RepositoryConfigurationStore] Unable to load ConfigurationInfo for
com.acme.foo/foo-server-plus/3.4.060322-SNAPSHOT/ear
java.io.FileNotFoundException:
C:\test\geronimo-1.1-SNAPSHOT\repository\com\acme\foo\foo-server-plus\3.4.060322-SNAPSHOT\
foo-server-plus-3.4.060322-SNAPSHOT.ear\META-INF\config.info (The system
cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:106)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.
java:401)
at
org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.jav
a:375)
{code}
Error if you attempt to undeploy the configuration you get:
{code}
11:04:27,699 ERROR [RepositoryConfigurationStore] Unable to load
ConfigurationInfo for com.acme.foo/foo-server-plus/3.4.0
60322-SNAPSHOT/ear
java.io.FileNotFoundException:
[jira] Closed: (GERONIMO-1810) Improve the Error: Unable to distribute foo.ear: Cannot deploy the requested application module message
[ http://issues.apache.org/jira/browse/GERONIMO-1810?page=all ] John Sisson closed GERONIMO-1810. - Resolution: Duplicate This has already been fixed by Erin's patch in GERONIMO-1360 (rev 399082). Improve the Error: Unable to distribute foo.ear: Cannot deploy the requested application module message - Key: GERONIMO-1810 URL: http://issues.apache.org/jira/browse/GERONIMO-1810 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 1.0 Reporter: John Sisson Assigned To: John Sisson Priority: Trivial Fix For: 1.1.1 Need to provide more information in the following error message, giving the user a bit more of a hint as to what the problem may be. C:\testgeronimo-1.0.1-SNAPSHOT\bin\deploy --user system --password manager deploy jstest.ear jstest.xml Using GERONIMO_BASE: C:\test\geronimo-1.0.1-SNAPSHOT Using GERONIMO_HOME: C:\test\geronimo-1.0.1-SNAPSHOT Using GERONIMO_TMPDIR: C:\test\geronimo-1.0.1-SNAPSHOT\var\temp Using JRE_HOME:C:\j2sdk1.4.2_10 Error: Unable to distribute jstest.ear: Cannot deploy the requested application module (planFile=C:\test\jstest.xml, moduleFile=C:\test\geronimo-1.0.1-SNAPSHOT\var\temp\geronimo-deployer59948.tmpdir\jstest.ear) In the case above it was due to my ear file accidentially having all the files under a directory. I propose we add the following to the end of the message: Check that the module file contains the expected deployment files and directory structure. If problems persist, ensure the appropriate module builder is running. -- 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-1810) Improve the Error: Unable to distribute foo.ear: Cannot deploy the requested application module message
[ http://issues.apache.org/jira/browse/GERONIMO-1810?page=all ] John Sisson closed GERONIMO-1810. - Improve the Error: Unable to distribute foo.ear: Cannot deploy the requested application module message - Key: GERONIMO-1810 URL: http://issues.apache.org/jira/browse/GERONIMO-1810 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 1.0 Reporter: John Sisson Assigned To: John Sisson Priority: Trivial Fix For: 1.1 Need to provide more information in the following error message, giving the user a bit more of a hint as to what the problem may be. C:\testgeronimo-1.0.1-SNAPSHOT\bin\deploy --user system --password manager deploy jstest.ear jstest.xml Using GERONIMO_BASE: C:\test\geronimo-1.0.1-SNAPSHOT Using GERONIMO_HOME: C:\test\geronimo-1.0.1-SNAPSHOT Using GERONIMO_TMPDIR: C:\test\geronimo-1.0.1-SNAPSHOT\var\temp Using JRE_HOME:C:\j2sdk1.4.2_10 Error: Unable to distribute jstest.ear: Cannot deploy the requested application module (planFile=C:\test\jstest.xml, moduleFile=C:\test\geronimo-1.0.1-SNAPSHOT\var\temp\geronimo-deployer59948.tmpdir\jstest.ear) In the case above it was due to my ear file accidentially having all the files under a directory. I propose we add the following to the end of the message: Check that the module file contains the expected deployment files and directory structure. If problems persist, ensure the appropriate module builder is running. -- 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] Created: (GERONIMO-2250) Error rather than exception from server whilst deploying causes deployer to hang (not end)
Error rather than exception from server whilst deploying causes deployer to hang (not end) -- Key: GERONIMO-2250 URL: http://issues.apache.org/jira/browse/GERONIMO-2250 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 1.1, 1.0 Reporter: John Sisson Priority: Minor Fix For: 1.x Whilst using the test application attached to GERONIMO-1996 I found that the Error from the server (e.g. java.lang.ExceptionInInitializerError ) caused the thread (see Thread-2 below) to end and the deploy command does not return. It appears that the run() methods for commands need to catch Throwable rather than Exception so that it can end more gracefully. Debugger output: Java HotSpot(TM) Client VM[localhost:8001] Thread [main] (Suspended) org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager(org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager).distribute(javax.enterprise.deploy.spi.Target[], java.io.File, java.io.File) line: 176 org.apache.geronimo.deployment.cli.CommandDeploy(org.apache.geronimo.deployment.cli.CommandDistribute).runCommand(javax.enterprise.deploy.spi.DeploymentManager, java.io.PrintWriter, boolean, javax.enterprise.deploy.spi.Target[], java.io.File, java.io.File) line: 75 org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(javax.enterprise.deploy.spi.DeploymentManager, java.io.PrintWriter, boolean, javax.enterprise.deploy.spi.Target[], java.io.File, java.io.File) line: 51 org.apache.geronimo.deployment.cli.CommandDeploy(org.apache.geronimo.deployment.cli.CommandDistribute).executeOnline(org.apache.geronimo.deployment.cli.ServerConnection, boolean, java.util.List, java.io.PrintWriter, java.io.File, java.io.File) line: 148 org.apache.geronimo.deployment.cli.CommandDeploy(org.apache.geronimo.deployment.cli.CommandDistribute).execute(java.io.PrintWriter, org.apache.geronimo.deployment.cli.ServerConnection, java.lang.String[]) line: 132 org.apache.geronimo.deployment.cli.CommandDeploy.execute(java.io.PrintWriter, org.apache.geronimo.deployment.cli.ServerConnection, java.lang.String[]) line: 60 org.apache.geronimo.deployment.cli.DeployTool.execute(java.lang.String[]) line: 159 org.apache.geronimo.deployment.cli.DeployTool.main(java.lang.String[]) line: 313 Thread [Thread-1] (Running) Thread [Connection HeartBeat] (Running) Thread [Notification Deliverer #1] (Running) Thread [Notification Fetcher #1] (Running) Thread [Thread-2] (Suspended (exception java.lang.ExceptionInInitializerError)) org.apache.geronimo.deployment.plugin.local.DistributeCommand.run() line: 65 java.lang.Thread.run() line: not available -- 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-2146) GBeanOverride ignores reference name when saving if artifact is not set
[ http://issues.apache.org/jira/browse/GERONIMO-2146?page=comments#action_12424749 ] John Sisson commented on GERONIMO-2146: --- Aaron checked in fix to 1.1 branch in http://svn.apache.org/viewvc?rev=425429view=rev GBeanOverride ignores reference name when saving if artifact is not set --- Key: GERONIMO-2146 URL: http://issues.apache.org/jira/browse/GERONIMO-2146 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: kernel Affects Versions: 1.1 Reporter: Aaron Mulder Assigned To: Aaron Mulder Fix For: 1.1.1 In writeXml the writing of name and module should be outside the if(artifact != null) block -- 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-2233) Deployment fails with InvalidConfigException: Unable to deserialize GBeanState when Sun JMX RI JAR is on classpath in EAR
[ http://issues.apache.org/jira/browse/GERONIMO-2233?page=all ]
John Sisson updated GERONIMO-2233:
--
Description:
h1. Problem
Deployment of an EAR that contains the Sun JMX RI 1.2 JAR in the classpath set
in the META-INF/MANIFEST.MF file of the JAR in the EAR fails. An EAR may
include a JMX implementation library so that it can run on J2EE 1.3 servers.
h1. Symptoms
The following error is seen on the server console:
{code}
23:58:47,831 ERROR [GBeanInstanceState] Error while starting; GBean is now in
the FAILED state: abstractName=geronimo-test/jira-g-n
nnn/1.0-SNAPSHOT/ear?configurationName=geronimo-test/jira-g-/1.0-SNAPSHOT/ear
org.apache.geronimo.kernel.config.InvalidConfigException: Unable to deserialize
GBeanState
at
org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(SerializedGBeanState.java:120)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans(SerializedGBeanState.java:65)
at
org.apache.geronimo.kernel.config.ConfigurationData.getGBeans(ConfigurationData.java:171)
at
org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:277)
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:933)
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:526)
at
org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:361)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:161)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:292)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:260)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
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:852)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:338)
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:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:852)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
at
mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203
)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
at
mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219)
at sun.reflect.GeneratedMethodAccessor347.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
[jira] Created: (GERONIMO-2233) Deployment fails with InvalidConfigException: Unable to deserialize GBeanState when Sun JMX RI JAR is on classpath in EAR
Deployment fails with InvalidConfigException: Unable to deserialize GBeanState
when Sun JMX RI JAR is on classpath in EAR
-
Key: GERONIMO-2233
URL: http://issues.apache.org/jira/browse/GERONIMO-2233
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 1.1, 1.0
Reporter: John Sisson
Priority: Minor
Fix For: 1.1.x
h1. Problem
Deployment of an EAR that contains the Sun JMX RI 1.2 JAR in the classpath set
in the META-INF/MANIFEST.MF file of the JAR in the EAR fails.
h1. Symptoms
The following error is seen on the server console:
{code}
23:58:47,831 ERROR [GBeanInstanceState] Error while starting; GBean is now in
the FAILED state: abstractName=geronimo-test/jira-g-n
nnn/1.0-SNAPSHOT/ear?configurationName=geronimo-test/jira-g-/1.0-SNAPSHOT/ear
org.apache.geronimo.kernel.config.InvalidConfigException: Unable to deserialize
GBeanState
at
org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(SerializedGBeanState.java:120)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans(SerializedGBeanState.java:65)
at
org.apache.geronimo.kernel.config.ConfigurationData.getGBeans(ConfigurationData.java:171)
at
org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:277)
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:933)
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:526)
at
org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:361)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:161)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:292)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:260)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:112)
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:852)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:338)
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:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:852)
at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168)
at
mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
[jira] Closed: (GERONIMO-2222) Application errors in static initialization blocks during serialization of configuration during deployment due to incorrect TCCL
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson closed GERONIMO-.
-
Fix Version/s: 1.2
Resolution: Fixed
Application errors in static initialization blocks during serialization of
configuration during deployment due to incorrect TCCL
-
Key: GERONIMO-
URL: http://issues.apache.org/jira/browse/GERONIMO-
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.1, 1.0
Reporter: John Sisson
Assigned To: John Sisson
Priority: Blocker
Fix For: 1.1.1, 1.2
Attachments: GERONIMO--v1.patch, jira-g--xerces-test.zip,
jira-g-.zip
h1. Problem
Exceptions and/or errors may occur in static initialization blocks invoked
whilst loading classes when serializing a configuration during deployment.
These same exceptions/errors don't occur when starting the configuration.
h1. Symptoms
Deployment of an EAR that has dependencies on its own copy of Xerces will
cause an exception similar to the following if Xerces is initialised in a
static block.
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.server.ejb.MyEJB.clinit
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:173)
at java.security.AccessController.doPrivileged(Native Method)
at
java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:170)
at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:557)
at
java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:591)
at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1142)
at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeClass(ObjectOutputStream.java:1082)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:996)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:187)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
[jira] Updated: (GERONIMO-2222) Application errors in static initialization blocks during serialization of configuration during deployment due to incorrect TCCL
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: jira-g-.zip
Test application attached that prints out the TCCL during static initialization
in an EJB. If you deploy the EAR you will see the following messages (when
this bug exists). The static initializer gets called twice (once during
serialization during deployment and the 2nd time when the configuration is
started). Notice that the TCCL differs between the two.
BugReproBean static initializer called
Thread.currentThread().getContextClassLoader() =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=geronimo/j2ee-security/1.1.1-SNAPSHOT/car]
BugReproBean.class.getClassLoader( =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=geronimo-test/jira-g-/1.0-SNAPSHOT/ear]
BugReproBean static initializer finished
BugReproBean static initializer called
Thread.currentThread().getContextClassLoader() =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=geronimo-test/jira-g-/1.0-SNAPSHOT/ear]
BugReproBean.class.getClassLoader( =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=geronimo-test/jira-g-/1.0-SNAPSHOT/ear]
BugReproBean static initializer finished
Application errors in static initialization blocks during serialization of
configuration during deployment due to incorrect TCCL
-
Key: GERONIMO-
URL: http://issues.apache.org/jira/browse/GERONIMO-
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.0, 1.1
Reporter: John Sisson
Assigned To: John Sisson
Priority: Blocker
Fix For: 1.1.1
Attachments: jira-g-.zip
h1. Problem
Exceptions and/or errors may occur in static initialization blocks invoked
whilst loading classes when serializing a configuration during deployment.
These same exceptions/errors don't occur when starting the configuration.
h1. Symptoms
Deployment of an EAR that has dependencies on its own copy of Xerces will
cause an exception similar to the following if Xerces is initialised in a
static block.
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.server.ejb.MyEJB.clinit
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:173)
at java.security.AccessController.doPrivileged(Native Method)
at
java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:170)
at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:557)
at
java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:591)
at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1142)
at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeClass(ObjectOutputStream.java:1082)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:996)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[jira] Updated: (GERONIMO-2222) Application errors in static initialization blocks during serialization of configuration during deployment due to incorrect TCCL
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: GERONIMO--v1.patch
Proposed patch attached. Has been tested using the application previously
attached to this JIRA.
Application errors in static initialization blocks during serialization of
configuration during deployment due to incorrect TCCL
-
Key: GERONIMO-
URL: http://issues.apache.org/jira/browse/GERONIMO-
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.0, 1.1
Reporter: John Sisson
Assigned To: John Sisson
Priority: Blocker
Fix For: 1.1.1
Attachments: GERONIMO--v1.patch, jira-g-.zip
h1. Problem
Exceptions and/or errors may occur in static initialization blocks invoked
whilst loading classes when serializing a configuration during deployment.
These same exceptions/errors don't occur when starting the configuration.
h1. Symptoms
Deployment of an EAR that has dependencies on its own copy of Xerces will
cause an exception similar to the following if Xerces is initialised in a
static block.
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.server.ejb.MyEJB.clinit
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:173)
at java.security.AccessController.doPrivileged(Native Method)
at
java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:170)
at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:557)
at
java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:591)
at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1142)
at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeClass(ObjectOutputStream.java:1082)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:996)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:187)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at
[jira] Commented: (GERONIMO-2208) bad classpath in geronimo-deploy-jsr88-1.1.jar
[
http://issues.apache.org/jira/browse/GERONIMO-2208?page=comments#action_12423200
]
John Sisson commented on GERONIMO-2208:
---
Could you please provide some more information on the steps to reproduce this
problem, along with a stackstrace of the ClassNotFoundException to aid
understanding of the issue and to help others searching JIRAs for similar
symptoms.
Thanks,
John
bad classpath in geronimo-deploy-jsr88-1.1.jar
--
Key: GERONIMO-2208
URL: http://issues.apache.org/jira/browse/GERONIMO-2208
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.1.x
Reporter: Ted Kirby
Fix For: 1.1.x, 1.2
When trying to do a remote deploy using geronimo-deploy-jsr88-1.1.jar, got a
class not found exception on org.apache.geronimo.util.encoders.Base64. This
class is packaged in geronimo-util-1.1.jar. The classpath in
geronimo-deploy-jsr88-1.1.jar is suspect. First, it does not include the
required geronimo-util-1.1.jar. Second, it includes itself, which I think is
unnecessary.
My change is to geronimo\modules\deploy-jsr88\src\conf\manifest.mf.
In the classpath, I changed:
../lib/geronimo-deploy-jsr88-${geronimo_version}.jar
---
../lib/geronimo-util-${geronimo_version}.jar
With that change, my remote deploy was successful.
--
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] Created: (GERONIMO-2226) Site migration to m2 build
Site migration to m2 build -- Key: GERONIMO-2226 URL: http://issues.apache.org/jira/browse/GERONIMO-2226 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: website Reporter: John Sisson Priority: Trivial Currently the Geronimo site is build using Ant. The Ant build has been recently updated to use Velocity to 1.5-dev (I built from svn rev 386004) to fix issue where generated html files have inconsistent line endings when building the site on Windows ( see http://www.mail-archive.com/velocity-dev@jakarta.apache.org/msg11613.html ) See http://svn.apache.org/viewcvs?rev=386059view=rev A conversion to Maven 2 needs to use a version of velocity that has this fix. You can test whether the version of velocity has the fix by: * running touch * in cygwin in the geronimo\site\xdocs directory * build the site * attempt to check in the generated site files under geronimo\site\docs - if you don't get any errors about inconsistent line endings then you are using the fixed version of velocity. For a list of dependencies required by velocity see the doco at http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/xdocs/jar-dependencies.xml . FYI, the current Ant build loads the jars in the geronimo\site\lib dir onto the classpath. I don't know if velocity's project.xml file is up to date as they aren't doing builds with maven yet AFAIK.. http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/project.xml Looks like we should wait until velocity 1.5 is released as we are currently running from a velocity 1.5 development build to get around some bugs. -- 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-1748) Site migration to Maven 2
[ http://issues.apache.org/jira/browse/GERONIMO-1748?page=all ] John Sisson closed GERONIMO-1748. - Fix Version/s: (was: 1.2) Resolution: Duplicate Assignee: John Sisson I seem to remember Jacek saying (a while ago..) we should replace the ant code with maven and this could be done as part of the m2 migration work. Anyway, it looks like we should wait until velocity 1.5 is released as we are currently running from a 1.5 development build to get around some bugs. Closing this JIRA and have created GERONIMO-2226 . John Site migration to Maven 2 - Key: GERONIMO-1748 URL: http://issues.apache.org/jira/browse/GERONIMO-1748 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: website Affects Versions: 1.2 Reporter: John Sisson Assigned To: John Sisson Priority: Minor Currently the Geronimo site is build using Ant. The Ant build has been recently updated to use Velocity to 1.5-dev (I built from svn rev 386004) to fix issue where generated html files have inconsistent line endings when building the site on Windows ( see http://www.mail-archive.com/velocity-dev@jakarta.apache.org/msg11613.html ) See http://svn.apache.org/viewcvs?rev=386059view=rev A conversion to Maven 2 needs to use a version of velocity that has this fix. You can test whether the version of velocity has the fix by: * running touch * in cygwin in the geronimo\site\xdocs directory * build the site * attempt to check in the generated site files under geronimo\site\docs - if you don't get any errors about inconsistent line endings then you are using the fixed version of velocity. For a list of dependencies required by velocity see the doco at http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/xdocs/jar-dependencies.xml . FYI, the current Ant build loads the jars in the geronimo\site\lib dir onto the classpath. I don't know if velocity's project.xml file is up to date as they aren't doing builds with maven yet AFAIK.. http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/project.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-2222) Application errors in static initialization blocks during serialization of configuration during deployment due to incorrect TCCL
[ http://issues.apache.org/jira/browse/GERONIMO-?page=all ]
John Sisson updated GERONIMO-:
--
Attachment: jira-g--xerces-test.zip
Attached test application that demonstrates Xerces problem when TCCL is not
correctly set during deployment. Need to build using m2 (mvn install) and use
deploy script in root directory.
Application errors in static initialization blocks during serialization of
configuration during deployment due to incorrect TCCL
-
Key: GERONIMO-
URL: http://issues.apache.org/jira/browse/GERONIMO-
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 1.1, 1.0
Reporter: John Sisson
Assigned To: John Sisson
Priority: Blocker
Fix For: 1.1.1
Attachments: GERONIMO--v1.patch, jira-g--xerces-test.zip,
jira-g-.zip
h1. Problem
Exceptions and/or errors may occur in static initialization blocks invoked
whilst loading classes when serializing a configuration during deployment.
These same exceptions/errors don't occur when starting the configuration.
h1. Symptoms
Deployment of an EAR that has dependencies on its own copy of Xerces will
cause an exception similar to the following if Xerces is initialised in a
static block.
{code}
java.lang.ClassCastException
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at org.apache.xerces.parsers.DOMParser.init(Unknown Source)
at com.foo.server.ejb.MyEJB.clinit
at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)
at
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1557)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:47)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:173)
at java.security.AccessController.doPrivileged(Native Method)
at
java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:170)
at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:557)
at
java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:591)
at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1142)
at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeClass(ObjectOutputStream.java:1082)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:996)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at
org.apache.geronimo.gbean.GBeanData.writeExternal(GBeanData.java:187)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.storeGBeans(SerializedGBeanState.java:139)
at
org.apache.geronimo.kernel.config.SerializedGBeanState.writeObject(SerializedGBeanState.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at
[jira] Created: (GERONIMO-2215) Add link to XBean site to Geronimo sub projects page.
Add link to XBean site to Geronimo sub projects page. - Key: GERONIMO-2215 URL: http://issues.apache.org/jira/browse/GERONIMO-2215 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: website Reporter: John Sisson Assigned To: Dain Sundstrom Priority: Minor A link needs to be added on the http://geronimo.apache.org/subprojects.html page to the http://geronimo.apache.org/xbean/ site -- 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] Created: (XBEAN-28) Update xbean poms with current site and mailing list addresses
Update xbean poms with current site and mailing list addresses -- Key: XBEAN-28 URL: http://issues.apache.org/jira/browse/XBEAN-28 Project: XBean Issue Type: Bug Affects Versions: 2.5 Reporter: John Sisson Assigned To: Dain Sundstrom Priority: Minor Fix For: 2.6 Update xbean poms with current site and mailing list addresses. They currently point to xbean.org. -- 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] Created: (GERONIMO-2197) NPE when the edit link is selected on the Security Realms console page
NPE when the edit link is selected on the Security Realms console page
Key: GERONIMO-2197
URL: http://issues.apache.org/jira/browse/GERONIMO-2197
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 1.1
Reporter: John Sisson
Assigned To: John Sisson
Fix For: 1.1.1
h1. Problem
Cannot edit a security realm by clicking on the edit link on the Security
Realms Server Console page.
h1. Symptom
The edit link appears to be non-responsive but an exception (shown below) is
thrown and should be visible on stdout or the geronimo log.
{code}
12:19:00,863 ERROR [Servlet] Exception caught:
java.lang.NullPointerException
at java.net.URI$Parser.parse(URI.java:2946)
at java.net.URI.init(URI.java:574)
at java.net.URI.create(URI.java:836)
at
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.actionLoadExistingRealm(SecurityRealmPortlet.java:
435)
at
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.processAction(SecurityRealmPortlet.java:207)
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:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
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:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:534)
{code}
h1. Cause
The SecurityRealmPortlet.load(..) method was passing the value objectName
instead of abstractName on the request.getParameter(string) call.
h1. Solution
Corrected the parameter name to be abstractName.
h1. Workaround
Add a new security realm with a different name and then delete the old realm by
stopping it and
[jira] Closed: (GERONIMO-2197) NPE when the edit link is selected on the Security Realms console page
[ http://issues.apache.org/jira/browse/GERONIMO-2197?page=all ]
John Sisson closed GERONIMO-2197.
-
Fix Version/s: 1.2
Resolution: Fixed
NPE when the edit link is selected on the Security Realms console page
Key: GERONIMO-2197
URL: http://issues.apache.org/jira/browse/GERONIMO-2197
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 1.1
Reporter: John Sisson
Assigned To: John Sisson
Fix For: 1.1.1, 1.2
h1. Problem
Cannot edit a security realm by clicking on the edit link on the Security
Realms Server Console page.
h1. Symptom
The edit link appears to be non-responsive but an exception (shown below)
is thrown and should be visible on stdout or the geronimo log.
{code}
12:19:00,863 ERROR [Servlet] Exception caught:
java.lang.NullPointerException
at java.net.URI$Parser.parse(URI.java:2946)
at java.net.URI.init(URI.java:574)
at java.net.URI.create(URI.java:836)
at
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.actionLoadExistingRealm(SecurityRealmPortlet.java:
435)
at
org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.processAction(SecurityRealmPortlet.java:207)
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:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
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:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:534)
{code}
h1. Cause
The SecurityRealmPortlet.load(..) method was
[jira] Closed: (GERONIMO-2117) Remove deployer-log4j.properties files - they are no longer used
[ http://issues.apache.org/jira/browse/GERONIMO-2117?page=all ] John Sisson closed GERONIMO-2117. - Fix Version/s: 1.2 Resolution: Fixed Remove deployer-log4j.properties files - they are no longer used Key: GERONIMO-2117 URL: http://issues.apache.org/jira/browse/GERONIMO-2117 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.1 Reporter: John Sisson Assigned To: John Sisson Priority: Trivial Fix For: 1.1.1, 1.2 Description The Geronimo 1.1 distribution contains a var\log\deployer-log4j.properties file but the file is not used. Symptom Changes to the var\log\deployer-log4j.properties file do not have any effect. Cause References to the file were removed as part of changes for GERONIMO-1306, remove modules/assembly GERONIMO-1294 remove offline capability from online deployment tool ( http://svn.apache.org/viewcvs?rev=354830view=rev ), but the var\log\.deployer-log4j.properties file wasn't deleted as part of those changes. Solution The var\log\deployer-log4j.properties file will be removed from future distributions. Workaround You can safely delete the var\log\deployer-log4j.properties 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] Commented: (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=comments#action_12421758 ] John Sisson commented on DAYTRADER-6: - I found that if I renamed the project.xml files in the following projects so they are ignored the build succeeded. 1.1\applications\daytrader 1.1\configs\daytrader-jetty 1.1\configs\daytrader-tomcat I seem to remember there was some mention of moving these projects out of the Geronimo build. Is there a JIRA for this so we don't forget. Not sure when this move was planned. I can workaround the issue, so it isn't high priority. 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 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)
[jira] Updated: (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 ] John Sisson updated DAYTRADER-6: Fix Version/s: (was: 1.1.1) 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 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 org.apache.geronimo.jetty.deployment.JettyModuleBuilder$$FastClassByCGLIB$$b30bba8a.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at
[jira] Closed: (GERONIMO-2194) Eclipse project names not generated consistently
[ http://issues.apache.org/jira/browse/GERONIMO-2194?page=all ]
John Sisson closed GERONIMO-2194.
-
Resolution: Fixed
Eclipse project names not generated consistently
Key: GERONIMO-2194
URL: http://issues.apache.org/jira/browse/GERONIMO-2194
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: buildsystem
Affects Versions: 1.1
Environment: Maven eclipse plugin version 1.11
Reporter: John Sisson
Assigned To: John Sisson
Priority: Trivial
Fix For: 1.1.1
h1. Problem
When running maven the maven eclipse plugin to generate eclipse projects for
Geronimo, e.g.
{{maven m:eclipse -Dmaven.eclipse.src.download=false}}
A number of configs and modules eclipse project names are not built using the
{{geronimo.maven.eclipse.xx}} properties in the
{{geronimo/etc/project.properties}} file.
(i) This problem only impacts developers working on Geronimo itself who use
eclipse with version 1.11 or later of the maven eclipse plugin.
h1. Symptom
When importing existing projects into eclipse you will see the following
projects do not have a prefix that you specified in the
{{geronimo/etc/project.properties}} file:
* axis
* axis-deployer
* client-deployer
* ge-activemq-rar
* shared-lib
* unavailable-client-deployer
* unavailable-ejb-deployer
* unavailable-webservices-deployer
h1. Cause
A number of new project.properties files have been added since GERONIMO-1856
was committed before the 1.1 release was shipped. These newly added
project.properties files did not set the {{maven.eclipse.project.name}}
property like other Geronimo projects.
h1. Solution
The newly added project.property files have been fixed so that they set the
{{maven.eclipse.project.name}} property like the other Geronimo
modules/configs.
h1. Workaround
None.
--
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-2117) Remove deployer-log4j.properties files - they are no longer used
[ http://issues.apache.org/jira/browse/GERONIMO-2117?page=all ] John Sisson updated GERONIMO-2117: -- Description: Description The Geronimo 1.1 distribution contains a var\log\deployer-log4j.properties file but the file is not used. Symptom Changes to the var\log\deployer-log4j.properties file do not have any effect. Cause References to the file were removed as part of changes for GERONIMO-1306, remove modules/assembly GERONIMO-1294 remove offline capability from online deployment tool ( http://svn.apache.org/viewcvs?rev=354830view=rev ), but the var\log\.deployer-log4j.properties file wasn't deleted as part of those changes. Solution The var\log\deployer-log4j.properties file will be removed from future distributions. Workaround You can safely delete the var\log\deployer-log4j.properties file. was:I can't see anything that is referencing the deployer-log4j.properties files, so they probably should be removed. Remove deployer-log4j.properties files - they are no longer used Key: GERONIMO-2117 URL: http://issues.apache.org/jira/browse/GERONIMO-2117 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.1 Reporter: John Sisson Assigned To: John Sisson Priority: Trivial Fix For: 1.1.1 Description The Geronimo 1.1 distribution contains a var\log\deployer-log4j.properties file but the file is not used. Symptom Changes to the var\log\deployer-log4j.properties file do not have any effect. Cause References to the file were removed as part of changes for GERONIMO-1306, remove modules/assembly GERONIMO-1294 remove offline capability from online deployment tool ( http://svn.apache.org/viewcvs?rev=354830view=rev ), but the var\log\.deployer-log4j.properties file wasn't deleted as part of those changes. Solution The var\log\deployer-log4j.properties file will be removed from future distributions. Workaround You can safely delete the var\log\deployer-log4j.properties 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] Created: (DAYTRADER-6) Longer version (1.1.1) causes build failures on Windows in daytrader-jetty config
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 Reporter: John Sisson 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 org.apache.geronimo.jetty.deployment.JettyModuleBuilder$$FastClassByCGLIB$$b30bba8a.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:817) at
[jira] Updated: (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 ] John Sisson updated DAYTRADER-6: Fix Version/s: 1.1.1 Affects Version/s: 1.1.1 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 Fix For: 1.1.1 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 org.apache.geronimo.jetty.deployment.JettyModuleBuilder$$FastClassByCGLIB$$b30bba8a.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
[jira] Created: (GERONIMO-2194) Eclipse project names not generated consistently
Eclipse project names not generated consistently
Key: GERONIMO-2194
URL: http://issues.apache.org/jira/browse/GERONIMO-2194
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: buildsystem
Affects Versions: 1.1
Environment: Maven eclipse plugin version 1.11
Reporter: John Sisson
Assigned To: John Sisson
Priority: Trivial
Fix For: 1.1.1
h1. Problem
When running maven the maven eclipse plugin to generate eclipse projects for
Geronimo, e.g.
{{maven m:eclipse -Dmaven.eclipse.src.download=false}}
A number of configs and modules eclipse project names are not built using the
{{geronimo.maven.eclipse.xx}} properties in the
{{geronimo/etc/project.properties}} file.
(i) This problem only impacts developers working on Geronimo itself who use
eclipse with version 1.11 or later of the maven eclipse plugin.
h1. Symptom
When importing existing projects into eclipse you will see the following
projects do not have a prefix that you specified in the
{{geronimo/etc/project.properties}} file:
* axis
* axis-deployer
* client-deployer
* ge-activemq-rar
* shared-lib
* unavailable-client-deployer
* unavailable-ejb-deployer
* unavailable-webservices-deployer
h1. Cause
A number of new project.properties files have been added since GERONIMO-1856
was committed before the 1.1 release was shipped. These newly added
project.properties files did not set the {{maven.eclipse.project.name}}
property like other Geronimo projects.
h1. Solution
The newly added project.property files have been fixed so that they set the
{{maven.eclipse.project.name}} property like the other Geronimo modules/configs.
h1. Workaround
None.
--
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-2161) [RTC] Remove Geronimo modules from dependencyManagement in root pom.xml
[
http://issues.apache.org/jira/browse/GERONIMO-2161?page=comments#action_12418906
]
John Sisson commented on GERONIMO-2161:
---
+1 : applied patch and tested build. Due to xmlbeans issue (which is a
separate problem not caused by this patch) It took a number of build attempts
using Jason's script he shared with me on IRC:
{noformat}
#!/bin/sh
# Drop all existing repo state
rm -rf ~/.m2/repository
# Clean, since mvn clean won't work everytime because of chicken-egg plugins
find . -name target -type d -exec rm -rf \{\} \;
# Build the G modules - 13 times to get around xmlbeans crap
for x in 1 2 3 4 5 6 7 8 9 10 11 12 13; do
mvn -Dstage=bootstrap -Dmaven.test.skip=true
done
# Build OpenEJB - 3 times to get around xmlbeans crap
( cd openejb2/modules; mvn clean; mvn install; mvn install; mvn install )
# Build G apps, config and assembly
mvn -Dstage=assemble -Dmaven.test.skip=true
{noformat}
[RTC] Remove Geronimo modules from dependencyManagement in root pom.xml
---
Key: GERONIMO-2161
URL: http://issues.apache.org/jira/browse/GERONIMO-2161
Project: Geronimo
Type: Task
Security: public(Regular issues)
Components: buildsystem
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.2
Attachments: GERONIMO-2161-configs-v1.1.sub.patch, GERONIMO-2161-v1.patch,
GERONIMO-2161-v2.patch
As I have mentioned before, I believe we should remove the Geronimo modules
that are currently listed in the root pom.xml:
This reduces the configuration of the pom by *~500 lines*.
Modules that reference these as dependencies will need their pom's adjusted
to include version${pom.version}/version and typecar/type for the
configs. But in many places version already exists with the
${geronimoVersion} property... which kinda negates the purpose of the
dependencyManagement section anyways.
I believe that it is more work to keep track of every module in the root pom
than it is to specify the additonal elements (mostly just
version${pom.version}/version) in child poms. There is no additional
maintenance, as the new elements never need to be changed.
Net effect if this change is less configuration to maintain and thus a less
brittle build that can adapt to change easier.
Specifically these should be removed:
{code:xml}
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdge-activemq-rar/artifactId
version${geronimoVersion}/version
typerar/type
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-activation/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-client/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-client-builder/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-common/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-connector/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-connector-builder/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-converter/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-core/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-config/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-jsr88/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-tool/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deployment/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-derby/artifactId
version${geronimoVersion}/version
/dependency
dependency
[jira] Commented: (GERONIMO-2161) [RTC] Remove Geronimo modules from dependencyManagement in root pom.xml
[
http://issues.apache.org/jira/browse/GERONIMO-2161?page=comments#action_12418909
]
John Sisson commented on GERONIMO-2161:
---
My +1 above is for the GERONIMO-2161-v2.patch.
[RTC] Remove Geronimo modules from dependencyManagement in root pom.xml
---
Key: GERONIMO-2161
URL: http://issues.apache.org/jira/browse/GERONIMO-2161
Project: Geronimo
Type: Task
Security: public(Regular issues)
Components: buildsystem
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.2
Attachments: GERONIMO-2161-configs-v1.1.sub.patch, GERONIMO-2161-v1.patch,
GERONIMO-2161-v2.patch
As I have mentioned before, I believe we should remove the Geronimo modules
that are currently listed in the root pom.xml:
This reduces the configuration of the pom by *~500 lines*.
Modules that reference these as dependencies will need their pom's adjusted
to include version${pom.version}/version and typecar/type for the
configs. But in many places version already exists with the
${geronimoVersion} property... which kinda negates the purpose of the
dependencyManagement section anyways.
I believe that it is more work to keep track of every module in the root pom
than it is to specify the additonal elements (mostly just
version${pom.version}/version) in child poms. There is no additional
maintenance, as the new elements never need to be changed.
Net effect if this change is less configuration to maintain and thus a less
brittle build that can adapt to change easier.
Specifically these should be removed:
{code:xml}
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdge-activemq-rar/artifactId
version${geronimoVersion}/version
typerar/type
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-activation/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-client/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-client-builder/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-common/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-connector/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-connector-builder/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-converter/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-core/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-config/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-jsr88/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deploy-tool/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-deployment/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-derby/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-directory/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-javamail-transport/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-j2ee/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
artifactIdgeronimo-j2ee-builder/artifactId
version${geronimoVersion}/version
/dependency
dependency
groupIdorg.apache.geronimo.modules/groupId
[jira] Commented: (GERONIMO-2132) Move activemq gbean integration modules from ActiveMQ to Geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-2132?page=comments#action_12418911 ] John Sisson commented on GERONIMO-2132: --- What is the status of this JIRA, as there has been an svn commit for it http://svn.apache.org/viewvc?rev=415034view=rev ? Are you planning on doing more work on this issue? Trying to piece togther the status of this issue and GERONIMO-2135. Move activemq gbean integration modules from ActiveMQ to Geronimo - Key: GERONIMO-2132 URL: http://issues.apache.org/jira/browse/GERONIMO-2132 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: ActiveMQ Reporter: Hiram Chirino Fix For: 1.2 Attachments: amq4.patch -- 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-592) Startup failure in Turkish language settings
[ http://issues.apache.org/jira/browse/GERONIMO-592?page=all ] John Sisson closed GERONIMO-592: Resolution: Cannot Reproduce Startup failure in Turkish language settings Key: GERONIMO-592 URL: http://issues.apache.org/jira/browse/GERONIMO-592 Project: Geronimo Type: Bug Components: kernel Versions: 1.0-M3 Environment: Windows XP with Turkish language settings Reporter: Gorkem Ercan Fix For: 1.2 If tried to start with java -jar server.jar in Turkish language setting. startup fails with no log messages. Console prints some error messages but these are due to failed services. -- 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-592) Startup failure in Turkish language settings
[ http://issues.apache.org/jira/browse/GERONIMO-592?page=comments#action_12418821 ] John Sisson commented on GERONIMO-592: -- Gorkem, can you please verify whether this problem still exists in the 1.1 release and if so provide more detailed error information. If it still exists we can re-open the issue. Startup failure in Turkish language settings Key: GERONIMO-592 URL: http://issues.apache.org/jira/browse/GERONIMO-592 Project: Geronimo Type: Bug Components: kernel Versions: 1.0-M3 Environment: Windows XP with Turkish language settings Reporter: Gorkem Ercan Fix For: 1.2 If tried to start with java -jar server.jar in Turkish language setting. startup fails with no log messages. Console prints some error messages but these are due to failed services. -- 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-2135) Improve the ActiveMQ GBeans
[
http://issues.apache.org/jira/browse/GERONIMO-2135?page=comments#action_12418544
]
John Sisson commented on GERONIMO-2135:
---
Comment from djencks on dev list 22nd June (
http://www.mail-archive.com/dev%40geronimo.apache.org/msg25153.html )
This patch addresses my major concerns. I consider it
a bug fix and thus not requiring further voting beyond
my previous +1, but in case anyone disagrees, I've
applied it and tested it to the best of my abilities
and vote +1.
thanks
david jencks
Improve the ActiveMQ GBeans
---
Key: GERONIMO-2135
URL: http://issues.apache.org/jira/browse/GERONIMO-2135
Project: Geronimo
Type: Improvement
Security: public(Regular issues)
Components: ActiveMQ
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 1.2
Attachments: GERONIMO-2135.patch
Suggestions by David Jencks:
I think that this gbean adaptation code should be in geronimo rather
than amq. I'm OK with applying it as is but would prefer some issues
to be addressed first or, even better, immediately after the
transfer (assuming it is done with svn mv).
1. DataSourceReference should be replaced by the geronimo class that
does the same thing, ConnectionFactorySource.
2. I think it would be preferable to get the module/configuration
classloader in the constructor as a magic attribute and use it in
BrokerServiceGBeanImpl.doStart rather than the classloader of
BrokerServiceGBeanImpl.
3. Same for TransportConnectorGBeanImpl.
4. This is a question, not really an issue, about this code:
+protected TransportConnector createBrokerConnector(String url)
throws Exception {
+return brokerService.getBrokerContainer().addConnector(url);
+}
To me it seems like this code is combining the functions of factory
object and container. Is this necessary and appropriate? I'd be
more comfortable with
Connector connector = ConnectorFactory.createConnector(url);
brokerService.getBrokerContainer().addConnector(connector);
I find that the combination style typically creates problems whenever
trying to extend stuff, say by wrapping the connector. What do you
think?
5. hardcoding the protocols in ActiveMQManagerGBean seems like a
temporary expedient at best.
6. javadoc on public JMSConnector addConnector( ... in the manager
gbean seems wrong... does not appear to return an object name.
7. Typo and innaccuracies in the first package.html... this stuff is
only going to work in geronimo, jsr77/88 is not enough.
8. I'm not sure exactly what our official policy is but I prefer to
remove public from methods in interfaces since it is the only
choice and implied.
--
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-2135) Improve the ActiveMQ GBeans
[
http://issues.apache.org/jira/browse/GERONIMO-2135?page=comments#action_12418545
]
John Sisson commented on GERONIMO-2135:
---
Comment from hiram on dev list 19th June (
http://www.mail-archive.com/dev%40geronimo.apache.org/msg24939.html) prior to
Gianny's Comment above.
Hi folks,
Looking for 3 +1s for the patch attached to
http://issues.apache.org/jira/browse/GERONIMO-2135.
This patch addresses previous concerns raised by David Jencks.
Items not addressed by the patch are:
#4: yes. I agree, but since these GBeans are just meant to be a simple
integration between Geronimo and ActiveMQ, we are taking some short
cuts. In general ActiveMQ allows you to configure many more options
than what the current GBeans allows you to do.
#5, I also agree, but I don't have a programmatic way of listing all
protocols since they are loaded by searching the classpath for
META-INF resources.
Improve the ActiveMQ GBeans
---
Key: GERONIMO-2135
URL: http://issues.apache.org/jira/browse/GERONIMO-2135
Project: Geronimo
Type: Improvement
Security: public(Regular issues)
Components: ActiveMQ
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 1.2
Attachments: GERONIMO-2135.patch
Suggestions by David Jencks:
I think that this gbean adaptation code should be in geronimo rather
than amq. I'm OK with applying it as is but would prefer some issues
to be addressed first or, even better, immediately after the
transfer (assuming it is done with svn mv).
1. DataSourceReference should be replaced by the geronimo class that
does the same thing, ConnectionFactorySource.
2. I think it would be preferable to get the module/configuration
classloader in the constructor as a magic attribute and use it in
BrokerServiceGBeanImpl.doStart rather than the classloader of
BrokerServiceGBeanImpl.
3. Same for TransportConnectorGBeanImpl.
4. This is a question, not really an issue, about this code:
+protected TransportConnector createBrokerConnector(String url)
throws Exception {
+return brokerService.getBrokerContainer().addConnector(url);
+}
To me it seems like this code is combining the functions of factory
object and container. Is this necessary and appropriate? I'd be
more comfortable with
Connector connector = ConnectorFactory.createConnector(url);
brokerService.getBrokerContainer().addConnector(connector);
I find that the combination style typically creates problems whenever
trying to extend stuff, say by wrapping the connector. What do you
think?
5. hardcoding the protocols in ActiveMQManagerGBean seems like a
temporary expedient at best.
6. javadoc on public JMSConnector addConnector( ... in the manager
gbean seems wrong... does not appear to return an object name.
7. Typo and innaccuracies in the first package.html... this stuff is
only going to work in geronimo, jsr77/88 is not enough.
8. I'm not sure exactly what our official policy is but I prefer to
remove public from methods in interfaces since it is the only
choice and implied.
--
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] Created: (GERONIMO-2155) Upgrade Derby to 10.1.3 and use the lib-debug distribution
Upgrade Derby to 10.1.3 and use the lib-debug distribution -- Key: GERONIMO-2155 URL: http://issues.apache.org/jira/browse/GERONIMO-2155 Project: Geronimo Type: Bug Security: public (Regular issues) Components: databases Versions: 1.0, 1.1 Reporter: John Sisson Assigned to: John Sisson Fix For: 1.x The Derby library we are using in Geronimo does not have line number debug information, which is useful in stack traces. This has been addressed in the upcoming Derby 10.1.3 release by providing a lib-debug distribution ( http://issues.apache.org/jira/browse/DERBY-178 ) . This has been discussed on the Geronimo dev list at: http://www.mail-archive.com/dev@geronimo.apache.org/msg25051.html -- 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] Reopened: (GERONIMO-1564) Use specific geronimo.assemble.xx properties in assembly project.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1564?page=all ]
John Sisson reopened GERONIMO-1564:
---
This has been reopened as the proposed changes in the description have not been
made and are not in 1.1.
Use specific geronimo.assemble.xx properties in assembly project.xml files
--
Key: GERONIMO-1564
URL: http://issues.apache.org/jira/browse/GERONIMO-1564
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: buildsystem
Versions: 1.0, 1.1
Reporter: John Sisson
Assignee: John Sisson
Fix For: 1.2
Currently it is not possible to specify more than one geronimo.assemble
property values for a dependency. E.G. the following does not work:
dependency
groupIdgeronimo/groupId
version${geronimo_spec_qname_version}/version
properties
geronimo.assemblelibrary/geronimo.assemble
geronimo.assemblerepository/geronimo.assemble
/properties
/dependency
We need to change the assembly plugin (and assembly project.xml files) to use
specific property names so that the following is possible:
dependency
groupIdgeronimo/groupId
version${geronimo_spec_qname_version}/version
properties
geronimo.assemble.librarytrue/geronimo.assemble.library
geronimo.assemble.repositorytrue/geronimo.assemble.repository
/properties
/dependency
Here are the proposed changes:
geronimo.assembleendorsed/geronimo.assemble
to:
geronimo.assemble.endorsedtrue/geronimo.assemble.endorsed
geronimo.assembleextension/geronimo.assemble
to:
geronimo.assemble.extensiontrue/geronimo.assemble.extension
geronimo.assembleinstall/geronimo.assemble
to:
geronimo.assemble.installtrue/geronimo.assemble.install
geronimo.assemblelibrary/geronimo.assemble
to:
geronimo.assemble.librarytrue/geronimo.assemble.library
geronimo.assemblerepository/geronimo.assemble
to:
geronimo.assemble.repositorytrue/geronimo.assemble.repository
geronimo.assembleunpack/geronimo.assemble
to:
geronimo.assemble.unpacktrue/geronimo.assemble.unpack
--
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-1564) Use specific geronimo.assemble.xx properties in assembly project.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1564?page=all ]
John Sisson updated GERONIMO-1564:
--
Fix Version: 1.2
(was: 1.1)
Version: 1.1
Use specific geronimo.assemble.xx properties in assembly project.xml files
--
Key: GERONIMO-1564
URL: http://issues.apache.org/jira/browse/GERONIMO-1564
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: buildsystem
Versions: 1.0, 1.1
Reporter: John Sisson
Assignee: John Sisson
Fix For: 1.2
Currently it is not possible to specify more than one geronimo.assemble
property values for a dependency. E.G. the following does not work:
dependency
groupIdgeronimo/groupId
version${geronimo_spec_qname_version}/version
properties
geronimo.assemblelibrary/geronimo.assemble
geronimo.assemblerepository/geronimo.assemble
/properties
/dependency
We need to change the assembly plugin (and assembly project.xml files) to use
specific property names so that the following is possible:
dependency
groupIdgeronimo/groupId
version${geronimo_spec_qname_version}/version
properties
geronimo.assemble.librarytrue/geronimo.assemble.library
geronimo.assemble.repositorytrue/geronimo.assemble.repository
/properties
/dependency
Here are the proposed changes:
geronimo.assembleendorsed/geronimo.assemble
to:
geronimo.assemble.endorsedtrue/geronimo.assemble.endorsed
geronimo.assembleextension/geronimo.assemble
to:
geronimo.assemble.extensiontrue/geronimo.assemble.extension
geronimo.assembleinstall/geronimo.assemble
to:
geronimo.assemble.installtrue/geronimo.assemble.install
geronimo.assemblelibrary/geronimo.assemble
to:
geronimo.assemble.librarytrue/geronimo.assemble.library
geronimo.assemblerepository/geronimo.assemble
to:
geronimo.assemble.repositorytrue/geronimo.assemble.repository
geronimo.assembleunpack/geronimo.assemble
to:
geronimo.assemble.unpacktrue/geronimo.assemble.unpack
--
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] Created: (GERONIMO-2136) Remove/Update licenses displayed in about page of console
Remove/Update licenses displayed in about page of console - Key: GERONIMO-2136 URL: http://issues.apache.org/jira/browse/GERONIMO-2136 Project: Geronimo Type: Bug Security: public (Regular issues) Components: console Versions: 1.1 Reporter: John Sisson Assigned to: John Sisson Priority: Trivial Fix For: 1.1.1 The licenses displayed in the console in the about page ( http://localhost:8080/console/about.jsp ) are a subset of those in Geronimo's LICENSE.txt file. Either this licenses on this page should be removed or they should be updated to match the LICENSE.txt file. See mail thread. http://www.mail-archive.com/dev%40geronimo.apache.org/msg24852.html -- 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] Created: (DAYTRADER-4) DayTrader README file out of date
DayTrader README file out of date - Key: DAYTRADER-4 URL: http://issues.apache.org/jira/browse/DAYTRADER-4 Project: DayTrader Type: Bug Versions: 1.1 Reporter: John Sisson This issue has been moved from GERONIMO-1436 - Currently the instructions say to run maven in the same directory as the README file, but just running maven from there does not do anything AFAIK. Also the instructions regarding creating the database seem to be old. Need input as to what the current installation instructions are. -- 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] Created: (DAYTRADER-5) Add LICENSE.txt and NOTICE.txt files
Add LICENSE.txt and NOTICE.txt files Key: DAYTRADER-5 URL: http://issues.apache.org/jira/browse/DAYTRADER-5 Project: DayTrader Type: Task Components: buildsystem Versions: 1.1 Reporter: John Sisson -- 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-1436) [daytrader] Build instructions in applications\daytrader\README file out of date
[ http://issues.apache.org/jira/browse/GERONIMO-1436?page=all ] John Sisson closed GERONIMO-1436: - Resolution: Invalid Moved issue to http://issues.apache.org/jira/browse/DAYTRADER-4. Patch applied. [daytrader] Build instructions in applications\daytrader\README file out of date Key: GERONIMO-1436 URL: http://issues.apache.org/jira/browse/GERONIMO-1436 Project: Geronimo Type: Bug Security: public(Regular issues) Components: sample apps Versions: 1.0 Reporter: John Sisson Priority: Minor Fix For: 1.2 Attachments: readme.patch Currently the instructions say to run maven in the same directory as the README file, but just running maven from there does not do anything AFAIK. -- 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] Created: (GERONIMO-2131) Installed Configuration message written using System.out.println(..) instead of using the log
Installed Configuration message written using System.out.println(..) instead of using the log --- Key: GERONIMO-2131 URL: http://issues.apache.org/jira/browse/GERONIMO-2131 Project: Geronimo Type: Bug Security: public (Regular issues) Components: Plugins Versions: 1.1 Reporter: John Sisson Priority: Trivial Fix For: 1.x I went to the http://jslap:8080/ page and clicked on the Servlet Examples and LDAP Demo and found that messages were written to system.out when I installed the configurations for those examples. This information should be logged rather than printed to System.out. See output below. D:\reltest\geronimo-1.1bin\geronimo.bat run Using GERONIMO_BASE: D:\reltest\geronimo-1.1 Using GERONIMO_HOME: D:\reltest\geronimo-1.1 Using GERONIMO_TMPDIR: D:\reltest\geronimo-1.1\var\temp Using JRE_HOME:C:\j2sdk1.4.2_10 Booting Geronimo Kernel (in Java 1.4.2_10)... Starting Geronimo Application Server v1.1 [**] 100% 37s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8009 0.0.0.0 Tomcat Connector AJP 8080 0.0.0.0 Tomcat Connector HTTP 8443 0.0.0.0 Tomcat Connector HTTPS 0.0.0.0 JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/webconsole-tomcat/1.1/car RAR: geronimo/activemq/1.1/car RAR: geronimo/system-database/1.1/car WAR: geronimo/remote-deploy-tomcat/1.1/car WAR: geronimo/welcome-tomcat/1.1/car Web Applications: http://JSLAP:8080/ http://JSLAP:8080/console http://JSLAP:8080/console-standard http://JSLAP:8080/remote-deploy Geronimo Application Server started # Installed configuration # id = geronimo/servlets-examples-tomcat/1.1-SNAPSHOT/car # location = D:\reltest\geronimo-1.1\repository\geronimo\servlets-examples-tomcat\1.1-SNAPSHOT\servlets-examples-tomcat-1.1-SNAPSH OT.car # Installed configuration # id = geronimo/ldap-demo-tomcat/1.1-SNAPSHOT/car # location = D:\reltest\geronimo-1.1\repository\geronimo\ldap-demo-tomcat\1.1-SNAPSHOT\ldap-demo-tomcat-1.1-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] Closed: (GERONIMO-2122) Request to add book to website
[ http://issues.apache.org/jira/browse/GERONIMO-2122?page=all ] John Sisson closed GERONIMO-2122: - Resolution: Fixed Site updated. Request to add book to website -- Key: GERONIMO-2122 URL: http://issues.apache.org/jira/browse/GERONIMO-2122 Project: Geronimo Type: Task Security: public(Regular issues) Components: website Reporter: John Sisson Assignee: John Sisson Priority: Trivial Attachments: GERONIMO-2122.patch The PMC has received a request to add a link to the following book on the website: Pro Apache Geronimo (Apr 06) http://www.apress.com/book/bookDisplay.html?bID=10095 -- 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] Created: (GERONIMO-2123) Improve information on books on Geronimo to indicate which version(s) of geronimo a book is primarily focussed on
Improve information on books on Geronimo to indicate which version(s) of geronimo a book is primarily focussed on - Key: GERONIMO-2123 URL: http://issues.apache.org/jira/browse/GERONIMO-2123 Project: Geronimo Type: Task Security: public (Regular issues) Components: website Reporter: John Sisson Priority: Minor Improve information on books on Geronimo to indicate which version(s) of geronimo a book is primarily focussed on. Suggested by djencks. -- 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-2122) Request to add book to website
[ http://issues.apache.org/jira/browse/GERONIMO-2122?page=all ] John Sisson updated GERONIMO-2122: -- Attachment: GERONIMO-2122.patch Patch for site\trunk and site\branches\may2006 Request to add book to website -- Key: GERONIMO-2122 URL: http://issues.apache.org/jira/browse/GERONIMO-2122 Project: Geronimo Type: Task Security: public(Regular issues) Components: website Reporter: John Sisson Assignee: John Sisson Priority: Trivial Attachments: GERONIMO-2122.patch The PMC has received a request to add a link to the following book on the website: Pro Apache Geronimo (Apr 06) http://www.apress.com/book/bookDisplay.html?bID=10095 -- 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] Created: (GERONIMO-2122) Request to add book to website
Request to add book to website -- Key: GERONIMO-2122 URL: http://issues.apache.org/jira/browse/GERONIMO-2122 Project: Geronimo Type: Task Security: public (Regular issues) Components: website Reporter: John Sisson Assigned to: John Sisson Priority: Trivial The PMC has received a request to add a link to the following book on the website: Pro Apache Geronimo (Apr 06) http://www.apress.com/book/bookDisplay.html?bID=10095 -- 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] Created: (GERONIMO-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public (Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- 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-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=all ] John Sisson updated GERONIMO-2112: -- Attachment: geronimo-1.1-RC-licenses-attributions-draft1.txt Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 Attachments: geronimo-1.1-RC-licenses-attributions-draft1.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- 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-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=all ] John Sisson updated GERONIMO-2112: -- Attachment: geronimo-1.1-RC-licenses-attributions-draft2.txt Updated/Added the following items: axis commons-fileupload commons-io commons-modeler dwr jaxr-api jstl stax-api wsdl4j Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 Attachments: LICENSE.txt, NOTICE.txt, NOTICES-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft2.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- 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-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=comments#action_12416112 ] John Sisson commented on GERONIMO-2112: --- We're getting closer. All licenses should be moved to the LICENSE.txt file. The NOTICE.txt file should only contain notices or attributions. Should probably be specific and identify the version of the CPL license (1.0). Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 Attachments: LICENSE.txt, NOTICE.txt, NOTICE.txt, NOTICES-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft2.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- 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] Created: (GERONIMO-2115) Exclude j2ee-installer assembly from 1.1 build by renaming project.xml file to project.xml.ignore
Exclude j2ee-installer assembly from 1.1 build by renaming project.xml file to project.xml.ignore - Key: GERONIMO-2115 URL: http://issues.apache.org/jira/browse/GERONIMO-2115 Project: Geronimo Type: Bug Security: public (Regular issues) Versions: 1.1 Reporter: John Sisson Assigned to: John Sisson Priority: Minor Fix For: 1.1 The j2ee-installer assembly is not functional on Geronimo 1.1, therefore the project.xml file for the assembly will be renamed to project.xml.ignore so that users building from source don't build the j2ee-installer assembly. -- 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-2115) Exclude j2ee-installer assembly from 1.1 build by renaming project.xml file to project.xml.ignore
[ http://issues.apache.org/jira/browse/GERONIMO-2115?page=all ] John Sisson closed GERONIMO-2115: - Resolution: Fixed Exclude j2ee-installer assembly from 1.1 build by renaming project.xml file to project.xml.ignore - Key: GERONIMO-2115 URL: http://issues.apache.org/jira/browse/GERONIMO-2115 Project: Geronimo Type: Bug Security: public(Regular issues) Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Priority: Minor Fix For: 1.1 The j2ee-installer assembly is not functional on Geronimo 1.1, therefore the project.xml file for the assembly will be renamed to project.xml.ignore so that users building from source don't build the j2ee-installer assembly. -- 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] Created: (GERONIMO-2117) Remove deployer-log4j.properties files - they are no longer used
Remove deployer-log4j.properties files - they are no longer used Key: GERONIMO-2117 URL: http://issues.apache.org/jira/browse/GERONIMO-2117 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions: 1.1 Reporter: John Sisson Assigned to: John Sisson Priority: Trivial Fix For: 1.1.1 I can't see anything that is referencing the deployer-log4j.properties files, so they probably should be removed. -- 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-693) Provide Java Service Wrapper scripts in bin directory
[ http://issues.apache.org/jira/browse/GERONIMO-693?page=all ] John Sisson updated GERONIMO-693: - Component: startup/shutdown Provide Java Service Wrapper scripts in bin directory - Key: GERONIMO-693 URL: http://issues.apache.org/jira/browse/GERONIMO-693 Project: Geronimo Type: New Feature Components: usability, startup/shutdown Versions: 1.0-M4, 1.0, 1.1 Environment: Windows, Linux, Mac OS X Reporter: Erin Mulder Assignee: John Sisson Priority: Minor Fix For: 1.x Attachments: wrapper.tar.gz It would be nice to have obvious startup.sh and startup.bat scripts in the bin directory so that the user doesn't need to look at the README file to figure out how to start the server. (java -jar bin/server.jar isn't hard -- it's just not quite as brainless as a script called startup). -- 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-693) Provide Java Service Wrapper scripts in bin directory
[ http://issues.apache.org/jira/browse/GERONIMO-693?page=all ] John Sisson updated GERONIMO-693: - Version: 1.0 1.1 Provide Java Service Wrapper scripts in bin directory - Key: GERONIMO-693 URL: http://issues.apache.org/jira/browse/GERONIMO-693 Project: Geronimo Type: New Feature Components: usability, startup/shutdown Versions: 1.0-M4, 1.0, 1.1 Environment: Windows, Linux, Mac OS X Reporter: Erin Mulder Assignee: John Sisson Priority: Minor Fix For: 1.x Attachments: wrapper.tar.gz It would be nice to have obvious startup.sh and startup.bat scripts in the bin directory so that the user doesn't need to look at the README file to figure out how to start the server. (java -jar bin/server.jar isn't hard -- it's just not quite as brainless as a script called startup). -- 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-1801) Restart/Shutdown functionality for Geronimo when using Java Service Wrapper
[ http://issues.apache.org/jira/browse/GERONIMO-1801?page=all ] John Sisson updated GERONIMO-1801: -- Fix Version: 1.x Restart/Shutdown functionality for Geronimo when using Java Service Wrapper --- Key: GERONIMO-1801 URL: http://issues.apache.org/jira/browse/GERONIMO-1801 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: startup/shutdown Versions: 1.x Environment: Windows, Linux, Mac OS X, Solaris, HP-UX Reporter: Mario Ruebsam Priority: Minor Fix For: 1.x If running Geronimo with Java Service Wrapper (also mentioned in GERONIMO-693), easy restart/shutdown functionality could be added to the JSW configuration by adding the following lines to the Java Service Wrapper wrapper.conf. # Filter settings. Add parameters as needed starting from 1 wrapper.filter.trigger.1=JSWRestartGeronimo wrapper.filter.action.1=RESTART wrapper.filter.trigger.2=JSWShutdownGeronimo wrapper.filter.action.2=SHUTDOWN wrapper.filter.trigger.3=java.lang.OutOfMemoryError wrapper.filter.action.3=RESTART The Servlet/JSP code for triggering shutdown/restart is then very simple by printing an output to the standard out or err e.g. System.out.println(JSWRestartGeronimo); or System.out.println(JSWShutdownGeronimo); Also the java.lang.OutOfMemoryError which is not easy to catch in the JVM can be handled this way using the JSW. If added to some JSW configuration scripts packaged with Geronimo the above configuration should also described in the JSW section in the current documentation. -- 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-1801) Restart/Shutdown functionality for Geronimo when using Java Service Wrapper
[ http://issues.apache.org/jira/browse/GERONIMO-1801?page=all ] John Sisson updated GERONIMO-1801: -- Version: 1.0 1.1 (was: 1.x) Restart/Shutdown functionality for Geronimo when using Java Service Wrapper --- Key: GERONIMO-1801 URL: http://issues.apache.org/jira/browse/GERONIMO-1801 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: startup/shutdown Versions: 1.0, 1.1 Environment: Windows, Linux, Mac OS X, Solaris, HP-UX Reporter: Mario Ruebsam Priority: Minor Fix For: 1.x If running Geronimo with Java Service Wrapper (also mentioned in GERONIMO-693), easy restart/shutdown functionality could be added to the JSW configuration by adding the following lines to the Java Service Wrapper wrapper.conf. # Filter settings. Add parameters as needed starting from 1 wrapper.filter.trigger.1=JSWRestartGeronimo wrapper.filter.action.1=RESTART wrapper.filter.trigger.2=JSWShutdownGeronimo wrapper.filter.action.2=SHUTDOWN wrapper.filter.trigger.3=java.lang.OutOfMemoryError wrapper.filter.action.3=RESTART The Servlet/JSP code for triggering shutdown/restart is then very simple by printing an output to the standard out or err e.g. System.out.println(JSWRestartGeronimo); or System.out.println(JSWShutdownGeronimo); Also the java.lang.OutOfMemoryError which is not easy to catch in the JVM can be handled this way using the JSW. If added to some JSW configuration scripts packaged with Geronimo the above configuration should also described in the JSW section in the current documentation. -- 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] Assigned: (GERONIMO-2096) PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open
[ http://issues.apache.org/jira/browse/GERONIMO-2096?page=all ] John Sisson reassigned GERONIMO-2096: - Assign To: John Sisson PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open - Key: GERONIMO-2096 URL: http://issues.apache.org/jira/browse/GERONIMO-2096 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core, Plugins Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Fix For: 1.1 The code contains the following statement, where the xml variable is a File. xform.transform(new DOMSource(doc), new StreamResult(xml)); We have experienced in another issue ( GERONIMO-2095 ) that this does not close the FileOutputStream that gets created automatically on your behalf. It is safer to create your own FileOutputStream and pass it on the StreamResult constructor and ensure it is closed in a finally block. See fix for GERONIMO-2095 for an example. -- 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-2096) PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open
[ http://issues.apache.org/jira/browse/GERONIMO-2096?page=all ] John Sisson closed GERONIMO-2096: - Resolution: Fixed Fixed. PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open - Key: GERONIMO-2096 URL: http://issues.apache.org/jira/browse/GERONIMO-2096 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core, Plugins Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Fix For: 1.1 The code contains the following statement, where the xml variable is a File. xform.transform(new DOMSource(doc), new StreamResult(xml)); We have experienced in another issue ( GERONIMO-2095 ) that this does not close the FileOutputStream that gets created automatically on your behalf. It is safer to create your own FileOutputStream and pass it on the StreamResult constructor and ensure it is closed in a finally block. See fix for GERONIMO-2095 for an example. -- 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-1638) Multiple servers sharing the same repo and config store
[ http://issues.apache.org/jira/browse/GERONIMO-1638?page=comments#action_12415496 ] John Sisson commented on GERONIMO-1638: --- Currently working on scripts as discussed at http://www.mail-archive.com/dev@geronimo.apache.org/msg22807.html . Have made changes but they need to be tested on windows, cygwin and unix, so looks like this is going to be for 1.1.1 . Multiple servers sharing the same repo and config store --- Key: GERONIMO-1638 URL: http://issues.apache.org/jira/browse/GERONIMO-1638 Project: Geronimo Type: New Feature Security: public(Regular issues) Components: usability Versions: 1.0 Reporter: Gianny Damour Assignee: John Sisson Fix For: 1.1 David J. sent to the dev mailing list: Many people have talked on and off about how to set up multiple servers sharing the same repository and config-store, but we haven't arrived at an agreed on way to do it. We have a prospective customer for this feature (Vincent Massol with Cargo) so I'd like to move beyond thinking about it in my head, discuss it, and have someone implement it. I believe any implementation will be more or less trivial, the hard part is figuring out what to do. I've only thought of ways to extend what we have now, rather than restructure anything or add big new capabilities. If someone sees a better way, please speak up. So, we have a ServerInfo gbean that knows where geronimo is located and can resolve absolute locations for other components. Then we have things like the repository and config store gbeans that typically are located outside the var dir and things like the logging framework, local attribute manager, derby, and tomcat, that typically keep stuff in the var directory. All or most of these start with the first configuration loaded so they can't have any attributes overridden by config.xml: in fact this file is read by one of the gbeans that we need to relocate. I've thought of two related solutions. Both of them involve giving ServerInfo knowledge of another path and another resolve method. One would be something like resolveVar and would normally resolve to geronimo_home/var. This would involve all the gbeans currently looking inside var having the var trimmed off the front of their paths and using the new resolveVar method. In this case we'd have different servers represented as e.g. var1 var2 var3 ... The other would give ServerInfo something like resolveServer which would normally resolve to geronimo_home. The gbeans looking inside var would keep their current paths and just call the new resolve method instead of the old one. In this case we'd have servers like var server1/var server2/var ... In either case I think starting geronimo with a command line argument pointing to the var directory is the only way to specify which server you want to run; the default would presumably be as now var. Several people have suggested putting an additional config-store into var for private use by a particular server. At the moment I think that providing a different config-store class that uses the new resolve method on server info would be the best way to do this. I'm not attached to these ideas but this is as far as my thinking has gone. Please comment. thanks david jencks -- 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] Assigned: (GERONIMO-2095) Problem with attribute manager
[ http://issues.apache.org/jira/browse/GERONIMO-2095?page=all ] John Sisson reassigned GERONIMO-2095: - Assign To: John Sisson Problem with attribute manager -- Key: GERONIMO-2095 URL: http://issues.apache.org/jira/browse/GERONIMO-2095 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core Environment: http://people.apache.org/~hogstrom/20060607/geronimo-jetty-j2ee-1.1-20060607.tar.gz Windows XP, cygwin Command line: java -jar bin/server.jar Free disk space: 3 Gb Reporter: Guillaume Nodet Assignee: John Sisson Priority: Critical Fix For: 1.1 [EMAIL PROTECTED] /cygdrive/c/tmp/geronimo-1.1-20060607 $ java -jar bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_06)... Starting Geronimo Application Server v1.1-20060607 [** ] 30% 21s Starting geronimo/system-database...20:32:49,484 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [** ] 84% 39s Starting geronimo/webconsole-jett...20:33:07,890 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [**] 100% 45s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8009 0.0.0.0 Jetty Connector AJP13 8080 0.0.0.0 Jetty Connector HTTP 8443 0.0.0.0 Jetty Connector HTTPS 0.0.0.0 JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/webconsole-jetty/1.1-20060607/car RAR: geronimo/activemq/1.1-20060607/car RAR: geronimo/system-database/1.1-20060607/car WAR: geronimo/remote-deploy-jetty/1.1-20060607/car WAR: geronimo/welcome-jetty/1.1-20060607/car Web Applications: http://guillaumes:8080/ http://guillaumes:8080/console http://guillaumes:8080/console-standard http://guillaumes:8080/remote-deploy Geronimo Application Server started 20:33:18,718 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) -- 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-2095) Problem with attribute manager
[ http://issues.apache.org/jira/browse/GERONIMO-2095?page=comments#action_12415482 ] John Sisson commented on GERONIMO-2095: --- Reproduced on JDK1.5.0_06: $ /c/Program Files/Java/jdk1.5.0_06/jre/bin/java -jar bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_06)... Starting Geronimo Application Server v1.1-412854 [**] 100% 23s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8009 0.0.0.0 Tomcat Connector AJP 8080 0.0.0.0 Tomcat Connector HTTP 8443 0.0.0.0 Tomcat Connector HTTPS 0.0.0.0 JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/webconsole-tomcat/1.1-412854/car RAR: geronimo/activemq/1.1-412854/car RAR: geronimo/system-database/1.1-412854/car WAR: geronimo/remote-deploy-tomcat/1.1-412854/car WAR: geronimo/welcome-tomcat/1.1-412854/car Web Applications: http://JSLAP:8080/ http://JSLAP:8080/console http://JSLAP:8080/console-standard http://JSLAP:8080/remote-deploy Geronimo Application Server started Server shutdown begun 03:17:00,031 ERROR [GBeanInstance] Problem in doStop of geronimo/j2ee-system/1.1-412854/car?ServiceModule=geronimo/j2ee-system/1.1-4 12854/car,j2eeType=AttributeStore,name=AttributeManager java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless this is manually corrected! (could not rename C:\geronimo-1.1-412854\var\config\config.xml.working to C: \geronimo-1.1-412854\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager.doStop(LocalAttributeManager.java:573) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1143) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:337) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:548) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:548) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:548) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:310) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.system.main.Daemon$1.run(Daemon.java:245) Server shutdown completed [EMAIL PROTECTED] /c/geronimo-1.1-412854 $ Problem with attribute manager -- Key: GERONIMO-2095 URL: http://issues.apache.org/jira/browse/GERONIMO-2095 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core Environment: http://people.apache.org/~hogstrom/20060607/geronimo-jetty-j2ee-1.1-20060607.tar.gz Windows XP, cygwin Command line: java -jar bin/server.jar Free disk space: 3 Gb Reporter: Guillaume Nodet Assignee: John Sisson Priority: Critical Fix For: 1.1 [EMAIL PROTECTED] /cygdrive/c/tmp/geronimo-1.1-20060607 $ java -jar bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_06)... Starting Geronimo Application Server v1.1-20060607 [** ] 30% 21s Starting geronimo/system-database...20:32:49,484 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source)
[jira] Created: (GERONIMO-2096) PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open
PluginInstallerGBean.updatePluginMetadata(..) may leave geronimo-plugin.xml file open - Key: GERONIMO-2096 URL: http://issues.apache.org/jira/browse/GERONIMO-2096 Project: Geronimo Type: Bug Security: public (Regular issues) Components: core, Plugins Versions: 1.1 Reporter: John Sisson Fix For: 1.1 The code contains the following statement, where the xml variable is a File. xform.transform(new DOMSource(doc), new StreamResult(xml)); We have experienced in another issue ( GERONIMO-2095 ) that this does not close the FileOutputStream that gets created automatically on your behalf. It is safer to create your own FileOutputStream and pass it on the StreamResult constructor and ensure it is closed in a finally block. See fix for GERONIMO-2095 for an example. -- 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] Created: (GERONIMO-2097) PluginRepositoryExporter.updateMavenMetadata(..) may leave maven-metadata.xml file open
PluginRepositoryExporter.updateMavenMetadata(..) may leave maven-metadata.xml file open --- Key: GERONIMO-2097 URL: http://issues.apache.org/jira/browse/GERONIMO-2097 Project: Geronimo Type: Bug Security: public (Regular issues) Components: core, Plugins Versions: 1.1 Reporter: John Sisson Priority: Trivial Fix For: 1.1.1 The code contains the following statement, where the mavenFile variable is a File. xform.transform(new DOMSource(doc), new StreamResult(mavenFile)); We have experienced in another issue ( GERONIMO-2095 ) that this does not close the FileOutputStream that gets created automatically on your behalf. It is safer to create your own FileOutputStream and pass it on the StreamResult constructor and ensure it is closed in a finally block. See fix for GERONIMO-2095 for an example. Since this is in a standalone tool, it probably isn't a high priority as the file will be closed when the JVM terminates, but this may not always be used as a standalone tool. -- 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-2095) Problem with attribute manager
[ http://issues.apache.org/jira/browse/GERONIMO-2095?page=all ] John Sisson closed GERONIMO-2095: - Resolution: Fixed Fixed. Problem with attribute manager -- Key: GERONIMO-2095 URL: http://issues.apache.org/jira/browse/GERONIMO-2095 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core Environment: http://people.apache.org/~hogstrom/20060607/geronimo-jetty-j2ee-1.1-20060607.tar.gz Windows XP, cygwin Command line: java -jar bin/server.jar Free disk space: 3 Gb Reporter: Guillaume Nodet Assignee: John Sisson Priority: Critical Fix For: 1.1 [EMAIL PROTECTED] /cygdrive/c/tmp/geronimo-1.1-20060607 $ java -jar bin/server.jar Booting Geronimo Kernel (in Java 1.5.0_06)... Starting Geronimo Application Server v1.1-20060607 [** ] 30% 21s Starting geronimo/system-database...20:32:49,484 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [** ] 84% 39s Starting geronimo/webconsole-jett...20:33:07,890 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) [**] 100% 45s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8009 0.0.0.0 Jetty Connector AJP13 8080 0.0.0.0 Jetty Connector HTTP 8443 0.0.0.0 Jetty Connector HTTPS 0.0.0.0 JMX Remoting Connector 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/webconsole-jetty/1.1-20060607/car RAR: geronimo/activemq/1.1-20060607/car RAR: geronimo/system-database/1.1-20060607/car WAR: geronimo/remote-deploy-jetty/1.1-20060607/car WAR: geronimo/welcome-jetty/1.1-20060607/car Web Applications: http://guillaumes:8080/ http://guillaumes:8080/console http://guillaumes:8080/console-standard http://guillaumes:8080/remote-deploy Geronimo Application Server started 20:33:18,718 ERROR [LocalAttributeManager] Error saving attributes java.io.IOException: EXTREMELY CRITICAL! Unable to move manageable attributes working file to proper file name! Configuration will revert to defaults unless t his is manually corrected! (could not rename C:\tmp\geronimo-1.1-20060607\var\config\config.xml.working to C:\tmp\geronimo-1.1-20060607\var\config\config.xml) at org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:449) at org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:618) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) -- 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] Created: (GERONIMO-2080) Create a Geronimo Bug Guidelines Page
Create a Geronimo Bug Guidelines Page - Key: GERONIMO-2080 URL: http://issues.apache.org/jira/browse/GERONIMO-2080 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: website Reporter: John Sisson Assigned to: John Sisson Fix For: 1.1.1 Create a Geronimo Bug Guidelines page (e.g. like http://db.apache.org/derby/DerbyBugGuidelines.html ) on the website off the JIRA link that discusses JIRA usage and may help prevent JIRA being used as a place to ask questions, with the link to JIRA on that page. -- 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-1453) GBeanOverride throws NullPointerException when more than one reference element specified
[ http://issues.apache.org/jira/browse/GERONIMO-1453?page=all ] John Sisson closed GERONIMO-1453: - Fix Version: 1.1 Resolution: Fixed Checked the code and the problem identified in the patch has been fixed. GBeanOverride throws NullPointerException when more than one reference element specified Key: GERONIMO-1453 URL: http://issues.apache.org/jira/browse/GERONIMO-1453 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core Versions: 1.0 Reporter: Kristian Koehler Fix For: 1.1 Attachments: GBeanOverride.patch Hi if there are more than one reference Element for a GBean within the config.xml file the GBeanOverride class throws a NullPointerException. Example GBean config to add: --- 8 --- gbean name=geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatWebContainer attribute name=catalinaHomevar/catalina/attribute reference name=EngineGBean patterngbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatEngine/gbean-name/pattern /reference reference name=ServerInfo patterngbean-namegeronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo/gbean-name/pattern /reference /gbean --- 8 --- Kristian -- 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] Created: (GERONIMO-2069) o.a.g.system.configuration.LocalAttributeManager.load() does not setErrorHandler when parsing
o.a.g.system.configuration.LocalAttributeManager.load() does not
setErrorHandler when parsing
--
Key: GERONIMO-2069
URL: http://issues.apache.org/jira/browse/GERONIMO-2069
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: startup/shutdown
Versions: 1.1
Reporter: John Sisson
Assigned to: John Sisson
Priority: Minor
Fix For: 1.1
There are two issues in the load() processing:
* If a validation error occurs, the file containing the error isn't identified.
The code needs to use inputsource.setSystemId(..) so the errors from the
parser identify the config.xml file, rather than displaying URI=null.
* No error handler is set up, so a warning message is issued from Xerces.
If the config.xml file is invalid, startup will produce output similar to the
following:
$./geronimo.sh run --long
Using GERONIMO_BASE:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
Using GERONIMO_HOME:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
Using GERONIMO_TMPDIR:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/var/temp
Using JRE_HOME:/usr/j2se
Booting Geronimo Kernel (in Java 1.4.2_10)...
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not
set, which is probably not what is desired. Parser will use a default
ErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.
Error: URI=null Line=74: cvc-complex-type.2.4.b: The content of element
'reference' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1:pattern}' is expected.
Module 1/20 geronimo/rmi-naming/1.1-SNAPSHOT/car started in
.594s
SNIP
--
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] Created: (GERONIMO-2070) config.xml validation error when attempting to clear references for a GBean
config.xml validation error when attempting to clear references for a GBean
---
Key: GERONIMO-2070
URL: http://issues.apache.org/jira/browse/GERONIMO-2070
Project: Geronimo
Type: Bug
Security: public (Regular issues)
Components: startup/shutdown
Versions: 1.1
Reporter: John Sisson
Assigned to: John Sisson
Priority: Blocker
Fix For: 1.1
Currently the j2ee-tomcat assembly's config.xml attempts to clear a GBean
reference in it's var\config.xml file by doing the following:
gbean name=TomcatEngine
reference name=TomcatValveChain /
/gbean
This results in the following validation error because the referenceType in the
local-attributes-1.1.xsd schema specifies minOccurs=1 for the child pattern
element. This does not match the logic in the GBeanOverride class that treats
zero pattern elements as an indication that references should be cleared for
the GBean.
Error: URI=null Line=74: cvc-complex-type.2.4.b: The content of element
'reference' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1:pattern}' is expected.
A recent change to the config.xml file in rev 407883 as exposed this problem.
--
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-2065) Not able to Build Geronimo1.0 , Geronimo 1.1
[ http://issues.apache.org/jira/browse/GERONIMO-2065?page=all ]
John Sisson closed GERONIMO-2065:
-
Fix Version: 1.1
Resolution: Duplicate
Assign To: John Sisson
Closing. Created more specific JIRAs GERONIMO-2070 and GERONIMO-2069 for these
issues in 1.1.
Not able to Build Geronimo1.0 , Geronimo 1.1
Key: GERONIMO-2065
URL: http://issues.apache.org/jira/browse/GERONIMO-2065
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: buildsystem
Versions: 1.0
Environment: Win2k , Java2_1.4_09
Reporter: Mansoor
Assignee: John Sisson
Priority: Critical
Fix For: 1.1
Hi Everybody ,
Iam facing lot of problems in building the server from scratch ,
1. I did svn checkout for Geronimo1.0 using the below command
svn co http://svn.apache.org/repos/asf/geronimo/branches/1.0/
geronimo1.0_src
2. Executed command maven new under the folder
geronimo1.0_src, result Build Successfull
3, Executed the command maven under the folder
geronimo1.0_src/assembelies/j2ee-tomcat-server/ ,
Result : Build failed , with following errors
The build cannot continue because of the following unsatisfied dependencies:
j2ee-security-1.0.1-SNAPSHOT.car
j2ee-corba-1.0.1-SNAPSHOT.car
tomcat-1.0.1-SNAPSHOT.car
directory-1.0.1-SNAPSHOT.car
ldap-realm-1.0.1-SNAPSHOT.car
system-database-1.0.1-SNAPSHOT.car
activemq-broker-1.0.1-SNAPSHOT.car
activemq-1.0.1-SNAPSHOT.car
client-system-1.0.1-SNAPSHOT.car
client-1.0.1-SNAPSHOT.car
client-security-1.0.1-SNAPSHOT.car
client-corba-1.0.1-SNAPSHOT.car
javamail-1.0.1-SNAPSHOT.car
hot-deployer-1.0.1-SNAPSHOT.car
j2ee-deployer-1.0.1-SNAPSHOT.car
tomcat-deployer-1.0.1-SNAPSHOT.car
ldap-demo-tomcat-1.0.1-SNAPSHOT.car
welcome-tomcat-1.0.1-SNAPSHOT.car
servlets-examples-tomcat-1.0.1-SNAPSHOT.car
jsp-examples-tomcat-1.0.1-SNAPSHOT.car
webconsole-tomcat-1.0.1-SNAPSHOT.car
jmxdebug-tomcat-1.0.1-SNAPSHOT.car
remote-deploy-tomcat-1.0.1-SNAPSHOT.car
uddi-tomcat-1.0.1-SNAPSHOT.car
daytrader-derby-tomcat-1.0.1-SNAPSHOT.car
daytrader-derby-tomcat-streamer-client-1.0.1-SNAPSHOT.car
online-deployer-1.0.1-SNAPSHOT.car
shutdown-1.0.1-SNAPSHOT.car
Total time: 4 minutes 4 seconds
Finished at: Sat May 27 15:59:46 IST 2006
And even when i tried downloading
geronimo1.1 and builded from assemebelies/j2ee-tomcat-server/ ,
Result was = Build Successfull but when i tried starting the server using
the below command i get following errors
C:\geronimo_src\geronimo1.1\assemblies\j2ee-tomcat-server\target\geronimo-1.1-SN
APSHOT\binjava -jar server.jar
Booting Geronimo Kernel (in Java 1.4.2_09)...
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not
set, which is probably not what is desired. Parser will use a default
ErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.
Error: URI=null Line=71: cvc-complex-type.2.4.b: The content of element
'referen
ce' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1;
:pattern}' is expected.
Starting Geronimo Application Server v1.1-SNAPSHOT
[*] 25% 9s Startup failed
org.apache.geronimo.kernel.config.LifecycleException: start of
geronimo/openejb/
1.1-SNAPSHOT/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:522)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:486)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(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:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:817)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
7)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$327d01f1.startConfiguration(generated)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.init(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Caused by: org.apache.geronimo.kernel.config.InvalidConfigException:
[jira] Closed: (GERONIMO-2070) config.xml validation error when attempting to clear references for a GBean
[ http://issues.apache.org/jira/browse/GERONIMO-2070?page=all ]
John Sisson closed GERONIMO-2070:
-
Resolution: Fixed
config.xml validation error when attempting to clear references for a GBean
---
Key: GERONIMO-2070
URL: http://issues.apache.org/jira/browse/GERONIMO-2070
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: startup/shutdown
Versions: 1.1
Reporter: John Sisson
Assignee: John Sisson
Priority: Blocker
Fix For: 1.1
Currently the j2ee-tomcat assembly's config.xml attempts to clear a GBean
reference in it's var\config.xml file by doing the following:
gbean name=TomcatEngine
reference name=TomcatValveChain /
/gbean
This results in the following validation error because the referenceType in
the local-attributes-1.1.xsd schema specifies minOccurs=1 for the child
pattern element. This does not match the logic in the GBeanOverride class
that treats zero pattern elements as an indication that references should be
cleared for the GBean.
Error: URI=null Line=74: cvc-complex-type.2.4.b: The content of element
'reference' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1:pattern}' is expected.
A recent change to the config.xml file in rev 407883 as exposed this problem.
--
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-2069) o.a.g.system.configuration.LocalAttributeManager.load() does not setErrorHandler when parsing
[ http://issues.apache.org/jira/browse/GERONIMO-2069?page=all ]
John Sisson closed GERONIMO-2069:
-
Resolution: Fixed
Fixed. Users will now get a more useful error giving the file name, line and
column number.
C:\testxgeronimo-1.1-SNAPSHOT\bin\geronimo.bat run --long
Using GERONIMO_HOME: C:\testx\geronimo-1.1-SNAPSHOT
Using GERONIMO_TMPDIR: C:\testx\geronimo-1.1-SNAPSHOT\var\temp
Using JRE_HOME:C:\j2sdk1.4.2_10
Booting Geronimo Kernel (in Java 1.4.2_10)...
00:09:55,937 ERROR [LocalAttributeManager] Unable to read saved manageable
attributes.SAX parse error: cvc-complex-type.2.4.b: The c
ontent of element 'pattern' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1:groupId, http://geronimo.a
pache.org/xml/ns/attributes-1.1:artifactId,
http://geronimo.apache.org/xml/ns/attributes-1.1:version,
http://geronimo.apache.org
/xml/ns/attributes-1.1:type,
http://geronimo.apache.org/xml/ns/attributes-1.1:module,
http://geronimo.apache.org/xml/ns/attribut
es-1.1:name}' is expected. at line 72, column 19 in entity
file:///C:/testx/geronimo-1.1-SNAPSHOT/var/config/config.xml
Module 1/20 geronimo/rmi-naming/1.1-SNAPSHOT/car started in
.297s
o.a.g.system.configuration.LocalAttributeManager.load() does not
setErrorHandler when parsing
-
Key: GERONIMO-2069
URL: http://issues.apache.org/jira/browse/GERONIMO-2069
Project: Geronimo
Type: Bug
Security: public(Regular issues)
Components: startup/shutdown
Versions: 1.1
Reporter: John Sisson
Assignee: John Sisson
Priority: Minor
Fix For: 1.1
There are two issues in the load() processing:
* If a validation error occurs, the file containing the error isn't
identified. The code needs to use inputsource.setSystemId(..) so the errors
from the parser identify the config.xml file, rather than displaying URI=null.
* No error handler is set up, so a warning message is issued from Xerces.
If the config.xml file is invalid, startup will produce output similar to the
following:
$./geronimo.sh run --long
Using GERONIMO_BASE:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
Using GERONIMO_HOME:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT
Using GERONIMO_TMPDIR:
/home/sissonj/OpenSourceJava/asf/geronimo/branches/1.1/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/var/temp
Using JRE_HOME:/usr/j2se
Booting Geronimo Kernel (in Java 1.4.2_10)...
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not
set, which is probably not what is desired. Parser will use a default
ErrorHandler to print the first 10 errors. Please call
the 'setErrorHandler' method to fix this.
Error: URI=null Line=74: cvc-complex-type.2.4.b: The content of element
'reference' is not complete. One of
'{http://geronimo.apache.org/xml/ns/attributes-1.1:pattern}' is expected.
Module 1/20 geronimo/rmi-naming/1.1-SNAPSHOT/car started in
.594s
SNIP
--
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-2038) assemblies\minimal-tomcat-server fails on windows due to file path length
[ http://issues.apache.org/jira/browse/GERONIMO-2038?page=all ] John Sisson closed GERONIMO-2038: - Resolution: Invalid What I thought was a long file name problem must have been another problem and does not occur any more. Closing issue as invalid. assemblies\minimal-tomcat-server fails on windows due to file path length - Key: GERONIMO-2038 URL: http://issues.apache.org/jira/browse/GERONIMO-2038 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Priority: Blocker Fix For: 1.1 Build failed on windows with openejb patch. It appears we have hit a filename limit again, as it failed because it couldn't delete C:\dev\geronimo\br\1.1\assemblies\minimal-tomcat-server\target When I shortened the directory name to min-tomcat-server and changed the artifact name to geronimo-tomcat-min it worked fine. If there are no objections, I will commit a change that changes the tomcat and jetty minimal assemblies to use min rather than minimal in their names. C:\dev\geronimo\br\1.1svn info Path: . URL: https://svn.apache.org/repos/asf/geronimo/branches/1.1 Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 407390 Node Kind: directory Schedule: normal Last Changed Author: kevan Last Changed Rev: 407349 Last Changed Date: 2006-05-18 04:30:34 +1000 (Thu, 18 May 2006) Properties Last Updated: 2006-03-31 07:54:02 +1000 (Fri, 31 Mar 2006) 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + 23:04:28,936 INFO [ReactorTag] + | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat 23:04:28,936 INFO [ReactorTag] | assemblies Geronimo Assembly for a Web Server running Tomcat | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO [ReactorTag] | Memory: 67M/107M 23:04:28,952 INFO
[jira] Created: (GERONIMO-2060) Changes made to packaging plugin without bumping up version
Changes made to packaging plugin without bumping up version --- Key: GERONIMO-2060 URL: http://issues.apache.org/jira/browse/GERONIMO-2060 Project: Geronimo Type: Bug Security: public (Regular issues) Components: buildsystem, Plugins Versions: 1.1 Reporter: John Sisson Assigned to: John Sisson Priority: Critical Fix For: 1.1 We should bump up version numbers of packaging plugin as changes were made to the plugin since the version number was bumped up (about 5 hours after) and some developers may have an out of date version in their local repository. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. On the 15th of May the following changes were made approx 5 hours apart: http://svn.apache.org/viewcvs?rev=406440view=rev http://svn.apache.org/viewcvs?rev=406500view=rev -- 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-2060) Changes made to plugins without bumping up version
[ http://issues.apache.org/jira/browse/GERONIMO-2060?page=all ] John Sisson updated GERONIMO-2060: -- Summary: Changes made to plugins without bumping up version (was: Changes made to packaging plugin without bumping up version) Description: We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. Here are the changes that I could find that didn't bump up plugin version numbers. http://svn.apache.org/viewcvs?rev=390754view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395662view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395883view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=395886view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin) http://svn.apache.org/viewcvs?rev=396475view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) was: We should bump up version numbers of packaging plugin as changes were made to the plugin since the version number was bumped up (about 5 hours after) and some developers may have an out of date version in their local repository. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. On the 15th of May the following changes were made approx 5 hours apart: http://svn.apache.org/viewcvs?rev=406440view=rev http://svn.apache.org/viewcvs?rev=406500view=rev Changes made to plugins without bumping up version -- Key: GERONIMO-2060 URL: http://issues.apache.org/jira/browse/GERONIMO-2060 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem, Plugins Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Priority: Critical Fix For: 1.1 We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. Here are the changes that I could find that didn't bump up plugin version numbers. http://svn.apache.org/viewcvs?rev=390754view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395662view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395883view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=395886view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin) http://svn.apache.org/viewcvs?rev=396475view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) -- 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-2060) Changes made to plugins without bumping up version
[ http://issues.apache.org/jira/browse/GERONIMO-2060?page=all ] John Sisson updated GERONIMO-2060: -- Description: We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin, version was incremented in rev 399794) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) The geronimo-packaging-plugin needs version bumped up. was: We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. Here are the changes that I could find that didn't bump up plugin version numbers. http://svn.apache.org/viewcvs?rev=390754view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395662view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395883view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=395886view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin) http://svn.apache.org/viewcvs?rev=396475view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) FYI, I have checked the other plugins and their version numbers have been updated in their last changes. http://svn.apache.org/viewcvs?rev=390754view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=393652view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395662view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=394439view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=395290view=rev (geronimo-assembly-plugin, version bumped up in 395629) http://svn.apache.org/viewcvs?rev=395662view=rev (geronimo-assembly-plugin, version bumped up in 396287) http://svn.apache.org/viewcvs?rev=396475view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=396548view=rev (geronimo-assembly-plugin) http://svn.apache.org/viewcvs?rev=397677view=rev (geronimo-assembly-plugin) Version bumbed up in rev 405881 (last change), so now should be ok http://svn.apache.org/viewcvs?rev=395883view=rev (geronimo-deployment-plugin) http://svn.apache.org/viewcvs?rev=396548view=rev (geronimo-deployment-plugin) Version bumbed up in rev 399898, so now should be ok.) Changes made to plugins without bumping up version -- Key: GERONIMO-2060 URL: http://issues.apache.org/jira/browse/GERONIMO-2060 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem, Plugins Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Priority: Critical Fix For: 1.1 We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin, version was incremented in rev 399794) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) The geronimo-packaging-plugin needs version bumped up. -- 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-2060) Changes made to plugins without bumping up version
[ http://issues.apache.org/jira/browse/GERONIMO-2060?page=all ] John Sisson closed GERONIMO-2060: - Resolution: Fixed Fixed. geronimo_packaging_plugin_version is now version 1.1.0-10 Changes made to plugins without bumping up version -- Key: GERONIMO-2060 URL: http://issues.apache.org/jira/browse/GERONIMO-2060 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem, Plugins Versions: 1.1 Reporter: John Sisson Assignee: John Sisson Priority: Critical Fix For: 1.1 We should bump up version numbers of plugins in the same commit as the plugin changes. There have been a number of commits where changes have been made to plugins but the version number wasn't bumped up. Not sure if this was the cause of my build problems in GERONIMO-2037 and (problems reported by Tony in the recent build problem on 1.1 branch thread) that that I fixed by deleting the plugins in the local repository. http://svn.apache.org/viewcvs?rev=396071view=rev (geronimo-packaging-plugin, version was incremented in rev 399794) http://svn.apache.org/viewcvs?rev=406500view=rev (geronimo-packaging-plugin) The geronimo-packaging-plugin needs version bumped up. -- 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] Assigned: (GERONIMO-2037) Build failing on some Windows boxes and Solaris x86
[ http://issues.apache.org/jira/browse/GERONIMO-2037?page=all ] John Sisson reassigned GERONIMO-2037: - Assign To: John Sisson Build failing on some Windows boxes and Solaris x86 --- Key: GERONIMO-2037 URL: http://issues.apache.org/jira/browse/GERONIMO-2037 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem Environment: Windows XP - 1.4.2_11-b06 Solaris x86 - 1.4.2_10-b03 Reporter: John Sisson Assignee: John Sisson Priority: Blocker Fix For: 1.1 I can build geronimo on my windows notebook ok (with the GERONIMO-1434 openejb patch applied). But when I try to build on my windows desktop (tried latest 1.4.2_11-b06 jvm) it fails with a JVM crash. I found that whilst running with diagnostic code enabled (slowing the build down) the build worked on my windows desktop. I think Joe Bohn had also run into this crash on Windows. I didn't get a JVM crash on Solaris x86, but got a NoClassDefFoundError (see below) in the same part of the build that had the JVM crash. *Windows Output *** 13:12:30,732 INFO [ReactorTag] | configurations Geronimo Configuration for performing service deployments 13:12:30,732 INFO [ReactorTag] | Memory: 96M/103M build:start: multiproject:install-callback: [echo] Running car:install for Geronimo Configuration for performing service deployments # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x7c92ae22, pid=5240, tid=4788 # # Java VM: Java HotSpot(TM) Client VM (1.4.2_11-b06 mixed mode) # Problematic frame: # C [ntdll.dll+0x2ae22] # --- T H R E A D --- Current thread (0x000377a8): JavaThread main [_thread_in_native, id=4788] siginfo: ExceptionCode=0xc005, reading address 0xd1d7763b Registers: EAX=0x00048b77, EBX=0x, ECX=0xd1d7763b, EDX=0x00030608 ESP=0x0007d858, EBP=0x0007d914, ESI=0x030654d0, EDI=0x0003 EIP=0x7c92ae22, EFLAGS=0x00010213 Top of Stack: (sp=0x0007d858) 0x0007d858: 77c2c21b 030654f0 04ba4238 0356 0x0007d868: 04ba4238 0008 000e 7ffdd000 0x0007d878: 001e 7ffdd000 000377a8 0007d860 0x0007d888: 63617061 0007d8fc 7c8399f3 7c809bd8 0x0007d898: d1d7763b 77c2f941 00048b77 0x0007d8a8: 030654d0 001e 0007d8c4 0x0007d8b8: 77c62448 01d4 004d 001e 0x0007d8c8: 001e 77c2e556 02fa1bd8 0007d90c Instructions: (pc=0x7c92ae22) 0x7c92ae12: 75 cc 89 75 94 8b 06 89 45 90 8b 4e 04 89 4d 88 0x7c92ae22: 8b 11 3b 50 04 0f 85 93 d1 ff ff 3b d6 0f 85 8b Stack: [0x0004,0x0008), sp=0x0007d858, free space=246k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [ntdll.dll+0x2ae22] C [MSVCRT.dll+0x1c2de] C [zip.dll+0x7a50] C [zip.dll+0x7792] C [zip.dll+0x1b2c] J java.util.zip.ZipFile.getEntry(JLjava/lang/String;)J J java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; J java.util.jar.JarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; J java.util.jar.JarFile.getJarEntry(Ljava/lang/String;)Ljava/util/jar/JarEntry; J sun.misc.URLClassPath$JarLoader.getResource(Ljava/lang/String;Z)Lsun/misc/Resource; J sun.misc.URLClassPath.getResource(Ljava/lang/String;Z)Lsun/misc/Resource; J java.net.URLClassLoader$1.run()Ljava/lang/Object; v ~StubRoutines::call_stub V [jvm.dll+0x72846] V [jvm.dll+0xac976] V [jvm.dll+0x72753] V [jvm.dll+0x881d7] C [java.dll+0x1061] J java.net.URLClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class; J java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; J java.lang.ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class; J java.lang.ClassLoader.loadClassInternal(Ljava/lang/String;)Ljava/lang/Class; v ~StubRoutines::call_stub V [jvm.dll+0x72846] V [jvm.dll+0xac976] V [jvm.dll+0x72753] V [jvm.dll+0x7255b] V [jvm.dll+0x725d3] V [jvm.dll+0xc40e0] V [jvm.dll+0xc3d47] V [jvm.dll+0xc3836] V [jvm.dll+0xc3745] V [jvm.dll+0xb6a18] V [jvm.dll+0xb6bca] V [jvm.dll+0xb6de3] V [jvm.dll+0x88ea7] j java.lang.Class.getDeclaredMethods0(Z)[Ljava/lang/reflect/Method;+0 J java.lang.Class.privateGetDeclaredMethods(Z)[Ljava/lang/reflect/Method; v ~RuntimeStub::alignment_frame_return Runtime1 stub j java.lang.Class.getDeclaredMethods()[Ljava/lang/reflect/Method;+10 j java.beans.Introspector$1.run()Ljava/lang/Object;+4 v ~StubRoutines::call_stub V [jvm.dll+0x72846] V [jvm.dll+0xac976] V [jvm.dll+0x72753] V [jvm.dll+0x881d7] C [java.dll+0x1015] J java.beans.Introspector.getPublicDeclaredMethods(Ljava/lang/Class;)[Ljava/lang/reflect/Method; J java.beans.Introspector.getTargetMethodInfo()[Ljava/beans/MethodDescriptor; v
