[jira] [Resolved] (GERONIMO-6002) Can't configure defaultJspServlet parameters

2012-02-22 Thread xiezhi (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

xiezhi resolved GERONIMO-6002.
--

Resolution: Fixed

We have tested this configuration in geronimo 3.0-beta-1. It works.

 Can't configure defaultJspServlet parameters
 

 Key: GERONIMO-6002
 URL: https://issues.apache.org/jira/browse/GERONIMO-6002
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 3.0
Reporter: Kevan Miller
Assignee: Kevan Miller
 Fix For: 3.0

 Attachments: jsp.development.mode


 It's not currently possible to configure the defaultJspServlet properties. 
 This means that you can't configure 'development' mode or trimSpaces.

--
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-6281) Geronimo home.dir is being used when server.dir should be used instead for SnapshotConfigXMLBuilder, ActiveMQ, and Karaf

2012-02-22 Thread Russell E Glaue (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13213762#comment-13213762
 ] 

Russell E Glaue commented on GERONIMO-6281:
---


For activemq.data, you just need to use a relative path for a new instance. For 
example, if the instance name is GERONIMO_SERVER=inst1, then you set it like 
this:
activemq.data=inst1/var/activemq

No need to add a absolute path there.


The problem is that ActiveMQ access activemq.data relative to the directory 
you are in when you start Geronimo.
That is if you start Geronimo, without the no configured instances, like this:
- $ cd /opt
- $ export GERONIMO_HOME=/opt/geronimo
- $ /opt/geronomo/bin/geronimo start
Then ActiveMQ uses the following path as activemq.data:
- /opt/var/activemq

In this scenario, we want ActiveMQ to use {{GERONIMO_HOME/var/activemq}}, and 
not {{PWD/var/activemq}}
For the configured instance example you provide, ActiveMQ would create 
{{/opt/inst1/var/activemq}}. It would not use 
{{/opt/geronimo/inst1/var/activemq}} as you would expect.

Now take for example that I want to start Geronimo as a unix service.
If {{GERONIMO_HOME=/opt/geronimo}}
And the unix service starts geronimo in {{/}} (file system root)
ActiveMQ will create {{/var/activemq}}
ActiveMQ does not use {{GERONIMO_HOME/var/activemq}} as you would be expecting

Geronimo will fail to start if it is being started by a non-root user since 
ActiveMQ will not have permissions to create {{/var/activemq}}

How do we address this?
My recommendation is to change ActiveMQ to use org.apache.geronimo.server.dir 
as the base path and not PWD.

 Geronimo home.dir is being used when server.dir should be used instead for 
 SnapshotConfigXMLBuilder, ActiveMQ, and Karaf
 

 Key: GERONIMO-6281
 URL: https://issues.apache.org/jira/browse/GERONIMO-6281
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
  Components: ActiveMQ, javaee6
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
Assignee: Russell E Glaue
Priority: Minor
  Labels: geronimo
 Attachments: geronimo-6281-activemq-config-substitutions.patch, 
 geronimo-6281-activemq.patch, geronimo-6281-karaf.patch, 
 geronimo-6281-snapshot.patch, geronimo-6281-trunk-karaf.patch


 This issue is related to GERONIMO-6270 , GERONIMO-6175 , GERONIMO-6174 , 
 GERONIMO-5987 , and is being used to specifically track modifications related 
 to correctly using the following properties:
 # org.apache.geronimo.home.dir (GERONIMO_HOME)
 # org.apache.geronimo.server.dir (GERONIMO_SERVER - new shell variable 
 introduced in GERONIMO-6275)
 # karaf.base
 # karaf.home
 Primary issue to be resolved: The org.apache.geronimo.home.dir property 
 (GERONIMO_HOME) is being referenced when the org.apache.geronimo.server.dir 
 property (GERONIMO_SERVER) should be instead.
 I have identified three places in Geronimo errors are occurring due to 
 improper use of the above java properties:
 # SnapshotConfigXMLBuilder - originally reported in GERONIMO-6270
 # ActiveMQ - is reported in a comment of GERONIMO-5987 , and is being 
 reported here as requested.
 # Karaf - is additionally reported in GERONIMO-6174 .
 Note the three issues in startup:
 # Karaf initialization script etc/shell.init.script
 -- Error in initialization script: /opt/geronimo3/etc/shell.init.script (No 
 such file or directory)
 -- Reason:
 --- This is because karaf.home/etc/shell.init.script is being accessed when 
 instead it should be karaf.base/etc/shell.init.script
 -- Solution:
 --- The {karaf.base} property should be the same value as the 
 {org.apache.geronimo.server.dir} property
 -- Affected Code:
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/RunClientMojo.java
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/StartServerMojo.java
 --- 
 trunk/framework/configs/karaf-framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/org.ops4j.pax.url.mvn.cfg
 --- 
 trunk/framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java
 ---

Can't create second repository

2012-02-22 Thread Russell E Glaue 
Does anyone know why the documented procedure for creating a second repository 
throws an error?

https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html

Unpack geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220 as /opt/geronimo3
Or unpack geronimo-tomcat7-javaee6-3.0-beta-1 as /opt/geronimo3

[root@server geronimo3]$ cd /opt/geronimo3
[root@server geronimo3]$ bin/geronimo start
Using GERONIMO_HOME:   /opt/geronimo3
Using GERONIMO_TMPDIR: /opt/geronimo3/var/temp
Using JRE_HOME:/usr/jdk1.6.0/jre
Using GERONIMO_OUT:/opt/geronimo3/var/log/geronimo.out

Geronimo started in background. PID: 8625
[root@server geronimo3]$ bin/deploy -port 1099 deploy repo2.xml
Using GERONIMO_HOME:   /opt/geronimo3
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME:/usr/jdk1.6.0_25/jre
Username: system
Password: ***
2012-02-22 13:09:32,223 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Unable to deploy repo2.xml: 
Unable to resolve reference ServerInfo
in gbean 
org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=Repository,name=Repo2
to a gbean matching the pattern 
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]
due to: No matches for referencePatterns: 
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo] 
(no matches)


	at 
org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
	at 
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)
	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)

Re: Can't create second repository

2012-02-22 Thread Russell E Glaue 
The documented procedures in 
https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html work 
for /data/geronimo2/geronimo-tomcat6-javaee5-2.2.1


