Stack trace while shutting down amq in geronimo 2.0
I'm seeing the following stack trace when shutting down the jetty6 geronimo server in trunk. Anyone have a clue about why, if it is a problem, and what we might do about it? thanks david jencks Server shutdown begun 00:37:33,024 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop (BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop (BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance (GBeanInstance.java:1146) 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:551) 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:551) 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:551) 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: 234) 00:37:33,028 ERROR [JournalPersistenceAdapter] Could not stop service: [EMAIL PROTECTED] Reason: SQL Exception: No current connection. SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop (BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop (BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance (GBeanInstance.java:1146) at
[jira] Created: (AMQ-1091) add a source distro to the maven2 build
add a source distro to the maven2 build --- Key: AMQ-1091 URL: https://issues.apache.org/activemq/browse/AMQ-1091 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Stack trace while shutting down amq in geronimo 2.0
I'm seeing the following stack trace when shutting down the jetty6 geronimo server in trunk. Anyone have a clue about why, if it is a problem, and what we might do about it? thanks david jencks Server shutdown begun 00:37:33,024 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop (BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop (BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance (GBeanInstance.java:1146) 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:551) 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:551) 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:551) 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: 234) 00:37:33,028 ERROR [JournalPersistenceAdapter] Could not stop service: [EMAIL PROTECTED] Reason: SQL Exception: No current connection. SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop (BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop (BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance (GBeanInstance.java:1146) at
[jira] Assigned: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-118: Assignee: Shiva Kumar H R Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMO-2576) Rollbacks at database level throws exception in Geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-2576?page=all ] Arunanthisivam Vimalathithen updated GERONIMO-2576: --- Priority: Blocker (was: Major) Rollbacks at database level throws exception in Geronimo Key: GERONIMO-2576 URL: http://issues.apache.org/jira/browse/GERONIMO-2576 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 1.1.1 Environment: Windows XP, DB2 Reporter: Arunanthisivam Vimalathithen Priority: Blocker Attachments: src.zip I have a stateless session EJB which accesses a DB2 datasource created using the tranql generic connector. This uses the container managed transaction. I am also using the DB2 9.1 universal JDBC drivers. For methods dealing with datasource related operations I have set sessionContext.setRollBackOnly() within the catch block of SQLException. This throws exceptions when there have to be rollbacks at the database level. For example trying to insert a duplicate record throws the following exception:- com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. Is there any way to turn auto-commit off? I have created an example scenario and attached the source with this issue. -- 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
Re: Improve 'Geronimo' Development--WORDY RESPONSE
Hi Sachin, this is a very good question and I've been dwelling on it for a number of weeks now after looking at the Geronimo deployment code, and the integration steps required for JSF 1.2. Being the new kid on the block in the community I feel there is another side to this problem that also has some room for improvement. Two of the things that first struck me about Geronimo when I joined the team were how little code there is in Geronimo proper (relatively), and how much a simple user interface with a topology and dependency viewer would really improve maven. So my three main points are that: 1 -- One of the primary strengths of Geronimo is how configurable it is and how so many other other services and functions can be integrated into it. I hesitate to use the word easily here though--it might be easy after a steep learning curve but it's not intuitively easy. 2 -- How there are really no GUI based tools to aid in the tasks required for integration, configuration, and building of Geronimo 3 -- How much time developers spend doing changes for integration, configuration, and the maven build, and how little time is spent writing Java code. This point may seem like somewhat of an exaggeration but I see the all the changes flowing into SVN/SVK everyday and the Java changes are easily surpassed by the various changes to XML type files I'm very visually oriented and consume and retain information much easier when it's in graphical in nature. So it just seems to me that we could easily create a GUI-based tool to aid in the tasks required for new integrations and configurations--not another IDE for Java development but maybe an analog such as an Integration and Configuration Environment (I can think of a very cool acronym here). So, I'm kinda envisioning a tool with some of the selected capabilities of Eclipse GEF, Visio, and XMLSpy. I for one would really benefit from a tool with these capabilities: -- See a hierarchical view of all the POM's required to build Geronimo and the dependencies between those POM's, and could selectively drill down from the top-most POM into all the other dependent levels, expand and collapse various trees in the hierarchy, and easily navigate and traverse the build and dependency topology -- Change XML in graphical or tabular view (like any XML editor or XMLSpy) such that the views/forms are created and validated with the appropriate XSD(s) instead of editing XML using a flat-file editor . This could apply not just to Maven POM XML files, but also Geronimo-specific deployment plan XML files, etc -- Search and display (and create or delete) dependencies and relationships graphically -- Graphically view all the dependencies and artifacts within a particular Geronimo assembly -- Graphically view all the dependencies for modules and GBeans -- Drag and drop dependencies and artifacts from lists to nodes in the topology -- Use wizards based on best-practices and past experiences for integration of new functions/services -- I could go on and on but I hope I've conveyed my thoughts. Of course, this is just my impression--it just seems we could be more productive if we could mitigate some of the effort required to configure and integrate new function and/or services into Geronimo with a GUI based tool (not yet another command line based tool) such that we could spend more productive time coding and less time integrating/configuring/building. Obviously, this is not a panacea but I'm wondering what others in the community think. I'm actually thinking it might be worthwhile for me to plan to spend some time over the holidays doing a simple staged prototype (e.g., first, display the maven build topology, then maybe graphically display the Geronimo specific deployment plans, etc...) and then solicit more feedback/comments. Any thoughts ?? Be brutal--I don't mind. Thanks much Tim Sachin Patel wrote: So since I've been working on Geronimo, one of the most annoying things developing Geronimo in an IDE is the overhead involved between modifing code and being able to test the code. For a single line change you have to rebuild and install the module, rebuild the assembly, and re-extract and relaunch the server image. This is needed since Geronimo loads classes from the server repository and currently cannot from the local m2 repo or from the target/classes directory itself. Well to ease the developer experience I think we need to change that. As a first step, I'd like to see if we can hook into geronimo a developers module that the repository code can delegate over to to load from the m2 repo. That itself would be an improvement and developers could simply rebuild the module without having to regen a new assembly. A step beyond that would be the ability to treat the source tree as a repo, and geronimo load directly from target/classes, this is tricker since the modules in the source tree don't follow a
[jira] Updated: (GERONIMO-1907) Deploy command should redeploy if the app is already deployed
[ http://issues.apache.org/jira/browse/GERONIMO-1907?page=all ] Vamsavardhana Reddy updated GERONIMO-1907: -- Fix Version/s: 1.x 2.0 (was: 1.2) Description: Attached patch, and changing fix version to 1.2. Also unassigning so that committers can review and update. (was: Attached patch, and changing fix version to 1.2. Also unassigning so that committers can review and update.) Deploy command should redeploy if the app is already deployed - Key: GERONIMO-1907 URL: http://issues.apache.org/jira/browse/GERONIMO-1907 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment, usability Affects Versions: 1.1 Reporter: Aaron Mulder Priority: Critical Fix For: 1.x, 2.0 Attachments: redeploy.patch Attached patch, and changing fix version to 1.2. Also unassigning so that committers can review and update. -- This message is automatically generated by JIRA. - 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-1314) Provide documentation that helps users make an informed decision as whether to use Tomcat or Jetty Web Container
[ http://issues.apache.org/jira/browse/GERONIMO-1314?page=all ] Vamsavardhana Reddy updated GERONIMO-1314: -- Fix Version/s: 1.x 2.0 (was: 1.2) Provide documentation that helps users make an informed decision as whether to use Tomcat or Jetty Web Container Key: GERONIMO-1314 URL: http://issues.apache.org/jira/browse/GERONIMO-1314 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: installer, Tomcat, web Affects Versions: Wish List Reporter: John Sisson Fix For: 1.x, 2.0 Currently a lot of users probably choose to use Tomcat because it has had more visibility and there isn't much Geronimo documentation about Jetty and why they might want to use it. Ideas: A link to a documentation page could possibly be presented in the installer where the users choose between Tomcat or Jetty. Can we provide help in the installer? Provide information on the features of the containers and anything that differentiates one from the other. Provide links to GBean configuration documentation for each container. Provide information mapping Tomcat and Jetty concepts for users who are already famiiar with one of the containers - make it easy for them to migrate existing apps. -- 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-1488) externalize sensitive data out of the deployment plans
[ http://issues.apache.org/jira/browse/GERONIMO-1488?page=all ] Vamsavardhana Reddy updated GERONIMO-1488: -- Fix Version/s: 2.0 (was: 1.2) externalize sensitive data out of the deployment plans -- Key: GERONIMO-1488 URL: http://issues.apache.org/jira/browse/GERONIMO-1488 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: security Affects Versions: Wish List Reporter: simon godik Fix For: 2.0 externalize sensitive data out of deployment plans. Reference secure-vault gbean and grant gbean permission to read vault for the given alias; Gbean-permission is granted in the deployment plan; deployment plan syntax needs to be extended to support gbean permissions -- 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-1746) Updates to Logger through Log Manager portlet under Console are not reflected in the server
[ http://issues.apache.org/jira/browse/GERONIMO-1746?page=all ] Vamsavardhana Reddy updated GERONIMO-1746: -- Fix Version/s: Wish List (was: 1.2) Updates to Logger through Log Manager portlet under Console are not reflected in the server --- Key: GERONIMO-1746 URL: http://issues.apache.org/jira/browse/GERONIMO-1746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Logging Affects Versions: 1.0 Environment: Win XP, Sun JDK 1.4.2_08 Reporter: Vamsavardhana Reddy Fix For: Wish List Changes made to the logger through Log Manager portlet are not reflected in the server. Through the admin console, I have changed the Config File from server-log4j.properties to a different file. The change is written to config.xml . Inspite of this new file name in config.xml, upon restart, the server still uses server-log4j.properties . Restarting the server after deleting server-log4j.properties logged the following error to console window. log4j:ERROR Could not read configuration file from URL [file:/C:/geronimo-1.0/va r/log/server-log4j.properties]. java.io.FileNotFoundException: C:\geronimo-1.0\var\log\server-log4j.properties ( The system cannot find the file specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(Unknown Source) at java.io.FileInputStream.init(Unknown Source) at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source) at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown So urce) at java.net.URL.openStream(Unknown Source) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato r.java:424) at org.apache.geronimo.system.logging.log4j.URLConfigurator.doConfigure( URLConfigurator.java:117) at org.apache.geronimo.system.logging.log4j.URLConfigurator.configure(UR LConfigurator.java:44) at org.apache.geronimo.system.logging.log4j.Log4jService.reconfigure(Log 4jService.java:518) at org.apache.geronimo.system.logging.log4j.Log4jService.doStart(Log4jSe rvice.java:561) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:936) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:132) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:537) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:208) at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans( Configuration.java:315) at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f 4b4a9b.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:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 178) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 173) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:286) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:82) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:404) log4j:ERROR Ignoring configuration file [file:/C:/geronimo-1.0/var/log/server-lo g4j.properties]. -- 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-1761) Change geronimo-util module to geronimo-crypto, give credit where credit is due
[ http://issues.apache.org/jira/browse/GERONIMO-1761?page=all ] Vamsavardhana Reddy updated GERONIMO-1761: -- Fix Version/s: 2.0 (was: 1.2) Change geronimo-util module to geronimo-crypto, give credit where credit is due --- Key: GERONIMO-1761 URL: http://issues.apache.org/jira/browse/GERONIMO-1761 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Affects Versions: 1.0 Reporter: Aaron Mulder Fix For: 2.0 The util module holds a bunch of crypto-related stuff. Speculation is that it's the non-encumbered code from bouncycastle. It should be in a more accurately named module and package, since it's not just generic util code. It would also be nice to put a note in every file header saying where it's from, or at least in NOTICE.txt perhaps. There may be improvements we want to track? -- 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-1807) Remove uses of ObjectName from core server
[ http://issues.apache.org/jira/browse/GERONIMO-1807?page=all ] Vamsavardhana Reddy updated GERONIMO-1807: -- Fix Version/s: 2.0 (was: 1.2) Remove uses of ObjectName from core server -- Key: GERONIMO-1807 URL: http://issues.apache.org/jira/browse/GERONIMO-1807 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Reporter: Dain Sundstrom Fix For: 2.0 Using the ObjectName class in the core server causes a dependency on the jmx classes. We are also in the process of moving away from these, but there are still many places that use this class. -- 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-1808) Replace AbstractName with URI
[ http://issues.apache.org/jira/browse/GERONIMO-1808?page=all ] Vamsavardhana Reddy updated GERONIMO-1808: -- Fix Version/s: 2.0 (was: 1.2) Replace AbstractName with URI - Key: GERONIMO-1808 URL: http://issues.apache.org/jira/browse/GERONIMO-1808 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Reporter: Dain Sundstrom Fix For: 2.0 Using a custom name class for Geronimo causes unnecessary extra dependencies on Geronimo jars. Instead of using a custom name class we can instead just encode our name into a URI. The following describes the current proposal: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Service+Names -- 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-1829) Service Plans should allow GBean references by interface (vs. by name)
[ http://issues.apache.org/jira/browse/GERONIMO-1829?page=all ] Vamsavardhana Reddy updated GERONIMO-1829: -- Fix Version/s: 1.x 2.0 (was: 1.2) Service Plans should allow GBean references by interface (vs. by name) -- Key: GERONIMO-1829 URL: http://issues.apache.org/jira/browse/GERONIMO-1829 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 1.0 Reporter: Aaron Mulder Fix For: 1.x, 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1842) Dynamically load jars from the WEB-INF/lib directory
[ http://issues.apache.org/jira/browse/GERONIMO-1842?page=all ] Vamsavardhana Reddy updated GERONIMO-1842: -- Fix Version/s: 1.x 2.0 (was: 1.2) Dynamically load jars from the WEB-INF/lib directory Key: GERONIMO-1842 URL: http://issues.apache.org/jira/browse/GERONIMO-1842 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: core Reporter: Prasad Kashyap Fix For: 1.x, 2.0 Currently the server has a hardcoded list of what it expects in the WEB-INF/lib dir. This means that additions/deletion of jars in that directory will not be picked up without actually redeploying that app. This seems like a major irritant. The best thing of course would be to dynamically pick up or drop jars from the lib directory as they are added/deleted. But we can, for now, settle for loading/unloading them at an app restart. This should be the bare minimum requirement. -- 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-1980) Move Plugin Installer from rmi-naming to j2ee-system
[ http://issues.apache.org/jira/browse/GERONIMO-1980?page=all ] Vamsavardhana Reddy updated GERONIMO-1980: -- Fix Version/s: 1.x 2.0 (was: 1.2) Move Plugin Installer from rmi-naming to j2ee-system Key: GERONIMO-1980 URL: http://issues.apache.org/jira/browse/GERONIMO-1980 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem, Plugins Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x, 2.0 Ideally, the plugin installer will be as high in the food chain as possible, so it can replace as much as possible without shutting itself down. Currently it is in rmi-naming. I tried moving it to j2ee-system, which requires the following new dependencies for j2ee-system: - geronimo-core - geronimo-management - geronimo-util - geronimo-j2ee-management_1.0_spec - concurrent Somehow, the net result of this was that the OpenEJB config could not load javax.ejb.EJBObject, so there's something funky going on with the class loaders when the above changes are made. -- 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-2028) Plugin export errors don't stop process, but cause it to fail much later
[ http://issues.apache.org/jira/browse/GERONIMO-2028?page=all ] Vamsavardhana Reddy updated GERONIMO-2028: -- Fix Version/s: 1.x 2.0 (was: 1.2) Plugin export errors don't stop process, but cause it to fail much later Key: GERONIMO-2028 URL: http://issues.apache.org/jira/browse/GERONIMO-2028 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x, 2.0 When exporting a plugin, if there are any errors loading the existing XML document, the console goes on to the export screen and just renders it entirely empty (including the module ID). It should instead produce an error message. To reproduce, edit repository/geronimo/welcome-jetty/1.1-SNAPSHOT/welcome-jetty-1.1-SNAPSHOT.car/META-INF/geronimo-plugin.xml to make it invalid, go to the console, select the plugins screen, pick geronimo/welcome-jetty/* as the configuration to export, and click the export button. You presently get a screen with a bunch of blank text fields, and should instead get an error message / 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] Updated: (GERONIMO-2045) Plugin prerequisites: for DB pools, support DB type/version and table validation
[ http://issues.apache.org/jira/browse/GERONIMO-2045?page=all ] Vamsavardhana Reddy updated GERONIMO-2045: -- Fix Version/s: 1.x 2.0 (was: 1.2) Plugin prerequisites: for DB pools, support DB type/version and table validation Key: GERONIMO-2045 URL: http://issues.apache.org/jira/browse/GERONIMO-2045 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x, 2.0 More robust database pool prerequisites for plugins: - check that one of a specific set of RDBMS name/version combinations is set for a connection pool prerequisite - check the schema somehow -- e.g. that some table exists, or some query returns an expected value -- 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-2128) Allow user to specify the Isolation Level for a CMP bean's SQL access
[ http://issues.apache.org/jira/browse/GERONIMO-2128?page=all ] Vamsavardhana Reddy updated GERONIMO-2128: -- Fix Version/s: 1.x 2.0 (was: 1.2) Allow user to specify the Isolation Level for a CMP bean's SQL access - Key: GERONIMO-2128 URL: http://issues.apache.org/jira/browse/GERONIMO-2128 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Reporter: Matt Hogstrom Fix For: 1.x, 2.0 Currently CMP beans all execute in the default isolation level of the datasource. This means that in many situations higher level locks are required for the database access than are required. This improvement will allow the user to specify a new attribute on a CMP entity bean isolation-level that will be the isolation level used for database access on this entity bean. This will require updates to OpenEJB and TranQL. -- 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-2127) Expose the ability to use Select for Update on CMP entity beans
[ http://issues.apache.org/jira/browse/GERONIMO-2127?page=all ] Vamsavardhana Reddy updated GERONIMO-2127: -- Fix Version/s: 1.x 2.0 (was: 1.2) Expose the ability to use Select for Update on CMP entity beans --- Key: GERONIMO-2127 URL: http://issues.apache.org/jira/browse/GERONIMO-2127 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Environment: All Reporter: Matt Hogstrom Fix For: 1.x, 2.0 Currently TranQL supports the generation sql to execute a select for update. Unfortunately, OpenEJB does not expose the ability in the current XSD to support this. As a result the CMP implementation we have does pass CTS but lacks the ability to deploy an application that is performant and provides for data consistency. This improvement will add an attribute into the XSD for OpenEJB so a new attribute will be added select-for-update that is an indicator to use a select for update on a query so database locking can be employed. Changes will be made to TranQL (Syntax Factories) to create the correct SQL as well as OpenEJB's CMP builders to honor the request. -- 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-2286) app client plan still uses Strings for dependency Module IDs
[ http://issues.apache.org/jira/browse/GERONIMO-2286?page=all ] Vamsavardhana Reddy updated GERONIMO-2286: -- Fix Version/s: 1.x 2.0 (was: 1.2) app client plan still uses Strings for dependency Module IDs Key: GERONIMO-2286 URL: http://issues.apache.org/jira/browse/GERONIMO-2286 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: application client, deployment Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x, 2.0 The geronimo-application-client schema has: xs:complexType name=resourceType xs:sequence xs:choice xs:element name=external-rar type=xs:string/ xs:element name=internal-rar type=xs:string/ /xs:choice xs:element ref=connector:connector/ /xs:sequence /xs:complexType That would typically be used like this: resource external-rartranql/tranql-connector/1.2/rar/external-rar connector ... /resource Everywhere else we've changed elements holding module IDs to be of patternType, using separate groupId, artifactId, version, and type elements. There's no reason external-rar should still be a single slash-delimited String here (though internal-rar should be since it's presumably a path within the 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] Updated: (GERONIMO-2387) Server life cycle log entries should be generated by the server
[ http://issues.apache.org/jira/browse/GERONIMO-2387?page=all ] Vamsavardhana Reddy updated GERONIMO-2387: -- Fix Version/s: 2.0 Server life cycle log entries should be generated by the server --- Key: GERONIMO-2387 URL: http://issues.apache.org/jira/browse/GERONIMO-2387 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 1.2, 1.1.2, 2.0 By default, geronimo should generate life cycle log entries. For example: 1) starting with environmental information 2) started 3) stopping -- 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-2399) Support both jetty 5 and jetty 6
[ http://issues.apache.org/jira/browse/GERONIMO-2399?page=all ] Vamsavardhana Reddy updated GERONIMO-2399: -- Fix Version/s: 1.x 2.0 (was: 1.2) Support both jetty 5 and jetty 6 Key: GERONIMO-2399 URL: http://issues.apache.org/jira/browse/GERONIMO-2399 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Jetty Affects Versions: 1.2 Reporter: David Jencks Fix For: 1.x, 2.0 For a while I think we're going to want to support both jetty 5 and jetty 6. In order to support this I suggest we rename trunk geronimo-jetty and geronimo-jetty-builder to geronimo-jetty5 and geronimo-jetty5-builder and similarly for the configs and rename the similar modules in sandbox/servlet2.5 geronimo-jetty6 and geronimo-jetty6-builder. I would like to get the proposed geronimo-jetty6* modules into trunk as soon as possible: I suggest the default profile does not build them but we have an additional profile that does. I realize there are issues with jee5 schema support that will require additional work to resolve: I'm planning to look into this. Jan has obviously made a big start in the servlet2.5 branch. -- 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-2411) CAR, WAR and EAR artifacts are missing NOTICE and LICENSE files.
[ http://issues.apache.org/jira/browse/GERONIMO-2411?page=all ] Vamsavardhana Reddy updated GERONIMO-2411: -- Fix Version/s: 2.0 CAR, WAR and EAR artifacts are missing NOTICE and LICENSE files. Key: GERONIMO-2411 URL: http://issues.apache.org/jira/browse/GERONIMO-2411 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.0, 1.2, 1.x, 1.1, 1.1.1, 1.1.x, 1.1.2 Reporter: Matt Hogstrom Fix For: 2.0, 1.2 For release of these artifacts they need to include the LICENSE and NOTICE files. Currently the build does not automatically include them. The M2 build needs to be updated to include these artifacts in the build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2424) Add config.xml support for ConfigurationAwareReference
[ http://issues.apache.org/jira/browse/GERONIMO-2424?page=all ] Vamsavardhana Reddy updated GERONIMO-2424: -- Fix Version/s: 1.x 2.0 (was: 1.2) Add config.xml support for ConfigurationAwareReference -- Key: GERONIMO-2424 URL: http://issues.apache.org/jira/browse/GERONIMO-2424 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: common, kernel, naming Affects Versions: 1.1.1 Reporter: Aaron Mulder Fix For: 1.x, 2.0 It would be nice if a GBean property of type ConfigurationAwareReference could be overridden in config.xml. This seems reasonable in that a ConfigurationAwareReference essentially holds an Artifact and a set of AbstractNameQueries, both of which are independently representable as Strings. Presently it looks like there's a PropertyEditor for AbstractNameQuery but not for Artifact or ConfigurationAwareReference. Not sure what XML editors might be available. (This is because some plugin gbeans use properties of type ConfigurationAwareReference to refer to e.g. a database connection pool, where the pool name was configured in some XML file processed by the plugin's deployer component.) -- 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-2489) Client builder bug is blocking usage of Daytrader AppClient
[ http://issues.apache.org/jira/browse/GERONIMO-2489?page=all ] Vamsavardhana Reddy updated GERONIMO-2489: -- Fix Version/s: 2.0 Client builder bug is blocking usage of Daytrader AppClient --- Key: GERONIMO-2489 URL: http://issues.apache.org/jira/browse/GERONIMO-2489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: application client Affects Versions: 1.1.1, 1.1 Reporter: Donald Woods Fix For: 2.0, 1.1.2, 1.2 Attachments: G2489-1.1.1.patch If you try to use the Daytrader app client, the following exception is thrown: java -jar client.jar wasce-samples/daytrader-derby-tomcat_streamer.jar/1.1/car 16:10:19,562 INFO [Log4jService] -- 16:10:19,562 INFO [Log4jService] Started Logging Service 16:10:22,484 WARN [RMIRegistryService] RMI Registry failed 16:10:22,500 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: abstractName=geronimo/rmi-naming/1.1/car?ServiceModule=geronimo /rmi-naming/1.1/car,j2eeType=GBean,name=RMIRegistry java.rmi.server.ExportException: Port already in use: 1099; nested exception is: java.net.BindException: Address already in use: NET_Bind at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:284) at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:219 ) at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:398) at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:131) at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:19 5) at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:107) at sun.rmi.registry.RegistryImpl.init(RegistryImpl.java:93) at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:1 98) at org.apache.geronimo.system.rmi.RMIRegistryService.doStart(RMIRegistry Service.java:58) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:374) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke rnelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:527) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:508) 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.gbean.GBeanLifecycle$$EnhancerByCGLIB$$ec0bda8e.s tartConfiguration(generated) at org.apache.geronimo.system.main.CommandLine.loadConfigurations(Comman dLine.java:167) at org.apache.geronimo.system.main.CommandLine.invokeMainGBean(CommandLi ne.java:92) at org.apache.geronimo.system.main.ClientCommandLine.init(ClientComman dLine.java:79) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:49) Caused by: java.net.BindException: Address already in use: NET_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398) at java.net.ServerSocket.bind(ServerSocket.java:331) at java.net.ServerSocket.init(ServerSocket.java:197) at
[jira] Updated: (GERONIMO-2493) Integrate Axis2 webservices
[ http://issues.apache.org/jira/browse/GERONIMO-2493?page=all ] Vamsavardhana Reddy updated GERONIMO-2493: -- Fix Version/s: 2.0 Integrate Axis2 webservices --- Key: GERONIMO-2493 URL: http://issues.apache.org/jira/browse/GERONIMO-2493 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Affects Versions: 1.2 Reporter: David Jencks Fix For: 1.2, 2.0 Integrate axis 2 for webservices. Probably at least 3 steps - pojo ws - ejb ws - ws client -- 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-2534) Security realms portlet should validate the realm-name for duplicate name
[ http://issues.apache.org/jira/browse/GERONIMO-2534?page=all ] Vamsavardhana Reddy updated GERONIMO-2534: -- Fix Version/s: 1.x 2.0 (was: 1.2) Security realms portlet should validate the realm-name for duplicate name - Key: GERONIMO-2534 URL: http://issues.apache.org/jira/browse/GERONIMO-2534 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.x, 2.0 Add new security realm function does not check if the realm-name entered by the user is already in use. There are no errors shown in the console, whereas the following error is logged: 18:32:12,033 ERROR [ProxyCollection] Listener threw exception java.lang.IllegalArgumentException: ConfigurationEntry already registered at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.addConfi guration(GeronimoLoginConfiguration.java:115) at org.apache.geronimo.security.jaas.GeronimoLoginConfiguration.memberAd ded(GeronimoLoginConfiguration.java:96) at org.apache.geronimo.gbean.runtime.ProxyCollection.addTarget(ProxyColl ection.java:102) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.targetAdde d(GBeanCollectionReference.java:96) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference.addTarget( GBeanCollectionReference.java:180) at org.apache.geronimo.gbean.runtime.GBeanCollectionReference$1.running( GBeanCollectionReference.java:110) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:526) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GB eanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepe ndency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepe ndency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:526) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GB eanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepe ndency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepe ndency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:374) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke rnelConfigurationManager.java:187) at
[jira] Closed: (GERONIMO-2547) Java source files still using group-id geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-2547?page=all ] Vamsavardhana Reddy closed GERONIMO-2547. - Resolution: Fixed Java source files still using group-id geronimo - Key: GERONIMO-2547 URL: http://issues.apache.org/jira/browse/GERONIMO-2547 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector, console Affects Versions: 1.2 Environment: geronimo-tomcat-j2ee-1.2-r470164 etc. Reporter: Vamsavardhana Reddy Fix For: 1.2 Some java source files are still using group-id geronimo in place of org.apache.geronimo.configs. A search for setGroupId(geronimo) yielded two results... SecurityRealmPortlet, Connector15DCBTest. There may be more using this group-id indirectly. -- 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-2549) NullPointerException: CommandListConfigurations
[ http://issues.apache.org/jira/browse/GERONIMO-2549?page=all ] Vamsavardhana Reddy updated GERONIMO-2549: -- Fix Version/s: 2.0 NullPointerException: CommandListConfigurations --- Key: GERONIMO-2549 URL: http://issues.apache.org/jira/browse/GERONIMO-2549 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.2 Environment: windows xp Reporter: Mark DeLaFranier Fix For: 1.2, 2.0 Attachments: GERONIMO-2549.patch deploy.bat search-plugins http://bogus-server/maven2 Using GERONIMO_BASE: D:\geronimo\1.2 Using GERONIMO_HOME: D:\geronimo\1.2 Using GERONIMO_TMPDIR: D:\geronimo\1.2\var\temp Using JRE_HOME:d:\dev\jdk142 Username: system Password: *** Exception in thread main java.lang.NullPointerException at org.apache.geronimo.deployment.cli.CommandListConfigurations.execute(CommandListConfigurations.java:84) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:160) at org.apache.geronimo.deployment.cli.DeployTool.main(DeployTool.java:314) -- 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-2551) Plugin hits NPE if maven-metadata listed artifact doesn't exist or JAR artifact maven-metadata doesn't exist
[ http://issues.apache.org/jira/browse/GERONIMO-2551?page=all ] Vamsavardhana Reddy updated GERONIMO-2551: -- Fix Version/s: 2.0 Plugin hits NPE if maven-metadata listed artifact doesn't exist or JAR artifact maven-metadata doesn't exist Key: GERONIMO-2551 URL: http://issues.apache.org/jira/browse/GERONIMO-2551 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1.1, 1.1.x, 1.2 Reporter: Donald Woods Fix For: 1.2, 2.0 Attachments: G2551-1.1.1.patch 1) If an artifact version listed in a repos maven-metadata.xml doesn't exist, then the PluginInstallerGBean code takes a NPE. 2) If a maven-metadat.xml doesn't exist for a dependent JAR file artifact the selected repo, then the PluginInstallerGBean code takes a NPE. -- 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-2555) Windows scripts don't work when used from different drive
[ http://issues.apache.org/jira/browse/GERONIMO-2555?page=all ] Vamsavardhana Reddy updated GERONIMO-2555: -- Fix Version/s: 2.0 Windows scripts don't work when used from different drive - Key: GERONIMO-2555 URL: http://issues.apache.org/jira/browse/GERONIMO-2555 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: general Affects Versions: 1.2, 1.1.2 Environment: Windows XP Reporter: Mark DeLaFranier Fix For: 1.1.2, 1.2, 2.0 Attachments: GERONIMO-2555.patch If the scripts: geronimo.bat, startup.bat, shutdown.bat, deploy.bat are launched from a drive other than the one Geronimo is located the cd portions do not work when trying to determine the script location. In order for a cross drive CD to work, the /d option must be used. -- 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-2559) cannot stop activemq via kernel shutdown
[ http://issues.apache.org/jira/browse/GERONIMO-2559?page=all ] Vamsavardhana Reddy updated GERONIMO-2559: -- Fix Version/s: 2.0 cannot stop activemq via kernel shutdown Key: GERONIMO-2559 URL: http://issues.apache.org/jira/browse/GERONIMO-2559 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 1.2 Environment: sun j2se 1.5.0_07 Reporter: Paul McMahan Fix For: 1.2, 2.0 Shutdown the server from the admin console. This ends up invoking kernel.shutdown(). The following stack trace is generated: 11:59:25,265 ERROR [JournalPersistenceAdapter] Could not stop service: org.apach [EMAIL PROTECTED] Reason: java.lang.Nul lPointerException java.lang.NullPointerException at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT rackingCoordinator.handleReleased(ConnectionTrackingCoordinator.java:127) at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT rackingCoordinator$$FastClassByCGLIB$$5d33aabf.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:820) 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:97) at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT racker$$EnhancerByCGLIB$$c20afa50.handleReleased(generated) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor. returnConnection(ConnectionTrackingInterceptor.java:81) at org.apache.geronimo.connector.outbound.GeronimoConnectionEventListene r.connectionClosed(GeronimoConnectionEventListener.java:67) at org.tranql.connector.AbstractManagedConnection.connectionClosed(Abstr actManagedConnection.java:102) at org.tranql.connector.jdbc.ConnectionHandle.close(ConnectionHandle.jav a:97) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultData baseLocker.java:81) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersis tenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(Jour nalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop(BrokerService GBeanImpl.java:107) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBean Instance.java:1146) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop( GBeanInstanceState.java:337) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$Shutdown Hook.run(KernelConfigurationManager.java:310) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(Basi cKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.jav a:645) at org.apache.geronimo.console.servermanager.ServerManagerPortlet.doView (ServerManagerPortlet.java:72) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218 ) at
[jira] Commented: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=comments#action_12456392 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-118: -- 1) Updations to Deployment tab: Deployment tab will now have an additional section called Class Loader Settings for specifying sys:hidden-classes and sys:non-overridable-classes sub-elements of sys:environment in geronimo-web.xml. Snapshot-1a.gif Snapshot-1b.gif demonstrates this. 2) Updations to Dependencies section: The wizard that comes up when Add or Edit button in Dependencies section is clicked, is updated to include sys:import sub-element of sys:dependency. Also Artifact Type is now a combo list. Snapshot-2a.gif, Snapshot-2b.gif Snapshot-2c.gif demonstrate this. 3) Updations to GBean References section: The wizard that comes up when Add or Edit button in GBean References section is clicked, is updated to support multiple ref-type elements and utmost one pattern element. Snapshot-3a.gif, Snapshot-3b.gif Snapshot-3c.gif demonstrate this. Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMO-2560) Realm added using SecurityRealm portlet does not work
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=all ] Vamsavardhana Reddy updated GERONIMO-2560: -- Fix Version/s: 2.0 Affects Version/s: 2.0 Priority: Critical (was: Major) Realm added using SecurityRealm portlet does not work - Key: GERONIMO-2560 URL: http://issues.apache.org/jira/browse/GERONIMO-2560 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 1.2, 2.0 Reporter: Vamsavardhana Reddy Priority: Critical Fix For: 1.2, 2.0 A new security realm added using SecurityRealm portlet does not get listed in the portlet. There are no deployment errors. Also, if an application is configured to authenticate against this realm, login is failing since the realm could not be found. The deployment plan for security realms generated in the console seems to use a service tag in place of gbean tag. If the service tag is changed to gbean tag, the realm is getting listed in the SecurityRealm portlet. -- 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-1786) JMS Listeners for protocols activeio, peer and openwire fail to start
[ http://issues.apache.org/jira/browse/GERONIMO-1786?page=all ] Vamsavardhana Reddy updated GERONIMO-1786: -- Fix Version/s: 2.0 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, 2.0 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 org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) 224: at
[jira] Updated: (GERONIMO-2613) Some portlets in the console can't size correctly
[ http://issues.apache.org/jira/browse/GERONIMO-2613?page=all ] Vamsavardhana Reddy updated GERONIMO-2613: -- Fix Version/s: 2.0 Some portlets in the console can't size correctly - Key: GERONIMO-2613 URL: http://issues.apache.org/jira/browse/GERONIMO-2613 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Environment: this is for revision r480769 Reporter: Hernan Cunico Fix For: 1.2, 2.0 Here is a list of portlets I saw having rendering problems. JMS Server Manager (uses just 50% of the available space) Installed Web Applications (does not wrap up, have to scroll sideways) Installed J2EE Connectors (does not wrap up, have to scroll sideways) Installed System Modules (does not wrap up, have to scroll sideways) Console Realm, both Console Realm Users and Console Realm Groups (uses just 50% of the available space) -- 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-2584) Hot deploy module/server restart, throws IllegalArgumentException if application deployed using hotdeployment
[ http://issues.apache.org/jira/browse/GERONIMO-2584?page=all ] Vamsavardhana Reddy updated GERONIMO-2584: -- Fix Version/s: 2.0 Hot deploy module/server restart, throws IllegalArgumentException if application deployed using hotdeployment - Key: GERONIMO-2584 URL: http://issues.apache.org/jira/browse/GERONIMO-2584 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Hot Deploy Dir Affects Versions: 1.2 Environment: Windows XP, but should be valid for all platforms Reporter: Rakesh Midha Fix For: 1.2, 2.0 Attachments: hotdepoystartup.patch This is a problem similar to one reported in https://issues.apache.org/jira/browse/GERONIMO-2402, the server restart or hot-deploy module restart fails with followng error if in a previous run you deployed an application using hot deployment. The exception trace is : 00:54:43,008 ERROR [DirectoryMonitor] Unable to scan file C:\geronimo\geronimobu ild\geronimo-tomcat-j2ee-1.2-SNAPSHOT\deploy\sampleHello during initialization java.lang.IllegalArgumentException: Invalid id: sampleHello at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:4 9) at org.apache.geronimo.deployment.hot.DirectoryHotDeployer.getDeployment Time(DirectoryHotDeployer.java:216) at org.apache.geronimo.deployment.hot.DirectoryMonitor.initialize(Direct oryMonitor.java:233) at org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMoni tor.java:206) at java.lang.Thread.run(Thread.java:534) 00:54:47,014 INFO [DirectoryHotDeployer] Deploying sampleHello 00:54:51,350 WARN [TomcatModuleBuilder] Web application . does not contain a WE B-INF/geronimo-web.xml deployment plan. This may or may not be a problem, depen ding on whether you have things like resource references that need to be resolve d. You can also give the deployer a separate deployment plan file on the comman d line. 00:54:51,841 ERROR [GBeanInstance] Problem in doFail of default/sampleHello/1163 964291070/war?J2EEApplication=null,j2eeType=WebModule,name=default/sampleHello/1 163964291070/war java.lang.RuntimeException: java.lang.NullPointerException at org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContai ner.java:339) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b07 3.invoke(generated) ... 31 more 00:54:51,841 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: abstractName=default/sampleHello/1163964291070/war?J2EEApplicat ion=null,j2eeType=WebModule,name=default/sampleHello/1163964291070/war java.lang.IllegalArgumentException: addChild: Child name '/sampleHello' is not unique at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase .java:749) Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuratio n default/sampleHello/1163964291070/war failed to start due to the following rea sons: The service J2EEApplication=null,j2eeType=WebModule,name=default/sampleHello/1 163964291070/war did not start because the doStart method threw an exception. java.lang.IllegalArgumentException: addChild: Child name '/sampleHello' is not unique at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase .java:749) Steps to recreate: 1. Start server 2. Deploy sample application, by placing sampleApp folder in deploy directory 3. Application will be deployed and runs fine. 4. Restart server, or restart hot-deploy module 5. The above mentioned exception is thrown. -- 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: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-1a.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-1b.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-2a.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-2b.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-3a.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif, Snapshot-3a.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-2c.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-3b.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif, Snapshot-3a.gif, Snapshot-3b.gif, Snapshot-3c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: Snapshot-3c.gif Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif, Snapshot-3a.gif, Snapshot-3b.gif, Snapshot-3c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMO-2377) deploying a new datasource with the same name does not indicate any problem in the console
[ http://issues.apache.org/jira/browse/GERONIMO-2377?page=all ] Vamsavardhana Reddy updated GERONIMO-2377: -- Fix Version/s: 2.0 deploying a new datasource with the same name does not indicate any problem in the console -- Key: GERONIMO-2377 URL: http://issues.apache.org/jira/browse/GERONIMO-2377 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Reporter: Bill Dudney Assigned To: Bill Dudney Fix For: 1.2, 2.0 Attachments: GERONIMO-2377.bdudney.patch Console acts as if it deployeed the datasource but the console spits out an error message; Deployer operation failed: Module console.dbpool/DefaultDS/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module console.dbpool/DefaultDS/1.0/rar already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.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:855) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:106) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:60) at java.lang.Thread.run(Thread.java:552) -- 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-2533) Password setup forms should use a confirmation field
[ http://issues.apache.org/jira/browse/GERONIMO-2533?page=all ] Vamsavardhana Reddy closed GERONIMO-2533. - Resolution: Fixed Password setup forms should use a confirmation field Key: GERONIMO-2533 URL: http://issues.apache.org/jira/browse/GERONIMO-2533 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Assigned To: Vamsavardhana Reddy Fix For: 1.2, 2.0 Some of the functions in admin console (For e.g., in keystores portlet, create new keystore page has a password field) require the user to setup a password. These pages should use a confirm field and validate that the user enters the same input in password and confirm fields. Without this, the users will not know if they have setup a different password than the one they intended to use. -- 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: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Attachment: GERONIMODEVTOOLS-118.patch Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Shiva Kumar H R Attachments: GERONIMODEVTOOLS-118.patch, Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif, Snapshot-3a.gif, Snapshot-3b.gif, Snapshot-3c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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] Updated: (GERONIMODEVTOOLS-118) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-118: - Patch Info: [Patch Available] Assignee: Sachin Patel (was: Shiva Kumar H R) Complete Editor Support for specifying Dependencies, Hidden Classes, Non Overridable Classes GBean References in geronimo-web.xml --- Key: GERONIMODEVTOOLS-118 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-118 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Attachments: GERONIMODEVTOOLS-118.patch, Snapshot-1a.gif, Snapshot-1b.gif, Snapshot-2a.gif, Snapshot-2b.gif, Snapshot-2c.gif, Snapshot-3a.gif, Snapshot-3b.gif, Snapshot-3c.gif Please see the discussion going on about this at dev@geronimo.apache.org mailing list: http://www.mail-archive.com/dev@geronimo.apache.org/msg35865.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
Re: CMP failures in 2.3 (was: Openjeb itests - 552 tests, 2 failures, 2 errors)
On 07/12/2006, at 11:10 AM, David Blevins wrote: On Dec 6, 2006, at 12:38 PM, Prasad Kashyap wrote: We are now down to just 2 failures and 2 errors on the Openejb-2.3 itests. The stack trace is here -- http://rifers.org/paste/show/ 2622 org.apache.openejb.test.TestFailureException : null; nested exception is: junit.framework.AssertionFailedError: Should have thrown DuplicateKeyException at junit.framework.Assert.fail(Assert.java:47) at org.apache.openejb.test.entity.cmp.CmpTransactionTests.testInvokeCreat eCreateSameCMP(CmpTransactionTests.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Transaction.testInvokeCreateFindForceCacheFlush Time elapsed: 0.32 sec FAILURE! junit.framework.AssertionFailedError: Received Exception class org.apache.openejb.test.TestFailureException : null; nested exception is: junit.framework.AssertionFailedError: expected:1 but was:0 at junit.framework.Assert.fail(Assert.java:47) at org.apache.openejb.test.entity.cmp.CmpTransactionTests.testInvokeCreat eFindForceCacheFlush(CmpTransactionTests.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Hi David, Sorry for not pro-actively helping (hope to be back to OEJB after some WADI stuff). I debugged the two above tests and identified the issue: an automatic pk generation were wrongly configured for the CMP BasicCmpBeanExplicitPK. This causes at least the two above failures. It seems that something is wrong with my build as I observe weird JNDI lookup problems and I am not sure that dropping the key- generator element does not impact other tests. So, Prasad, could you please do me favor and drop this element for BasicCmpBeanExplicitPK and re-execute? Meanwhile, I will try to fix my build. Thanks, Gianny CMRMappingTests.testOneToManyDoNotSetCMR Time elapsed: 0.26 sec ERROR! org.apache.openejb.test.TestFailureException: null; nested exception is: junit.framework.AssertionFailedError: Received Exception class javax.transaction.RollbackException : Unable to commit: transaction marked for rollback at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean.te stOneToManyDoNotSetCMR(CMRMappingFacadeBean.java:245) at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean$ $FastClassByCGLIB$$9687c6d6.invoke(generated) at org.apache.openejb.dispatch.AbstractMethodOperation.invoke (AbstractMethodOperation.java:58) at org.apache.openejb.slsb.BusinessMethod.execute (BusinessMethod.java:36) CMRMappingTests.testOneToOneDoNotSetCMR Time elapsed: 0.06 sec ERROR! org.apache.openejb.test.TestFailureException: null; nested exception is: junit.framework.AssertionFailedError: Received Exception class javax.transaction.RollbackException : Unable to commit: transaction marked for rollback at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean.te stOneToOneDoNotSetCMR(CMRMappingFacadeBean.java:137) at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean$ $FastClassByCGLIB$$9687c6d6.invoke(generated) at org.apache.openejb.dispatch.AbstractMethodOperation.invoke (AbstractMethodOperation.java:58) at org.apache.openejb.slsb.BusinessMethod.execute (BusinessMethod.java:36) Nothing is jumping out at me. Gianny, you have any ideas? -David
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
+1 Thanks Anita ... although I think the shorter tomcat6 is perfectly clear and easier to type. Other stuff: axis axis1 cxf cxf1 openjpa openjpa1 I think this will really reduce confusion about what is running in a server. So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. Can we discuss and settle this soon? thanks david jencks Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com
Re: How to build devtools/eclipse-plugin?
That would be really good if you could do that. A mvn install at the root will pull down everything you need and generate the assemblies. On Dec 6, 2006, at 6:31 PM, Jason Dillon wrote: Is there any special requirements to build this puppy? Does Eclipse need to be installed or something? I'm asking first... have not actually tried yet... but would like to hook this up to automatically build if possible. --jason -sachin
Re: svn commit: r483063 - in /geronimo/server/trunk: ./ assemblies/geronimo-boilerplate-minimal/ configs/client-system/ configs/j2ee-system/ configs/online-deployer/ configs/upgrade-cli/ maven-plugins
interesting... I use win xp and sun jdk, and have a fully functional
console with jetty6 server Revision: 483117. Now I always start the
server using bin\startup.
thanks
Anita
--- Joe Bohn [EMAIL PROTECTED] wrote:
I think this may have removed a bit too much :-)
Now, when attempting to use the Web Console for any of the servers in
trunk we get a NoClassDefFoundError for a xerces class when we hit
the
console welcome page. Paul avoided this on the tomcat 6 work by
adding
a dependency in config\tomcat(6) on xercesImpl. I've verified that
this
works for jetty too. I'll go ahead and check that change in for
jetty
jetty6 (Paul is already covering tomcat with his checkin).
Joe
[EMAIL PROTECTED] wrote:
Author: akulshreshtha
Date: Wed Dec 6 05:05:35 2006
New Revision: 483063
URL: http://svn.apache.org/viewvc?view=revrev=483063
Log:
Upgrade xerces to 2.8.1, GERONIMO-2594 Remove xmlParserApis and
xalan
Remove xerces from everywhere except console
Modified:
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml
geronimo/server/trunk/configs/client-system/pom.xml
geronimo/server/trunk/configs/j2ee-system/pom.xml
geronimo/server/trunk/configs/online-deployer/pom.xml
geronimo/server/trunk/configs/upgrade-cli/pom.xml
geronimo/server/trunk/maven-plugins/car-maven-plugin/pom.xml
geronimo/server/trunk/modules/geronimo-system/pom.xml
geronimo/server/trunk/pom.xml
Modified:
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml?view=diffrev=483063r1=483062r2=483063
==
---
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml
(original)
+++
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml
Wed Dec 6 05:05:35 2006
@@ -156,16 +156,6 @@
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
/artifactItem
-
-artifactItem
-groupIdxerces/groupId
-
artifactIdxmlParserAPIs/artifactId
-/artifactItem
-
-artifactItem
-groupIdxalan/groupId
-artifactIdxalan/artifactId
-/artifactItem
/artifactItems
outputDirectory${project.build.directory}/classes/lib/endorsed/outputDirectory
/configuration
Modified: geronimo/server/trunk/configs/client-system/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/client-system/pom.xml?view=diffrev=483063r1=483062r2=483063
==
--- geronimo/server/trunk/configs/client-system/pom.xml (original)
+++ geronimo/server/trunk/configs/client-system/pom.xml Wed Dec 6
05:05:35 2006
@@ -47,16 +47,6 @@
artifactIdgeronimo-j2ee-management_1.0_spec/artifactId
/dependency
-dependency
-groupIdxerces/groupId
-artifactIdxercesImpl/artifactId
-/dependency
-
-dependency
-groupIdxerces/groupId
-artifactIdxmlParserAPIs/artifactId
-/dependency
-
/dependencies
build
@@ -142,16 +132,6 @@
element
groupIdxstream/groupId
artifactIdxstream/artifactId
-/element
-element
-groupIdxerces/groupId
-artifactIdxercesImpl/artifactId
-
classpathPrefix../lib/endorsed/classpathPrefix
-/element
-element
-groupIdxerces/groupId
-artifactIdxmlParserAPIs/artifactId
-
classpathPrefix../lib/endorsed/classpathPrefix
/element
/classpath
classpathPrefix../lib/classpathPrefix
Modified: geronimo/server/trunk/configs/j2ee-system/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/j2ee-system/pom.xml?view=diffrev=483063r1=483062r2=483063
==
--- geronimo/server/trunk/configs/j2ee-system/pom.xml (original)
+++ geronimo/server/trunk/configs/j2ee-system/pom.xml Wed Dec 6
[jira] Created: (GERONIMODEVTOOLS-120) Refinements to the Web Container section of Deployment Plan Editors
Refinements to the Web Container section of Deployment Plan Editors - Key: GERONIMODEVTOOLS-120 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: Snapshot-1.gif GUI for Web Container section in General tab is updated as shown in Snapshot1.gif and Snapshot2.gif . When Specify as GBean Link radio button is chosen, the section will only ask for GBean Link. And when Specify as GBean Pattern radio button is chosen, it will only ask for the sub-elements of pattern element. -- 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: (GERONIMODEVTOOLS-120) Refinements to the Web Container section of Deployment Plan Editors
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-120: - Attachment: Snapshot-1.gif Refinements to the Web Container section of Deployment Plan Editors - Key: GERONIMODEVTOOLS-120 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: Snapshot-1.gif GUI for Web Container section in General tab is updated as shown in Snapshot1.gif and Snapshot2.gif . When Specify as GBean Link radio button is chosen, the section will only ask for GBean Link. And when Specify as GBean Pattern radio button is chosen, it will only ask for the sub-elements of pattern element. -- 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: (GERONIMODEVTOOLS-120) Refinements to the Web Container section of Deployment Plan Editors
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-120: - Attachment: Snapshot-2.gif Refinements to the Web Container section of Deployment Plan Editors - Key: GERONIMODEVTOOLS-120 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: GERONIMODEVTOOLS-120.patch, Snapshot-1.gif, Snapshot-2.gif GUI for Web Container section in General tab is updated as shown in Snapshot1.gif and Snapshot2.gif . When Specify as GBean Link radio button is chosen, the section will only ask for GBean Link. And when Specify as GBean Pattern radio button is chosen, it will only ask for the sub-elements of pattern element. -- 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: (GERONIMODEVTOOLS-120) Refinements to the Web Container section of Deployment Plan Editors
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-120: - Attachment: GERONIMODEVTOOLS-120.patch Refinements to the Web Container section of Deployment Plan Editors - Key: GERONIMODEVTOOLS-120 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-120 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: GERONIMODEVTOOLS-120.patch, Snapshot-1.gif, Snapshot-2.gif GUI for Web Container section in General tab is updated as shown in Snapshot1.gif and Snapshot2.gif . When Specify as GBean Link radio button is chosen, the section will only ask for GBean Link. And when Specify as GBean Pattern radio button is chosen, it will only ask for the sub-elements of pattern element. -- 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
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
On 12/6/06, David Jencks [EMAIL PROTECTED] wrote: So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. I'll make this change right away, also using geronimo-tomcat6-jee5 and geronimo-tomcat6-minimal for the assemblies as well (unless you omitted them intentionally). Best wishes, Paul
[jira] Created: (GERONIMODEVTOOLS-121) Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors
Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors - Key: GERONIMODEVTOOLS-121 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-121 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Can't appreciate the significance of the check box button for Add a runtime dependency to Geronimo's shared library in the General tab of Deployment Plan Editors. Is it very important to keep it? If not let's remove it to save some screen space on the General tab of Deployment Plan Editors. -- 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: (GERONIMODEVTOOLS-121) Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-121?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-121: - Attachment: GERONIMODEVTOOLS-121.patch Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors - Key: GERONIMODEVTOOLS-121 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-121 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: GERONIMODEVTOOLS-121.patch Can't appreciate the significance of the check box button for Add a runtime dependency to Geronimo's shared library in the General tab of Deployment Plan Editors. Is it very important to keep it? If not let's remove it to save some screen space on the General tab of Deployment Plan Editors. -- 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-2636) Update Jetty 6 assembly to use Jasper 6 for JSP 2.1 support
Update Jetty 6 assembly to use Jasper 6 for JSP 2.1 support --- Key: GERONIMO-2636 URL: http://issues.apache.org/jira/browse/GERONIMO-2636 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Reporter: Joe Bohn Assigned To: Joe Bohn The Jetty 6 assembly is currently still using JSP 2.0 provided by tomcat jasper 5.5.15. We need JSP 2.1 support for Jave EE 5 and one quick way to get this is to just use the support provided by the next level of Jasper in tomcat 6. We can still investigate converting over to the Jetty JSP 2.1 support provided in Jetty 6 this is just to get some JSP 2.1 support in quickly. -- 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: (GERONIMODEVTOOLS-121) Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-121?page=all ] Sachin Patel closed GERONIMODEVTOOLS-121. - Resolution: Won't Fix This is needed, and was a feature request. Remove the check box button for Add a runtime dependency to Geronimo's shared library from the General tab of Deployment Plan Editors - Key: GERONIMODEVTOOLS-121 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-121 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 1.x Reporter: Shiva Kumar H R Assigned To: Sachin Patel Fix For: 1.x Attachments: GERONIMODEVTOOLS-121.patch Can't appreciate the significance of the check box button for Add a runtime dependency to Geronimo's shared library in the General tab of Deployment Plan Editors. Is it very important to keep it? If not let's remove it to save some screen space on the General tab of Deployment Plan Editors. -- 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-17) Dojo-based interface for Daytrader
[ http://issues.apache.org/jira/browse/DAYTRADER-17?page=comments#action_12456442 ] Christopher James Blythe commented on DAYTRADER-17: --- Had a short discussion with Matt the other day... The current patch contains a full-blown 0.4.0 version of the dojo source tree. That adds a lot of files to the Daytrader src tree if checked in as is. Obviously, we could rely on the shared version of Dojo provided by the Geronimo server as Paul has already mentioned. However, this fails to address other application servers that do not provie a Dojo implmentation. Matt and I came up with the following solution... - package up the 0.4.0 dojo src in an independent war file - have the Daytrader dojo UI reference this package - checkin the pre-packaged dojo war as a single file If you would like to switch to the dojo impl provided with Geronimo, simply change the request path in the Daytrader code. Thoughts, comments, suggestions? Dojo-based interface for Daytrader -- Key: DAYTRADER-17 URL: http://issues.apache.org/jira/browse/DAYTRADER-17 Project: DayTrader Issue Type: New Feature Components: Web Tier Affects Versions: 1.2 Reporter: Christopher James Blythe Attachments: daytrader-17.zip, daytrader-17.zip Have opened this to track work on the Dojo-based UI for Daytrader that I have been playing around with. -- 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: (GERONIMODEVTOOLS-117) Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117?page=comments#action_12456451 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-117: -- I face the same issue as Michael; that the Dependencies section doesn't show the just added dependency (say when creating geronimo-web.xml from scratch). Shouldn't this be resolved? I will work on this. Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies -- Key: GERONIMODEVTOOLS-117 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 1.2.0 Environment: http://people.apache.org:80/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.2.0-v200611280908-deployable.zip Reporter: Michael Moser Assigned To: Sachin Patel Trying to add the axis library as dependency to my application. After clicking the Add-button on the deployment configuration tab I get a dialog. When - after entering the data - I click Finish nothing happens. The dialog remains and the .xml file remains as it was. When I hit finish again, the dialog disappears but the XML file still remains unchanged. And the reason is: Unhandled event loop exception java.lang.ArrayStoreException at org.eclipse.emf.common.util.BasicEList.assign(BasicEList.java:188) at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList.java:619) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAddUnique(NotifyingListImpl.java:323) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:280) at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:600) at org.apache.geronimo.st.v11.ui.wizards.DependencyWizard.performFinish(DependencyWizard.java:241) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.apache.geronimo.st.ui.sections.AbstractTableSection$3.widgetSelected(AbstractTableSection.java:217) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) According to NG (news:[EMAIL PROTECTED]) this should have been fixed, but I just downloaded the latest available build (see environment) and the same bug still exists. Michael -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see:
[jira] Updated: (GERONIMODEVTOOLS-117) Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-117: - Component/s: eclipse-plugin Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies -- Key: GERONIMODEVTOOLS-117 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.2.0 Environment: http://people.apache.org:80/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.2.0-v200611280908-deployable.zip Reporter: Michael Moser Assigned To: Sachin Patel Trying to add the axis library as dependency to my application. After clicking the Add-button on the deployment configuration tab I get a dialog. When - after entering the data - I click Finish nothing happens. The dialog remains and the .xml file remains as it was. When I hit finish again, the dialog disappears but the XML file still remains unchanged. And the reason is: Unhandled event loop exception java.lang.ArrayStoreException at org.eclipse.emf.common.util.BasicEList.assign(BasicEList.java:188) at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList.java:619) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAddUnique(NotifyingListImpl.java:323) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:280) at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:600) at org.apache.geronimo.st.v11.ui.wizards.DependencyWizard.performFinish(DependencyWizard.java:241) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.apache.geronimo.st.ui.sections.AbstractTableSection$3.widgetSelected(AbstractTableSection.java:217) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) According to NG (news:[EMAIL PROTECTED]) this should have been fixed, but I just downloaded the latest available build (see environment) and the same bug still exists. Michael -- 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: (GERONIMODEVTOOLS-113) Granualize trace statements
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-113?page=all ] Shiva Kumar H R updated GERONIMODEVTOOLS-113: - Component/s: eclipse-plugin Granualize trace statements --- Key: GERONIMODEVTOOLS-113 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-113 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Sachin Patel Assigned To: Sachin Patel Priority: Minor Fix For: 1.x Too many trace statements, need to break them down into INFO, ERROR, FINE and FINEST or something similar. -- 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
Daytrader-22 patch
Matt et al, I have provided the new patch as we had discussed on the JIRA ( http://issues.apache.org/jira/browse/DAYTRADER-22?page=all) awhile back but the patch still hasn't been gone in. Could you please go ahead and commit it? Regards Piyush Agarwal
[jira] Closed: (GERONIMODEVTOOLS-117) Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117?page=all ] Sachin Patel closed GERONIMODEVTOOLS-117. - Fix Version/s: 1.x Resolution: Fixed This is fixed in trunk. Geronimo deployement plan editor crashes with ArrayStoreException when adding dependencies -- Key: GERONIMODEVTOOLS-117 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-117 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.2.0 Environment: http://people.apache.org:80/dist/geronimo/eclipse/unstable/g-eclipse-plugin-1.2.0-v200611280908-deployable.zip Reporter: Michael Moser Assigned To: Sachin Patel Fix For: 1.x Trying to add the axis library as dependency to my application. After clicking the Add-button on the deployment configuration tab I get a dialog. When - after entering the data - I click Finish nothing happens. The dialog remains and the .xml file remains as it was. When I hit finish again, the dialog disappears but the XML file still remains unchanged. And the reason is: Unhandled event loop exception java.lang.ArrayStoreException at org.eclipse.emf.common.util.BasicEList.assign(BasicEList.java:188) at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList.java:619) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAddUnique(NotifyingListImpl.java:323) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:280) at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:600) at org.apache.geronimo.st.v11.ui.wizards.DependencyWizard.performFinish(DependencyWizard.java:241) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.apache.geronimo.st.ui.sections.AbstractTableSection$3.widgetSelected(AbstractTableSection.java:217) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) According to NG (news:[EMAIL PROTECTED]) this should have been fixed, but I just downloaded the latest available build (see environment) and the same bug still exists. Michael -- 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
xalan : Re: svn commit: r483418 - /geronimo/server/trunk/pom.xml
Gianny, I have just built geronimo-jett6-jee5 rev 483465. I have a fully functional console without xalan. Xalan was removed from the build in the morning. It appears that someone accidentally added xalan to the build later in the day. Please let me know if you need it for some specific purpose. Thanks Anita --- [EMAIL PROTECTED] wrote: Author: gdamour Date: Thu Dec 7 03:04:01 2006 New Revision: 483418 URL: http://svn.apache.org/viewvc?view=revrev=483418 Log: Define xalan dependency version number such that assembly works. Modified: geronimo/server/trunk/pom.xml Modified: geronimo/server/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?view=diffrev=483418r1=483417r2=483418 == --- geronimo/server/trunk/pom.xml (original) +++ geronimo/server/trunk/pom.xml Thu Dec 7 03:04:01 2006 @@ -427,6 +427,12 @@ version1.5.2/version /dependency +dependency +groupIdxalan/groupId +artifactIdxalan/artifactId +version2.7.0/version +/dependency + !-- org.apache.xml.serialize.XMLSerializer is used by castor, hence this is still needed -- dependency groupIdxerces/groupId Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
On Dec 6, 2006, at 8:11 PM, David Jencks wrote: I'm not sure who I've talked to about this or where but I think really really strongly that we should include the major version number of the projects we integrate in our artifactIds relating to those external projects. A couple people have pointed out that something like jetty_6 or geronimo-jetty6-builder is more consistent with our spec naming than jetty6 or geronimo-jetty6-naming. I don't really care about that, although I think the shorter tomcat6 is perfectly clear and easier to type. Other stuff: axis axis1 cxf cxf1 openjpa openjpa1 I think this will really reduce confusion about what is running in a server. So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. Can we discuss and settle this soon? Not sure I feel quite as strongly as you.. but I'm giving it a try... ;-) So, any module written explicitly for an external project (i.e. non- Geronimo) would have the external project's major version number encoded in it's name? But not minor number? So, activemq, wadi, would be added to your above list? Heh. How about geronimo-jetty-clustering-wadi? ;-) geronimo-jetty5-clustering- wadi2? --kevan
Re: Stack trace while shutting down amq in geronimo 2.0
Yes I am seeing this too. Still investigating.. Thanks Anita --- David Jencks [EMAIL PROTECTED] wrote: I'm seeing the following stack trace when shutting down the jetty6 geronimo server in trunk. Anyone have a clue about why, if it is a problem, and what we might do about it? thanks david jencks Server shutdown begun 00:37:33,024 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop (BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop (BrokerServiceGBeanImpl.java:106) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance (GBeanInstance.java:1146) 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:551) 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:551) 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:551) 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: 234) 00:37:33,028 ERROR [JournalPersistenceAdapter] Could not stop service: [EMAIL PROTECTED] Reason: SQL Exception: No current connection. SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException (Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection (Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.rollback (Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback (Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback (ManagedXAConnection.java:121) at org.tranql.connector.AbstractManagedConnection $LocalTransactionImpl.rollback(AbstractManagedConnection.java:196) at org.tranql.connector.jdbc.ConnectionHandle.rollback (ConnectionHandle.java:135) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop (DefaultDatabaseLocker.java:80) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop (JDBCPersistenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop (JournalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop (ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
On Dec 7, 2006, at 6:26 AM, Paul McMahan wrote: On 12/6/06, David Jencks [EMAIL PROTECTED] wrote: So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. I'll make this change right away, also using geronimo-tomcat6-jee5 and geronimo-tomcat6-minimal for the assemblies as well (unless you omitted them intentionally). Nope, I just forgot them. Many thanks david jencks Best wishes, Paul
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
On Dec 7, 2006, at 7:57 AM, Kevan Miller wrote: On Dec 6, 2006, at 8:11 PM, David Jencks wrote: I'm not sure who I've talked to about this or where but I think really really strongly that we should include the major version number of the projects we integrate in our artifactIds relating to those external projects. A couple people have pointed out that something like jetty_6 or geronimo-jetty6-builder is more consistent with our spec naming than jetty6 or geronimo-jetty6-naming. I don't really care about that, although I think the shorter tomcat6 is perfectly clear and easier to type. Other stuff: axis axis1 cxf cxf1 openjpa openjpa1 I think this will really reduce confusion about what is running in a server. So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. Can we discuss and settle this soon? Not sure I feel quite as strongly as you.. but I'm giving it a try... ;-) So, any module written explicitly for an external project (i.e. non- Geronimo) would have the external project's major version number encoded in it's name? But not minor number? So, activemq, wadi, would be added to your above list? Heh. How about geronimo-jetty-clustering-wadi? ;-) geronimo-jetty5- clustering-wadi2? yup thanks david jencks --kevan
Re: [jira] Commented: (SM-751) Flow tracing with correlation id
--- Btw, looking at the patch, I was wondering if it would be interesting to have a multi-level correlationId, so that we could trace the exchange to its parent exchange and from the parent to the grand-parent and so forth... Hi, Sorry to drag out an old email, but I was wondering if the proposition above made it into the code ? It would be quite useful to have ... (as I see it when a new correlationid is added into the properties of an exchange which already has one, another property records the parentcorrelationid ... ) Hi Guillaume, thanks for your reply. Not yet. Would you mind raising another issue for that ? Sure. If you have any time to write a patch ... ;) well, i could try, but I'm not sure if I know my way around the code well enough. I get the impression that the servicemix-bpe component is not using the latest ode code - however, as it is today, this component *doesn't* seem to be sticking the correlationID, into exchanges it is making. This would be useful here too. I guess this will also be a problem with any non-servicemix components too :) ? servicemix-bpe also doesn't add the senderEndpoint as a property into the exchanges it makes. I'm currently looking at the audit component, and knowing the senderEndpoint is important to know the initiator of an exchange (?), or can I find this out some other way ... (?) correlationId and senderEndpoint seem generally useful things to ship around in MessageExchanges. Is this the sort of thing JBI should specify I wonder ... ? Roger ps. the SVN trunk doesn't seem to build the core module at the moment. ? thanks, Roger Flow tracing with correlation id Key: SM-751 URL: https://issues.apache.org/activemq/browse/SM-751 Project: ServiceMix Issue Type: Improvement Reporter: Gianfranco Boccalon Attachments: servicemix-components.zip Add the possibility to trace the flow of the messages inside a Service Assembly. For example, if we have a Service Assembly composed of three components, two binding components (call them BC1 and BC2) and a service engine (SE) organized in this sequence BC1-SE-BC2, we need to recognize that the output messages produced by the SE component are related to some messages provided by BC1. To do this, we need to add a process correlation id to the message exchanges and to modify the used components, to propagate this correlation id in all Message Exchanges sent. Enclosed there is the modified code for the following components: - HTTP binding component: here I added the code to generate the correlation Id and set it in the Message Exchange - Splitter - Router (the lightweight component)
[jira] Updated: (GERONIMO-2439) add secure transport support to POP3 (i.e., SSL)
[ http://issues.apache.org/jira/browse/GERONIMO-2439?page=all ] Jason Warner updated GERONIMO-2439: --- Attachment: POP3SSLConnection.patch New class POP3SSLStore.java can be used in place of POP3Store to create an SSL connection. No other POP3Store functions are affected. add secure transport support to POP3 (i.e., SSL) Key: GERONIMO-2439 URL: http://issues.apache.org/jira/browse/GERONIMO-2439 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: mail Reporter: Jason Warner Assigned To: Rick McGuire Priority: Minor Attachments: POP3SSLConnection.patch SSL authentication added to POP3 -- 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
Milestone versions in JIRA for G2.0
Since we're breaking our 2.0 release into milestones, it seems appropriate for us to create some versions in JIRA for them so features and defects can be targeted to them. (ex. 2.0-M1, 2.0- M2...). If there aren't any objections, I'll go ahead and create them. -sachin
Re: Milestone versions in JIRA for G2.0
+1 On 12/7/06, Sachin Patel [EMAIL PROTECTED] wrote: Since we're breaking our 2.0 release into milestones, it seems appropriate for us to create some versions in JIRA for them so features and defects can be targeted to them. (ex. 2.0-M1, 2.0-M2...). If there aren't any objections, I'll go ahead and create them. -sachin
Re: Milestone versions in JIRA for G2.0
+1 Cheers! Hernan Sachin Patel wrote: Since we're breaking our 2.0 release into milestones, it seems appropriate for us to create some versions in JIRA for them so features and defects can be targeted to them. (ex. 2.0-M1, 2.0-M2...). If there aren't any objections, I'll go ahead and create them. -sachin
[jira] Closed: (GERONIMO-2489) Client builder bug is blocking usage of Daytrader AppClient
[ http://issues.apache.org/jira/browse/GERONIMO-2489?page=all ] David Jencks closed GERONIMO-2489. -- Resolution: Cannot Reproduce I haven't had any problems running either the streamer or ws daytrader app clients, so I think this must have gotten fixed by now. Reopen if there's still a problem, with more details. Client builder bug is blocking usage of Daytrader AppClient --- Key: GERONIMO-2489 URL: http://issues.apache.org/jira/browse/GERONIMO-2489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: application client Affects Versions: 1.1.1, 1.1 Reporter: Donald Woods Fix For: 1.1.2, 1.2, 2.0 Attachments: G2489-1.1.1.patch If you try to use the Daytrader app client, the following exception is thrown: java -jar client.jar wasce-samples/daytrader-derby-tomcat_streamer.jar/1.1/car 16:10:19,562 INFO [Log4jService] -- 16:10:19,562 INFO [Log4jService] Started Logging Service 16:10:22,484 WARN [RMIRegistryService] RMI Registry failed 16:10:22,500 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: abstractName=geronimo/rmi-naming/1.1/car?ServiceModule=geronimo /rmi-naming/1.1/car,j2eeType=GBean,name=RMIRegistry java.rmi.server.ExportException: Port already in use: 1099; nested exception is: java.net.BindException: Address already in use: NET_Bind at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:284) at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:219 ) at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:398) at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:131) at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:19 5) at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:107) at sun.rmi.registry.RegistryImpl.init(RegistryImpl.java:93) at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:1 98) at org.apache.geronimo.system.rmi.RMIRegistryService.doStart(RMIRegistry Service.java:58) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:981) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio nGBeans(ConfigurationUtil.java:374) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke rnelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:527) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon figuration(SimpleConfigurationManager.java:508) 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.gbean.GBeanLifecycle$$EnhancerByCGLIB$$ec0bda8e.s tartConfiguration(generated) at org.apache.geronimo.system.main.CommandLine.loadConfigurations(Comman dLine.java:167) at org.apache.geronimo.system.main.CommandLine.invokeMainGBean(CommandLi ne.java:92) at org.apache.geronimo.system.main.ClientCommandLine.init(ClientComman dLine.java:79) at org.apache.geronimo.system.main.ClientCommandLine.main(ClientCommandL ine.java:49) Caused by: java.net.BindException: Address already in use: NET_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at
Re: Stack trace while shutting down amq in geronimo 2.0
This trace is produced by geronimo-framework. The trace is produced when attributes of JavaCompContext (rmi-naming) are viewed by jconsole. Thanks Anita [*] 100% 4s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 4242 0.0.0.0 Remote Login Listener 0.0.0.0 JMX Remoting Connector Geronimo Application Server started 13:08:02,015 WARN [MBeanGBeanBridge] Exception while getting attribute environment javax.management.ReflectionException at org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j ava:122) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttributes(MBeanGBeanBridge. java:143) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttributes(DynamicMetaDataImpl.j ava:125) at com.sun.jmx.mbeanserver.MetaDataImpl.getAttributes(MetaDataImpl.java:189) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBea nServerInterceptor.java:696) at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:686) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.jav a:1389) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java :81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnec tionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnecti onImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.getAttributes(RMIConnectionImpl.j ava:633) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.getEnvironment(ContextFlyweigh t.java:144) at org.apache.xbean.naming.context.ContextFlyweight$$FastClassByCGLIB$$592f1945.in voke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.ja va:38) at org.apache.geronimo.gbean.runtime.GBeanAttribute.getValue(GBeanAttribute.java:3 90) at org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(GBeanInstance.java :681) at org.apache.geronimo.kernel.basic.BasicKernel.getAttribute(BasicKernel.java:178) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j ava:118) ... 22 more --- anita kulshreshtha [EMAIL PROTECTED] wrote: The shutdown of geronimo-tomcat-minimal server produces this trace: 12:34:10,671 INFO [root] -- 12:38:32,171 WARN [BasicLifecycleMonitor] Exception occured while notifying listener java.lang.NullPointerException at org.apache.geronimo.gjndi.binding.GBeanBinding.removeBinding(GBeanBinding.java:159) at org.apache.geronimo.gjndi.binding.GBeanBinding$GBeanLifecycleListener.stopped(GBeanBinding.java:108) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppedEvent(BasicLifecycleMonitor.java:197) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$500(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppedEvent(BasicLifecycleMonitor.java:259) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:359) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551) 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:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at
[jira] Closed: (GERONIMO-1991) Change configuration to module in java classes
[ http://issues.apache.org/jira/browse/GERONIMO-1991?page=all ] Dain Sundstrom closed GERONIMO-1991. Resolution: Later Assignee: Dain Sundstrom Renaming the classes isn't important. Change configuration to module in java classes -- Key: GERONIMO-1991 URL: http://issues.apache.org/jira/browse/GERONIMO-1991 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Dain Sundstrom Assigned To: Dain Sundstrom -- 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
Re: CMP failures in 2.3 (was: Openjeb itests - 552 tests, 2 failures, 2 errors)
I dropped the key-generator element from the BasicCmpBeanExplicitPK cmp entity and that fixed the 2 failures. Please apply the patch in - https://issues.apache.org/jira/browse/OPENEJB-402 We are now down to just 2 errors ! Thanx Prasad On 12/7/06, Gianny Damour [EMAIL PROTECTED] wrote: On 07/12/2006, at 11:10 AM, David Blevins wrote: On Dec 6, 2006, at 12:38 PM, Prasad Kashyap wrote: We are now down to just 2 failures and 2 errors on the Openejb-2.3 itests. The stack trace is here -- http://rifers.org/paste/show/ 2622 org.apache.openejb.test.TestFailureException : null; nested exception is: junit.framework.AssertionFailedError: Should have thrown DuplicateKeyException at junit.framework.Assert.fail(Assert.java:47) at org.apache.openejb.test.entity.cmp.CmpTransactionTests.testInvokeCreat eCreateSameCMP(CmpTransactionTests.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Transaction.testInvokeCreateFindForceCacheFlush Time elapsed: 0.32 sec FAILURE! junit.framework.AssertionFailedError: Received Exception class org.apache.openejb.test.TestFailureException : null; nested exception is: junit.framework.AssertionFailedError: expected:1 but was:0 at junit.framework.Assert.fail(Assert.java:47) at org.apache.openejb.test.entity.cmp.CmpTransactionTests.testInvokeCreat eFindForceCacheFlush(CmpTransactionTests.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Hi David, Sorry for not pro-actively helping (hope to be back to OEJB after some WADI stuff). I debugged the two above tests and identified the issue: an automatic pk generation were wrongly configured for the CMP BasicCmpBeanExplicitPK. This causes at least the two above failures. It seems that something is wrong with my build as I observe weird JNDI lookup problems and I am not sure that dropping the key- generator element does not impact other tests. So, Prasad, could you please do me favor and drop this element for BasicCmpBeanExplicitPK and re-execute? Meanwhile, I will try to fix my build. Thanks, Gianny CMRMappingTests.testOneToManyDoNotSetCMR Time elapsed: 0.26 sec ERROR! org.apache.openejb.test.TestFailureException: null; nested exception is: junit.framework.AssertionFailedError: Received Exception class javax.transaction.RollbackException : Unable to commit: transaction marked for rollback at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean.te stOneToManyDoNotSetCMR(CMRMappingFacadeBean.java:245) at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean$ $FastClassByCGLIB$$9687c6d6.invoke(generated) at org.apache.openejb.dispatch.AbstractMethodOperation.invoke (AbstractMethodOperation.java:58) at org.apache.openejb.slsb.BusinessMethod.execute (BusinessMethod.java:36) CMRMappingTests.testOneToOneDoNotSetCMR Time elapsed: 0.06 sec ERROR! org.apache.openejb.test.TestFailureException: null; nested exception is: junit.framework.AssertionFailedError: Received Exception class javax.transaction.RollbackException : Unable to commit: transaction marked for rollback at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean.te stOneToOneDoNotSetCMR(CMRMappingFacadeBean.java:137) at org.apache.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean$ $FastClassByCGLIB$$9687c6d6.invoke(generated) at org.apache.openejb.dispatch.AbstractMethodOperation.invoke (AbstractMethodOperation.java:58) at org.apache.openejb.slsb.BusinessMethod.execute (BusinessMethod.java:36) Nothing is jumping out at me. Gianny, you have any ideas? -David
Re: Stack trace while shutting down amq in geronimo 2.0
I get this error when shutting down jee5-jetty6 jee5-tomcat
Regards
Krish
On 12/7/06, anita kulshreshtha [EMAIL PROTECTED] wrote:
This trace is produced by geronimo-framework. The trace is produced
when attributes of JavaCompContext (rmi-naming) are viewed by jconsole.
Thanks
Anita
[*] 100% 4s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
4242 0.0.0.0 Remote Login Listener
0.0.0.0 JMX Remoting Connector
Geronimo Application Server started
13:08:02,015 WARN [MBeanGBeanBridge] Exception while getting attribute
environment
javax.management.ReflectionException
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j
ava:122)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttributes(MBeanGBeanBridge.
java:143)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttributes(DynamicMetaDataImpl.j
ava:125)
at
com.sun.jmx.mbeanserver.MetaDataImpl.getAttributes(MetaDataImpl.java:189)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBea
nServerInterceptor.java:696)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:686)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.jav
a:1389)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java
:81)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnec
tionImpl.java:1245)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnecti
onImpl.java:1348)
at
javax.management.remote.rmi.RMIConnectionImpl.getAttributes(RMIConnectionImpl.j
ava:633)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
org.apache.xbean.naming.context.ContextFlyweight.getEnvironment(ContextFlyweigh
t.java:144)
at
org.apache.xbean.naming.context.ContextFlyweight$$FastClassByCGLIB$$592f1945.in
voke(generated)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.ja
va:38)
at
org.apache.geronimo.gbean.runtime.GBeanAttribute.getValue(GBeanAttribute.java:3
90)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(GBeanInstance.java
:681)
at
org.apache.geronimo.kernel.basic.BasicKernel.getAttribute(BasicKernel.java:178)
at
org.apache.geronimo.system.jmx.MBeanGBeanBridge.getAttribute(MBeanGBeanBridge.j
ava:118)
... 22 more
--- anita kulshreshtha [EMAIL PROTECTED] wrote:
The shutdown of geronimo-tomcat-minimal server produces this
trace:
12:34:10,671 INFO [root]
--
12:38:32,171 WARN [BasicLifecycleMonitor] Exception occured while
notifying listener
java.lang.NullPointerException
at
org.apache.geronimo.gjndi.binding.GBeanBinding.removeBinding(GBeanBinding.java:159)
at
org.apache.geronimo.gjndi.binding.GBeanBinding$GBeanLifecycleListener.stopped(GBeanBinding.java:108)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppedEvent(BasicLifecycleMonitor.java:197)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$500(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppedEvent(BasicLifecycleMonitor.java:259)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:359)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:551)
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:551)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
1.2 Beta Tasks
We only have a few remaining optional and required tasks before we can cut the 1.2 beta :D TASK: Review YOUR JIRAs --- We have 60 JIRAs assigned to 1.2. Please review the issues assigned to you, and if you do not plan on fixing them in the next say 7 days move out of 1.2. Those with JIRAs remaining [1] at the end of the release will be shamed :) Other Tasks --- Normally legal is the biggest problem, and Kevan has done a wonderful in this area. FWIU, the only remaining legal issue is the presence Sun schemas and dtds in the servlet and jsp spec jars, and Kevan is working to find out if they are a real problem. Any thing else I missed Kevan? We have a few remaining SNAPSHOTS dependencies in the tree [2]. OpenEJB and Yoko are still being worked on for this release so a SNAPSHOT dependency is fine. ActiveIO and OpenJPA have released versions for the code we are using and I will work to replace this today. Matt promised me a release of TranQL for this release, and I am hoping to get this today. We have an exception being thrown in shutdown from GBeanBinding.removeBinding():159 and I'll fix that today. Thanks for all the help. Hopefully we can get the beta shipped next week! -dain [1] Currently assigned JIRA for 1.2 Aaron Mulder 3 Alan Cabrera 1 Bill Dudney 1 Christopher M. Cardona 1 David Jencks 20 Donald Woods 1 Gianny Damour 1 Kevan Miller 6 Matt Hogstrom 2 Prasad Kashyap 1 Rakesh Midha 1 Rick McGuire 1 Unassigned 21 [2] Current SNAPSHOT dependencies: activeio-core-3.0-SNAPSHOT.jar geronimo-schema-j2ee_1.4-1.1-SNAPSHOT.jar geronimo-schema-jee_5-1.0-SNAPSHOT.jar geronimo-javamail_1.3.1_spec-1.2-SNAPSHOT.jar geronimo-jpa_3.0_spec-1.0-SNAPSHOT.jar openejb-axis-2.2-incubating-SNAPSHOT.jar openejb-builder-2.2-incubating-SNAPSHOT.jar openejb-corba-2.2-incubating-SNAPSHOT.jar openejb-corba-builder-2.2-incubating-SNAPSHOT.jar openejb-core-2.2-incubating-SNAPSHOT.jar openejb-pkgen-builder-2.2-incubating-SNAPSHOT.jar openejb-yoko-2.2-incubating-SNAPSHOT.jar openjpa-all-0.9.6-incubating-SNAPSHOT.jar tranql-1.4-SNAPSHOT.jar tranql-connector-1.3-SNAPSHOT.jar tranql-connector-derby-common-1.2-SNAPSHOT.jar tranql-connector-1.3-SNAPSHOT.jar tranql-connector-derby-common-1.2-SNAPSHOT.jar yoko-core-1.0-incubating-M2-SNAPSHOT.jar yoko-rmi-impl-1.0-incubating-M2-SNAPSHOT.jar yoko-rmi-spec-1.0-incubating-M2-SNAPSHOT.jar yoko-spec-corba-1.0-incubating-M2-SNAPSHOT.jar yoko-spec-corba-1.0-incubating-M2-SNAPSHOT.jar
[jira] Closed: (GERONIMO-1987) Change configuration to module
[ http://issues.apache.org/jira/browse/GERONIMO-1987?page=all ] Dain Sundstrom closed GERONIMO-1987. Fix Version/s: 1.1 (was: 1.2) Resolution: Fixed All completed sub-tasks were closed in 1.1 Change configuration to module -- Key: GERONIMO-1987 URL: http://issues.apache.org/jira/browse/GERONIMO-1987 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.1 Reporter: Dain Sundstrom Fix For: 1.1 It seems like configuration can be confusing, as it more traditionally refers to a larger scope like an entire installation. For example, if you say you have two different WebLogic configurations or two different Apache (HTTP) configurations, you're saying either you have two installations, or you have two totally separate product configurations available for the same product installation. You're not saying you have an app and a database pool within one runtime, but that's what two different configurations presently would mean in relation to Geronimo. It seems like it would be clearer to say that a Geronimo installation loads many modules, and each module includes many components (GBeans). -- 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-1917) repository doesn't deal well with case insensitive file systems
[ http://issues.apache.org/jira/browse/GERONIMO-1917?page=all ] Dain Sundstrom updated GERONIMO-1917: - Fix Version/s: 2.0 (was: 1.2) This will not be fixed in 1.2 repository doesn't deal well with case insensitive file systems --- Key: GERONIMO-1917 URL: http://issues.apache.org/jira/browse/GERONIMO-1917 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: kernel Affects Versions: 1.1, 1.1.1, 1.1.x, 1.1.2 Reporter: David Jencks Fix For: 1.1.2, 2.0 If you've installed a configuration A/B/1/car and then look for a/b/1/car, the repository will claim it's there on a case insensitive file system, but then further logic in the config store/ manager blows up because those are different artifacts. Solution appears to be to check when locating an artifact that the case from the file system matches the case you are asking for. -- 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-434) Connection factories extracted from conceptually wrong gbean
[ http://issues.apache.org/jira/browse/GERONIMO-434?page=all ] David Jencks updated GERONIMO-434: -- Fix Version/s: Wish List (was: 1.x) Connection factories extracted from conceptually wrong gbean Key: GERONIMO-434 URL: http://issues.apache.org/jira/browse/GERONIMO-434 Project: Geronimo Issue Type: Improvement Components: connector Affects Versions: 1.0-M4 Reporter: David Jencks Assigned To: David Jencks Fix For: Wish List Currently connection factories/datasources (or their proxies) are obtained from the JCAManagedConnectionFactory gbean. Since there is a ConnectionFactory/Datasource gbean for the jsr-77 requirements, it would make more sense to obtain the connection factory/datasource from there. This would have the additional feature of allowing one to set up several connection factories under different names that all use the same ConnectionManager and ManagedConnectionFactory. This would for instance let you set up separately named QueueConnectionFactory and TopicConnectionFactory that share the same connections: named appropriately, this can let you leave out resource-refs in plans for apps that call the factories different names. -- 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-250) Connector tries to commit after connection error
[ http://issues.apache.org/jira/browse/GERONIMO-250?page=all ] David Jencks updated GERONIMO-250: -- Fix Version/s: 2.0 (was: 1.x) Connector tries to commit after connection error Key: GERONIMO-250 URL: http://issues.apache.org/jira/browse/GERONIMO-250 Project: Geronimo Issue Type: Bug Components: connector Affects Versions: 1.0-M2 Reporter: Simon Godik Assigned To: David Jencks Fix For: 2.0 If a resource adapter indicates a connection has had a fatal error, then the connection manager destroys the managed connection but still attempts to commit/rollback at transaction end. This is bad as the connection has already been destroyed. -- 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-268) Connection Error handling problems
[ http://issues.apache.org/jira/browse/GERONIMO-268?page=all ] David Jencks updated GERONIMO-268: -- Fix Version/s: 2.0 (was: 1.x) Connection Error handling problems -- Key: GERONIMO-268 URL: http://issues.apache.org/jira/browse/GERONIMO-268 Project: Geronimo Issue Type: Bug Components: connector Affects Versions: 1.0-M2 Reporter: David Jencks Assigned To: David Jencks Fix For: 2.0 A managed connection that encounters a fatal error and calls ConnectionErrorOccured on the GeronimoConnectionEventListener may not have the resources held by geronimo cleaned up properly. In particular, if several ejbs have handles to this mc, the connection tracking won't work properly. Only the currently active component (ejb) will have it's handle(s) removed from tracking. When the other handles are disociated or closed, errors are likely, such as putting the destroyed managed connection back into the pool. -- 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-383) xmlbeans magic allows us to accept some invalid deployment descriptors
[ http://issues.apache.org/jira/browse/GERONIMO-383?page=all ] David Jencks updated GERONIMO-383: -- Fix Version/s: Wish List (was: 1.x) Assignee: (was: David Jencks) I doubt I will have time to look into this in the forseeable future. xmlbeans magic allows us to accept some invalid deployment descriptors -- Key: GERONIMO-383 URL: http://issues.apache.org/jira/browse/GERONIMO-383 Project: Geronimo Issue Type: Bug Components: deployment Affects Versions: 1.0-M2 Reporter: David Jencks Fix For: Wish List The element reordering and other xmlbeans magic we do to convert pre-1.4 deployment descriptors to 1.4 versions can have the unintended side effect of converting invalid 1.4 descriptors to valid ones. This has been fixed in SchemaConversionUtils.convertToServletSchema for servlet 1.3 web.xml. We should apply this same fix of checking for namespace before conversion to other modules (ejb etc) and extend the checking to: 1. look for the DOCTYPE using xmlbeans 2. converting to a made-up namespace for that dtd 3. validating against xmlbeans objects for the schema corresponding to the 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] Updated: (GERONIMO-1460) Tomcat web plan should take multiple hosts, create HostGBeans as necessary
[ http://issues.apache.org/jira/browse/GERONIMO-1460?page=all ] David Jencks updated GERONIMO-1460: --- Fix Version/s: Wish List (was: 1.2) Assignee: (was: David Jencks) I don't think this is practical to do and I don't think I'll have time to think about it in the forseeable future. Tomcat web plan should take multiple hosts, create HostGBeans as necessary -- Key: GERONIMO-1460 URL: http://issues.apache.org/jira/browse/GERONIMO-1460 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat, web Affects Versions: 1.0 Reporter: Aaron Mulder Fix For: Wish List The Tomcat web plan should take multiple host elements, and for each one: - if a HostGBean is present, associate to that - if a HostGBean is not present, create a default one and start it, and then associate to that -- 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-1461) Unify virtual host settings for Tomcat Jetty into generic web plan
[ http://issues.apache.org/jira/browse/GERONIMO-1461?page=all ] David Jencks reassigned GERONIMO-1461: -- Assignee: (was: David Jencks) I don't think it's practical to do this. Unify virtual host settings for Tomcat Jetty into generic web plan Key: GERONIMO-1461 URL: http://issues.apache.org/jira/browse/GERONIMO-1461 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: web Affects Versions: 1.0 Reporter: Aaron Mulder Fix For: Wish List The geronimo-web-1.0.xsd schema should include a 0-N element for virtual host name, which both Tomcat and Jetty should use. Then the container-specific virtual host settings can be removed from the Tomcat and Jetty specific config formats, and replaced with the portable setting in the Tomcat and Jetty specific plan formats. -- 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-1470) Our context root settings should take precedence over those from application.xml
[ http://issues.apache.org/jira/browse/GERONIMO-1470?page=all ] David Jencks updated GERONIMO-1470: --- Fix Version/s: 2.0 (was: 1.2) Our context root settings should take precedence over those from application.xml Key: GERONIMO-1470 URL: http://issues.apache.org/jira/browse/GERONIMO-1470 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: 2.0 Someone on IRC pointed out that the context-root setting in application.xml is an assembly-time setting and should be overridden by the deploy-time setting in our web plans. At the moment the application.xml setting overrides the web plan setting. This is a trivial change, but I want to make sure there are no objections to it. -- 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
Re: Milestone versions in JIRA for G2.0
+1 Anita --- Sachin Patel [EMAIL PROTECTED] wrote: Since we're breaking our 2.0 release into milestones, it seems appropriate for us to create some versions in JIRA for them so features and defects can be targeted to them. (ex. 2.0-M1, 2.0- M2...). If there aren't any objections, I'll go ahead and create them. -sachin Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.
[jira] Closed: (GERONIMO-1574) Spring integration with Geronimo Transaction Manager
[ http://issues.apache.org/jira/browse/GERONIMO-1574?page=all ] David Jencks closed GERONIMO-1574. -- Resolution: Won't Fix After the tx refactoring and global jndi, you should be able to access the geronimo tx manager in spring using the normal spring components. Spring integration with Geronimo Transaction Manager Key: GERONIMO-1574 URL: http://issues.apache.org/jira/browse/GERONIMO-1574 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: transaction manager Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: Wish List For a reasonable spring integration, we need to expose some of our components wrapped in spring interfaces. The most obvious is the transaction manager. -- 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
Re: svn commit: r483201 [1/2] - in /geronimo/server/trunk: applications/console/geronimo-console-framework/ applications/console/geronimo-console-standard/ applications/demo/ applications/geronimo-ca-
My understanding is that this will be done so that Geronimo can support more than one version of a third party artifact within a particular build tree, a la GERONIMO-2399. BTW, I'm holding off making any changes to the tomcat artifcatIds in trunk until this discussion winds down :-) Best wishes, Paul On 12/7/06, Joe Bohn [EMAIL PROTECTED] wrote: It seems like this will make upgrading to newer versions of projects more difficult. As the major version changes there will be changes that percolate across the geronimo modules, configs, assemblies, etc... It's not impossible to maintain by any means, but it is a little more difficult and error prone. We've already seen a little of this with jetty6 (initial jetty6 image including both jetty 5 jetty 6 items, testsuite changes, etc...). Can you please summarize the rationale for this again and the benefits to be gained? Thanks, Joe David Jencks wrote: I'm not sure who I've talked to about this or where but I think really really strongly that we should include the major version number of the projects we integrate in our artifactIds relating to those external projects. A couple people have pointed out that something like jetty_6 or geronimo-jetty6-builder is more consistent with our spec naming than jetty6 or geronimo-jetty6-naming. I don't really care about that, although I think the shorter tomcat6 is perfectly clear and easier to type. Other stuff: axis axis1 cxf cxf1 openjpa openjpa1 I think this will really reduce confusion about what is running in a server. So, I'd like the tomcat modules to be renamed geronimo-tomcat6, geronimo-tomcat6-builder, tomcat6, tomcat6-deployer. Can we discuss and settle this soon? thanks david jencks ps. I'm planning to remove the jetty[5] stuff from trunk soon.
[jira] Commented: (GERONIMO-2439) add secure transport support to POP3 (i.e., SSL)
[ http://issues.apache.org/jira/browse/GERONIMO-2439?page=comments#action_12456540 ] Rick McGuire commented on GERONIMO-2439: Jason, there are a couple of problems here that need to be fixed: 1) Comments in the POP3 files still refer to smtp and smtps. This really should be cleaned up (nit picking here). 2) The default port for POP3Store and POP3SSLStore are different. This really needs to be handled the way SMTPTransport/SMTPSTransport do it, with the default port value specified on the constructor. Just attach a new patch when you have these things fixed. add secure transport support to POP3 (i.e., SSL) Key: GERONIMO-2439 URL: http://issues.apache.org/jira/browse/GERONIMO-2439 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: mail Reporter: Jason Warner Assigned To: Rick McGuire Priority: Minor Attachments: POP3SSLConnection.patch SSL authentication added to POP3 -- 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-2559) cannot stop activemq via kernel shutdown
[ http://issues.apache.org/jira/browse/GERONIMO-2559?page=all ] Dain Sundstrom closed GERONIMO-2559. Resolution: Fixed This was fixed some where in 1.2 :) cannot stop activemq via kernel shutdown Key: GERONIMO-2559 URL: http://issues.apache.org/jira/browse/GERONIMO-2559 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 1.2 Environment: sun j2se 1.5.0_07 Reporter: Paul McMahan Fix For: 1.2, 2.0 Shutdown the server from the admin console. This ends up invoking kernel.shutdown(). The following stack trace is generated: 11:59:25,265 ERROR [JournalPersistenceAdapter] Could not stop service: org.apach [EMAIL PROTECTED] Reason: java.lang.Nul lPointerException java.lang.NullPointerException at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT rackingCoordinator.handleReleased(ConnectionTrackingCoordinator.java:127) at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT rackingCoordinator$$FastClassByCGLIB$$5d33aabf.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:820) 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:97) at org.apache.geronimo.connector.outbound.connectiontracking.ConnectionT racker$$EnhancerByCGLIB$$c20afa50.handleReleased(generated) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor. returnConnection(ConnectionTrackingInterceptor.java:81) at org.apache.geronimo.connector.outbound.GeronimoConnectionEventListene r.connectionClosed(GeronimoConnectionEventListener.java:67) at org.tranql.connector.AbstractManagedConnection.connectionClosed(Abstr actManagedConnection.java:102) at org.tranql.connector.jdbc.ConnectionHandle.close(ConnectionHandle.jav a:97) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultData baseLocker.java:81) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersis tenceAdapter.java:202) at org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(Jour nalPersistenceAdapter.java:254) at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:443) at org.apache.activemq.gbean.BrokerServiceGBeanImpl.doStop(BrokerService GBeanImpl.java:107) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBean Instance.java:1146) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop( GBeanInstanceState.java:337) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan ceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja va:551) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja va:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$Shutdown Hook.run(KernelConfigurationManager.java:310) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(Basi cKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.jav a:645) at org.apache.geronimo.console.servermanager.ServerManagerPortlet.doView (ServerManagerPortlet.java:72) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218 ) at
[jira] Updated: (GERONIMO-2411) Add NOTICE and LICENSE files to CAR, WAR and EAR artifacts
[ http://issues.apache.org/jira/browse/GERONIMO-2411?page=all ] Dain Sundstrom updated GERONIMO-2411: - Summary: Add NOTICE and LICENSE files to CAR, WAR and EAR artifacts (was: CAR, WAR and EAR artifacts are missing NOTICE and LICENSE files.) Issue Type: Task (was: Bug) Assignee: Dain Sundstrom Priority: Blocker (was: Major) Add NOTICE and LICENSE files to CAR, WAR and EAR artifacts -- Key: GERONIMO-2411 URL: http://issues.apache.org/jira/browse/GERONIMO-2411 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 1.0, 1.2, 1.x, 1.1, 1.1.1, 1.1.x, 1.1.2 Reporter: Matt Hogstrom Assigned To: Dain Sundstrom Priority: Blocker Fix For: 2.0, 1.2 For release of these artifacts they need to include the LICENSE and NOTICE files. Currently the build does not automatically include them. The M2 build needs to be updated to include these artifacts in the build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
