[jira] Created: (GERONIMO-484) Repeated Deploys of WAR Generate OOM Exception

Repeated Deploys of WAR Generate OOM Exception -- Key: GERONIMO-484 URL: http://nagoya.apache.org/jira/browse/GERONIMO-484 Project: Apache Geronimo Type: Bug Components: web Versions: 1.0-M3 Environment: WinXP

[jira] Updated: (GERONIMO-484) Repeated Deploys of WAR Generate OOM Exception

[ http://nagoya.apache.org/jira/browse/GERONIMO-484?page=history ] Seth Ladd updated GERONIMO-484: --- Attachment: minimaltest.war The webapp used in the over-and-over test. Includes only web.xml and a welcome.jsp Repeated Deploys of WAR Generate OOM

Build failed - Error parsing project.xml 'D:\Projects\J2EE\geronimo\activemq\modules\core\project.xml'

I did a maven m:update (now at Geronimo revision 71524) and did a maven m:rebuild and got the following error. Is anyone else having this problem? Seems to be related to recent changes to ActiveMQ: http://cvs.activemq.codehaus.org/changelog/activemq/?cs=MAIN:mgaffney:20041115221102 Thanks,

Re: Build failed - Error parsing project.xml 'D:\Projects\J2EE\geronimo\activemq\modules\core\project.xml'

Just fixed that. I think :) -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Nov 15, 2004, at 4:23 PM, [EMAIL PROTECTED] wrote: I did a maven m:update (now at Geronimo revision 71524) and did a maven m:rebuild and got the following error. Is anyone else

[Axis modules]Should I commit in directly?

Hi All; I have few more excluded test cases up for the axis geronimo module! Should I check them in directly? BTW Is there way to verify I have not broke the build (something more than get it work in my machine!) How it usually done? Unfortunately am 12 hours behind US time and had I break

Geronimo :: Derby :: Connector compile error

Doing a maven m:build in a clean geronimo directory, I checked that a recent tranql-connector-1.0-SNAPSHOT.jar has been downloaded into the .maven repository. Yet the build fails because the org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory.setExceptionSorterClass function

Re: Geronimo :: Derby :: Connector compile error

It looks like it may be related to Alan's recent change.. http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=5663 Seems that org.tranql.connector.jdbc.AbstractXADataSourceMCF.java hasn't been changed to have a setExceptionSorterClass method. Currently it has: public String

Re: build failed Mon Nov 15 13:13:05 PST 2004

I also have the test failing. On the topic of resources being temporarily unavailable.. Looked at the stack trace for the failed test and saw that org.apache.geronimo.remoting.transport.TransportLoader is doing the bind that failed. Do you think TransportLoader (implements GBeanLifecycle)

Re: [Axis modules]Should I commit in directly?

+1 from. I'll cover your back :) thanks, dims On Mon, 15 Nov 2004 18:23:45 -0800, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; I have few more excluded test cases up for the axis geronimo module! Should I check them in directly? BTW Is there way to verify I have not broke the build

Re: [Axis modules]Should I commit in directly?

Apache SVN seem to down (https://svn.apache.org/repos/asf/webservices/axis/) will try tommarow. Thanks Srinath On Tue, 16 Nov 2004 06:57:02 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: +1 from. I'll cover your back :) thanks, dims On Mon, 15 Nov 2004 18:23:45 -0800, Srinath

[jira] Created: (GERONIMO-485) Connector deployment should convert 1.0 dds to 1.5 dds before processing them.

Connector deployment should convert 1.0 dds to 1.5 dds before processing them. -- Key: GERONIMO-485 URL: http://nagoya.apache.org/jira/browse/GERONIMO-485 Project: Apache Geronimo Type:

[jira] Created: (GERONIMO-486) ActivationSpec metadata is attached to the wrong gbean.

ActivationSpec metadata is attached to the wrong gbean. --- Key: GERONIMO-486 URL: http://nagoya.apache.org/jira/browse/GERONIMO-486 Project: Apache Geronimo Type: Bug Components: connector Versions: 1.0-M3

Re: Geronimo :: Derby :: Connector compile error

Thanks, David. maven m:update m:build worked with just a few hiccups. Had to go into derby-connector and run maven to build the rar. Some security tests that were failing yesterday succeeded today. My Hello session bean doesn't deploy to the running server using the following command: java

Re: Question about deployer classloaders/plan hierarchy.

I talked with Jeremy and Aaron more about this. Our current idea, very similar to one Dain proposed also, is something like this: 1. Each config-builder will be split into two parts: one that needs no particular classes and recognizes whether it knows how to build a module, and one that may

Re: Geronimo :: Derby :: Connector compile error

Actually, it looks like I checked in a change to add the deployer a little while ago. So perhaps you hadn't done a full rebuild since then or something. In any case, the very latest builds should start the runtime deployer by default. Aaron On Tue, 16 Nov 2004, Craig Johannsen wrote:

[jira] Closed: (GERONIMO-486) ActivationSpec metadata is attached to the wrong gbean.

[ http://nagoya.apache.org/jira/browse/GERONIMO-486?page=history ] David Jencks closed GERONIMO-486: - Resolution: Fixed Fix Version: 1.0-M4 Implemented in revision 76049 ActivationSpec metadata is attached to the wrong gbean.

[jira] Closed: (GERONIMO-485) Connector deployment should convert 1.0 dds to 1.5 dds before processing them.

[ http://nagoya.apache.org/jira/browse/GERONIMO-485?page=history ] David Jencks closed GERONIMO-485: - Resolution: Fixed Fix Version: 1.0-M4 Implemented in revision 76049 Connector deployment should convert 1.0 dds to 1.5 dds before

[jira] Closed: (GERONIMO-456) Rename LocalLoginRemoteLocalModuleLocalRealmRemote...

[ http://nagoya.apache.org/jira/browse/GERONIMO-456?page=history ] Aaron Mulder closed GERONIMO-456: - Resolution: Fixed Fix Version: 1.0-M4 Rename LocalLoginRemoteLocalModuleLocalRealmRemote...

[jira] Commented: (GERONIMO-365) Need ability to create queue/topic outside RAR

[ http://nagoya.apache.org/jira/browse/GERONIMO-365?page=comments#action_4 ] David Jencks commented on GERONIMO-365: --- The metadata (activation spec GBeanData) for doing this is now available from the resource module gbean, see GERONIMO-486

[jira] Closed: (GERONIMO-420) Refactor *UserPrincipal and *GroupPrincipal

[ http://nagoya.apache.org/jira/browse/GERONIMO-420?page=history ] Aaron Mulder closed GERONIMO-420: - Resolution: Won't Fix It turns out it's useful to be able to distinguish. Might want to move common code into a superclass, but don't want to