Something changed between 2.2 and 3.0. And ether that change breaks the support 
for multiple repositories, or the documented procedure needs to be updated to 
reflect the changes if that support still exists.


Can anyone weigh in on what they know?

-RG



On 02/22/2012 01:02 PM, Russell E Glaue wrote:

Does anyone know why the documented procedure for creating a second repository
throws an error?
https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html

Unpack geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220 as /opt/geronimo3
Or unpack geronimo-tomcat7-javaee6-3.0-beta-1 as /opt/geronimo3

[root@server geronimo3]$ cd /opt/geronimo3
[root@server geronimo3]$ bin/geronimo start
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_TMPDIR: /opt/geronimo3/var/temp
Using JRE_HOME: /usr/jdk1.6.0/jre
Using GERONIMO_OUT: /opt/geronimo3/var/log/geronimo.out

Geronimo started in background. PID: 8625
[root@server geronimo3]$ bin/deploy -port 1099 deploy repo2.xml
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME: /usr/jdk1.6.0_25/jre
Username: system
Password: ***
2012-02-22 13:09:32,223 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Unable to deploy repo2.xml:
Unable to resolve reference ServerInfo
in gbean
org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=Repository,name=Repo2

to a gbean matching the pattern
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]
due to: No matches for referencePatterns:
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]
(no matches)

at
org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
at
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)

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)

Re: Can't create second repository

2012-02-22 Thread Russell E Glaue 
From what I could decipher, it appears that in Geronimo 3.0 a GBeanInfo class 
is loaded from a classloader 
org.eclipse.osgi.framework.internal.core.BundleContextImpl


The OSGI is what is different from Geronimo 2.2.

Would this suggest the issue might be within the Geronimo 3.0 OSGI 
implementation?

-RG


On 02/22/2012 01:50 PM, Russell E Glaue wrote:

The documented procedures in
https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html work
for /data/geronimo2/geronimo-tomcat6-javaee5-2.2.1

Something changed between 2.2 and 3.0. And ether that change breaks the support
for multiple repositories, or the documented procedure needs to be updated to
reflect the changes if that support still exists.

Can anyone weigh in on what they know?

-RG



On 02/22/2012 01:02 PM, Russell E Glaue wrote:

Does anyone know why the documented procedure for creating a second repository
throws an error?
https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html

Unpack geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220 as /opt/geronimo3
Or unpack geronimo-tomcat7-javaee6-3.0-beta-1 as /opt/geronimo3

[root@server geronimo3]$ cd /opt/geronimo3
[root@server geronimo3]$ bin/geronimo start
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_TMPDIR: /opt/geronimo3/var/temp
Using JRE_HOME: /usr/jdk1.6.0/jre
Using GERONIMO_OUT: /opt/geronimo3/var/log/geronimo.out

Geronimo started in background. PID: 8625
[root@server geronimo3]$ bin/deploy -port 1099 deploy repo2.xml
Using GERONIMO_HOME: /opt/geronimo3
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME: /usr/jdk1.6.0_25/jre
Username: system
Password: ***
2012-02-22 13:09:32,223 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Unable to deploy repo2.xml:
Unable to resolve reference ServerInfo
in gbean
org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=Repository,name=Repo2


to a gbean matching the pattern
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]

due to: No matches for referencePatterns:
[?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]

(no matches)

at
org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)

at
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)


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)

Re: Can't create second repository

2012-02-22 Thread David Jencks 
I'm not entirely sure what state the 3.0 beta 1 code is in, but I would expect 
that if you wanted to add another repository you would need to add it to the 
mvn url handler configuration in etc/org.ops4j.pax.url.mvn.properties.  Im not 
100% sure what will happen.  The result may be to copy any bundle you load from 
the new repository into the standard repository.

I don't think any procedures that worked for 2.x would work for 3.

thanks
david jencks

On Feb 22, 2012, at 11:02 AM, Russell E Glaue wrote:

 Does anyone know why the documented procedure for creating a second 
 repository throws an error?
 https://cwiki.apache.org/GMOxDOC30/configuring-multiple-repositories.html
 
 Unpack geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220 as /opt/geronimo3
 Or unpack geronimo-tomcat7-javaee6-3.0-beta-1 as /opt/geronimo3
 
 [root@server geronimo3]$ cd /opt/geronimo3
 [root@server geronimo3]$ bin/geronimo start
 Using GERONIMO_HOME:   /opt/geronimo3
 Using GERONIMO_TMPDIR: /opt/geronimo3/var/temp
 Using JRE_HOME:/usr/jdk1.6.0/jre
 Using GERONIMO_OUT:/opt/geronimo3/var/log/geronimo.out
 
 Geronimo started in background. PID: 8625
 [root@server geronimo3]$ bin/deploy -port 1099 deploy repo2.xml
 Using GERONIMO_HOME:   /opt/geronimo3
 Using GERONIMO_TMPDIR: var/temp
 Using JRE_HOME:/usr/jdk1.6.0_25/jre
 Username: system
 Password: ***
 2012-02-22 13:09:32,223 ERROR [DeployTool] Error:
 org.apache.geronimo.common.DeploymentException: Unable to deploy repo2.xml: 
 Unable to resolve reference ServerInfo
in gbean 
 org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=Repository,name=Repo2
to a gbean matching the pattern 
 [?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]
due to: No matches for referencePatterns: 
 [?j2eeType=GBean,name=ServerInfo#org.apache.geronimo.system.serverinfo.ServerInfo]
  (no matches)
 
   at 
 org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
   at 
 org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)
   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)

[jira] [Commented] (GERONIMO-6281) Geronimo home.dir is being used when server.dir should be used instead for SnapshotConfigXMLBuilder, ActiveMQ, and Karaf

2012-02-22 Thread Forrest Xia (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13214248#comment-13214248
 ] 

Forrest Xia commented on GERONIMO-6281:
---

Yes, as you said, it uses $PWD as the root dir, I does not notice that before :)

I made a change in order to use o.a.g.server.dir property for activemq.data.

3.0-beta@1292631, 3.0 trunk@1292632

