Re: [NOTICE] Creating server/branches/2.1.4
I committed a minimal fix to branches/2.1 and can't find any problems in the build or tck. Keep your eyes open and fingers crossed :-) thanks david jencks On Feb 26, 2009, at 7:52 PM, Joe Bohn wrote: Thanks for the heads up David. No, I didn't start the branch yet. I got tied up in some other things. Perhaps tomorrow. Even still, we can still put fixes in for a few days while we wait for out dependencies to get released. Thanks, Joe David Jencks wrote: Hi Joe, I just discovered a problem (GERONIMO-4554) that ideally I'd like to fix in 2.1.4. I'm hoping to fix it tonight AFAICT you haven't actually branched yet so hopefully this will not disrupt things appreciably. thanks david jencks On Feb 24, 2009, at 11:30 AM, Joe Bohn wrote: We're getting very close to a Geronimo 2.1.4 release. I think it's nearly time to create a branch to prepare for the release. So, I'm planning to create a branch on Thursday afternoon (2/26). Please carefully consider any changes in the branches/2.1 that might destabilize things and consider holding off until after the branch. I do anticipate that there will continue to be bug fixes and other minor changes. Hopefully, we will be in a position to create a release candidate sometime next week. Thanks, Joe
[jira] Assigned: (GERONIMO-4556) Farm deployment of configurations using JNDI resource references does not work
[
https://issues.apache.org/jira/browse/GERONIMO-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianny Damour reassigned GERONIMO-4556:
---
Assignee: Gianny Damour
> Farm deployment of configurations using JNDI resource references does not work
> --
>
> Key: GERONIMO-4556
> URL: https://issues.apache.org/jira/browse/GERONIMO-4556
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 2.1.3
>Reporter: Gianny Damour
>Assignee: Gianny Damour
>
> Due to the transformation of the name of a configuration when it is
> distributed to a server farm (i.e. the _G_SLAVE suffix is appended) JNDI
> resource references can not be resolved.
> Here is an user provided stack trace which illustrates this problem:
> {code}
> java.lang.IllegalStateException: No configuration found for id:
> clustering/clustering/2.1/war
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.getConfiguration(AbstractEntryFactory.java:110)
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.resolveTargetName(AbstractEntryFactory.java:126)
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.getGBean(AbstractEntryFactory.java:64)
> at
> org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:44)
> at
> org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:33)
> at
> org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpriseNamingContext(EnterpriseNamingContext.java:55)
> at
> org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:181)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4556) Farm deployment of configurations using JNDI resource references does not work
[
https://issues.apache.org/jira/browse/GERONIMO-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianny Damour updated GERONIMO-4556:
Description:
Due to the transformation of the name of a configuration when it is distributed
to a server farm (i.e. the _G_SLAVE suffix is appended) JNDI resource
references can not be resolved.
Here is an user provided stack trace which illustrates this problem:
{code}
java.lang.IllegalStateException: No configuration found for id:
clustering/clustering/2.1/war
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getConfiguration(AbstractEntryFactory.java:110)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.resolveTargetName(AbstractEntryFactory.java:126)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getGBean(AbstractEntryFactory.java:64)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:44)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:33)
at
org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpriseNamingContext(EnterpriseNamingContext.java:55)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:181)
{code}
was:
Due to the transformation of the name of a configuration when it is distributed
to a server farm (i.e. the _G_SLAVE suffix is appended) JNDI resource
references can not be resolved.
Here is an user provided stack trace which illustrates this problem:
{code}
java.lang.IllegalStateException: No configuration found for id:
clustering/clustering/2.1/war
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getConfiguration(AbstractEntryFactory.java:110)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.resolveTargetName(AbstractEntryFactory.java:126)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getGBean(AbstractEntryFactory.java:64)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:44)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:33)
at
org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpriseNamingContext(EnterpriseNamingContext.java:55)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:181)
{code]
> Farm deployment of configurations using JNDI resource references does not work
> --
>
> Key: GERONIMO-4556
> URL: https://issues.apache.org/jira/browse/GERONIMO-4556
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 2.1.3
>Reporter: Gianny Damour
>
> Due to the transformation of the name of a configuration when it is
> distributed to a server farm (i.e. the _G_SLAVE suffix is appended) JNDI
> resource references can not be resolved.
> Here is an user provided stack trace which illustrates this problem:
> {code}
> java.lang.IllegalStateException: No configuration found for id:
> clustering/clustering/2.1/war
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.getConfiguration(AbstractEntryFactory.java:110)
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.resolveTargetName(AbstractEntryFactory.java:126)
> at
> org.apache.geronimo.naming.reference.AbstractEntryFactory.getGBean(AbstractEntryFactory.java:64)
> at
> org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:44)
> at
> org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:33)
> at
> org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpriseNamingContext(EnterpriseNamingContext.java:55)
> at
> org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:181)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4556) Farm deployment of configurations using JNDI resource references does not work
Farm deployment of configurations using JNDI resource references does not work
--
Key: GERONIMO-4556
URL: https://issues.apache.org/jira/browse/GERONIMO-4556
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 2.1.3
Reporter: Gianny Damour
Due to the transformation of the name of a configuration when it is distributed
to a server farm (i.e. the _G_SLAVE suffix is appended) JNDI resource
references can not be resolved.
Here is an user provided stack trace which illustrates this problem:
{code}
java.lang.IllegalStateException: No configuration found for id:
clustering/clustering/2.1/war
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getConfiguration(AbstractEntryFactory.java:110)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.resolveTargetName(AbstractEntryFactory.java:126)
at
org.apache.geronimo.naming.reference.AbstractEntryFactory.getGBean(AbstractEntryFactory.java:64)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:44)
at
org.apache.geronimo.naming.reference.ResourceReferenceFactory.buildEntry(ResourceReferenceFactory.java:33)
at
org.apache.geronimo.naming.enc.EnterpriseNamingContext.createEnterpriseNamingContext(EnterpriseNamingContext.java:55)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.(TomcatWebAppContext.java:181)
{code]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-162) "geronimo/stop-server -p 3099" can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
[ https://issues.apache.org/jira/browse/GSHELL-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677248#action_12677248 ] Shawn Jiang commented on GSHELL-162: Another option is to keep -p for geronimo/start-server but the port passed by -p should override the NamingPort vaule in config.substitutions.properties. > "geronimo/stop-server -p 3099" can't shutdown a server with NamingPort > changed to 3099 in config_substitutions.properties. > -- > > Key: GSHELL-162 > URL: https://issues.apache.org/jira/browse/GSHELL-162 > Project: GShell > Issue Type: Bug > Security Level: public(Regular issues) > Components: CLI > Environment: XP + SUN JDK 1.5 + > geronimo-tomcat-2.1.4-snapshot_20090225 >Reporter: Shawn Jiang >Assignee: Jason Dillon > > Reproduce steps: > 1, Change NamingPort=3099 in var/config-substitutions.properties. > 2, Use GShell command "geronimo/start-server" to start the server. > 3, Use Use GShell command "geronimo/stop-server -p 3099" to stop the server. > Expected result: the server could be shutdown and return to the GShell > command line mode. > Actually result: The server can't be shutdown, can't return to the GShell > command line. > Root Cause: > You have to use "geronimo/start-server -p 3099" to start server if you want > use "geronimo/stop-server -p 3099" to stop the server. > I believe there should not be a -p args for geronimo/start-server command. > Instead, geronimo/start-server should read NamingPort=3099 in > config.substitutions.properties to avoid the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties
I don't think this is a application specific problem. I did some test and found the reproduce steps and the root cause here: Reproduce steps: 1, Change NamingPort=3099 from 1099 in var/config-substitutions.properties. 2, Use GShell command "geronimo/start-server“ to start the server. 3, Use Use GShell command "geronimo/stop-server -p 3099“ to stop the server. Expected result: the server could be shutdown and return to the GShell command line mode. Actually result: The server can't be shutdown, can't return to the GShell command line. Root Cause: You have to use "geronimo/start-server -p 3099" to start server if you want use "geronimo/stop-server -p 3099“ to stop the server. I believe there should not a -p args for geronimo/start-server command. Instead, geronimo/start-server should read NamingPort=3099 in config.substitutions.properties to avoid the problem. I've created a JIRA to track this problem: https://issues.apache.org/jira/browse/GSHELL-162 On Thu, Feb 26, 2009 at 4:33 AM, Jeff Lu (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676766#action_12676766 > ] > > Jeff Lu commented on GERONIMO-4518: > --- > > Jarek, > > I found the problem that is within our apps when shutdown is issued, one of > the threads was in a forever wait state causing shutdown to hang. Problem > solved. > > Thank you > >> Can't shutdown the server when host was set to 127.0.0.1 in >> config-substitutions.properties >> --- >> >> Key: GERONIMO-4518 >> URL: https://issues.apache.org/jira/browse/GERONIMO-4518 >> Project: Geronimo >> Issue Type: Bug >> Security Level: public(Regular issues) >> Components: startup/shutdown >> Affects Versions: 2.1.4, 2.2 >> Environment: Windows XP + Sun JDK 1.5 >> Reporter: Shawn Jiang >> Assignee: Jarek Gawor >> Fix For: 2.1.4, 2.2 >> >> Attachments: G4518_Shawn.patch >> >> >> 1, change the host in config-substitutions.properties to 127.0.0.1 >> 2, start the server. >> 3, shutdown the server. >> *expected result*: the server could be shutdown. >> *actual result*: the sever can't be shutdown with exception: >> java.net.ConnectException: Connection refused: connect >> -- >> C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1 >> Using GERONIMO_HOME: C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT >> Using GERONIMO_TMPDIR: var\temp >> Using JRE_HOME: D:\dev\JDKs\sun_jdk1.5.0_15\jre >> log4j:WARN No appenders could be found for logger >> (org.apache.geronimo.kernel.basic.BasicKernel). >> log4j:WARN Please initialize the log4j system properly. >> Username: system >> Password: *** >> Locating server on 127.0.0.1:1099... >> Could not communicate with the server. The server may not be running or the >> port number may be inco >> rrect (Connection refused to host: 6.153.277.58; nested exception is: >> java.net.ConnectException: Connection refused: connect) > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Shawn
[jira] Created: (GSHELL-162) "geronimo/stop-server -p 3099" can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
"geronimo/stop-server -p 3099" can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties. -- Key: GSHELL-162 URL: https://issues.apache.org/jira/browse/GSHELL-162 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Components: CLI Environment: XP + SUN JDK 1.5 + geronimo-tomcat-2.1.4-snapshot_20090225 Reporter: Shawn Jiang Assignee: Jason Dillon Reproduce steps: 1, Change NamingPort=3099 in var/config-substitutions.properties. 2, Use GShell command "geronimo/start-server" to start the server. 3, Use Use GShell command "geronimo/stop-server -p 3099" to stop the server. Expected result: the server could be shutdown and return to the GShell command line mode. Actually result: The server can't be shutdown, can't return to the GShell command line. Root Cause: You have to use "geronimo/start-server -p 3099" to start server if you want use "geronimo/stop-server -p 3099" to stop the server. I believe there should not be a -p args for geronimo/start-server command. Instead, geronimo/start-server should read NamingPort=3099 in config.substitutions.properties to avoid the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [NOTICE] Creating server/branches/2.1.4
Thanks for the heads up David. No, I didn't start the branch yet. I got tied up in some other things. Perhaps tomorrow. Even still, we can still put fixes in for a few days while we wait for out dependencies to get released. Thanks, Joe David Jencks wrote: Hi Joe, I just discovered a problem (GERONIMO-4554) that ideally I'd like to fix in 2.1.4. I'm hoping to fix it tonight AFAICT you haven't actually branched yet so hopefully this will not disrupt things appreciably. thanks david jencks On Feb 24, 2009, at 11:30 AM, Joe Bohn wrote: We're getting very close to a Geronimo 2.1.4 release. I think it's nearly time to create a branch to prepare for the release. So, I'm planning to create a branch on Thursday afternoon (2/26). Please carefully consider any changes in the branches/2.1 that might destabilize things and consider holding off until after the branch. I do anticipate that there will continue to be bug fixes and other minor changes. Hopefully, we will be in a position to create a release candidate sometime next week. Thanks, Joe
[BUILD] trunk: Failed for Revision: 748362
Geronimo Revision: 748362 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes 16 seconds
[INFO] Finished at: Thu Feb 26 21:39:21 EST 2009
[INFO] Final Memory: 617M/1006M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/logs-2100-tomcat/test.log
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:43.703
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:00.969)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:27.949)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.232)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.006)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:27.935)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:20.008)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:43.508)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:48.396)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:47.302)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:39.612)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.687)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.425) Java
returned: 1
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:31.299)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:58.670)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:51.964)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:05.484)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.998)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.918)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:34.965) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.596)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:27.569)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
[jira] Created: (GERONIMO-4555) Can't start App Client after stop it from console
Can't start App Client after stop it from console -- Key: GERONIMO-4555 URL: https://issues.apache.org/jira/browse/GERONIMO-4555 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1.4 Environment: OS:Windows 2003 JDK:1.5 Reporter: viola.lu Priority: Minor 1.Deploy an application client, and stop its server module, but after that there is just an "uninstall"button left, can't re-start it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [NOTICE] Creating server/branches/2.1.4
Hi Joe, I just discovered a problem (GERONIMO-4554) that ideally I'd like to fix in 2.1.4. I'm hoping to fix it tonight AFAICT you haven't actually branched yet so hopefully this will not disrupt things appreciably. thanks david jencks On Feb 24, 2009, at 11:30 AM, Joe Bohn wrote: We're getting very close to a Geronimo 2.1.4 release. I think it's nearly time to create a branch to prepare for the release. So, I'm planning to create a branch on Thursday afternoon (2/26). Please carefully consider any changes in the branches/2.1 that might destabilize things and consider holding off until after the branch. I do anticipate that there will continue to be bug fixes and other minor changes. Hopefully, we will be in a position to create a release candidate sometime next week. Thanks, Joe
[jira] Created: (GERONIMO-4554) Cant deploy an ejb web service as a plugin using car-maven-plugin
Cant deploy an ejb web service as a plugin using car-maven-plugin
-
Key: GERONIMO-4554
URL: https://issues.apache.org/jira/browse/GERONIMO-4554
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: car-maven-plugin
Affects Versions: 2.1.3
Reporter: David Jencks
Assignee: David Jencks
Fix For: 2.1.4, 2.2
I tried to deploy an ejb web service using the car-maven-plugin. The cxf and
axis2 ejb deployers set up the wslink gbean with a reference to the web
container. This is set in the plan for the deployers as "WebContainer" but the
geronimo-plugin.xml overrides this to "${webContainer}". The jetty and tomcat
plugins use a config-substitutions entry to e.g. set
webContainer=JettyWebContainer
So, this all works on a server where all the plugins are installed. However it
doesn't work when using the car-maven-plugin since the config.xml overrides and
config-substitutions are not applied.
We need to either make the config modifications work for the car-maven-plugin
or make sure none of the deployers the car-maven-plugin might use depend on
these customizations to work. For instance, we could change all the names to
WebContainer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 748273
Geronimo Revision: 748273 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 50 seconds
[INFO] Finished at: Thu Feb 26 15:40:26 EST 2009
[INFO] Final Memory: 389M/1000M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/logs-1500-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:44.529
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:11.554)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.270)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.396)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.084)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:13.281)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.367)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.402)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:44.601)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:26.043)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:39.334)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.575)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.485) Java
returned: 1
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.823)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:55.095)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:50.783)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:03.447)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.733)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:45.574)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:41.417)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.493)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test
Request for a OpenJPA 1.2.1 release
Mike, it looks like all of our TCK failures related to JPA have been fixed and verified. Can you start the process of cutting a 1.2.1 branch while we finish our TCK runs? I'd still wait until we have the complete results in (probably sometime Friday) before you start a RC vote. Thanks, Donald Michael Dick wrote: Hi Kevan, I've been planning on doing a 1.2.1 release "real soon now" for a while. I'll start working on it later this week (early next week at the latest). Regards, -mike On Tue, Jan 27, 2009 at 11:04 AM, Kevan Miller wrote: Thanks Kevin and Jeremy for helping to resolve OPENJPA-872. Is there an outlook for an OpenJPA 1.2.1 release? Geronimo is going to need a release prior to releasing Geronimo 2.1.4 and 2.2. I guess we could consider using openjpa.jdbc.QuerySQLCache=false as a work-around, but I'd rather avoid that... Meantime, we'll start using 1.2.1-SNAPSHOT --kevan
[BUILD] trunk: Failed for Revision: 748129
Geronimo Revision: 748129 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 21 seconds
[INFO] Finished at: Thu Feb 26 09:41:05 EST 2009
[INFO] Final Memory: 387M/996M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/logs-0900-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.494
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:11.798)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.624)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.245)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.515)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:15.339)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.956)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.138)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:46.557)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:46.587)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.982)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.279)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.539) Java
returned: 1
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:30.842)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:57.687)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:50.510)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:06.276)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.580)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.708)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:41.060)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.061)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
Apache HTTP Server+WASCE+ActiveMQ Performance Tune?
Hi,ALL: G server+ActiveMQ without Apache http server will serves http request at about 94% success, but if i setup apache http server to loadbalance two g-servers, performance is half worse than without it.Can someone help tune it or someboday have any performance data about it?Thanks a lot! -- viola
[BUILD] trunk: Failed for Revision: 748044
Geronimo Revision: 748044 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 55 seconds
[INFO] Finished at: Thu Feb 26 03:42:44 EST 2009
[INFO] Final Memory: 421M/972M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090226/logs-0300-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:44.415
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:14.552)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:30.489)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:35.766)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.653)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:12.496)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.934)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.700)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:45.050)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:57.995)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:39.646)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:29.380)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.529) Java
returned: 1
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:32.399)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:57.235)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:57.685)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:06.282)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.116)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.164)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:42.404)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.538)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
