[BUILD] trunk: Failed for Revision: 724064
Geronimo Revision: 724064 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081207/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081207
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 302 minutes 55 seconds
[INFO] Finished at: Sun Dec 07 02:06:41 EST 2008
[INFO] Final Memory: 446M/668M
[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/20081207/logs-2100-tomcat/test.log
[INFO] snapshot org.apache.geronimo.framework:geronimo-plugin:2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-config:2.2-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.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:41.552
[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 34 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:00:57.235)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:27.679)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.420)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:15.845)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:37.700)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.809)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:41.841)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.071)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:52.852)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:44.656)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.014)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.492)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:30.090)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:48.581)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:50.293)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:12:06.644)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise-testsuite/sec-client SUCCESS (0:00:25.896)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:49.585)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security
[jira] Created: (GERONIMO-4451) locking and unlocking for availability of a keystore results in duplicate attributes in config.xml
locking and unlocking for availability of a keystore results in duplicate attributes in config.xml -- Key: GERONIMO-4451 URL: https://issues.apache.org/jira/browse/GERONIMO-4451 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1.3 Environment: Ubuntu Linux 8.10, Sun Java 1.6, Geronimo 2.1.3 w/ Jetty. Reporter: Christian Svensson Transcribing mail conversation: Hello! I've been trying for the better part of today getting keystores to automatically unlock on startup - with very limited success. Is there something that I should know about keystore password / key password? Digging around some old mailing list threads said something about key password must be equal to keystore password - any more of those gotchas? The problem is that I create (or change password on geronimo-default for that matter) a new keystore, assign SSL to use the certificate and restart the server: org.apache.geronimo.management.geronimo.KeystoreIsLocked: Keystore 'plasma-ssl' is locked; please use the keystore page in the admin console to unlock it at org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLContext(FileKeystoreManager.java:343) at org.apache.geronimo.jetty6.connector.GeronimoSelectChannelSSLListener.createSSLContext(GeronimoSelectChannelSSLListener.java:54) Resetting the SSL connector to using geronimo-default / geronimo with secret / secret as passwords makes it work again - but why on earth doesn't Geronimo unlock my keystores on startup? I mean, it saves the password (or something like it) in config.xml. - This is how I created my setup: 1. Create a new keystore 'plasma-ssl' 2. Create a new private key 'wildcard' 3. Now the text on Available says trust only or something like that, I lock it and then unlock it in order for it to change to 1 key ready 4. Then I configure my HTTPS connector to use the new keystore 5. Since the web server does not seem to do anything when I press Shutdown in the console, I use Ctrl+C to kill it. 6. Start the server again 7. Message appears. --- Hmm... the 3rd step is indeed unearthing a bug. At that step, a second attribute element is getting added (instead of replacing the existing element) to the keystore gbean for keystorePassword and keyPasswords attributes in config.xml . Can you create an issue in the JIRA [1]? The problem summary is, locking and unlocking for availability of a keystore results in duplicate attributes in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r718393 [1/2] - in /geronimo/server/trunk/plugins/monitoring: ./ agent-car-jmx/ agent-car-jmx/src/main/history/ agent-car-jmx/src/main/plan/ agent-ds/ agent-ds/src/main/plan/ agent-ejb
Seems like this has been fixed. Thanks a lot! Trygve On Thu, Nov 27, 2008 at 1:42 AM, David Jencks [EMAIL PROTECTED]wrote: I think I see one way to fix this. now for some time to try it out. I'm thinking of adding a realm that generates a subject with only the required mejb-user principal for the ejb timer to use. I added a comment to the jira issue to try to remind me about this :-/ thanks david jencks On Nov 26, 2008, at 9:28 AM, Trygve Hardersen wrote: Yes I've changed the password. In /plugins/monitoring/agent/src/main/plan/plan.xml the monitoring-user is set to system/manager. If I set my local system password to manager, the server starts fine. If I don't, the server fails to start unless I disable the org.apache.geronimo.plugins.monitoring/agent/2.2-SNAPSHOT/car plugin. I build my own Geronimo distros (mainly to be able to run on 1.6, though this was fixed yesterday in the client plugin), and I get around this by picking up a password from Maven's settings.xml and putting that in the plan.xml for the monitoring/agent plugin. Thanks! Trygve On Wed, Nov 26, 2008 at 6:15 PM, David Jencks [EMAIL PROTECTED]wrote: It shouldn't. Can you confirm that all you have changed is the password for system in var/security/users.properties?I'm focussed on a couple other projects at the moment but I'll try to find some time to investigate. thanks david jencks On Nov 26, 2008, at 7:50 AM, Trygve Hardersen wrote: Hi I'm developing a project that uses Geronimo trunk. Does the org.apache.geronimo.plugins.monitoring/agent/2.2-SNAPSHOT/car plugin require the password for the system user to be set to manager (i.e. the default)? My server fails to start when I use something else. Is there a way, besides changing plan.xml for the plugin, to set a different password? Thanks in advance! Trygve On Mon, Nov 17, 2008 at 10:37 PM, [EMAIL PROTECTED] wrote: Author: djencks Date: Mon Nov 17 13:37:30 2008 New Revision: 718393 URL: http://svn.apache.org/viewvc?rev=718393view=rev Log: GERONIMO-4415 start of code cleanup and use of jpa in console. Also add a server assembly for testing
[BUILD] branches/2.0: Failed for Revision: 724224
Geronimo Revision: 724224 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20081207/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.0/20081207/unit-test-reports mvn install:install-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), openqa (http://maven.openqa.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:0.8.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.openqa.selenium.client-drivers -DartifactId=selenium-java-client-driver \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.client-drivers -DartifactId=selenium-java-client-driver \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:0.8.1 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT from the specified remote repositories: central (http://repo1
[jira] Created: (GERONIMODEVTOOLS-550) Sharedlib problems when root directory of the project in the Eclipse workspace is different than project name
Sharedlib problems when root directory of the project in the Eclipse workspace is different than project name - Key: GERONIMODEVTOOLS-550 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-550 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.2, 2.2.0, 2.1.4 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.0.2, 2.2.0, 2.1.4 Problem is that the first segment of the output directory in the classpath entry for the project is always the name of the project,, not the subdirectory in the Eclipse workspace where the project resides. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] DayTrader 2.1.3 release
Does anybody have any information on this? I'm a bit reluctant to vote +1 on this given that our released artifacts don't include everything produced by the build. Joe Joe Bohn wrote: Donald Woods wrote: I was thinking of going with what we have, which is to manually install the app clients. There are instructions in the README on how to do that. I'm confused by this. The tomcat client plugins *are* built when you do a local build (as the README mentions) ... and supposedly they can be installed as plugins according to the README as well (I didn't try this). So why are these tomcat client car files not included in the staging-repo content that we are voting on? We're voting on both the source and the artifacts ... so if the source when built produces the artifacts it seems like we should be voting on those too. BTW, only the tomcat cars exist as an archive file ... there are jetty versions but they only exist in an unpacked form. Here are the artifacts for the clients produced by the build: ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car ./daytrader-tomcat/target/daytrader-streamer-client-2.1.3.car ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car ./daytrader-tomcat/target/daytrader-ws-client-2.1.3.car ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car Is there some strange build processing that is creating these which is not honored by the mvn release plugin? Joe Maybe we can get them setup as plugins in daytrader/trunk for the 2.2 release. -Donald Lin Sun wrote: Hi Donald, Thanks for getting this out for vote! Do we plan to allow users to install the app client as G plugin? If so, I think there is a manual work, that is to add the app client's plugin.xml file to the plugin catalog (geronimo-plugins.xml). I think we've got code to pack the app client car file and copy it onto local .m2 repo. Thanks Lin On Tue, Dec 2, 2008 at 5:03 PM, Donald Woods [EMAIL PROTECTED] wrote: I'm working on updating the daytrader/branches/2.1 for a 2.1.3 release (will rename it to branches/2.1.3 shortly.) Once everything is ready, I'll put it up for a vote. BTW - I'm not creating a branches/2.1 for on-going maintenance, as if it is ever needed, we can copy over the 2.1.3 tag to create it. I'm just wanting to get this overdue Daytrader 2.1.x out so we can focus on the 2.2 release. -Donald
Re: [DISCUSS] Release Concurrent Spec jar (1.0) version 1.0-EA
ummm ... does anybody else want to vote (or comment) beyond Jarek and myself? Joe Joe Bohn wrote: Discussion thread for Concurrent Spec release 1.0-EA Joe
Re: license headers
On Dec 6, 2008, at 8:02 PM, David Jencks wrote: I noticed that one plan file in samples/trunk had an obsolete license header. Does anyone have a tool to check for correct headers and the time and inclination to run it on the samples? Rat checks for Apache src license headers, but doesn't distinguish between old and new-style headers. When we first made the change of license headers, I used a simple grep to look for offenders. I use to run before a release, but looks like a some bad headers have slipped in... This works pretty well: grep -Rni --include=*.java --include=*.xml copyright 2 * or grep -Rni --exclude=NOTICE --exclude=LICENSE copyright 2 * --kevan
[BUILD] branches/2.0: Failed for Revision: 724266
Geronimo Revision: 724266 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20081208/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.0/20081208/unit-test-reports mvn install:install-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), openqa (http://maven.openqa.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:0.8.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.openqa.selenium.client-drivers -DartifactId=selenium-java-client-driver \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.client-drivers -DartifactId=selenium-java-client-driver \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.client-drivers:selenium-java-client-driver:jar:0.8.1 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.openqa.selenium.server -DartifactId=selenium-server \ -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT 2) org.openqa.selenium.server:selenium-server:jar:0.8.1 -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-selenium:jar:2.0.3-SNAPSHOT from the specified remote repositories: central
Re: [Doc]Duplicate pages on monitoring topic, your comments appreciated.
Thanks for pointing this out. A couple of comments from me: 1. Maybe merging the two is better than simply keeping the second link. For example the first link mentioned that we can Select more information to display by adding a second graph. As the two data series scroll in time, we will be able to detect any correlation between the data. 2. If we keep the second link, and remove the first one, I suggest that we edit their parent page as well: http://cwiki.apache.org/confluence/display/GMOxDOC22/Monitoring+the+health+of+the+Apache+Geronimo+server Teresa From: chi runhua [EMAIL PROTECTED] To: dev@geronimo.apache.org Sent: Friday, December 5, 2008 2:05:00 PM Subject: [Doc]Duplicate pages on monitoring topic, your comments appreciated. Hi all, I found two pages about monitoring status of servers with similar content. So I'm suggesting to keep only one of them in G2.2 Doc.. 1. http://cwiki.apache.org/confluence/display/GMOxDOC22/Monitoring+status+of+servers 2. http://cwiki.apache.org/confluence/display/GMOxDOC22/Monitoring Personally, I prefer No.2 because this one is more in detail. Jeff Chi
[jira] Commented: (GERONIMO-3655) Invalid MdbInstanceFactory behaviour
[ https://issues.apache.org/jira/browse/GERONIMO-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12654328#action_12654328 ] Manu T George commented on GERONIMO-3655: - Still fails in 2.1 branch. Will need to bump up the openejb version to 3.1 to fix this Invalid MdbInstanceFactory behaviour Key: GERONIMO-3655 URL: https://issues.apache.org/jira/browse/GERONIMO-3655 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.0.1, 2.0.2 Environment: Microsoft Windows XP, Sun Java 1.5.0_10, Apache Geronimo 2.0.1 Reporter: Alexei Akimov Attachments: badmdb.zip org.apache.openejb.core.mdb.MdbInstanceFactory class pass invalid ThreadContext instance to ThreadContext.exit method at line 263 of its constructBean method. This brokes stack-like usage of ThreadContext objects and leads to problems during lazy initialization of ejb components when they called for the first time from the web tier. In particular ClassCastException is thrown in org.apache.geronimo.tomcat.interceptor.InstanceContextBeforeAfter.before() at line 49, because ConnectorInstanceContextImpl instance is returned instead of SharedConnectorInstanceContext instance. This error results in that org.apache.geronimo.tomcat.listener.DispatchListener.beforeDispatch method does not put any data into the current context stack so when the afterDispatch method is called the current context stack throws java.util.EmptyStackException. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