thanks!

 Geronimo home.dir is being used when server.dir should be used instead for 
 SnapshotConfigXMLBuilder, ActiveMQ, and Karaf
 

 Key: GERONIMO-6281
 URL: https://issues.apache.org/jira/browse/GERONIMO-6281
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
  Components: ActiveMQ, javaee6
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
Assignee: Russell E Glaue
Priority: Minor
  Labels: geronimo
 Attachments: geronimo-6281-activemq-config-substitutions.patch, 
 geronimo-6281-activemq.patch, geronimo-6281-karaf.patch, 
 geronimo-6281-snapshot.patch, geronimo-6281-trunk-karaf.patch


 This issue is related to GERONIMO-6270 , GERONIMO-6175 , GERONIMO-6174 , 
 GERONIMO-5987 , and is being used to specifically track modifications related 
 to correctly using the following properties:
 # org.apache.geronimo.home.dir (GERONIMO_HOME)
 # org.apache.geronimo.server.dir (GERONIMO_SERVER - new shell variable 
 introduced in GERONIMO-6275)
 # karaf.base
 # karaf.home
 Primary issue to be resolved: The org.apache.geronimo.home.dir property 
 (GERONIMO_HOME) is being referenced when the org.apache.geronimo.server.dir 
 property (GERONIMO_SERVER) should be instead.
 I have identified three places in Geronimo errors are occurring due to 
 improper use of the above java properties:
 # SnapshotConfigXMLBuilder - originally reported in GERONIMO-6270
 # ActiveMQ - is reported in a comment of GERONIMO-5987 , and is being 
 reported here as requested.
 # Karaf - is additionally reported in GERONIMO-6174 .
 Note the three issues in startup:
 # Karaf initialization script etc/shell.init.script
 -- Error in initialization script: /opt/geronimo3/etc/shell.init.script (No 
 such file or directory)
 -- Reason:
 --- This is because karaf.home/etc/shell.init.script is being accessed when 
 instead it should be karaf.base/etc/shell.init.script
 -- Solution:
 --- The {karaf.base} property should be the same value as the 
 {org.apache.geronimo.server.dir} property
 -- Affected Code:
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/RunClientMojo.java
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/StartServerMojo.java
 --- 
 trunk/framework/configs/karaf-framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/org.ops4j.pax.url.mvn.cfg
 --- 
 trunk/framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java
 --- 
 trunk/framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java
 --- 
 trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/serverinfo/BasicServerInfo.java
 --- 
 trunk/framework/modules/geronimo-main/src/main/java/org/apache/geronimo/main/FrameworkLauncher.java
 -- These code files are affected, but in relation to specifying the repository
 --- 
 trunk/framework/configs/karaf-framework/src/main/distribution/text/etc/org.ops4j.pax.url.mvn.cfg
 --- 
 trunk/framework/features/framework/src/main/distribution/text/etc/org.ops4j.pax.url.mvn.cfg
 # SnapshotConfigXMLBuilder var/monitoring/ directory
 -- (A) ERROR [SnapshotConfigXMLBuilder] Could not make the directory 
 /opt/geronimo3/var/monitoring/
 -- (B) ERROR [SnapshotConfigXMLBuilder] 
 /opt/geronimo3/var/monitoring/snapshot-config.xml (Not a directory)
 -- Reason:
 --- This is because SnapshotConfigXMLBuilder is looking for 
 $PWD/var/monitoring
 -- Solution:
 --- SnapshotConfigXMLBuilder should instead be using a full path to 
 var/monitoring, i.e. org.apache.geronimo.server.dir/var/monitoring
 -- Affected code:
 --- 
 trunk/plugins/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/ejb/snapshot/SnapshotProcessor.java
 ---

[jira] [Resolved] (GERONIMO-6281) Geronimo home.dir is being used when server.dir should be used instead for SnapshotConfigXMLBuilder, ActiveMQ, and Karaf

2012-02-22 Thread Forrest Xia (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Forrest Xia resolved GERONIMO-6281.
---

   Resolution: Fixed
Fix Version/s: 3.0-beta-2
   3.0

Russell, I set it to resolved, if not agreed, please reopen.

Thank you for your great contribution!

 Geronimo home.dir is being used when server.dir should be used instead for 
 SnapshotConfigXMLBuilder, ActiveMQ, and Karaf
 

 Key: GERONIMO-6281
 URL: https://issues.apache.org/jira/browse/GERONIMO-6281
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
  Components: ActiveMQ, javaee6
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
Assignee: Russell E Glaue
Priority: Minor
  Labels: geronimo
 Fix For: 3.0, 3.0-beta-2

 Attachments: geronimo-6281-activemq-config-substitutions.patch, 
 geronimo-6281-activemq.patch, geronimo-6281-karaf.patch, 
 geronimo-6281-snapshot.patch, geronimo-6281-trunk-karaf.patch


 This issue is related to GERONIMO-6270 , GERONIMO-6175 , GERONIMO-6174 , 
 GERONIMO-5987 , and is being used to specifically track modifications related 
 to correctly using the following properties:
 # org.apache.geronimo.home.dir (GERONIMO_HOME)
 # org.apache.geronimo.server.dir (GERONIMO_SERVER - new shell variable 
 introduced in GERONIMO-6275)
 # karaf.base
 # karaf.home
 Primary issue to be resolved: The org.apache.geronimo.home.dir property 
 (GERONIMO_HOME) is being referenced when the org.apache.geronimo.server.dir 
 property (GERONIMO_SERVER) should be instead.
 I have identified three places in Geronimo errors are occurring due to 
 improper use of the above java properties:
 # SnapshotConfigXMLBuilder - originally reported in GERONIMO-6270
 # ActiveMQ - is reported in a comment of GERONIMO-5987 , and is being 
 reported here as requested.
 # Karaf - is additionally reported in GERONIMO-6174 .
 Note the three issues in startup:
 # Karaf initialization script etc/shell.init.script
 -- Error in initialization script: /opt/geronimo3/etc/shell.init.script (No 
 such file or directory)
 -- Reason:
 --- This is because karaf.home/etc/shell.init.script is being accessed when 
 instead it should be karaf.base/etc/shell.init.script
 -- Solution:
 --- The {karaf.base} property should be the same value as the 
 {org.apache.geronimo.server.dir} property
 -- Affected Code:
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/RunClientMojo.java
 --- 
 framework/buildsupport/geronimo-maven-plugin/src/main/java/org/apache/geronimo/mavenplugins/geronimo/server/StartServerMojo.java
 --- 
 trunk/framework/configs/karaf-framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/framework/src/main/distribution/text/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/system.properties
 --- 
 trunk/framework/features/client/src/main/filtered-resources/resources/instances/client/etc/org.ops4j.pax.url.mvn.cfg
 --- 
 trunk/framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartServerCommand.java
 --- 
 trunk/framework/modules/geronimo-shell-base/src/main/java/org/apache/geronimo/shell/geronimo/StartClientCommand.java
 --- 
 trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/serverinfo/BasicServerInfo.java
 --- 
 trunk/framework/modules/geronimo-main/src/main/java/org/apache/geronimo/main/FrameworkLauncher.java
 -- These code files are affected, but in relation to specifying the repository
 --- 
 trunk/framework/configs/karaf-framework/src/main/distribution/text/etc/org.ops4j.pax.url.mvn.cfg
 --- 
 trunk/framework/features/framework/src/main/distribution/text/etc/org.ops4j.pax.url.mvn.cfg
 # SnapshotConfigXMLBuilder var/monitoring/ directory
 -- (A) ERROR [SnapshotConfigXMLBuilder] Could not make the directory 
 /opt/geronimo3/var/monitoring/
 -- (B) ERROR [SnapshotConfigXMLBuilder] 
 /opt/geronimo3/var/monitoring/snapshot-config.xml (Not a directory)
 -- Reason:
 --- This is because SnapshotConfigXMLBuilder is looking for 
 $PWD/var/monitoring
 -- Solution:
 --- SnapshotConfigXMLBuilder should instead be using a full path to 
 var/monitoring, i.e. org.apache.geronimo.server.dir/var/monitoring
 -- Affected code:
 --- 
 trunk/plugins/monitoring/agent-ejb/src/main/java/org/apache/geronimo/monitoring/ejb/snapshot/SnapshotProcessor.java
 ---

