[jira] [Commented] (GERONIMO-6286) o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places
[ https://issues.apache.org/jira/browse/GERONIMO-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215364#comment-13215364 ] Forrest Xia commented on GERONIMO-6286: --- They looks good to me, thank you very much for the patches. Want to know if you did some testing with those patches? > o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places > > > Key: GERONIMO-6286 > URL: https://issues.apache.org/jira/browse/GERONIMO-6286 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 > (Tikanga); Java JDK1.6.0_25 >Reporter: Russell E Glaue > Labels: geronimo > Attachments: geronimo-6286-BaseJava-StartServer-StartClient.patch, > geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch > > > There are some code files still using org.apache.geronimo.home.dir when > instead they should ideally be using org.apache.geronimo.server.dir . > - > framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6272) server can not be started if installation path contains bracket "()"
[ https://issues.apache.org/jira/browse/GERONIMO-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215358#comment-13215358 ] Forrest Xia commented on GERONIMO-6272: --- Yes, agreed. It might be a karaf issue. > server can not be started if installation path contains bracket "()" > > > Key: GERONIMO-6272 > URL: https://issues.apache.org/jira/browse/GERONIMO-6272 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: win7 64bit,oracle jdk 1.6.0_26 >Reporter: Saphen Qiu > Labels: bracket, startup > > I install geronimo on this path c:\New folder (x), I can not start server > with any commands, and get the following errors. > But if I rename the folder to "New folder" without "()", then the server can > be started successfully. > *** > C:\New folder (x)\bin>geronimo.bat run -c > Using GERONIMO_HOME: C:\New folder (x) > Using GERONIMO_TMPDIR: C:\New folder (x)\var\temp > Using JRE_HOME:C:\Program\Java\jdk1.6.0_26\jre > __ _ > / /___ _ (_) ___ >/ / __ / _ \/ ___/ __ \/ __ \/ // __ `__ \/ __ \ > / /_/ // __/ / / /_/ / / / / // / / / / / /_/ / > \/ \___/_/ \/_/ /_/_//_/ /_/ /_/\/ > Apache Geronimo (3.0-beta-2-SNAPSHOT) > Hit '' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '' or 'osgi:shutdown' to shutdown Geronimo. > geronimo> 2012-02-14 15:39:27,135 WARN [FeaturesServiceImpl] Unable to add > features repository mvn:org.apache.geronimo. > framework/karaf-framework/3.0-beta-2-SNAPSHOT/xml/features at startup > java.lang.RuntimeException: URL > [mvn:org.apache.geronimo.framework/karaf-framework/3.0-beta-2-SNAPSHOT/xml/features] > cou > ld not be resolved. > at > org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195) > at > org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:49) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:918) > 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.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:226) > at > org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:824) > at > org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:636) > at > org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724) > at > org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) > at > org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) > at > org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl > .java:640) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.j > ava:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206 > ) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 2012-02-14 15:39:27,830 WARN [JexlEngine] > org.apache.aries.blueprint.ext.JexlExpressionParser.evaluate@56![0,10]: 'kara > f.base;' undefined variable
[jira] [Commented] (GERONIMO-6284) Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/
[
https://issues.apache.org/jira/browse/GERONIMO-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215356#comment-13215356
]
Forrest Xia commented on GERONIMO-6284:
---
Hi Russell,
See change http://svn.apache.org/viewvc?view=rev&rev=1291886 for how to fix the
start failure when deploying to the new target.
Thanks for continuous testing.
Forrest
> Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/
> --
>
> Key: GERONIMO-6284
> URL: https://issues.apache.org/jira/browse/GERONIMO-6284
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4
> (Tikanga)
>Reporter: Russell E Glaue
>Assignee: Forrest Xia
>Priority: Minor
> Labels: geronimo
>
> Cannot deploy to a Geronimo Instance. Deploy expects GERONIMO_HOME/var/...
> Create a new Geronimo instance as documented in
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
> - remove GERONIMO_HOME/etc
> - remove GERONIMO_HOME/var
> - create the empty file GERONIMO_HOME/var
> Start the Geronimo instance as follows:
> {noformat:borderStyle=solid}
> linux$ cd /opt/geronimo3/gserv1
> linux$ env JAVA_HOME=/usr/jdk1.6.0 GERONIMO_SERVER=gserv1
> /opt/geronimo3/bin/geronimo run
> {noformat}
> Create a second repository for the new instance
> - mkdir {{gserv1/repository}}
> - Create {{gserv1/repository.xml}} as documented in
> https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html
> {noformat:borderStyle=solid}
> http://geronimo.apache.org/xml/ns/deployment-1.2";>
>
>
>org.example.configs
> myrepo
> 2.2
> car
>
>
>
> org.apache.geronimo.framework
> j2ee-system
> 2.2
> car
>
>
>
>
>
> class="org.apache.geronimo.system.repository.Maven2Repository">
>gserv1/repository/
>false
>
> ServerInfo
>
>
> class="org.apache.geronimo.system.configuration.RepositoryConfigurationStore">
>
>Repo2
>
>
>
> {noformat}
> Deploy the repository.xml file
> {noformat:borderStyle=solid}
> linux$ cd /opt/geronimo3
> linux$ env JAVA_HOME=/usr/jdk1.6.0 GERONIMO_SERVER=gserv1
> /opt/geronimo3/bin/deploy -port 1199 deploy
> /opt/geronimo3/gserv1/repository.xml
> {noformat}
> The following error results:
> {noformat:borderStyle=solid}
> Using GERONIMO_HOME: /opt/geronimo3
> Using GERONIMO_SERVER: /opt/geronimo3/gserv1
> Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
> Using JRE_HOME:/usr/jdk1.6.0_25/jre
> 2012-02-21 15:33:44,695 ERROR [GBeanInstanceState] Error while starting;
> GBean is now in the FAILED state:
> abstractName="org.apache.geronimo.framework/online-deployer/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/online-deployer/3.0-SNAPSHOT/car,j2eeType=AttributeStore,name=AttributeManager"
> java.io.IOException: Unable to create directory for
> list:/opt/geronimo3/var/config
> at
> org.apache.geronimo.system.configuration.LocalAttributeManager.ensureParentDirectory(LocalAttributeManager.java:607)
> at
> org.apache.geronimo.system.configuration.LocalAttributeManager.load(LocalAttributeManager.java:352)
> at
> org.apache.geronimo.system.configuration.LocalAttributeManager.doStart(LocalAttributeManager.java:561)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1000)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555)
> at
> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
> at
> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
> at
> org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
> at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176)
> at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45)
> at
> org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105)
> at
> org.apache.geronimo.gbean.
[jira] [Updated] (GERONIMO-6286) o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places
[ https://issues.apache.org/jira/browse/GERONIMO-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Russell E Glaue updated GERONIMO-6286: -- Attachment: geronimo-6286-BaseJava-StartServer-StartClient.patch geronimo-6286-BaseJava-StartServer-StartClient.patch Modifies: - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java Please review this patch. I thought it best to keep this one simple and require the user to specify the full path for the org.apache.geronimo.server.dir if they wish to define it. > o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places > > > Key: GERONIMO-6286 > URL: https://issues.apache.org/jira/browse/GERONIMO-6286 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 > (Tikanga); Java JDK1.6.0_25 >Reporter: Russell E Glaue > Labels: geronimo > Attachments: geronimo-6286-BaseJava-StartServer-StartClient.patch, > geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch > > > There are some code files still using org.apache.geronimo.home.dir when > instead they should ideally be using org.apache.geronimo.server.dir . > - > framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (GERONIMO-6286) o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places
[ https://issues.apache.org/jira/browse/GERONIMO-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215028#comment-13215028 ] Russell E Glaue edited comment on GERONIMO-6286 at 2/23/12 8:37 PM: geronimo-6286-BaseJava-StartServer-StartClient.patch Modifies: - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/BaseJavaCommand.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java Please review this patch. I thought it best to keep this one simple and require the user to specify the full path for the org.apache.geronimo.server.dir if they wish to define it. was (Author: rglaue): geronimo-6286-BaseJava-StartServer-StartClient.patch Modifies: - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java Please review this patch. I thought it best to keep this one simple and require the user to specify the full path for the org.apache.geronimo.server.dir if they wish to define it. > o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places > > > Key: GERONIMO-6286 > URL: https://issues.apache.org/jira/browse/GERONIMO-6286 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 > (Tikanga); Java JDK1.6.0_25 >Reporter: Russell E Glaue > Labels: geronimo > Attachments: geronimo-6286-BaseJava-StartServer-StartClient.patch, > geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch > > > There are some code files still using org.apache.geronimo.home.dir when > instead they should ideally be using org.apache.geronimo.server.dir . > - > framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6286) o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places
[ https://issues.apache.org/jira/browse/GERONIMO-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Russell E Glaue updated GERONIMO-6286: -- Attachment: geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch Modifies: - framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java - framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java - framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java > o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places > > > Key: GERONIMO-6286 > URL: https://issues.apache.org/jira/browse/GERONIMO-6286 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 > (Tikanga); Java JDK1.6.0_25 >Reporter: Russell E Glaue > Labels: geronimo > Attachments: > geronimo-6286-EmbeddedDaemon-CommandUnlockKeystore-DeployUtils.patch > > > There are some code files still using org.apache.geronimo.home.dir when > instead they should ideally be using org.apache.geronimo.server.dir . > - > framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java > - > framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java > - > framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6286) o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places
o.a.g.server.dir should be used instead of o.a.g.home.dir in misc places Key: GERONIMO-6286 URL: https://issues.apache.org/jira/browse/GERONIMO-6286 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Affects Versions: 3.0-beta-1 Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 (Tikanga); Java JDK1.6.0_25 Reporter: Russell E Glaue There are some code files still using org.apache.geronimo.home.dir when instead they should ideally be using org.apache.geronimo.server.dir . - framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java - framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java - framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/DeployUtils.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java - framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6272) server can not be started if installation path contains bracket "()"
[ https://issues.apache.org/jira/browse/GERONIMO-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214875#comment-13214875 ] Russell E Glaue commented on GERONIMO-6272: --- The batch files that start Geronimo obtain the correct path from the system by navigating to GERONIMO_HOME and obtaining that path reported by the system. In this case the path is being passed in with the parenthesis. karaf.base in 3.0-beta is being set to GERONIMO_HOME So I would suppose that either Karaf itself is having an issue with this type of formatted path, or the JexlExpressionParser which handles the resolution of properties is having the issue. However GERONIMO_HOME is being passed in the same in geronimo.bat as -Dorg.apache.geronimo.home.dir="%GERONIMO_HOME%" and -Dkaraf.base="%GERONIMO_HOME%", so I would suppose the issue is more directly related to Karaf itself. So if it is Karaf having the issue and not JexlExpressionParser, then this issue is no related to GERONIMO-6281. The work-around for the time being is of course to use a path with safe characters for GERONIMO_HOME. > server can not be started if installation path contains bracket "()" > > > Key: GERONIMO-6272 > URL: https://issues.apache.org/jira/browse/GERONIMO-6272 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-beta-1 > Environment: win7 64bit,oracle jdk 1.6.0_26 >Reporter: Saphen Qiu > Labels: bracket, startup > > I install geronimo on this path c:\New folder (x), I can not start server > with any commands, and get the following errors. > But if I rename the folder to "New folder" without "()", then the server can > be started successfully. > *** > C:\New folder (x)\bin>geronimo.bat run -c > Using GERONIMO_HOME: C:\New folder (x) > Using GERONIMO_TMPDIR: C:\New folder (x)\var\temp > Using JRE_HOME:C:\Program\Java\jdk1.6.0_26\jre > __ _ > / /___ _ (_) ___ >/ / __ / _ \/ ___/ __ \/ __ \/ // __ `__ \/ __ \ > / /_/ // __/ / / /_/ / / / / // / / / / / /_/ / > \/ \___/_/ \/_/ /_/_//_/ /_/ /_/\/ > Apache Geronimo (3.0-beta-2-SNAPSHOT) > Hit '' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '' or 'osgi:shutdown' to shutdown Geronimo. > geronimo> 2012-02-14 15:39:27,135 WARN [FeaturesServiceImpl] Unable to add > features repository mvn:org.apache.geronimo. > framework/karaf-framework/3.0-beta-2-SNAPSHOT/xml/features at startup > java.lang.RuntimeException: URL > [mvn:org.apache.geronimo.framework/karaf-framework/3.0-beta-2-SNAPSHOT/xml/features] > cou > ld not be resolved. > at > org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195) > at > org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:49) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:918) > 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.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:226) > at > org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:824) > at > org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:636) > at > org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724) > at > org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) > at > org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) > at > org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl > .java:640) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227) > at > java.uti
[jira] [Commented] (GERONIMO-6284) Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/
[
https://issues.apache.org/jira/browse/GERONIMO-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214859#comment-13214859
]
Russell E Glaue commented on GERONIMO-6284:
---
I was able to deploy the repository for the Geronimo instance with a simple
work-around.
The work-around is to copy a config.xml and config-substitutions.properties to
GERONIMO_HOME/var/config.
Apparently the deployer code looks to see if those are there, and it causes
problems if they do not exist.
However, if they exist, but you are deploying with a GERONIMO_SERVER defined,
they are checked but not modified.
I do not know if these config files are actually read. And if they are read,
there will be a problem if the GERONIMO_SERVER/var/config/{file} are not the
same files as the deployer looks for in GERONIMO_HOME/var/config/{file}
Also, though I was able to deploy/install a war to the second repository for
the Geronimo instance, it did not successfully load. This is the same error as
reported in the previous commend.
None the less, here is how I successfully deployed the second repository for a
Geronimo instance. Also following is the procedure and error message in
deploying the WAR.
Repository plan:
{noformat:borderStyle=solid}
http://geronimo.apache.org/xml/ns/deployment-1.2";>
org.example.configs.gserv1
gserv1repo
2.2
car
org.apache.geronimo.framework
j2ee-system
car
repository/
true
ServerInfo
gserv1
{noformat}
Setup:
- To setup a Geronimo instance, follow the procedures in
https://cwiki.apache.org/confluence/display/GMOxDOC30/Running+multiple+Geronimo+instances
- remove GERONIMO_HOME/etc
- remove GERONIMO_HOME/var
- Start the gserv1 instance with: {{cd $GERONIMO_HOME; env
GERONIMO_SERVER=gserv1 bin/geronimo run}} (The patch from GERONIMO-6275 is
needed)
Workaround:
{noformat:borderStyle=solid}
[root@server geronimo3]# mkdir -p $GERONIMO_HOME/var/config
[root@server geronimo3]# cp -p $GERONIMO_SERVER/var/config/config.xml
$GERONIMO_HOME/var/config/config.xml
[root@server geronimo3]# cp -p
$GERONIMO_SERVER/var/config/config-substitutions.properties
$GERONIMO_HOME/var/config/config-substitutions.properties
{noformat}
Plan Deployment:
{noformat:borderStyle=solid}
[root@server geronimo3]# env GERONIMO_SERVER=gserv1 bin/deploy -port 1199
deploy gserv1/repository.xml
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_SERVER: /opt/geronimo3/gserv1
Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
Deployed org.example.configs.gserv1/gserv1repo/2.2/car
[root@server geronimo3]# diff var/config/config.xml gserv1/var/config/config.xml
262a263
>
[root@server geronimo3]# env GERONIMO_SERVER=gserv1 bin/deploy -port 1199
list-targets
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_SERVER: /opt/geronimo3/gserv1
Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
Available Targets:
org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local
org.example.configs.gserv1/gserv1repo/2.2/car?ServiceModule=org.example.configs.gserv1/gserv1repo/2.2/car,j2eeType=ConfigurationStore,name=Localgserv1
{noformat}
WAR Deployment:
{noformat:borderStyle=solid}
[root@server geronimo3]# env GERONIMO_SERVER=gserv1 bin/deploy -port 1199
deploy --targets "Localgserv1" cviewer-3.0.0.0.war
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_SERVER: /opt/geronimo3/gserv1
Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
2012-02-23 11:04:58,573 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Operation failed: load of
com.ibm.wasce.samples/cviewer/3.0.0.0/car failed
URL [mvn:com.ibm.wasce.samples/cviewer/3.0.0.0/car] could not be
resolved.
URL [mvn:com.ibm.wasce.samples/cviewer/3.0.0.0/car] could not be
resolved.
at
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:168)
at
org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124)
at
org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171)
at
org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at
org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32)
{noformat}
Conclusions:
- the proper config files are ultimately used
- however, the deployer code still expects to see GERONIMO
[jira] [Commented] (GERONIMO-6284) Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/
[
https://issues.apache.org/jira/browse/GERONIMO-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214817#comment-13214817
]
Russell E Glaue commented on GERONIMO-6284:
---
I was able to successfully deploy the plan to a Geronimo install with no
configured instances.
I tested a few different configured plans and determined the problem with the
currently documented plan was the version number of "2.2" in the
org.apache.geronimo.framework j2ee-system dependency. Once that was removed, I
was able to deploy the wiki documented plan.
However, when deploying the cviewer-3.0.0.0.war in GERONIMO-6285 to the second
repository, it failed on load operation. It did deploy to the primary
repository and load successfully.
Here is the plan for my second repository
{noformat:borderStyle=solid}
http://geronimo.apache.org/xml/ns/deployment-1.2";>
org.example.configs.repo2
myrepo2
2.2
car
org.apache.geronimo.framework
j2ee-system
car
repo2/
true
ServerInfo
Repo2
{noformat}
Here is the output from attempting to deploy the war to the second repository
{noformat:borderStyle=solid}
[root@server geronimo3-beta]# bin/deploy -port 1099 list-targets
Using GERONIMO_HOME: /opt/geronimo3-beta
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
Available Targets:
org.apache.geronimo.framework/j2ee-system/3.0-beta-1/car?ServiceModule=org.apache.geronimo.framework/j2ee-system/3.0-beta-1/car,j2eeType=ConfigurationStore,name=Local
org.example.configs.repo2/myrepo2/2.2/car?ServiceModule=org.example.configs.repo2/myrepo2/2.2/car,j2eeType=ConfigurationStore,name=Local2
[root@server geronimo3-beta]# bin/deploy -port 1099 deploy --targets "Local2"
cviewer-3.0.0.0.war
Using GERONIMO_HOME: /opt/geronimo3-beta
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
2012-02-23 09:58:38,418 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Operation failed: load of
com.ibm.wasce.samples/cviewer/3.0.0.0/car failed
URL [mvn:com.ibm.wasce.samples/cviewer/3.0.0.0/car] could not be
resolved.
URL [mvn:com.ibm.wasce.samples/cviewer/3.0.0.0/car] could not be
resolved.
at
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:168)
at
org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124)
at
org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171)
at
org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at
org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32)
[root@server geronimo3-beta]# bin/deploy -port 1099 deploy cviewer-3.0.0.0.war
Using GERONIMO_HOME: /opt/geronimo3-beta
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Username: system
Password: ***
Deployed com.ibm.wasce.samples/cviewer/3.0.0.0/car @ /cviewer
{noformat}
> Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/
> --
>
> Key: GERONIMO-6284
> URL: https://issues.apache.org/jira/browse/GERONIMO-6284
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: 3.0-beta-1
> Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4
> (Tikanga)
>Reporter: Russell E Glaue
>Assignee: Forrest Xia
>Priority: Minor
> Labels: geronimo
>
> Cannot deploy to a Geronimo Instance. Deploy expects GERONIMO_HOME/var/...
> Create a new Geronimo instance as documented in
> https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
> - remove GERONIMO_HOME/etc
> - remove GERONIMO_HOME/var
> - create the empty file GERONIMO_HOME/var
> Start the Geronimo instance as follows:
> {noformat:borderStyle=solid}
> linux$ cd /opt/geronimo3/gserv1
> linux$ env JAVA_HOME=/usr/jdk1.6.0 GERONIMO_SERVER=gserv1
> /opt/geronimo3/bin/geronimo run
> {noformat}
> Create a second repository for the new instance
> - mkdir {{gserv1/repository}}
> - Create {{gserv1/repository.xml}} as documented in
> https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html
> {noformat:borderStyle=solid}
> http://geronimo.apache.org/xml/ns/deployment-1.2";>
>
>
>org.example.configs
> myrepo
> 2.2
> car
>
>
>
> org.apache.geronimo.framework
> j2ee-system
> 2.2
>
[jira] [Resolved] (GERONIMO-6280) Upgrade Apache Derby on 2.2 branch
[ https://issues.apache.org/jira/browse/GERONIMO-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trygve Sanne Hardersen resolved GERONIMO-6280. -- Resolution: Fixed Fix Version/s: (was: Verification Required) 2.2.2 > Upgrade Apache Derby on 2.2 branch > -- > > Key: GERONIMO-6280 > URL: https://issues.apache.org/jira/browse/GERONIMO-6280 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Verification Required >Reporter: Kevan Miller >Assignee: Trygve Sanne Hardersen > Fix For: 2.2.2 > > > Trygve's patch includes upgrades to Derby. I had someone ask about the > version of Derby on 2.2. > Should be pretty simple to pull out the Derby specific updates from Trygve's > patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6280) Upgrade Apache Derby on 2.2 branch
[ https://issues.apache.org/jira/browse/GERONIMO-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trygve Sanne Hardersen reassigned GERONIMO-6280: Assignee: Trygve Sanne Hardersen > Upgrade Apache Derby on 2.2 branch > -- > > Key: GERONIMO-6280 > URL: https://issues.apache.org/jira/browse/GERONIMO-6280 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Verification Required >Reporter: Kevan Miller >Assignee: Trygve Sanne Hardersen > Fix For: Verification Required > > > Trygve's patch includes upgrades to Derby. I had someone ask about the > version of Derby on 2.2. > Should be pretty simple to pull out the Derby specific updates from Trygve's > patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4379) Default to get from JVM's JAAS Configuration if it is not found in Geronimo's own implementation
[ https://issues.apache.org/jira/browse/GERONIMO-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4379. Resolution: Won't Fix Seem that there is no scenario to require this function. > Default to get from JVM's JAAS Configuration if it is not found in > Geronimo's own implementation > - > > Key: GERONIMO-4379 > URL: https://issues.apache.org/jira/browse/GERONIMO-4379 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: JDK 1.5/Windows XP >Reporter: Ivan >Priority: Minor > Fix For: Wish List > > Attachments: Geronimo-4379.patch > > > While configuring the JAAS Login in the Geronimo, I just found that we use > GeronimoLoginConfiguration to replace the JVM's ConfigurationFile, shall we > give an opportunity to let the user to get the config from JVM's > Configuration. > For example, first, we could check from Gronimo's setting, if null is > returned, we could invoke oldConguration.getAppConfigurationEntry(name). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6203) Too many unwanted dependencies are added for a simple web application
[ https://issues.apache.org/jira/browse/GERONIMO-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6203: -- Assignee: Ivan > Too many unwanted dependencies are added for a simple web application > - > > Key: GERONIMO-6203 > URL: https://issues.apache.org/jira/browse/GERONIMO-6203 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan >Priority: Minor > > While deploying a simple web application, too many unwanted dependencies are > added, it could be checked from the geronimo-plugins.xml file in the META-INF > directory of deployed application. > I understand that, sometimes it is hard to determine whether the dependency > is required in the createModule process, like axis2 etc, but we need to > remove it later if it is not required. > > org.apache.geronimo.configs > tomcat7 > 3.0-SNAPSHOT > car > all > > > org.apache.geronimo.configs > wink > 3.0-SNAPSHOT > car > all > > > org.apache.geronimo.modules > geronimo-bval > jar > all > > > org.apache.geronimo.configs > axis > car > all > > > org.apache.geronimo.configs > axis2 > car > all > > > org.apache.geronimo.configs > j2ee-corba-yoko > 3.0-SNAPSHOT > car > all > > > org.apache.geronimo.configs > openjpa2 > 3.0-SNAPSHOT > car > all > > > org.apache.geronimo.configs > openejb > car > classes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6180) Persistence ref info should not processed by EJBBuilder
[ https://issues.apache.org/jira/browse/GERONIMO-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6180. Resolution: Fixed Fix Version/s: 3.0-beta-2 Think that this should be fixed. > Persistence ref info should not processed by EJBBuilder > --- > > Key: GERONIMO-6180 > URL: https://issues.apache.org/jira/browse/GERONIMO-6180 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > For those persistence reference information in the spec DD, they should not > be processed by EJB builder, as they will be handled by JPA builder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6169) Recursive lookup while the default comp entry is configured
[ https://issues.apache.org/jira/browse/GERONIMO-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6169. Resolution: Fixed Think that this should be fixed now. > Recursive lookup while the default comp entry is configured > --- > > Key: GERONIMO-6169 > URL: https://issues.apache.org/jira/browse/GERONIMO-6169 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > If there is an resource entry like java:comp/EJBContext configured in the DD > or added by other modules, and the responsible module has not processed it, > AdminObjectRefBuilder will add a JndiReference in the binding map, which will > cause the infinite lookup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6194) Sort gbeans while stopping the configuration
[ https://issues.apache.org/jira/browse/GERONIMO-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6194. Resolution: Fixed Fix Version/s: 3.0-beta-2 > Sort gbeans while stopping the configuration > > > Key: GERONIMO-6194 > URL: https://issues.apache.org/jira/browse/GERONIMO-6194 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: kernel >Affects Versions: 3.0-M1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > Usually, the order of the gbeans in the configuration is not an issue while > starting the gbeans, as there will be listeners added for the gbean if its > required dependencies are not started, and it will be retried in the later. > But while stopping the gbeans, the order is important, e.g. if gbean A is > dependent on gbean b, and b is stopped before a, then there will an exception > thrown from GBeanDependency, and the doFail method will be invoked, not the > the doStop method. Although doStop and doFail have the same logic in most of > gbeans, it is better to avoid this. > I am planning to sort the gbeans by their dependency relations in one > configuration while stopping the configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6204) Decouple OpenWebBeans dependency from web containers
[ https://issues.apache.org/jira/browse/GERONIMO-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6204. Resolution: Fixed Fix Version/s: 3.0-beta-2 3.0 > Decouple OpenWebBeans dependency from web containers > > > Key: GERONIMO-6204 > URL: https://issues.apache.org/jira/browse/GERONIMO-6204 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > Attachments: > 0003-GERONIMO-6204-Decouple-OpenWebBeans-from-web-contain.patch > > > Now, even for a simple web application, Geronimo also creates a webbeans > context, and it really affect the performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6266) The jndi prefix URL could not work before the web application is totally started
[ https://issues.apache.org/jira/browse/GERONIMO-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6266. Resolution: Fixed Fix Version/s: 3.0-beta-2 3.0 Assignee: Ivan > The jndi prefix URL could not work before the web application is totally > started > > > Key: GERONIMO-6266 > URL: https://issues.apache.org/jira/browse/GERONIMO-6266 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 3.0, 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0, 3.0-beta-2 > > > If the those load-on-startup servlets use the servletContext.getResource > method to get a jndi prefix URL, they could not get the contents by > URL.openStream method, as the resources are only binded to the web > application classloader while the TomcatWebApp GBean is started. > Although we have binded the resources with the current thread, it seems to be > ignored in Tomcat codes. I opened a bug entry in Tomcat community, > https://issues.apache.org/bugzilla/show_bug.cgi?id=52563 > If they did not accept it or we have no chance to include the change in the > 3.0-beta-2 release, there should be workaround codes to make it work in > Geronimo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
