[jira] Commented: (GERONIMO-4363) Update plugin metadata (especially category) to represent function of a plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770403#action_12770403 ] Forrest Xia commented on GERONIMO-4363: --- tried CSA function and seems the plugins were properly categorized, and I can use key words to filter expected plugins. so maybe this jira could be fixed. Update plugin metadata (especially category) to represent function of a plugin -- Key: GERONIMO-4363 URL: https://issues.apache.org/jira/browse/GERONIMO-4363 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.2 Reporter: Lin Sun Assignee: Lin Sun Fix For: Wish List In addition to plugin profiles, we decided on dev list that we can assign tags to plugins. Category was proposed to tag all the plugins. For example, if a plugin has JMS function, we want to make sure word JMS exists in the plugin's category. If a plugin belongs to admin console, we want to make sure word Administration Console exists in the plugin's category. I'll perform a scan on our plugins and update them, so that changes in G4362 will work accurately. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4362) Allow users to filter plugins on server assembly portlet allow users to turn on expert users mode
[ https://issues.apache.org/jira/browse/GERONIMO-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-4362. - Allow users to filter plugins on server assembly portlet allow users to turn on expert users mode --- Key: GERONIMO-4362 URL: https://issues.apache.org/jira/browse/GERONIMO-4362 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Lin Sun Assignee: Lin Sun Fix For: 2.2 Per discussion on dev list - http://www.nabble.com/Re%3A-svn-commit%3A-r702586---in--geronimo-server-trunk-plugingroups-console-jetty%3A-.--pom.xml-src--src-main--src-main-history--src-main-history-dependencies.xml-src-main-plan--to19871519s134.html#a19871519 It is desired to have some sort of filter function on the custom server assembly portlet. If a user types ejb, he can see all ejb related plugins. If a user types ejb jms, he can see all ejb and jms related plugins. It is also desired to have an expert user mode so that a user can see all the system plugins optionally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4362) Allow users to filter plugins on server assembly portlet allow users to turn on expert users mode
[ https://issues.apache.org/jira/browse/GERONIMO-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770405#action_12770405 ] Forrest Xia commented on GERONIMO-4362: --- verified the impl. and seems it works well. So it may be closed now. Allow users to filter plugins on server assembly portlet allow users to turn on expert users mode --- Key: GERONIMO-4362 URL: https://issues.apache.org/jira/browse/GERONIMO-4362 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Lin Sun Assignee: Lin Sun Fix For: 2.2 Per discussion on dev list - http://www.nabble.com/Re%3A-svn-commit%3A-r702586---in--geronimo-server-trunk-plugingroups-console-jetty%3A-.--pom.xml-src--src-main--src-main-history--src-main-history-dependencies.xml-src-main-plan--to19871519s134.html#a19871519 It is desired to have some sort of filter function on the custom server assembly portlet. If a user types ejb, he can see all ejb related plugins. If a user types ejb jms, he can see all ejb and jms related plugins. It is also desired to have an expert user mode so that a user can see all the system plugins optionally. -- 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: 830071
Geronimo Revision: 830071 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/unit-test-reports Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), ibiblio.org (http://repo.exist.com/maven2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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:597) 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.apache.felix:org.osgi.core:jar:1.5.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.felix -DartifactId=org.osgi.core -Dversion=1.5.0-SNAPSHOT -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.apache.felix -DartifactId=org.osgi.core -Dversion=1.5.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.felix:org.osgi.core:jar:1.5.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm:jar:3.1_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.bundles -DartifactId=asm -Dversion=3.1_1-SNAPSHOT -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.apache.geronimo.bundles -DartifactId=asm -Dversion=3.1_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm:jar:3.1_1-SNAPSHOT 3) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.bundles -DartifactId=asm-commons -Dversion=3.1_1-SNAPSHOT -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.apache.geronimo.bundles -DartifactId=asm-commons -Dversion=3.1_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), ibiblio.org (http
[jira] Commented: (GERONIMO-4906) DB connection problem
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770416#action_12770416 ] Jean-Jacques Parent commented on GERONIMO-4906: --- I am still investigating the origin of my problem, may be some additional informations: I used a special oracle driver with trace functionalities. It was not possible to set a high level of logs because of bad performances but we have the same information: connection interrupted (stopped). I succeeded to reproduce the problem in my development environment by unplugging the network cable of my server. Indeed, the following actions in the application after re-plugging the cable are giving: connection interrupted. Some questions according to this kind of situation: 1 is this means that after a problem, maybe a network one, all the connection pool managed by Geronimo falls into an invalidate state and this pool will always give a connection even if this one is broken. (Unless this connection is removed by the idle timeout or by restarting the server) 2 Why the Geronimo pool does not killed those corrupted connexions? 3 is it a good idea to set the connection idle timeout to 0, in order to force the pool to kill the maximum of connections especially when those become unsafe? We are still investigating the reasons why the connection pool become unsafe, but I don't understand why broken connections are still available in the pool... DB connection problem - Key: GERONIMO-4906 URL: https://issues.apache.org/jira/browse/GERONIMO-4906 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 2.0.1 Environment: Geronimo running on Windows server 2003 (Virtual Machine) Oracle 10g Driver jdbc 10.2.0.1 Spring-Version: 2.0.2 Hibernate-Version: 3.2.0.cr4 Reporter: Jean-Jacques Parent Attachments: config.xml, Errors_samples.txt Your expertise on my problem will be helpful. Once a week, I get a DB connectivity problem with my application. No new DB transaction can be open. After a few minutes, the situation can come back as normal, if not the Geronimo server has to be restarted. I ask our technicians about connectivity and performance, but they found nothing wrong. I give you the stack trace in attachment with the different kind of error message. You will see that it looks like a network problem, but maybe this could also be due to a jdbc, timeout...? My pool configuration is as follow Pool Min Size:25 The minimum number of connections in the pool. The default is 0. Pool Max Size:140 The maximum number of connections in the pool. The default is 10. Blocking Timeout: 5000 (in milliseconds) The length of time a caller will wait for a connection. The default is 5000. Idle Timeout: 5(in minutes) How long a connection can be idle before being closed. The default is 15. Any help will be appreciate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4892) Farm Deployment Error if deploy more than one applications
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770484#action_12770484
]
Amit puri commented on GERONIMO-4892:
-
I am facing same problem in Geronimo 2.1.4 as well when I tried two war files.
Here Application get deployed on all the cluster members but did not start
because of this error(org.apache.geronimo.kernel.GBeanAlreadyExistsException:
GBean already registered: geronimo:J2EEServer=geronimo,nodeName=NODE-B) When I
started the second application from Admin console of individual server
instances, it started fine without any exception.
Farm Deployment Error if deploy more than one applications
--
Key: GERONIMO-4892
URL: https://issues.apache.org/jira/browse/GERONIMO-4892
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: commands
Affects Versions: 2.2
Environment: oS: winxp and win2003
Reporter: viola.lu
Attachments: TwoFarm.zip
Win2003 as master node( NODE2) with config.xml
...
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node1
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE1/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns10=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns8=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns14_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns12_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10_=http://geronimo.apache.org/xml/ns/attributes-1.2;
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=protocolrmi/ns:property
ns:property name=host9.186.10.167/ns:property
ns:property name=port1099/ns:property
ns:property name=urlPathJMXConnector/ns:property
ns:property name=localfalse/ns:property
/ns:javabean
/attribute
/gbean
gbean name=NodeInfo
attribute name=name${ClusterNodeName}/attribute
/gbean
gbean name=ClusterInfo
attribute name=name${FarmName}/attribute
/gbean
/module
...
WinXP as node 1
WinXp. as node 1
..
module name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car
gbean
name=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node2
gbeanInfo=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=nameNODE2/attribute
attribute
propertyEditor=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor
name=extendedJMXConnectorInfo
ns:javabean
class=org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo
xmlns= xmlns:ns20=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns10=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns22=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
xmlns:ns12=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns14=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns16=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns18=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns19=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6_=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns4=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns6=http://geronimo.apache.org/xml/ns/plugins-1.3;
xmlns:ns7=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns8=http://geronimo.apache.org/xml/ns/attributes-1.2;
xmlns:ns18_=http://geronimo.apache.org/xml/ns/attributes-1.2;
[jira] Created: (GERONIMO-4933) Some optimization for loaded bundle checking
Some optimization for loaded bundle checking Key: GERONIMO-4933 URL: https://issues.apache.org/jira/browse/GERONIMO-4933 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: kernel, osgi Affects Versions: 3.0 Reporter: Ivan Priority: Minor Fix For: 3.0 The full loop checking whether the bundle is loaded is less efficient. Seems that OSGI will maintaine a location-bundle map inside, if the bundle of the same location is installed, the existing bundle will return immediently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4933) Some optimization for loaded bundle checking
[ https://issues.apache.org/jira/browse/GERONIMO-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-4933: --- Attachment: GERONIMO-4933.patch Both the original code logic and the proposed patch has a pre-condition: we always use the same URL for bundle installation. Or we would get symbolic name existed exception. Please help to review the patch, thanks ! Some optimization for loaded bundle checking Key: GERONIMO-4933 URL: https://issues.apache.org/jira/browse/GERONIMO-4933 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel, osgi Affects Versions: 3.0 Reporter: Ivan Priority: Minor Fix For: 3.0 Attachments: GERONIMO-4933.patch The full loop checking whether the bundle is loaded is less efficient. Seems that OSGI will maintaine a location-bundle map inside, if the bundle of the same location is installed, the existing bundle will return immediently. -- 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: 830158
Geronimo Revision: 830158 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/unit-test-reports Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) 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.apache.felix:org.osgi.core:jar:1.5.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.felix -DartifactId=org.osgi.core -Dversion=1.5.0-SNAPSHOT -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.apache.felix -DartifactId=org.osgi.core -Dversion=1.5.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.felix:org.osgi.core:jar:1.5.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm:jar:3.1_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.bundles -DartifactId=asm -Dversion=3.1_1-SNAPSHOT -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.apache.geronimo.bundles -DartifactId=asm -Dversion=3.1_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm:jar:3.1_1-SNAPSHOT 3) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.bundles -DartifactId=asm-commons -Dversion=3.1_1-SNAPSHOT -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.apache.geronimo.bundles -DartifactId=asm-commons -Dversion=3.1_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.bundles:asm-commons:jar:3.1_1-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http
[jira] Created: (GERONIMO-4934) Make application client container work under osgi
Make application client container work under osgi - Key: GERONIMO-4934 URL: https://issues.apache.org/jira/browse/GERONIMO-4934 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller updated GERONIMO-4871: --- Fix Version/s: (was: 2.2) 2.2.1 Good guess, but doesn't seem to help. Since I created a 2.2.1 release in Jira, moving the fix version to there... Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reopened GERONIMO-4871: Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 830141
Geronimo Revision: 830141 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091027/build-0800.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091027
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 42 minutes 22 seconds
[INFO] Finished at: Tue Oct 27 08:48:02 EDT 2009
[INFO] Final Memory: 322M/998M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091027/logs-0800-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/2.2/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/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:51.751
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.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:22.863)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:38.753)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:47.152)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:24.028)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:40.474)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:38.545)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:02.718)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:58.351)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:08.179)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:52.227)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:38.100)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:37.227)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:40.472)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:12.778)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:22.092)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:57.428)
[INFO] enterprise-testsuite/sec-client-tests RUNNING
[INFO] enterprise-testsuite/sec-client-tests SUCCESS (0:00:34.312)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:59.276)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:58.362)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:36.859)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:35.090)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770567#action_12770567 ] Quintin Beukes commented on GERONIMO-4871: -- It has to be something that changed between that 2. I'm sure that part is obvious for anyone reading this. It has to also be something the 2 does different. Perhaps related to a JavaAgent or JMX? Something else that captures the signal? Have you tried echoing the command geronimo.sh uses to start and then running it manually, removing arguments until you find on that could possibly trigger this? Does the same happen when you run the minimal server? Have you tried to remove modules until you could perhaps find one, which without it everything works? If I had a Mac I would have a look at it, but ... : Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770576#action_12770576 ] Quintin Beukes commented on GERONIMO-4871: -- Check if the -Xrs option is specified perhaps, by echoing the final command used to start the JVM. -Xrs disables this. Further, try adding a shutdown hook and the doing a SIGTERM. Check if the shutdown hooks execute, but the thread dump doesn't work, or if neither work. Q Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770581#action_12770581 ] Quintin Beukes commented on GERONIMO-4871: -- One final note. Perhaps the logging level is configured differently. Try setting the log levels to trace on the Geronimo logging and the JRE logging - in fact, on all logging frameworks accessible. Maybe somehow it logs to another file somewhere. I had a look around on google, and it does seem like there are cases where people had to change their logging levels in order to see the thread dumps. Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770583#action_12770583 ] Quintin Beukes commented on GERONIMO-4871: -- Unless I imagined things, it looks like Geronimo is now capturing stdout/stderr and sending it to the geronimo.log instead of geronimo.out. And also depending on the output type it prints a progress bar. This wasn't the case in 2.1. I had to look at all my System.out.println() statements in geronimo.out, where the other day I found they were being sent to geronimo.log after the server completed starting. If this is programmatically, maybe it's related to this. It comes back to my previous comment. Maybe it IS doing the thread dump, you just can't find to where, or the pipe is broken and it goes into nothingness. Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?
[ https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770596#action_12770596 ] Kevan Miller commented on GERONIMO-4871: Thanks for the ideas Quintin. Agreed that there's something unique in G 2.2. I don't know of any javaagent changes in 2.2. JMX changed, but current branches/2.1 has also changed the way that JMX is started in a 2.1.5-SNAPSHOT server. There are some new/updated libraries in 2.2, also. I'm running geronimo in foreground (geronimo.sh run) and we don't capture STDOUT or redirect to file. The same Geronimo binary works fine on Linux using the same command to start (i.e. prints thread stacks), testing on Mac OS doesn't work. So, something in 2.2 seems to cause different behavior unique to Mac OS. In the scheme of things, this is relatively minor. And may well be a Mac OS JDK bug... Will leave it open for now... Something blocking 'kill -3' signals? - Key: GERONIMO-4871 URL: https://issues.apache.org/jira/browse/GERONIMO-4871 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Fix For: 2.2.1 I occasionally use 'kill -3' to cause a java process to dump all thread stacks. For some reason, this isn't working on Geronimo 2.2 -- 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: 830291
Geronimo Revision: 830291 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), central (http://repo1.maven.org/maven2) Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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:597) 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.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), central (http://repo1.maven.org/maven2) Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project
[jira] Assigned: (GERONIMO-4658) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else.
[ https://issues.apache.org/jira/browse/GERONIMO-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-4658: -- Assignee: David Jencks (was: Ivan) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else. Key: GERONIMO-4658 URL: https://issues.apache.org/jira/browse/GERONIMO-4658 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Attachments: GERONIMO-4658.patch, GERONIMO-4658_2.patch Should be able to edit artifact-aliases in the console. I think they are available through the local attribute manager gbean. They can certainly be installed there. In particular, when adding a jar, you should be able to add an artifact alias at the same time so it replaces something else. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4921) Use OSGI's way to manage the server repository
[ https://issues.apache.org/jira/browse/GERONIMO-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12770692#action_12770692 ] David Jencks commented on GERONIMO-4921: I think we need to modify the pax-mvn-url code to send reference urls to felix (or whatever else is needed). For native libraries, there must be a better solution than copying the whole bundle. I'm just not worried about this yet. Use OSGI's way to manage the server repository -- Key: GERONIMO-4921 URL: https://issues.apache.org/jira/browse/GERONIMO-4921 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Ivan Fix For: 3.0 Some install/uninstall action should be done via OSGI API or Karaf functions more easily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 830406
Geronimo Revision: 830406 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091027/build-2000.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091027/unit-test-reports
Downloading:
http://svn.apache.org/repos/asf/openejb/repo//org/apache/xbean/xbean-asm-shaded/3.6/xbean-asm-shaded-3.6.jar
Downloading:
http://download.java.net/maven/1/org.apache.xbean/jars/xbean-asm-shaded-3.6.jar
Downloading:
http://repo.exist.com/maven2/org/apache/xbean/xbean-asm-shaded/3.6/xbean-asm-shaded-3.6.jar
118K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0a394260d8d16ba233796bc68b5f4188442e37fe'; remote =
'3e5ce3998772b6a8ccd401ee1caf33fd8949c8d2' - RETRYING
Downloading:
http://repo.exist.com/maven2/org/apache/xbean/xbean-asm-shaded/3.6/xbean-asm-shaded-3.6.jar
118K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'0a394260d8d16ba233796bc68b5f4188442e37fe'; remote =
'3e5ce3998772b6a8ccd401ee1caf33fd8949c8d2' - IGNORING
Downloading:
http://people.apache.org/repo/m2-incubating-repository/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar
Downloading:
http://svn.apache.org/repos/asf/openejb/repo//org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar
Downloading:
http://download.java.net/maven/1/org.codehaus.swizzle/jars/swizzle-stream-1.0.1.jar
Downloading:
http://repo.exist.com/maven2/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar
42K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository/quartz/quartz/1.5.2/quartz-1.5.2.jar
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository/quartz/quartz/1.5.2/quartz-1.5.2.jar
Downloading:
http://svn.apache.org/repos/asf/openejb/repo//quartz/quartz/1.5.2/quartz-1.5.2.jar
Downloading: http://download.java.net/maven/1/quartz/jars/quartz-1.5.2.jar
Downloading: http://repo.exist.com/maven2/quartz/quartz/1.5.2/quartz-1.5.2.jar
379K downloaded
Downloading:
http://repo.exist.com/maven2/org/apache/openejb/openejb-ejbd/3.1.2/openejb-ejbd-3.1.2.jar
54K downloaded
Downloading:
http://repo.exist.com/maven2/org/apache/openejb/openejb-server/3.1.2/openejb-server-3.1.2.jar
73K downloaded
Downloading:
http://repo.exist.com/maven2/org/apache/openejb/openejb-client/3.1.2/openejb-client-3.1.2.jar
195K downloaded
Downloading:
http://repo.exist.com/maven2/org/apache/openejb/openejb-multicast/3.1.2/openejb-multicast-3.1.2.jar
27K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference :
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not
a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference :
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not
a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 30 source files to
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/GeronimoSecurityService.java:[53,45]
[deprecation]
login(java.lang.String,javax.security.auth.callback.CallbackHandler) in
org.apache.geronimo.security.ContextManager has been deprecated
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EjbModuleImplGBean.java:[35,8]
cannot find symbol
symbol : constructor
EjbModuleImpl(java.lang.String,org.apache.geronimo.management.J2EEServer,org.apache.geronimo.management.J2EEApplication,java.lang.String,java.util.Collectioncapture
of ? extends
org.apache.geronimo.management.EJB,java.lang.ClassLoader,org.apache.geronimo.openejb.OpenEjbSystem,org.apache.openejb.assembler.classic.EjbJarInfo)
location: class org.apache.geronimo.openejb.EjbModuleImpl
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EjbModuleImplGBean.java:[39,8]
cannot find symbol
symbol : method start()
location: class org.apache.geronimo.openejb.EjbModuleImplGBean
/home/geronimo/geronimo/2.2/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb
[jira] Closed: (GERONIMO-4658) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else.
[ https://issues.apache.org/jira/browse/GERONIMO-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4658. -- Resolution: Fixed Fix Version/s: 3.0 2.2 rev rev 830386, 830411 in trunk The patch had duplicates in the new files, easy to fix. I also fixed up exception handling a bit and alphateized the aliases. This could use some documentation since if you edit the LHS of an alias it creates a new entry rather than replacing the old one. Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else. Key: GERONIMO-4658 URL: https://issues.apache.org/jira/browse/GERONIMO-4658 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2, 3.0 Attachments: GERONIMO-4658.patch, GERONIMO-4658_2.patch Should be able to edit artifact-aliases in the console. I think they are available through the local attribute manager gbean. They can certainly be installed there. In particular, when adding a jar, you should be able to add an artifact alias at the same time so it replaces something else. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4927) keystorePass attribute on TomcatWebSSLConnector GBean should be encrypted/obscured
[ https://issues.apache.org/jira/browse/GERONIMO-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4927: --- Affects Version/s: (was: 2.2.1) 2.2 2.1.5 Fix Version/s: (was: 2.2) 2.2.1 tomcat ssl should be using one of out keystore gbeans so it doesn't need to know about the password at all. Not gonna happen for 2.2 anyway... keystorePass attribute on TomcatWebSSLConnector GBean should be encrypted/obscured -- Key: GERONIMO-4927 URL: https://issues.apache.org/jira/browse/GERONIMO-4927 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.5, 2.2 Reporter: Kevan Miller Fix For: 2.1.5, 2.2.1, 3.0 keystorePass does not conform to the current convention for encrypting/obscuring GBean attributes. Currently, attribute names with 'password' will be encrypted. We should either recognize keystorePass as an attribute requiring encryption or add a new keystorePassword attribute and start using that (with some appropriate migration logic, if a 'keystorePass' is configured). I guess I prefer the latter option. Other opinions? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4646) Warn during a war deployment, if no WEB-INF/web.xml file is found
[ https://issues.apache.org/jira/browse/GERONIMO-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4646. -- Resolution: Fixed Fix Version/s: (was: 2.1.5) 2.2 rev 830415. Not fixed in 2.1.5. Not appropriate for trunk since 3.0 encourages annotations instead of web.xml. Warn during a war deployment, if no WEB-INF/web.xml file is found - Key: GERONIMO-4646 URL: https://issues.apache.org/jira/browse/GERONIMO-4646 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.4, 2.2 Reporter: Kevan Miller Fix For: 2.2 Attachments: GERONIMO-4646 2.patch, GERONIMO-4646 2.patch, GERONIMO-4646.patch, GERONIMO-4646.patch, GERONIMO-4646.PNG Per the specs, a WAR without a WEB-INF/web.xml is a valid WAR file. However, it's also an indication of a poorly formatted WAR. It seems like it would be useful to log a warning, if we don't find a WEB-INF/web.xml file, just like we log a WARN, if a geronimo-web.xml file is not found: 2009-05-25 22:13:12,535 WARN [TomcatModuleBuilder] Web application . does not contain a WEB-INF/geronimo-web.xml deployment plan. This may or may not be a problem, depending on whether you have things like resource references that need to be resolved. You can also give the deployer a separate deployment plan file on the command line. -- 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: 830417
Geronimo Revision: 830417 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20091027/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) 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.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.framework:geronimo-kernel:bundle:3.0-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project
Re: Singletons in Geronimo
The changes look good, though I seem to be running into an issue creating the car for the wadi stuff. Not sure what might be happening and looking for ideas. Here's the -e output: [INFO] [car:package] [INFO] Packaging module configuration: /Users/dblevins/work/ geronimo-22-branch/plugins/openejb/openejb-clustering-wadi/target/work/ plan.xml [INFO] GBean references are not using proxies [INFO] ClassLoading behaviour has changed. The Original Classloading mode is in effect. If you are experiencing a problem you can change the behaviour by specifying - DXorg.apache.geronimo.kernel.config.MPCLSearchOption= property. Specify =safe to revert to the original behaviour. This is a temporary change until we decide whether or not to make it permanent for the 2.0 release [INFO] Started deployer: org.apache.geronimo.framework/geronimo-gbean- deployer/2.2-SNAPSHOT/car [INFO] The Strict Manifest Classpath processing mode is in effect. This option can be altered by specifying - DXorg.apache.geronimo.deployment.LenientMFCP=true|false Specify =true for more lenient processing such as ignoring missing jars and references that are not spec compliant. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] could not package plugin Embedded error: Unable to create configuration for deployment [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: could not package plugin at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 584) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:292) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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:592) 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.plugin.MojoExecutionException: could not package plugin at org .apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java: 212) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 559) ... 16 more Caused by: org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org .apache .geronimo .deployment .DeploymentContext.createTempConfiguration(DeploymentContext.java:151) at org .apache .geronimo.deployment.DeploymentContext.init(DeploymentContext.java: 131) at org .apache .geronimo.deployment.DeploymentContext.init(DeploymentContext.java: 111) at org .apache .geronimo .deployment .service .ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:227) at org .apache .geronimo .deployment .service .ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257) 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:592) at org .apache .geronimo .gbean .runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org .apache .geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org .apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java: 850) at