[jira] [Commented] (GERONIMO-6284) Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/

2012-02-22 Thread Forrest Xia (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13214259#comment-13214259
 ] 

Forrest Xia commented on GERONIMO-6284:
---

The new repo plan you need to update like this:

module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
 environment
  moduleId
   groupIdorg.example.configs/groupId
artifactIdmyrepo/artifactId
version2.2/version
typecar/type
  /moduleId
  dependencies
   dependency
groupIdorg.apache.geronimo.framework/groupId
artifactIdj2ee-system/artifactId
typecar/type
   /dependency
  /dependencies
  hidden-classes/
  non-overridable-classes/
 /environment
 gbean name=Repo2 
class=org.apache.geronimo.system.repository.Maven2Repository
   attribute name=rootrepository//attribute
   attribute name=resolveToServertrue/attribute
   reference name=ServerInfo
nameServerInfo/name
   /reference
 /gbean
 gbean name=Local2 
class=org.apache.geronimo.system.configuration.RepositoryConfigurationStore
  reference name=Repository
   nameRepo2/name
  /reference
 /gbean
/module

Then you can deploy the new geronimo configurationstore into folder 
GERONIMO_HOME/gserv1/repository

 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
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}
 module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
  environment
   moduleId
groupIdorg.example.configs/groupId
 artifactIdmyrepo/artifactId
 version2.2/version
 typecar/type
   /moduleId
   dependencies
dependency
 groupIdorg.apache.geronimo.framework/groupId
 artifactIdj2ee-system/artifactId
 version2.2/version
 typecar/type
/dependency
   /dependencies
   hidden-classes/
   non-overridable-classes/
  /environment
  gbean name=Repo2 
 class=org.apache.geronimo.system.repository.Maven2Repository
attribute name=rootgserv1/repository//attribute
attribute name=resolveToServerfalse/attribute
reference name=ServerInfo
 nameServerInfo/name
/reference
  /gbean
  gbean name=Local2 
 class=org.apache.geronimo.system.configuration.RepositoryConfigurationStore
   reference name=Repository
nameRepo2/name
   /reference
  /gbean
 /module
 {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

[jira] [Resolved] (GERONIMO-6175) Environment variable org.apache.geronimo.repository.boot.path not used, Repository path does not observe named instances

2012-02-22 Thread Forrest Xia (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Forrest Xia resolved GERONIMO-6175.
---

Resolution: Won't Fix
  Assignee: Forrest Xia

o.a.g.repository.boot.path is not used in geronimo for a long time, so close 
this jira.

 Environment variable org.apache.geronimo.repository.boot.path not used, 
 Repository path does not observe named instances
 

 Key: GERONIMO-6175
 URL: https://issues.apache.org/jira/browse/GERONIMO-6175
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Affects Versions: 3.0, 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

 I only list this issue as minor, as the issue does not prevent running 
 Geronimo, or more than one copy of Geronimo on a single server. However, this 
 issue does prevent the proper utilization of multiple named server instances.
 Two issues:
 # On startup, Geronimo does not use the repository relative to the named 
 server instance directory.
 # We are unable to set the repository with the property 
 org.apache.geronimo.repository.boot.path to be relative to the named server 
 instance directory.
 From what I could decipher, these are the (or some) of the primary classes 
 defining the repository
 - 
 framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/ConfigurationUtil.java
 - 
 plugins/jaxws/geronimo-jaxws-sun-tools/src/main/java/org/apache/geronimo/jaxws/sun/tools/JAXWSToolsCLI.java
 - 
 plugins/cxf/geronimo-cxf-tools/src/main/java/org/apache/geronimo/cxf/tools/JAXWSToolsCLI.java
 And the property org.apache.geronimo.repository.boot.path has a prepended 
 X in each of the three files.
 This tells me it was specifically disabled, and probably for some big issue.
 {noformat:borderStyle=solid}
 # 
 framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/ConfigurationUtil.java
 ...
 Collection repositories = null;
 ArtifactResolver artifactResolver = null;
 if (enableBootRepo) {
 String repository = 
 System.getProperty(Xorg.apache.geronimo.repository.boot.path, repository);
 Maven2Repository bootRepository = new Maven2Repository(new 
 File(getBootDirectory(), repository));
 repositories = Collections.singleton(bootRepository);
 artifactResolver = new DefaultArtifactResolver(new 
 DefaultArtifactManager(), bootRepository);
 } else {
 // a bootstrap configuration can not have any dependencies
 List dependencies = 
 configurationData.getEnvironment().getDependencies();
 if (!dependencies.isEmpty()) {
 
 configurationData.getEnvironment().setDependencies(Collections.EMPTY_SET);
 }
 }
 ...
 {noformat}
 To produce this issue, follow these steps:
 # Unpack the latest Geronimo javaee6 bundle as /opt/geronimo3
 # Create a Geronimo named instance directory as /opt/geronimo3/gserv1
 # Move the directories var, etc, and repository into /opt/geronimo3/gserv1
 # If patch GERONIMO-6275 in applied, start with this:
 -- env JAVA_HOME=/usr/jdk1.6.0 GERONIMO_SERVER=/opt/geronimo3/gserv1 
 /opt/geronimo3/bin/geronimo run
 # Or. without the patch, Use this start script
 {noformat:borderStyle=solid}
 #!/bin/bash
 GHOME=/opt/geronimo3
 GVIRT=gserv1
 # Must change to the server directory in order to work around ActiveMQ lock
 # file conflict issue reported in GERONIMO-5987.
 cd ${GHOME}/${GVIRT}
 # Uncomment for the Workaround of issues in GERONIMO-6174
 export GERONIMO_TMPDIR=${GHOME}/${GVIRT}/var/temp
 GERONIMO_OPTS=${GERONIMO_OPTS} -Dkaraf.home=${GHOME}/${GVIRT}
 #
 # Attempt to specify the correct root path to the repository for this
 # named server instance
 GERONIMO_OPTS=${GERONIMO_OPTS} 
 -Dorg.apache.geronimo.repository.boot.path=${GHOME}/${GVIRT}/repository
 #
 GERONIMO_OPTS=${GERONIMO_OPTS} -Dorg.apache.geronimo.server.name=${GVIRT}
 export GERONIMO_OPTS
 ${GHOME}/bin/geronimo run
 {noformat}
 When starting the Geronimo named server instance with the above start script 
 the following error is experienced:
 {noformat:borderStyle=solid}
 [user@linux gserv1]# ./start.sh 
 Using GERONIMO_HOME:   /opt/geronimo3
 Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
 Using JRE_HOME:/usr/jdk1.6.0/jre
   
  __   _   
 / /___  _    (_) ___  
/ / __ / _ \/ ___/ __ \/ __ \/ // __ `__ \/ __ \  
   / /_/ //

[jira] [Resolved] (GERONIMO-6275) Defining and Using org.apache.geronimo.server.dir versus org.apache.geronimo.home.dir in shell scripts

2012-02-22 Thread Forrest Xia (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Forrest Xia resolved GERONIMO-6275.
---

   Resolution: Fixed
Fix Version/s: 3.0-beta-2
   3.0

patch applied, so close this jira. 

 Defining and Using org.apache.geronimo.server.dir versus 
 org.apache.geronimo.home.dir in shell scripts
 --

 Key: GERONIMO-6275
 URL: https://issues.apache.org/jira/browse/GERONIMO-6275
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
  Components: startup/shutdown
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
Assignee: Russell E Glaue
Priority: Minor
  Labels: geronimo
 Fix For: 3.0, 3.0-beta-2

 Attachments: geronimo-6275-B-comments-cygwin-procrun.patch, 
 geronimo-6275-B-comments.patch, geronimo-6275-procrun_service.patch, 
 geronimo-6275.patch


 Related: GERONIMO-6270, GERONIMO-6175, GERONIMO-6174, GERONIMO-5987, 
 GERONIMO-4229
 It would be easier to support multiple server instances of Geronimo if there 
 is one shell variable that is used to reference the path on disk to the 
 instance, proposed as GERONIMO_SERVER as opposed to the GERONIMO_HOME 
 installation path. This issue tracks the discussion and modification of such 
 a change.
 GERONIMO_SERVER defines:
 - GERONIMO_SERVER defaults to GERONIMO_HOME if no instances are specified
 - GERONIMO_SERVER is expanded to GERONIMO_HOME/GERONIMO_SERVER if 
 GERONIMO_SERVER is a relative path
 - GERONIMO_SERVER defines org.apache.geronimo.server.dir
 In the java code there are the following properties:
 # org.apache.geronimo.home.dir - equivelant to GERONIMO_HOME shell variable
 # org.apache.geronimo.server.dir - proposed to be equivelant to 
 GERONIMO_SERVER 
 The words BASE versus HOME appear a few times in the source. Once example 
 is karaf.home and karaf.base properties. According to the code usage, it 
 is aparant that these terms are assumed to mean these things:
 # HOME - path location on disk of read-only binaries and configuration
 # BASE - path location on disk of read-write configuration and data storage
 The term BASE is intended to point at a Geronimo Server Instance Base path. 
 However, this has not been clearly defined, and has appeared to cause some 
 misusage. Thus this and other issues lead to the removal of GERONIMO_BASE 
 shell variable and org.apache.geronimo.base.dir java property in 
 GERONIMO-4229 .
 Currently, to start a Geronimo Instance, the org.apache.geronimo.server.dir 
 java property must be defined in the GERONIMO_OPTS variable. However, this 
 prevents the Shell scripts from being able to know and use the path location 
 to the Geronimo Server Instance.
 In particular, there are a few issues affected by a variable like this not 
 being available.
 # Reported in GERONIMO-6174 - GERONIMO_TMPDIR is set in the shell/bat scripts 
 as GERONIMO_HOME/var/tmp. In turn, the java property java.io.tmpdir is set 
 to GERONIMO_TMPDIR (this is GERONIMO_HOME/var/tmp). Shouldn't GERONIMO_TMPDIR 
 instead be set to a value provided by GERONIMO_SERVER/var/tmp ?
 -- affected scripts: client, deploy, geronimo, internalLauncher, jaxws-tools
 -- This can be argued to whether or not all Geronimo Server Instance should 
 share a common temp directory.
 # Reported in GERONIMO-6174 - The java properties karaf.home and karaf.base 
 are both being set to GERONIMO_HOME. When instead karaf.base should be set to 
 a value held by GERONIMO_SERVER.
 -- affected scripts: client, geronimo, internalLauncher
 -- see resulting errors and reasoning in GERONIMO-6174
 # Not Reported - The java property java.util.logging.config.file is being set 
 to GERONIMO_HOME/etc/java.util.logging.properties . It is intended to be an 
 empty configuration file. This only causes a problem when using instances if 
 GERONIMO_HOME/etc does not exist (it would not exist if GERONIMO_SERVER/etc 
 is intended to be used).
 -- affected scripts: client, geronimo, internalLauncher
 # Not Reported - Logging startup output to GERONIMO_HOME/var/log/geronimo.out 
 - Obviously if multiple instances are being started, this should be 
 GERONIMO_SERVER/var/log/geronimo.out . Any error is silent if 
 var/log/geronimo.out does not exist.
 -- affected scripts: geronimo
 # Not Reported - The register-service script does a grep and awk on 
 GERONIMO_HOME/var/config/config-substitutions.properties to discover the 
 portOffset . Obviously this will not work for multiple instances
 -- The register-service script does not take multiple instances into 
 consideration at all
 -- affected

[jira] [Assigned] (GERONIMO-6284) Cannot deploy to multiple instances, deploy expects GERONIMO_HOME/var/

2012-02-22 Thread Forrest Xia (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Forrest Xia reassigned GERONIMO-6284:
-

Assignee: Forrest Xia

 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}
 module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
  environment
   moduleId
groupIdorg.example.configs/groupId
 artifactIdmyrepo/artifactId
 version2.2/version
 typecar/type
   /moduleId
   dependencies
dependency
 groupIdorg.apache.geronimo.framework/groupId
 artifactIdj2ee-system/artifactId
 version2.2/version
 typecar/type
/dependency
   /dependencies
   hidden-classes/
   non-overridable-classes/
  /environment
  gbean name=Repo2 
 class=org.apache.geronimo.system.repository.Maven2Repository
attribute name=rootgserv1/repository//attribute
attribute name=resolveToServerfalse/attribute
reference name=ServerInfo
 nameServerInfo/name
/reference
  /gbean
  gbean name=Local2 
 class=org.apache.geronimo.system.configuration.RepositoryConfigurationStore
   reference name=Repository
nameRepo2/name
   /reference
  /gbean
 /module
 {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

[jira] [Commented] (GERONIMO-6175) Environment variable org.apache.geronimo.repository.boot.path not used, Repository path does not observe named instances

2012-02-22 Thread Russell E Glaue (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13214275#comment-13214275
 ] 

Russell E Glaue commented on GERONIMO-6175:
---

The focus is now on creating second repositories for Geronimo instances.
GERONIMO-6284

All instances will share a primary repository, and utilize second repositories 
for local deployments.

 Environment variable org.apache.geronimo.repository.boot.path not used, 
 Repository path does not observe named instances
 

 Key: GERONIMO-6175
 URL: https://issues.apache.org/jira/browse/GERONIMO-6175
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Affects Versions: 3.0, 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

 I only list this issue as minor, as the issue does not prevent running 
 Geronimo, or more than one copy of Geronimo on a single server. However, this 
 issue does prevent the proper utilization of multiple named server instances.
 Two issues:
 # On startup, Geronimo does not use the repository relative to the named 
 server instance directory.
 # We are unable to set the repository with the property 
 org.apache.geronimo.repository.boot.path to be relative to the named server 
 instance directory.
 From what I could decipher, these are the (or some) of the primary classes 
 defining the repository
 - 
 framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/ConfigurationUtil.java
 - 
 plugins/jaxws/geronimo-jaxws-sun-tools/src/main/java/org/apache/geronimo/jaxws/sun/tools/JAXWSToolsCLI.java
 - 
 plugins/cxf/geronimo-cxf-tools/src/main/java/org/apache/geronimo/cxf/tools/JAXWSToolsCLI.java
 And the property org.apache.geronimo.repository.boot.path has a prepended 
 X in each of the three files.
 This tells me it was specifically disabled, and probably for some big issue.
 {noformat:borderStyle=solid}
 # 
 framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/ConfigurationUtil.java
 ...
 Collection repositories = null;
 ArtifactResolver artifactResolver = null;
 if (enableBootRepo) {
 String repository = 
 System.getProperty(Xorg.apache.geronimo.repository.boot.path, repository);
 Maven2Repository bootRepository = new Maven2Repository(new 
 File(getBootDirectory(), repository));
 repositories = Collections.singleton(bootRepository);
 artifactResolver = new DefaultArtifactResolver(new 
 DefaultArtifactManager(), bootRepository);
 } else {
 // a bootstrap configuration can not have any dependencies
 List dependencies = 
 configurationData.getEnvironment().getDependencies();
 if (!dependencies.isEmpty()) {
 
 configurationData.getEnvironment().setDependencies(Collections.EMPTY_SET);
 }
 }
 ...
 {noformat}
 To produce this issue, follow these steps:
 # Unpack the latest Geronimo javaee6 bundle as /opt/geronimo3
 # Create a Geronimo named instance directory as /opt/geronimo3/gserv1
 # Move the directories var, etc, and repository into /opt/geronimo3/gserv1
 # If patch GERONIMO-6275 in applied, start with this:
 -- env JAVA_HOME=/usr/jdk1.6.0 GERONIMO_SERVER=/opt/geronimo3/gserv1 
 /opt/geronimo3/bin/geronimo run
 # Or. without the patch, Use this start script
 {noformat:borderStyle=solid}
 #!/bin/bash
 GHOME=/opt/geronimo3
 GVIRT=gserv1
 # Must change to the server directory in order to work around ActiveMQ lock
 # file conflict issue reported in GERONIMO-5987.
 cd ${GHOME}/${GVIRT}
 # Uncomment for the Workaround of issues in GERONIMO-6174
 export GERONIMO_TMPDIR=${GHOME}/${GVIRT}/var/temp
 GERONIMO_OPTS=${GERONIMO_OPTS} -Dkaraf.home=${GHOME}/${GVIRT}
 #
 # Attempt to specify the correct root path to the repository for this
 # named server instance
 GERONIMO_OPTS=${GERONIMO_OPTS} 
 -Dorg.apache.geronimo.repository.boot.path=${GHOME}/${GVIRT}/repository
 #
 GERONIMO_OPTS=${GERONIMO_OPTS} -Dorg.apache.geronimo.server.name=${GVIRT}
 export GERONIMO_OPTS
 ${GHOME}/bin/geronimo run
 {noformat}
 When starting the Geronimo named server instance with the above start script 
 the following error is experienced:
 {noformat:borderStyle=solid}
 [user@linux gserv1]# ./start.sh 
 Using GERONIMO_HOME:   /opt/geronimo3
 Using GERONIMO_TMPDIR: /opt/geronimo3/gserv1/var/temp
 Using JRE_HOME:/usr/jdk1.6.0/jre
   
  __   _   
 / /___

[jira] [Created] (GERONIMODEVTOOLS-787) Failed to hot deploy a resource file

2012-02-22 Thread Patrick Ouyang (Created) (JIRA) 
Failed to hot deploy a resource file


 Key: GERONIMODEVTOOLS-787
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-787
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Patrick Ouyang


It seems that G3 pickup the modified 4cb files from the wrong place. (4cb file 
is a resource file)

expect:C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web/target/classes/v4contentsource/source/en/TestContent1Web/Sample.4cb

actual:C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web/src/main/webapp/WEB-INF/classes/v4contentsource/source/en/TestContent1Web/Sample.4cb

Exception trace throw out from G3:

java.io.FileNotFoundException: 
C:\workspaces\Ride\New\sample1\TestContent1\TestContent1Web\src\main\webapp\WEB-INF\classes\v4contentsource\source\en\TestContent1Web\Sample.4cb
 (The system cannot find the path specified.)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:123)
at java.io.FileInputStream.init(FileInputStream.java:83)
at 
org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.findAndReplaceFiles(GeronimoServerBehaviourDelegate.java:1040)
at 
org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.tryFileReplace(GeronimoServerBehaviourDelegate.java:971)
at 
org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:453)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:952)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893)
at 
org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

This is the issue of GeronimoServerBehaviourDelegate. Please see the below code.

String sourceFile = module.getProject().getFile(rootFolder + ch + 
moduleFile.getModuleRelativePath() + ch + 
moduleFile.getName()).getLocation().toString();

The path was constructed by three part.

rootFolder: C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web

moduleFile.getModuleRelativePath(): 
src/main/webapp/WEB-INF/classes/v4contentsource/source/en/TestContent1Web

moduleFile.getName(): Sample.4cb

G3 supposed that all the resources should come from main/webapp 

--
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] (GERONIMODEVTOOLS-787) Failed to hot deploy a resource file

2012-02-22 Thread Patrick Ouyang (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Ouyang updated GERONIMODEVTOOLS-787:


Attachment: TouchAndGo.png

 Failed to hot deploy a resource file
 

 Key: GERONIMODEVTOOLS-787
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-787
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
Reporter: Patrick Ouyang
 Attachments: TouchAndGo.png


 It seems that G3 pickup the modified 4cb files from the wrong place. (4cb 
 file is a resource file)
 expect:C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web/target/classes/v4contentsource/source/en/TestContent1Web/Sample.4cb
 actual:C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web/src/main/webapp/WEB-INF/classes/v4contentsource/source/en/TestContent1Web/Sample.4cb
 Exception trace throw out from G3:
 java.io.FileNotFoundException: 
 C:\workspaces\Ride\New\sample1\TestContent1\TestContent1Web\src\main\webapp\WEB-INF\classes\v4contentsource\source\en\TestContent1Web\Sample.4cb
  (The system cannot find the path specified.)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.init(FileInputStream.java:123)
 at java.io.FileInputStream.init(FileInputStream.java:83)
 at 
 org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.findAndReplaceFiles(GeronimoServerBehaviourDelegate.java:1040)
 at 
 org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.tryFileReplace(GeronimoServerBehaviourDelegate.java:971)
 at 
 org.apache.geronimo.st.v30.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:453)
 at 
 org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:952)
 at 
 org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
 at 
 org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893)
 at 
 org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
 This is the issue of GeronimoServerBehaviourDelegate. Please see the below 
 code.
 String sourceFile = module.getProject().getFile(rootFolder + ch + 
 moduleFile.getModuleRelativePath() + ch + 
 moduleFile.getName()).getLocation().toString();
 The path was constructed by three part.
 rootFolder: C:/workspaces/Ride/New/sample1/TestContent1/TestContent1Web
 moduleFile.getModuleRelativePath(): 
 src/main/webapp/WEB-INF/classes/v4contentsource/source/en/TestContent1Web
 moduleFile.getName(): Sample.4cb
 G3 supposed that all the resources should come from main/webapp 

--
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-6258) HttpClient classloading problem while deploying ejb application

2012-02-22 Thread xiezhi (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

xiezhi updated GERONIMO-6258:
-

Attachment: geronimo-application.xml

the content from openejb-jar.xml in testForClassLoading.zip

 HttpClient classloading problem while deploying ejb application
 ---

 Key: GERONIMO-6258
 URL: https://issues.apache.org/jira/browse/GERONIMO-6258
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
 Environment: Windows 64 bit and 32 bit
Reporter: Michel Jonker
 Attachments: geronimo-application.xml, testForClassLoading.zip


 When I create ejb (or web) applications that contain the latest http client 
 (4.1.2) I cannot make the application run succesfully on WAS CE 3.0
 Deployment from Eclipse or through the Browser result in the same behaviour.
 I have added the jars through to the repository (The eclipse plugin 
 recognizes them as such).
 More details can be found here
 http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14775203
 I will also upload a sample eclipse project

--
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-6258) HttpClient classloading problem while deploying ejb application

2012-02-22 Thread xiezhi (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13214367#comment-13214367
 ] 

xiezhi commented on GERONIMO-6258:
--

I have deployed your application by transfering the content of openejb-jar.xml 
to geronimo-application.xml.
But when started the application, I got some exceptions from the server log.

2012-02-23 14:19:44,752 INFO  [config] Configuring 
Service(id=DefaultStatefulContainer, type=Container, provider-id=Default 
Stateful Container)
2012-02-23 14:19:44,753 INFO  [config] Configuring 
Service(id=DefaultSingletonContainer, type=Container, provider-id=Default 
Singleton Container)
2012-02-23 14:19:44,753 INFO  [config] Configuring 
Service(id=DefaultBMPContainer, type=Container, provider-id=Default BMP 
Container)
2012-02-23 14:19:44,754 INFO  [config] Configuring 
Service(id=DefaultCMPContainer, type=Container, provider-id=Default CMP 
Container)
2012-02-23 14:19:44,754 INFO  [config] Configuring 
Service(id=DefaultManagedContainer, type=Container, provider-id=Default Managed 
Container)
2012-02-23 14:19:44,755 INFO  [config] Configuring enterprise application: 
d:\Test\Server\ce3000frombuildServer\wasce-server-3.0.0.0\bin\default\Test6258EAR\1.0\car
2012-02-23 14:19:44,784 INFO  [OpenEJB] Auto-deploying ejb HelloWorld: 
EjbDeployment(deployment-id=Test6258.jar/HelloWorld)
2012-02-23 14:19:44,784 INFO  [config] Enterprise application 
d:\Test\Server\ce3000frombuildServer\wasce-server-3.0.0.0\bin\default\Test6258EAR\1.0\car
 loaded.
2012-02-23 14:19:47,033 INFO  [SupportedModesServiceImpl] Portlet mode 'edit' 
not found for portletId: 'plugin.Deployment!-2135677113|0'
2012-02-23 14:19:48,872 INFO  [SupportedModesServiceImpl] Portlet mode 'edit' 
not found for portletId: 'plugin.Deployment!-2135677113|0'
2012-02-23 14:20:04,307 INFO  [SupportedModesServiceImpl] Portlet mode 'edit' 
not found for portletId: 'console-base.WARModules!-717254442|0'
2012-02-23 14:20:04,307 INFO  [SupportedModesServiceImpl] Portlet mode 'help' 
not found for portletId: 'console-base.WARModules!-717254442|0'
2012-02-23 14:20:06,344 INFO  [SupportedModesServiceImpl] Portlet mode 'edit' 
not found for portletId: 'console-base.EARModules!-1281652050|0'
2012-02-23 14:20:06,349 INFO  [SupportedModesServiceImpl] Portlet mode 'help' 
not found for portletId: 'console-base.EARModules!-1281652050|0'
2012-02-23 14:20:10,825 INFO  [KernelContextGBean] bound gbean 
default/Test6258EAR/1.0/car?EJBModule=Test6258.jar,J2EEApplication=default/Test6258EAR/1.0/car,j2eeType=ValidatorFactory,name=ValidatorFactory
 at name jca:/default/Test6258EAR/ValidatorFactory/ValidatorFactory
2012-02-23 14:20:10,864 INFO  [startup] Assembling app: 
d:\Test\Server\ce3000frombuildServer\wasce-server-3.0.0.0\bin\default\Test6258EAR\1.0\car
2012-02-23 14:20:10,868 INFO  [startup] Jndi(name=HelloWorldLocalBean) -- 
Ejb(deployment-id=Test6258.jar/HelloWorld)
2012-02-23 14:20:10,868 INFO  [startup] 
Jndi(name=global/Test6258EAR/Test6258/HelloWorld!nl.mic.test.HelloWorld) -- 
Ejb(deployment-id=Test6258.jar/HelloWorld)
2012-02-23 14:20:10,869 INFO  [startup] 
Jndi(name=global/Test6258EAR/Test6258/HelloWorld) -- 
Ejb(deployment-id=Test6258.jar/HelloWorld)
2012-02-23 14:20:10,869 INFO  [CdiBuilder] existing thread singleton service in 
SystemInstance() 
org.apache.geronimo.openejb.cdi.ThreadSingletonServiceAdapter@5c285c28
2012-02-23 14:20:10,871 INFO  [startup] Deployed 
Application(path=d:\Test\Server\ce3000frombuildServer\wasce-server-3.0.0.0\bin\default\Test6258EAR\1.0\car)
2012-02-23 14:20:10,873 INFO  [EjbModuleImpl] 
createApplication.createdEjbTest6258.jar/HelloWorldHelloWorldDefaultStatelessContainer
2012-02-23 14:20:10,880 INFO  [EjbModuleImpl] 
createApplication.startedEjbTest6258.jar/HelloWorldHelloWorldDefaultStatelessContainer
2012-02-23 14:20:11,433 INFO  [SupportedModesServiceImpl] Portlet mode 'edit' 
not found for portletId: 'console-base.EARModules!-1281652050|0'
2012-02-23 14:20:11,433 INFO  [SupportedModesServiceImpl] Portlet mode 'help' 
not found for portletId: 'console-base.EARModules!-1281652050|0'
2012-02-23 14:21:00,873 INFO  [Transaction] TX NotSupported: Suspended 
transaction org.apache.geronimo.transaction.manager.TransactionImpl@699d699d
2012-02-23 14:21:00,874 ERROR [OpenEJB] The bean instance business method 
encountered a system exception: argument type mismatch
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at 
org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181)
at

[jira] [Assigned] (GERONIMO-6283) Duplicate contextID regiestered!

2012-02-22 Thread Ivan (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan reassigned GERONIMO-6283:
--

Assignee: Ivan

 Duplicate contextID regiestered!
 

 Key: GERONIMO-6283
 URL: https://issues.apache.org/jira/browse/GERONIMO-6283
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: xiezhi
Assignee: Ivan
  Labels: axis,builder,context
 Fix For: 3.0-beta-2

   Original Estimate: 12h
  Remaining Estimate: 12h

 Recurring steps refer to GERONIMO-6225, deploy it to G server, you will see 
 an exception in server.log.
 2012-02-21 10:41:08,115 ERROR [EjbModuleBuilder] 
 AxisModuleBuilderExtension.initContext() failed: Duplicate contextID 
 registered! 
 ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean
 org.apache.geronimo.common.DeploymentException: Duplicate contextID 
 registered! 
 ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean
   at 
 org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:182)
   at 
 org.apache.geronimo.axis.builder.AxisModuleBuilderExtension.initContext(AxisModuleBuilderExtension.java:178)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.doInitContext(EjbModuleBuilder.java:835)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:758)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:686)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:736)

--
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-6283) Duplicate contextID regiestered!

2012-02-22 Thread Ivan (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan resolved GERONIMO-6283.


   Resolution: Fixed
Fix Version/s: 3.0-beta-2

Commit changes to trunk at rev.1292668 and 3.0-beta2 branch at rev.1292669

 Duplicate contextID regiestered!
 

 Key: GERONIMO-6283
 URL: https://issues.apache.org/jira/browse/GERONIMO-6283
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 3.0-beta-1
Reporter: xiezhi
  Labels: axis,builder,context
 Fix For: 3.0-beta-2

   Original Estimate: 12h
  Remaining Estimate: 12h

 Recurring steps refer to GERONIMO-6225, deploy it to G server, you will see 
 an exception in server.log.
 2012-02-21 10:41:08,115 ERROR [EjbModuleBuilder] 
 AxisModuleBuilderExtension.initContext() failed: Duplicate contextID 
 registered! 
 ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean
 org.apache.geronimo.common.DeploymentException: Duplicate contextID 
 registered! 
 ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean
   at 
 org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:182)
   at 
 org.apache.geronimo.axis.builder.AxisModuleBuilderExtension.initContext(AxisModuleBuilderExtension.java:178)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.doInitContext(EjbModuleBuilder.java:835)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:758)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:686)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:736)

--
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