[VOTE] Release Geronimo Customized Tomcat 7.0.0.1

2010-05-24 Thread Ivan
Please vote for Geronimo Customized Tomcat 7.0.0.1
a. Recently, Tomcat community has begun their vote for Tomcat 7 RC 3, so
current version should be a more stable one.
b. About the license issues found in the vote for Geronimo Tomcat 7.0.0.0,
as those files have been donated, so they are properly under ASL 2.0. At
this time, no files are removed explictly.
c. If the vote could be passed on time, I would like use this version in M1
branch.

 Vote will be open for 72 hours.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)


Staging repo:

https://repository.apache.org/content/repositories/orgapachegeronimo-007/


Source repo:

https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.0.1/

-- 

I have run the servlet/JSP TCK, at least, the failed cases should not caused
by Tomcat codes itself.

The codes until rev 947397 are merged from Tomcat 7.0 trunk.

-- 
Ivan


Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.1

2010-05-24 Thread Ivan
Here is my +1

2010/5/24 Ivan xhh...@gmail.com

 Please vote for Geronimo Customized Tomcat 7.0.0.1
 a. Recently, Tomcat community has begun their vote for Tomcat 7 RC 3, so
 current version should be a more stable one.
 b. About the license issues found in the vote for Geronimo Tomcat 7.0.0.0,
 as those files have been donated, so they are properly under ASL 2.0. At
 this time, no files are removed explictly.
 c. If the vote could be passed on time, I would like use this version in M1
 branch.

  Vote will be open for 72 hours.

  [ ] +1  approve
  [ ] +0  no opinion
  [ ] -1  disapprove (and reason why)


 Staging repo:

 https://repository.apache.org/content/repositories/orgapachegeronimo-007/


 Source repo:


 https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.0.1/

 --

 I have run the servlet/JSP TCK, at least, the failed cases should not
 caused by Tomcat codes itself.

 The codes until rev 947397 are merged from Tomcat 7.0 trunk.

 --
 Ivan




-- 
Ivan


[jira] Assigned: (GERONIMO-5328) deployment-testsuite/jca-cms-tests has failures

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang reassigned GERONIMO-5328:
-

Assignee: Shawn Jiang

 deployment-testsuite/jca-cms-tests has failures
 ---

 Key: GERONIMO-5328
 URL: https://issues.apache.org/jira/browse/GERONIMO-5328
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Shawn Jiang
 Attachments: TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] special Geronimo OpenEJB 3.1.3.0 release (second attempt)

2010-05-24 Thread Rick McGuire
The vote to release the special OpenEJB release passes with 4 +1 votes 
and no 0 or -1 votes.  Voting +1 were


Rick McGuire
Hai Hong Xu (Ivan)
Donald Woods
David Blevins

The artifacts will be promoted to the central repository today.

Rick

On 5/17/2010 9:30 AM, Rick McGuire wrote:

Please vote for the geronimo openejb 3.1.3.0 release

This is a version of openejb based on revision r942249.  This is a 
special release to be used on the Geronimo 3.0-M1 release and is being 
released under the org.apache.geronimo.ext.openejb groupid.


Differences from the first attempt:

Copyright headers added to

container/openejb-osgi/src/main/resources/default.openejb.conf
container/openejb-activemq4/src/main/resources/login.config
container/openejb-core/src/main/resources/login.config
container/openejb-osgi/src/main/resources/login.config
container/openejb-core/src/main/resources/schema/ejb-jar_1_1.xsd


LICENSE file updated to include the W3C license for the following files:

container/openejb-jee/src/main/resources/META-INF/schema/xml.xsd
server/openejb-axis/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd 




This is the working version of openejb that works with Geronimo 3.0.  
This component is dependent upon the XBean release that is also 
currently up for a vote.  You may need to build XBean yourself to 
build openejb from the tag file at:


https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.7

Staging repo is here:

https://repository.apache.org/content/repositories/orgapachegeronimo-037/

tag is here:

https://svn.apache.org/repos/asf/geronimo/external/tags/openejb-3.1.3.0

Vote open 72 hours.  Note also that this is contingent upon the XBean 
vote also passing.


[ ] +1 release this
[ ] 0 don't care
[ ] -1 don't release this (please explain)

Rick




[jira] Created: (GERONIMO-5341) (master node)NODE-A's Web Application page in Console doesn't display the app(cviewer) which has been deployed.

2010-05-24 Thread LiWenQin (JIRA)
(master node)NODE-A's Web Application page in Console doesn't display the 
app(cviewer) which has been deployed.
---

 Key: GERONIMO-5341
 URL: https://issues.apache.org/jira/browse/GERONIMO-5341
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Clustering
Affects Versions: 2.2.1
 Environment: windows xp
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1


I try to test clustering-farm node.
NODE-A is master node(prot:8080), and after executing the sentence below:
deploy.bat --user system --password manager deploy --targets 
org.apache.geronimo.configs/farming/2.2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2.1-SNAPSHOT/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore
 SampleHome\cviewer-2.1.1.4.war
the sentence runs successfully.

However, I find that the (master node)NODE-A's Web Application Portlet in 
console does NOT display the app/cviewer, nor does it launch app through 
http://localhost:8080/cviewer.

PS: the NODE-B(prot:8090) can correctly display the app/cviewer in NODE-B's 
Web Application Portlet, and can launch it via http://localhost:8090/cviewer

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5177) Removing an entry from the Repository results in NullPointerException

2010-05-24 Thread Ben Liang (JIRA)

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

Ben Liang commented on GERONIMO-5177:
-

Hi all,

I have fixed this problem and now the patch does the following changes:

1.only jar file can be removed from repository directly which is not using by 
other components.

2.when removing a component , a confirm dialog will promote.

3.the removing result will show on the top of the page and when removing failed 
the message will show the error reason.


Ben 

 Removing an entry from the Repository results in NullPointerException
 -

 Key: GERONIMO-5177
 URL: https://issues.apache.org/jira/browse/GERONIMO-5177
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Windows XP 32 bit SP3, Java 1.6.0u18, Jetty version of 
 Geronimo
Reporter: Michelle Bhaal
Assignee: Ben Liang
 Fix For: 2.2.1

 Attachments: 5177.patch, geronimo.crash


 Removing an entry from the Repository results in a NullPointerException.  
 This is similar to GERONIMO-4157 but invoked differently.
 HTTP ERROR 500
 Problem accessing 
 /console/portal/Services/Repository/__ac0x3console-base0x2RepositoryViewer!604305819%7C0/__pm0x3console-base0x2RepositoryViewer!604305819%7C0_view.
  Reason:
 Server Error
 Caused by:
 java.lang.NullPointerException
   at 
 org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:116)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5177) Removing an entry from the Repository results in NullPointerException

2010-05-24 Thread Ben Liang (JIRA)

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

Ben Liang updated GERONIMO-5177:


Attachment: 5177_new.patch

 Removing an entry from the Repository results in NullPointerException
 -

 Key: GERONIMO-5177
 URL: https://issues.apache.org/jira/browse/GERONIMO-5177
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Windows XP 32 bit SP3, Java 1.6.0u18, Jetty version of 
 Geronimo
Reporter: Michelle Bhaal
Assignee: Ben Liang
 Fix For: 2.2.1

 Attachments: 5177.patch, 5177_new.patch, geronimo.crash


 Removing an entry from the Repository results in a NullPointerException.  
 This is similar to GERONIMO-4157 but invoked differently.
 HTTP ERROR 500
 Problem accessing 
 /console/portal/Services/Repository/__ac0x3console-base0x2RepositoryViewer!604305819%7C0/__pm0x3console-base0x2RepositoryViewer!604305819%7C0_view.
  Reason:
 Server Error
 Caused by:
 java.lang.NullPointerException
   at 
 org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:116)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5342) File not found Exception when set activemq share file system master/slave

2010-05-24 Thread viola.lu (JIRA)
File not found Exception when set activemq share file system master/slave
---

 Key: GERONIMO-5342
 URL: https://issues.apache.org/jira/browse/GERONIMO-5342
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: ActiveMQ
Affects Versions: 2.2.1
 Environment: WIndows 2003 Sp2
JDk: sun jdk 1.5.22
Reporter: viola.lu
Priority: Minor


1.Set a samba share allowing anonymous access in LAN,
2.Create two geronimo install directory in the same box,  change their 
var/activemq/config/activemq.xml as below:
persistenceAdapter
  amqPersistenceAdapter directory=\\9.186.10.68\share/
/persistenceAdapter

3.Start both servers, but errors exist
2010-05-24 19:17:37,656 ERROR [GBeanInstanceState] Error while starting; GBean 
is now in the FAILED state: 
abstractName=org.apache.geronimo.configs/activemq-broker/2.2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.2.1-SNAPSHOT/car,j2eeType=JMSServer,name=DefaultActiveMQBroker
java.io.FileNotFoundException: \\9.186.10.68\share\lock (Access is denied)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.init(RandomAccessFile.java:212)
at 
org.apache.activemq.store.amq.AMQPersistenceAdapter.start(AMQPersistenceAdapter.java:175)
at 
org.apache.activemq.broker.BrokerService.start(BrokerService.java:466)
at 
org.apache.geronimo.activemq.BrokerServiceGBeanImpl.doStart(BrokerServiceGBeanImpl.java:120)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:953)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:539)
at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816)
at 
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at 
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at 
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at 
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$9516750c.startConfiguration(generated)
at 
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:204)
at 
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:87)
at 
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)


reference doc:
http://activemq.apache.org/shared-file-system-master-slave.html


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5342) File not found Exception when set activemq share file system master/slave

2010-05-24 Thread viola.lu (JIRA)

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

viola.lu updated GERONIMO-5342:
---

Attachment: activemq_share.xml

 File not found Exception when set activemq share file system master/slave
 ---

 Key: GERONIMO-5342
 URL: https://issues.apache.org/jira/browse/GERONIMO-5342
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 2.2.1
 Environment: WIndows 2003 Sp2
 JDk: sun jdk 1.5.22
Reporter: viola.lu
Priority: Minor
 Attachments: activemq_share.xml


 1.Set a samba share allowing anonymous access in LAN,
 2.Create two geronimo install directory in the same box,  change their 
 var/activemq/config/activemq.xml as below:
 persistenceAdapter
   amqPersistenceAdapter directory=\\9.186.10.68\share/
 /persistenceAdapter
 3.Start both servers, but errors exist
 2010-05-24 19:17:37,656 ERROR [GBeanInstanceState] Error while starting; 
 GBean is now in the FAILED state: 
 abstractName=org.apache.geronimo.configs/activemq-broker/2.2.1-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.2.1-SNAPSHOT/car,j2eeType=JMSServer,name=DefaultActiveMQBroker
 java.io.FileNotFoundException: \\9.186.10.68\share\lock (Access is denied)
   at java.io.RandomAccessFile.open(Native Method)
   at java.io.RandomAccessFile.init(RandomAccessFile.java:212)
   at 
 org.apache.activemq.store.amq.AMQPersistenceAdapter.start(AMQPersistenceAdapter.java:175)
   at 
 org.apache.activemq.broker.BrokerService.start(BrokerService.java:466)
   at 
 org.apache.geronimo.activemq.BrokerServiceGBeanImpl.doStart(BrokerServiceGBeanImpl.java:120)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:953)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:539)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
   at 
 org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
   at 
 org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
   at 
 org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
   at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:592)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816)
   at 
 org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
   at 
 org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
   at 
 org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
   at 
 org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$9516750c.startConfiguration(generated)
   at 
 org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:204)
   at 
 org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:87)
   at 
 org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
   at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
   at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
 reference doc:
 http://activemq.apache.org/shared-file-system-master-slave.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5338) ActiveMQ port is not listed as a listening port and is always bound to localhost

2010-05-24 Thread Kevan Miller (JIRA)

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

Kevan Miller updated GERONIMO-5338:
---

Fix Version/s: 3.0
Affects Version/s: 3.0

3.0, as it's working on other versions.

 ActiveMQ port is not listed as a listening port and is always bound to 
 localhost
 

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


  Listening on Ports:
 1050 10.0.1.8CORBA Naming Service
 1099 10.0.1.8RMI Naming
 1527 10.0.1.8Derby Connector
 2001 10.0.1.8OpenEJB ORB Adapter
 4201 10.0.1.8OpenEJB Daemon
 4203 10.0.1.8OpenEJB Daemon
 6142 239.255.3.2 OpenEJB Daemon
 6882 10.0.1.8OpenEJB ORB Adapter
 8009 0.0.0.0 Tomcat Connector AJP TomcatAJPConnector
 8080 0.0.0.0 Tomcat Connector HTTP BIO TomcatWebConnector
 8443 0.0.0.0 Tomcat Connector HTTPS BIO TomcatWebSSLConnector
  10.0.1.8JMX Remoting Connector
 No ActiveMQ
 netstat output:
 tcp4   0  0  127.0.0.1.61616*.*LISTEN

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5337) ServerHostName does not control the bind ip address for Tomcat Connectors

2010-05-24 Thread Kevan Miller (JIRA)

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

Kevan Miller commented on GERONIMO-5337:


As long as it's configurable via config-substitution.properties, that's fine.

 ServerHostName does not control the bind ip address for Tomcat Connectors
 -

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


 ServerHostName in config-substitutions.properties does not control the bind 
 address for Tomcat Connectors. They are always 0.0.0.0
 Note I didn't test Jetty. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: svn commit: r946147 - in /geronimo/server/branches/3.0-M1: LICENSE NOTICE pom.xml

2010-05-24 Thread Kevan Miller

On May 19, 2010, at 8:15 AM, rickmcgu...@apache.org wrote:

 Author: rickmcguire
 Date: Wed May 19 12:15:04 2010
 New Revision: 946147
 
 URL: http://svn.apache.org/viewvc?rev=946147view=rev
 Log:
 update LICENSE/NOTICE files for latest dependency versions
 
 Modified:
geronimo/server/branches/3.0-M1/LICENSE
geronimo/server/branches/3.0-M1/NOTICE
geronimo/server/branches/3.0-M1/pom.xml

Rick,
Many thanks for working on license and notice files!

In 2.2, we separated our source and binary license/notice files. This seems to 
have recombined them. I think they should be separated. 

Oh, perhaps the 2.2 license/notice files weren't properly ported to trunk? And 
you were following the template that were already in place? Take a look at the 
2.2 LICENSE/NOTICE files and let me know what you think.

--kevan

[BUILD] branches/2.1: Failed for Revision: 947542

2010-05-24 Thread gawor
Geronimo Revision: 947542 built with tests included
 
See the full build-0200.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100524/build-0200.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100524
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 29 minutes 19 seconds
[INFO] Finished at: Mon May 24 02:35:22 EDT 2010
[INFO] Final Memory: 302M/1009M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100524/logs-0200-tomcat/
 
[INFO] Running console-testsuite.basic-console
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 95.265 
sec  FAILURE!
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 15, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 77.245 
sec  FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100524/logs-0200-jetty/
 
[INFO] Running console-testsuite.basic-console
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 98.235 
sec  FAILURE!
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 15, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 75.456 
sec  FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20100524/samples-0200.log
 
Build status: FAILED
 


Re: svn commit: r946147 - in /geronimo/server/branches/3.0-M1: LICENSE NOTICE pom.xml

2010-05-24 Thread Rick McGuire

On 5/24/2010 10:09 AM, Kevan Miller wrote:

On May 19, 2010, at 8:15 AM, rickmcgu...@apache.org wrote:

   

Author: rickmcguire
Date: Wed May 19 12:15:04 2010
New Revision: 946147

URL: http://svn.apache.org/viewvc?rev=946147view=rev
Log:
update LICENSE/NOTICE files for latest dependency versions

Modified:
geronimo/server/branches/3.0-M1/LICENSE
geronimo/server/branches/3.0-M1/NOTICE
geronimo/server/branches/3.0-M1/pom.xml
 

Rick,
Many thanks for working on license and notice files!

In 2.2, we separated our source and binary license/notice files. This seems to 
have recombined them. I think they should be separated.

Oh, perhaps the 2.2 license/notice files weren't properly ported to trunk? And 
you were following the template that were already in place? Take a look at the 
2.2 LICENSE/NOTICE files and let me know what you think.
   


I certainly was following the template that was already here in 3.0, so 
I guess the changes never got ported into 3.0.  I'll take a look at how 
this was handled in 2.2.


Rick


--kevan
   




[jira] Resolved: (GERONIMO-5335) ClassNotFoundException running 'geronimo stop'

2010-05-24 Thread Jarek Gawor (JIRA)

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

Jarek Gawor resolved GERONIMO-5335.
---

Resolution: Fixed

Committed fixes to trunk (revision 947660) and 3.0-M1 branch (revision 947661). 
The shutdown command (or geronimo stop) should work fine now with stored 
geronimo credentials.


 ClassNotFoundException running 'geronimo stop'
 --

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


 I get the following CNFE when running the 'geronimo stop' command:
 2010-05-22 16:10:10,319 ERROR [AbstractEncryption] Unable to decrypt
 java.lang.ClassNotFoundException: 
 org.apache.geronimo.deployment.cli.DeployUtils$SavedAuthentication
 at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:315)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
 at 
 org.apache.felix.framework.ModuleImpl.searchDynamicImports(ModuleImpl.java:1554)
 at 
 org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:765)
 at 
 org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
 at 
 org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:247)
 at javax.crypto.SunJCE_i.resolveClass(DashoA13*..)
 at 
 java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
 at 
 java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
 at 
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at javax.crypto.SealedObject.getObject(DashoA13*..)
 at 
 org.apache.geronimo.crypto.AbstractEncryption.decrypt(AbstractEncryption.java:78)
 at 
 org.apache.geronimo.crypto.EncryptionManager.decrypt(EncryptionManager.java:108)
 at 
 org.apache.geronimo.deployment.cli.DeployUtils.readSavedCredentials(DeployUtils.java:171)
 at 
 org.apache.geronimo.deployment.cli.StopServer.execute(StopServer.java:127)
 at 
 org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107)
 at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:67)
 at 
 org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
 at 
 org.apache.geronimo.cli.shutdown.ShutdownCLI.main(ShutdownCLI.java:32)
 Server stop does work, however.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



ApacheCon 2010: Technical Talks CFP

2010-05-24 Thread Kevan Miller
Geronimo Community,
Reminder of the Call For Participation for ApacheCon North America 2010: 
https://blogs.apache.org/foundation/entry/call_for_participation_technical_talks

Submissions are due Friday, May 28 by midnight PDT.

--kevan

[jira] Created: (GERONIMO-5343) Replace config-substitutions.properties by use of config admin

2010-05-24 Thread David Jencks (JIRA)
Replace config-substitutions.properties by use of config admin
--

 Key: GERONIMO-5343
 URL: https://issues.apache.org/jira/browse/GERONIMO-5343
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: core
Affects Versions: 3.0
Reporter: David Jencks
 Fix For: 3.0


OSGI has a fairly sophisticated customization system, config admin.  We should 
look into replacing our homegrown config-substitutions stuff with this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5337) ServerHostName does not control the bind ip address for Tomcat Connectors

2010-05-24 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-5337:


cf https://issues.apache.org/jira/browse/GERONIMO-5343.  I think we should 
eliminate config-substitutions.properties eventually.

 ServerHostName does not control the bind ip address for Tomcat Connectors
 -

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


 ServerHostName in config-substitutions.properties does not control the bind 
 address for Tomcat Connectors. They are always 0.0.0.0
 Note I didn't test Jetty. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5343) Replace config-substitutions.properties by use of config admin

2010-05-24 Thread Jarek Gawor (JIRA)

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

Jarek Gawor commented on GERONIMO-5343:
---

What do you mean by replace exactly? We can just feed the config-substitutions 
properties into config admin. So that the we can continue to use 
config-substitutions file and access the properties via config admin at the 
same time.



 Replace config-substitutions.properties by use of config admin
 --

 Key: GERONIMO-5343
 URL: https://issues.apache.org/jira/browse/GERONIMO-5343
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: core
Affects Versions: 3.0
Reporter: David Jencks
 Fix For: 3.0


 OSGI has a fairly sophisticated customization system, config admin.  We 
 should look into replacing our homegrown config-substitutions stuff with this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: svn commit: r944122 - in /geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main: resources/ webapp/WEB-INF/view/configmanager/

2010-05-24 Thread Kevan Miller

On May 14, 2010, at 1:49 AM, genspr...@apache.org wrote:

 Author: genspring
 Date: Fri May 14 05:49:37 2010
 New Revision: 944122
 
 URL: http://svn.apache.org/viewvc?rev=944122view=rev
 Log:
 GERONIMO-5274 Deploy New/Install New Application portlet needs some love to 
 help out newbies, patch from Hu Di
 
 Modified:

 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_en.properties

 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_zh.properties

 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/portletinfo_en.properties

 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/portletinfo_zh.properties

 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/webapp/WEB-INF/view/configmanager/deployHelp.jsp

I'm guessing that this change has broken the branches/2.1 automated build 
testsuite. All of the 2.1 have failed since May 15. May 14 was the last 
successful build. For further evidence, I believe this is the test failure:
 
---
Test set: console-testsuite.basic-console
---
Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.282 sec  
FAILURE!
testDeploymentLink(org.apache.geronimo.testsuite.console.DeploymentPortletTest) 
 Time elapsed: 0.311 sec   FAILURE!
com.thoughtworks.selenium.SeleniumException: ERROR: Element link=Deploy New not 
found
at 
com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
at 
com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)
at 
com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:167)
at 
org.apache.geronimo.testsuite.console.DeploymentPortletTest.testDeploymentLink(DeploymentPortletTest.java:36)

--kevan

 
 Modified: 
 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_en.properties
 URL: 
 http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_en.properties?rev=944122r1=944121r2=944122view=diff
 ==
 --- 
 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_en.properties
  (original)
 +++ 
 geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_en.properties
  Fri May 14 05:49:37 2010
 @@ -121,8 +121,9 @@ car.viewForDownload.prerequisites   
 car.viewForDownload.website   = Web Site
 
 configmanager.common.archive = Archive
 -configmanager.common.plan= Plan
 -configmanager.common.startAppAfterInstall= Start app after install
 +configmanager.common.plan= Plan(optional)
 +configmanager.common.startAppAfterInstall= Start application after 
 installation
 +configmanager.common.redeployapplication = Redeploy application
 configmanager.deploy.migratedPlan= Migrated plan
 configmanager.deploy.migratedPlanSummary = The deployment plan you 
 provided appears to be for a previous version of the application server. A 
 migrated version of your plan is provided below for your convenience.  Not 
 all deployment plans can be fully migrated so some manual editing may be 
 required before the migrated plan can be deployed.
 configmanager.deploy.originalPlan= Original plan
 @@ -130,11 +131,12 @@ configmanager.deploy.redeployApplication
 configmanager.deploy.saveLocally = Save this plan locally
 configmanager.deploy.showMigratedPlan= Show Migrated plan
 configmanager.deploy.showOriginalPlan= Show original plan
 -configmanager.deployHelp.archiveExp  = Browse to select the war 
 file in the Archive box.
 +configmanager.deployHelp.archiveExp  = Browse to select the Java 
 EE archive file in the Archive box.
 configmanager.deployHelp.installApplication  = Install the application in 
 the Geronimo server.
 -configmanager.deployHelp.planExp = If the deployment plan is 
 separate from the war file, then browse to select it.
 +configmanager.deployHelp.planExp = If the deployment plan is 
 separate from the archive file, then browse to select it.  If the deployment 
 plan is packaged within the archive file, then leave this field blank.
 configmanager.deployHelp.startAppAfterInstallExp = Check this to 
 automatically start the application when it is installed. Otherwise, the user 
 can start the application by clicking on the associated quot;Startquot; 
 toggle in thequot;Installed 

[jira] Resolved: (GERONIMO-5246) Geronimo 3.0 version of activemq still has spring dependencies.

2010-05-24 Thread Jarek Gawor (JIRA)

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

Jarek Gawor resolved GERONIMO-5246.
---

  Assignee: Jarek Gawor
Resolution: Fixed

geronimo-activemq module has been removed from svn as it was replaced by the 
geronimo-activemq-blueprint module.


 Geronimo 3.0 version of activemq still has spring dependencies. 
 

 Key: GERONIMO-5246
 URL: https://issues.apache.org/jira/browse/GERONIMO-5246
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 3.0
Reporter: Rick McGuire
Assignee: Jarek Gawor
 Fix For: 3.0


 The geronimo-activemq plugin still contains dependencies on a number of 
 springframework components, and there is code that will not compile cleanly 
 if these dependencies are removed.  The main problem classes are 
 BrokerServiceGBeanImpl and GeronmoPropertyPlaceholderConfigurer.  The 
 compilation failure of these classes causes problems with a couple of other 
 classes.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5337) ServerHostName does not control the bind ip address for Tomcat Connectors

2010-05-24 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5337:


How would we preserve plugin overrides in car-maven-plugin then?  Or would 
switching to osgi version ranges allow us to finally remove all of the hard 
coded version info in CARs?


 ServerHostName does not control the bind ip address for Tomcat Connectors
 -

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


 ServerHostName in config-substitutions.properties does not control the bind 
 address for Tomcat Connectors. They are always 0.0.0.0
 Note I didn't test Jetty. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5343) Replace config-substitutions.properties by use of config admin

2010-05-24 Thread Donald Woods (JIRA)

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

Donald Woods commented on GERONIMO-5343:


How would we preserve plugin overrides in car-maven-plugin then? Or would 
switching to osgi version ranges allow us to finally remove all of the hard 
coded version info in CARs?

 Replace config-substitutions.properties by use of config admin
 --

 Key: GERONIMO-5343
 URL: https://issues.apache.org/jira/browse/GERONIMO-5343
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: core
Affects Versions: 3.0
Reporter: David Jencks
 Fix For: 3.0


 OSGI has a fairly sophisticated customization system, config admin.  We 
 should look into replacing our homegrown config-substitutions stuff with this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.1

2010-05-24 Thread Rick McGuire

=1

This looks much cleaner than the 7.0.0.0 version.

Rick

On 5/24/2010 2:21 AM, Ivan wrote:

Please vote for Geronimo Customized Tomcat 7.0.0.1
a. Recently, Tomcat community has begun their vote for Tomcat 7 RC 3, 
so current version should be a more stable one.
b. About the license issues found in the vote for Geronimo Tomcat 
7.0.0.0, as those files have been donated, so they are properly under 
ASL 2.0. At this time, no files are removed explictly.
c. If the vote could be passed on time, I would like use this version 
in M1 branch.


 Vote will be open for 72 hours.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)


Staging repo:

https://repository.apache.org/content/repositories/orgapachegeronimo-007/


Source repo:

https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.0.1/

--

I have run the servlet/JSP TCK, at least, the failed cases should not 
caused by Tomcat codes itself.


The codes until rev 947397 are merged from Tomcat 7.0 trunk.

--
Ivan




[BUILD] trunk: Failed for Revision: 947766

2010-05-24 Thread gawor
Geronimo Revision: 947766 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 6 seconds
[INFO] Finished at: Mon May 24 15:38:50 EDT 2010
[INFO] Final Memory: 541M/982M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524/logs-1500-tomcat/
 
 
262K downloaded  (plexus-utils-1.5.9.jar)
313K downloaded  (surefire-booter-2.5.jar)
Downloading: 
file:///home/geronimo/.m2/jtidy.repository/org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
[INFO] Unable to find resource 'org.apache.maven.surefire:surefire-api:jar:2.5' 
in repository local (file:///home/geronimo/.m2/jtidy.repository)
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
557K downloaded  (surefire-api-2.5.jar)
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] No tests to run.
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/3.0-SNAPSHOT/testsuite-3.0-SNAPSHOT.pom
[INFO] [failsafe:verify {execution: verify}]
[INFO] No tests to run.
[INFO] 
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot 
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for 
updates from codehaus.snapshots
[INFO] snapshot 
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for 
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[WARNING] DEPRECATED [systemProperties]: Use systemPropertyVariables instead.
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] No tests to run.
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO] [failsafe:verify {execution: verify}]
[INFO] No tests to run.
[INFO] 
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/deploy-3.0-SNAPSHOT.jar
[org.codehaus.mojo.pluginsupport.logging.Logging] : Initialized
[INFO] [geronimo:start-server

[jira] Assigned: (GERONIMO-5247) IllegalStateException during Geronimo build.

2010-05-24 Thread Jarek Gawor (JIRA)

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

Jarek Gawor reassigned GERONIMO-5247:
-

Assignee: Jarek Gawor

 IllegalStateException during Geronimo build. 
 -

 Key: GERONIMO-5247
 URL: https://issues.apache.org/jira/browse/GERONIMO-5247
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: osgi
Affects Versions: 3.0
Reporter: Rick McGuire
Assignee: Jarek Gawor
 Fix For: 3.0


 The following IllegalStateException occurs over and over during the Geronimo 
 build process:
 java.lang.IllegalStateException: ObjectFactoryBuilder already set
 at 
 javax.naming.spi.NamingManager.setObjectFactoryBuilder(NamingManager.
 java:94)
 at org.apache.aries.jndi.startup.Activator.start(Activator.java:52)
 at 
 org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
 ion.java:661)
 at org.apache.felix.framework.Felix.activateBundle(Felix.java:1801)
 at org.apache.felix.framework.Felix.startBundle(Felix.java:1723)
 at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.starting(D
 ependencyManager.java:191)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.bundleChan
 ged(DependencyManager.java:89)
 at 
 org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC
 allback(EventDispatcher.java:800)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(
 EventDispatcher.java:728)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event
 Dispatcher.java:610)
 at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3670)
 at org.apache.felix.framework.Felix.activateBundle(Felix.java:1791)
 at org.apache.felix.framework.Felix.startBundle(Felix.java:1723)
 at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.starting(D
 ependencyManager.java:191)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.bundleChan
 ged(DependencyManager.java:89)
 at 
 org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC
 allback(EventDispatcher.java:800)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(
 EventDispatcher.java:728)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event
 Dispatcher.java:610)
 at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3670)
 at org.apache.felix.framework.Felix.activateBundle(Felix.java:1791)
 at org.apache.felix.framework.Felix.startBundle(Felix.java:1723)
 at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.starting(D
 ependencyManager.java:191)
 at 
 org.apache.geronimo.system.configuration.DependencyManager.bundleChan
 ged(DependencyManager.java:89)
 at 
 org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC
 allback(EventDispatcher.java:800)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(
 EventDispatcher.java:728)
 at 
 org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event
 Dispatcher.java:610)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: Adding OSGi support to Geronimo spec jars.

2010-05-24 Thread David Blevins
Having a look at this code and trying to figure out what the impact is on 
non-Geronimo consumers who might be using OSGi.

The geronimo-osgi-registry seems fairly small (just 10 classes including the 
inner classes) and only using the OSGi core and compendium jars.

I grocked from the description that it is used to look for a provider of the 
related API jar, but didn't get some specifics.

  1. Using EJB as an example, how does one say I am a provider.  There is no 
i am the EJB container interface to implement so what exactly are we looking 
for?

  2. What is the effect if the Activator is activated and no provider is found?


Any insight?


-David


On Feb 26, 2010, at 5:35 AM, Rick McGuire wrote:

 I've been taking a hard look at what Servicemix had done to the various spec 
 jars to make them better behaved in an OSGi environment.  This is being done 
 with the intent of adding similar support to the base Geronimo spec jars.  
 I'm taking a fresh approach to this rather than necessarily just copying what 
 Servicemix is doing.  I've found a number of interesting things during this 
 process, so I thought it would be good to do a brain dump of what I've found 
 and how I'm planning on implementing this.
 
 The basics of the Servicemix approach is to add an Activator to each of the 
 spec bundle that maintains a registry of factory class information.  Each 
 spec bundle have a listener that tracks bundle activity and will check for 
 factory information in the META-INF/services directory of each started 
 bundle.  Each started bundle has its own listener and own copy of the factory 
 information.  The registry information is used in the various places spec 
 code needs to dynamically load provider classes for different subsystems.  
 For example, loading a persistence provider.  All classloading is done lazily 
 when a request is made for a matching class file.  The spec code retrieves 
 the loaded classes and handles all details of creating the instances using 
 the retrieved classes.
 
 Jarek Gawor suggested I might want to take a look at what the Aries project 
 had for processing the META-INF/services information.  This test 
 implementation, called spifly, uses the OSGi extender pattern to inspect 
 the META-INF/services directories and uses that information to automatically 
 register services in the OSGi services registry.  In this situation, the 
 classes are eagerly loaded, instances are created (which requires a 
 no-argument constructor) and the services are registered in the OSGi registry.
 
 So, we have one set of information, but two different interpretations of how 
 this information should be used.  The new implementation I was working on was 
 using the extender pattern to maintain a single registry of this information 
 that could be accessed using a provider registry service.  This would have a 
 single listener, with a single version of the registry, and each bundle that 
 required the service would just have a thin accessor layer to call the 
 registry service if it was available.  This is essentially combining the 
 approaches used by Servicemix and spifly.
 
 However, I was becoming increasingly concerned about this dual interpretation 
 of the META-INF/services information, and started researching what 
 conventions were in play with this.  What I found was there is a new feature 
 in Java SE 6 called the ServiceLoader:
 
 http://java.sun.com/javase/6/docs/api/java/util/ServiceLoader.html
 
 The service loader uses the META-INF/services information to create mappings 
 between interface classes and concrete implementations of these interfaces.  
 This is similar to the spifly approach, but there are a few fundamental 
 differences.  The biggest difference is that each instance of the 
 ServiceLoader class will instantiate a new instance of the implementation 
 class when needed.  For spifly, there is only ever a single instance of the 
 service created.  Both spifly and Servicemix are only processing the first 
 line of the services files, while the ServiceLoader defines that an 
 individual definition file can define a one-to-many interface/implementation 
 mapping.  So, now we're up to 3 different interpretations of the 
 META-INF/services information.
 
 Looking a little deeper into how Servicemix was using this information, I 
 found that it was bending the intent of the META-INF/services information a 
 bit.  The ServiceLoader definitions are intended to create mappings between 
 interface classes and implementers of a given interface.  The service mix 
 lookups were being used to directly resolve implementation classes.  To do 
 this, the service definition file would need to use the same class as both 
 interface name and implementer class.  This has a nice side effect of 
 allowing particular implementations to be selectively replaced, but this is a 
 usage that could cause problems if the information was picked up by either 
 spifly or ServiceLoader.  This violated 

Re: Adding OSGi support to Geronimo spec jars.

2010-05-24 Thread David Jencks

On May 24, 2010, at 2:18 PM, David Blevins wrote:

 Having a look at this code and trying to figure out what the impact is on 
 non-Geronimo consumers who might be using OSGi.
 
 The geronimo-osgi-registry seems fairly small (just 10 classes including the 
 inner classes) and only using the OSGi core and compendium jars.
 
 I grocked from the description that it is used to look for a provider of the 
 related API jar, but didn't get some specifics.
 
  1. Using EJB as an example, how does one say I am a provider.  There is no 
 i am the EJB container interface to implement so what exactly are we 
 looking for?


EJB is not an example.  the provider stuff works for 2 situations:

1. Service providers, where you have a META-INF/services/interface-name file 
containing one line, the name of an implementing class in the current jar 
(bundle)  In this case, put a SPI-Provider manifest header in and your class 
will be accessible to service consumers via ProviderLocator.getServices(...) 
and related methods.

2. you need to make a class from your bundle available to others without them 
knowing about or getting inside your bundle.  Put a Export-SPI-provider header 
in your manifest whose value is a comma separated list of the classes you want 
to make available.  Consumers can load the classes by calling 
ProviderLocator.loadClass(className);
 
  2. What is the effect if the Activator is activated and no provider is found?

There are 2 activators.  I guess you mean the one in provider-locator?  If it 
isn't found, then you fall back on normal classloader tricks for trying to find 
services classes.  These won't normally work in an osgi environment.

thanks
david jencks

 
 
 Any insight?
 
 
 -David
 
 
 On Feb 26, 2010, at 5:35 AM, Rick McGuire wrote:
 
 I've been taking a hard look at what Servicemix had done to the various spec 
 jars to make them better behaved in an OSGi environment.  This is being done 
 with the intent of adding similar support to the base Geronimo spec jars.  
 I'm taking a fresh approach to this rather than necessarily just copying 
 what Servicemix is doing.  I've found a number of interesting things during 
 this process, so I thought it would be good to do a brain dump of what I've 
 found and how I'm planning on implementing this.
 
 The basics of the Servicemix approach is to add an Activator to each of the 
 spec bundle that maintains a registry of factory class information.  Each 
 spec bundle have a listener that tracks bundle activity and will check for 
 factory information in the META-INF/services directory of each started 
 bundle.  Each started bundle has its own listener and own copy of the 
 factory information.  The registry information is used in the various places 
 spec code needs to dynamically load provider classes for different 
 subsystems.  For example, loading a persistence provider.  All classloading 
 is done lazily when a request is made for a matching class file.  The spec 
 code retrieves the loaded classes and handles all details of creating the 
 instances using the retrieved classes.
 
 Jarek Gawor suggested I might want to take a look at what the Aries project 
 had for processing the META-INF/services information.  This test 
 implementation, called spifly, uses the OSGi extender pattern to inspect 
 the META-INF/services directories and uses that information to automatically 
 register services in the OSGi services registry.  In this situation, the 
 classes are eagerly loaded, instances are created (which requires a 
 no-argument constructor) and the services are registered in the OSGi 
 registry.
 
 So, we have one set of information, but two different interpretations of how 
 this information should be used.  The new implementation I was working on 
 was using the extender pattern to maintain a single registry of this 
 information that could be accessed using a provider registry service.  This 
 would have a single listener, with a single version of the registry, and 
 each bundle that required the service would just have a thin accessor layer 
 to call the registry service if it was available.  This is essentially 
 combining the approaches used by Servicemix and spifly.
 
 However, I was becoming increasingly concerned about this dual 
 interpretation of the META-INF/services information, and started researching 
 what conventions were in play with this.  What I found was there is a new 
 feature in Java SE 6 called the ServiceLoader:
 
 http://java.sun.com/javase/6/docs/api/java/util/ServiceLoader.html
 
 The service loader uses the META-INF/services information to create mappings 
 between interface classes and concrete implementations of these interfaces.  
 This is similar to the spifly approach, but there are a few fundamental 
 differences.  The biggest difference is that each instance of the 
 ServiceLoader class will instantiate a new instance of the implementation 
 class when needed.  For spifly, there is only ever a single instance 

Re: Adding OSGi support to Geronimo spec jars.

2010-05-24 Thread David Blevins

On May 24, 2010, at 3:49 PM, David Jencks wrote:

 
 On May 24, 2010, at 2:18 PM, David Blevins wrote:
 
 1. Using EJB as an example, how does one say I am a provider.  There is no 
 i am the EJB container interface to implement so what exactly are we 
 looking for?
 
 
 EJB is not an example.  the provider stuff works for 2 situations:

The activator and locator were added to the EJB spec jar.  Was that a mistake?


-David



Re: Adding OSGi support to Geronimo spec jars.

2010-05-24 Thread David Jencks

On May 24, 2010, at 5:06 PM, David Blevins wrote:

 
 On May 24, 2010, at 3:49 PM, David Jencks wrote:
 
 
 On May 24, 2010, at 2:18 PM, David Blevins wrote:
 
 1. Using EJB as an example, how does one say I am a provider.  There is 
 no i am the EJB container interface to implement so what exactly are we 
 looking for?
 
 
 EJB is not an example.  the provider stuff works for 2 situations:
 
 The activator and locator were added to the EJB spec jar.  Was that a mistake?
I was wrong... thinking of ejb 3.  You need a META-INF/services file for 
EJBContainerProvider and the SPI-Provider header in the manifest.  EJB 3.1 is 
an example.

BTW the only way I've talked the maven-bundle-plugin into adding this header is 
to supply a value such as SPI-Providertrue/SPI-Provider  Anyone know a 
value-free way?

thanks
david jencks

 
 
 -David
 



[jira] Assigned: (GERONIMO-5337) ServerHostName does not control the bind ip address for Tomcat Connectors

2010-05-24 Thread Ivan (JIRA)

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

Ivan reassigned GERONIMO-5337:
--

Assignee: Ivan

 ServerHostName does not control the bind ip address for Tomcat Connectors
 -

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


 ServerHostName in config-substitutions.properties does not control the bind 
 address for Tomcat Connectors. They are always 0.0.0.0
 Note I didn't test Jetty. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5344) Hook env-entries and servlet init-params up to config admin

2010-05-24 Thread David Jencks (JIRA)
Hook env-entries and servlet init-params up to config admin
---

 Key: GERONIMO-5344
 URL: https://issues.apache.org/jira/browse/GERONIMO-5344
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: naming, web
Affects Versions: 3.0
Reporter: David Jencks
 Fix For: 3.0


Since the osgi approved parameter customization facility is config admin and 
we're supposed to let people change at least env-entries we ought to use config 
admin for customizing these values.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (GERONIMO-5011) EJB Web Service security not working at all in G 2.2

2010-05-24 Thread Delos Dai (JIRA)

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

Delos Dai resolved GERONIMO-5011.
-

Resolution: Fixed

Right, you need to add role mapping the deployment plan.

But I also find the @RunAs will cause other exceptions after I added role 
mapping. It's due to the exception thrown in getSubjectForRole() of 
ApplicationPrincipalRoleConfigurationManager. With my fix in revision #947890, 
a default subject is returned instead of an exception.Then, the @RunAs works 
fiine. 

 EJB Web Service security not working at all in G 2.2
 

 Key: GERONIMO-5011
 URL: https://issues.apache.org/jira/browse/GERONIMO-5011
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Geronimo 2.2 with Tomcat 6, Windows XP, Java 6
Reporter: Łukasz Budnik
Assignee: Delos Dai
Priority: Blocker
 Fix For: 2.2.1

 Attachments: secure-ejb-web-service.zip


 EJB Web Service security was working in 2.1.x. Now, there are exceptions 
 thrown.
 openejb-jar.xml:
 enterprise-beans
   session
   ejb-nameHelloWebService/ejb-name
   web-service-security
 security-realm-namegeronimo-admin/security-realm-name
   transport-guaranteeCONFIDENTIAL/transport-guarantee
   auth-methodBASIC/auth-method
   /web-service-security
   /session
 /enterprise-beans
 Causes the following errors in log:
 org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car
 2010-01-04 14:37:18,213 INFO  [OpenEJB] Auto-deploying ejb HelloWebService: 
 EjbDeployment(deployment-id=secure-ejb-web-service/HelloWebService)
 2010-01-04 14:37:18,229 INFO  [config] Enterprise application 
 org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car loaded.
 2010-01-04 14:37:19,041 ERROR [EjbModuleBuilder] 
 AxisModuleBuilderExtension.initContext() failed: Duplicate contextID 
 registered! 
 org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car?EJBModule=org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=HelloWebService
 org.apache.geronimo.common.DeploymentException: Duplicate contextID 
 registered! 
 org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car?EJBModule=org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=HelloWebService
   at 
 org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:128)
   at 
 org.apache.geronimo.axis.builder.AxisModuleBuilderExtension.initContext(AxisModuleBuilderExtension.java:165)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:541)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:592)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136)
   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.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
   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:619)
 2010-01-04 14:37:19,041 ERROR [EjbModuleBuilder] 
 GeronimoSecurityBuilderImpl.addGBeans() failed: Unknown pattern type: null
 java.lang.IllegalArgumentException: Unknown pattern type: null
   at 
 org.apache.geronimo.gbean.ReferencePatterns.init(ReferencePatterns.java:44)
   at 
 org.apache.geronimo.gbean.GBeanData.setReferencePatterns(GBeanData.java:173)
   at 
 org.apache.geronimo.gbean.GBeanData.setReferencePattern(GBeanData.java:165)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:220)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150)
   at 
 

[jira] Resolved: (GERONIMO-5010) Transport confifential not working, 403 instead of 302 HTTP headers returned

2010-05-24 Thread Delos Dai (JIRA)

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

Delos Dai resolved GERONIMO-5010.
-

Resolution: Fixed

 Transport confifential not working, 403 instead of 302 HTTP headers returned
 

 Key: GERONIMO-5010
 URL: https://issues.apache.org/jira/browse/GERONIMO-5010
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 2.2
 Environment: G 2.2 with Tomcat 6, running on Windows XP with Java 6
Reporter: Łukasz Budnik
Assignee: Delos Dai
Priority: Blocker
 Fix For: 2.2.1


 I found it out by accident I was migrating Web Service which uses 
 CONFIDENTIAL transport layer security.
 By looking at the tcpmon I found out that POST request weren't forwarded to 
 HTTPS and was served using plain HTTP.
 The quickest way to reproduce this error:
 http://localhost:8080/console/secure
 Instead of being brought to https schema (followed by HTTP 302), the result 
 is: HTTP 403 error.
 It was all working in G 2.1.x.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (GERONIMO-5319) web-testsuite/test-web-references/web-references-ejb and web-testsuite/test-web-references/web-references-war have failures

2010-05-24 Thread Delos Dai (JIRA)

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

Delos Dai reassigned GERONIMO-5319:
---

Assignee: Delos Dai

 web-testsuite/test-web-references/web-references-ejb and 
 web-testsuite/test-web-references/web-references-war have failures
 ---

 Key: GERONIMO-5319
 URL: https://issues.apache.org/jira/browse/GERONIMO-5319
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Delos Dai
 Attachments: TestSuite.txt, TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 947887

2010-05-24 Thread gawor
Geronimo Revision: 947887 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 34 minutes 49 seconds
[INFO] Finished at: Mon May 24 21:38:46 EDT 2010
[INFO] Final Memory: 536M/995M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100524/logs-2100-tomcat/
 
 
262K downloaded  (plexus-utils-1.5.9.jar)
313K downloaded  (surefire-booter-2.5.jar)
Downloading: 
file:///home/geronimo/.m2/jtidy.repository/org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
[INFO] Unable to find resource 'org.apache.maven.surefire:surefire-api:jar:2.5' 
in repository local (file:///home/geronimo/.m2/jtidy.repository)
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
557K downloaded  (surefire-api-2.5.jar)
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] No tests to run.
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/3.0-SNAPSHOT/testsuite-3.0-SNAPSHOT.pom
[INFO] [failsafe:verify {execution: verify}]
[INFO] No tests to run.
[INFO] 
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot 
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for 
updates from codehaus.snapshots
[INFO] snapshot 
org.apache.geronimo.testsupport:testsupport-commands:3.0-SNAPSHOT: checking for 
updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[WARNING] DEPRECATED [systemProperties]: Use systemPropertyVariables instead.
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] No tests to run.
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO] [failsafe:verify {execution: verify}]
[INFO] No tests to run.
[INFO] 
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/deploy-3.0-SNAPSHOT.jar
[org.codehaus.mojo.pluginsupport.logging.Logging] : Initialized
[INFO] [geronimo:start-server

[jira] Commented: (GERONIMO-4580) Wrong Display Name element in ra.xml of tranql-connector-derby-embed-local-1.4.rar

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang commented on GERONIMO-4580:
---

David,

Will you release a 1.7 version  ?

 Wrong Display Name element in ra.xml of  
 tranql-connector-derby-embed-local-1.4.rar
 -

 Key: GERONIMO-4580
 URL: https://issues.apache.org/jira/browse/GERONIMO-4580
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.4, 2.2
Reporter: Gang Yin
Assignee: Shawn Jiang
 Fix For: 2.2.1


 In ra.xml of  tranql-connector-derby-embed-local-1.4.rar, the Display 
 Name element should be TranQL Embedded Local Transaction Resource Adapter 
 for Apache Derby rather than TranQL Embedded XA Resource Adapter for Apache 
 Derby.
 Because Admin Console depends on this value to distinguish TranQL adapters, 
 this mistake will cause Admin console to display wrong infomation when edit a 
 database pool of type Derby Embeded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-4807) Hidden-classes does not support excluding files

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4807:
--

Fix Version/s: 2.2.2
   (was: 2.2.1)

won't fix this in 221 release.

 Hidden-classes does not support excluding files
 ---

 Key: GERONIMO-4807
 URL: https://issues.apache.org/jira/browse/GERONIMO-4807
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.2
 Environment: OS X 10.5, Java 6
Reporter: Trygve Hardersen
 Fix For: 2.2.2


 It is not possible to exclude files with a . in the file name using the 
 hidden-classes classloader functionality. Example:
 build.properties -- a file that lives on the root of a JAR in a parent 
 classloader
 When creating a hidden-classes filter on build.properties, it is treated 
 as build/properties, which would be correct for a Java class, but not for a 
 plain file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-4807) Hidden-classes does not support excluding files

2010-05-24 Thread Trygve Hardersen (JIRA)

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

Trygve Hardersen commented on GERONIMO-4807:


Jeg jobber ikke lengre i Jotta!
I no longer work at Jotta!

Trygve Hardersen
try...@hypobytes.com


 Hidden-classes does not support excluding files
 ---

 Key: GERONIMO-4807
 URL: https://issues.apache.org/jira/browse/GERONIMO-4807
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.2
 Environment: OS X 10.5, Java 6
Reporter: Trygve Hardersen
 Fix For: 2.2.2


 It is not possible to exclude files with a . in the file name using the 
 hidden-classes classloader functionality. Example:
 build.properties -- a file that lives on the root of a JAR in a parent 
 classloader
 When creating a hidden-classes filter on build.properties, it is treated 
 as build/properties, which would be correct for a Java class, but not for a 
 plain file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5206) Assembly may start failed when server-security-config car is not assembled

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-5206:
--

Fix Version/s: (was: 2.2.1)

won't fix this in 221 release.

 Assembly may start failed when server-security-config car is not assembled
 --

 Key: GERONIMO-5206
 URL: https://issues.apache.org/jira/browse/GERONIMO-5206
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
Affects Versions: 2.1.5, 2.2.1
Reporter: Rex Wang
 Fix For: Wish List


 refer GERONIMO-5204
 If a plugin has a dependency to j2ee-security, but not explicitly depends on 
 server-security-config, assembly with this plugin will start failed with the 
 error FileKeystoreManager must have a root that's a valid readable directory 
 (./var/security/keystores)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4296:
--

Fix Version/s: 2.2.2
   (was: 2.2.1)

won't fix this in 221 release.

 Start Derby NetworkServerControl with credentials to prevent unauthorized 
 shutdowns
 ---

 Key: GERONIMO-4296
 URL: https://issues.apache.org/jira/browse/GERONIMO-4296
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: databases
Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2
Reporter: Donald Woods
Assignee: Ivan
Priority: Minor
 Fix For: 2.1.6, 2.2.2

 Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip


 Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start 
 our embedded Derby server with credentials, to prevent any other apps on 
 localhost from stopping our Derby instance.  The following Derby release note 
 details the scenario and the new API -
 http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585
 We could either use random uid/pwd values to start the Derby server, which 
 would be the most secure, but would keep other apps from using our Derby 
 server.  The other option, would be to set uid/pwd GBean attributes and 
 default the to the default system/manager values and leave it up to the user 
 to change them.
 Note:  This may also require some Samples, Testsuite and Portlet chagnes to 
 handle the required DB auth.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-4757) java.lang.IllegalStateException error when use install-plugin goal

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4757:
--

Fix Version/s: (was: 2.2.1)
   2.1.6
   2.2.2

won't fix this in 221 release.

 java.lang.IllegalStateException error when use install-plugin goal
 

 Key: GERONIMO-4757
 URL: https://issues.apache.org/jira/browse/GERONIMO-4757
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: geronimo-maven-plugin
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: os:windows
Reporter: viola.lu
Assignee: Ivan
Priority: Minor
 Fix For: 2.1.6, 2.2.2

 Attachments: GERONIMO-4757.patch


 1.Maven repository is c::\Documents and 
 Settings\Administrator.IBM-B92C72F1CB7\.m2\repository, 
 Build plugin-farm-it plugin under plugins/clustering/pluin-farm-it
 there is an execution in its pom.xml which install this plugin-farm-it plugin 
 to maven repository
 execution
 idinstall-plugin/id
 phaseinstall/phase
 goals
 goalinstall-plugin/goal
 /goals
 !--configuration--
 
 !--defaultGeronimoRepositoryhttp://geronimo.apache.org/plugins/geronimo-${version}//defaultGeronimoRepository--
 !--/configuration--
 /execution
 2.But when it execute install-plugin goal, there is an error:
 2009-07-21 10:40:20,859 ERROR [PluginRepositoryDownloader] Unable to format 
 plugin repository URL C:\Documents and 
 Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/
 java.net.URISyntaxException: Illegal character in opaque part at index 2: 
 C:\Documents and Settings\Administrator.IBM-B92C72F1CB7\.m2\repository/
   at java.net.URI$Parser.fail(URI.java:2821)
   at java.net.URI$Parser.checkChars(URI.java:2994)
   at java.net.URI$Parser.parse(URI.java:3031)
   at java.net.URI.init(URI.java:590)
   at 
 org.apache.geronimo.system.plugin.PluginRepositoryDownloader.resolveRepository(PluginRepositoryDownloader.java:231)
   at 
 org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:202)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885)
   at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
   at 
 org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
   at java.lang.Thread.run(Thread.java:810)
 Exception in thread DefaultThreadPool 0 java.lang.IllegalStateException: 
 Can't locate repo C:\Documents and 
 Settings\Administrator.IBM-B92C72F1CB7\.m2\repository
   at 
 org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:204)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean.getDefaultSourceRepository(PluginInstallerGBean.java:670)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:713)
   at 
 org.apache.geronimo.system.plugin.PluginInstallerGBean$3.run(PluginInstallerGBean.java:885)
   at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
   at 
 org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
   at java.lang.Thread.run(Thread.java:810)
 It's cozed by maven repositry  path containing space, which is forbidden in 
 URI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5323) Chinese and Japanese Translation for JIRA 5055

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-5323:
--

Fix Version/s: 2.2.2
   (was: 2.2.1)

won't fix this in 221 release.

 Chinese and Japanese Translation for JIRA 5055
 --

 Key: GERONIMO-5323
 URL: https://issues.apache.org/jira/browse/GERONIMO-5323
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: Windows XP
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.2

 Attachments: screenshot-1.jpg, screenshot-2.jpg


 The console will display English (it should display Chinese/English)  in a 
 few lines with Using Informix tranql XA  in g221 , if the browse language is 
 set to Chinese/Japanese. 
 Who can help translate and modify the files below?
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_zh.properties
  
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_ja.properties
 Thanks!
 PS: Refer to https://issues.apache.org/jira/browse/GERONIMO-5055,
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_en.properties
  has been modified. You can modify systemdatabase_zh.properties  
 systemdatabase_ja.properties accordingly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (GERONIMO-4363) Update plugin metadata (especially category) to represent function of a plugin

2010-05-24 Thread Shawn Jiang (JIRA)

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

Shawn Jiang closed GERONIMO-4363.
-

Resolution: Fixed

Closing it because it's been verified.

 Update plugin metadata (especially category) to represent function of a plugin
 --

 Key: GERONIMO-4363
 URL: https://issues.apache.org/jira/browse/GERONIMO-4363
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Plugins
Affects Versions: 2.2
Reporter: Lin Sun
Assignee: Lin Sun
 Fix For: 2.2.1, Verification Required


 In addition to plugin profiles, we decided on dev list that we can assign 
 tags to plugins.   Category was proposed to tag all the plugins.  For 
 example, if a plugin has JMS function, we want to make sure word JMS exists 
 in the plugin's category.   If a plugin belongs to admin console, we want to 
 make sure word Administration Console exists in the plugin's category.
 I'll perform a scan on our plugins and update them, so that changes in G4362 
 will work accurately.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (GERONIMO-5319) web-testsuite/test-web-references/web-references-ejb and web-testsuite/test-web-references/web-references-war have failures

2010-05-24 Thread Forrest Xia (JIRA)

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

Forrest Xia closed GERONIMO-5319.
-

Resolution: Invalid

Selenium test cases require suitexmlfiles config in failsafe plugin, after 
correcting it, the failed cases are passed finally, so close this jira.

 web-testsuite/test-web-references/web-references-ejb and 
 web-testsuite/test-web-references/web-references-war have failures
 ---

 Key: GERONIMO-5319
 URL: https://issues.apache.org/jira/browse/GERONIMO-5319
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Delos Dai
 Attachments: TestSuite.txt, TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5318) enterprise-testsuite/ejb-tests/ejb-ear has failures

2010-05-24 Thread Forrest Xia (JIRA)

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

Forrest Xia updated GERONIMO-5318:
--

Attachment: TestSuite.txt

 enterprise-testsuite/ejb-tests/ejb-ear has failures
 ---

 Key: GERONIMO-5318
 URL: https://issues.apache.org/jira/browse/GERONIMO-5318
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Delos Dai
 Attachments: TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Reopened: (GERONIMO-5318) enterprise-testsuite/ejb-tests/ejb-ear has failures

2010-05-24 Thread Forrest Xia (JIRA)

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

Forrest Xia reopened GERONIMO-5318:
---


Reopen after correcting a failsafe config issue. Now the ejb-tests has 
failures. See the attachment for details.

 enterprise-testsuite/ejb-tests/ejb-ear has failures
 ---

 Key: GERONIMO-5318
 URL: https://issues.apache.org/jira/browse/GERONIMO-5318
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Delos Dai
 Attachments: TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (GERONIMO-5328) deployment-testsuite/jca-cms-tests has failures

2010-05-24 Thread Forrest Xia (JIRA)

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

Forrest Xia closed GERONIMO-5328.
-

Fix Version/s: 2.2.1
   Resolution: Fixed

PasswordCredentialLoginModuleWrapperGBean is renamed to 
PasswordCredentialLoginModuleWrapper, after update the geronimo DD file, the 
failed case is passed. Thanks Shawn for this patch!

 deployment-testsuite/jca-cms-tests has failures
 ---

 Key: GERONIMO-5328
 URL: https://issues.apache.org/jira/browse/GERONIMO-5328
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public(Regular issues) 
Reporter: Forrest Xia
Assignee: Shawn Jiang
 Fix For: 2.2.1

 Attachments: TestSuite.txt




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5318) enterprise-testsuite/ejb-tests/ejb-ear has failures

2010-05-24 Thread Forrest Xia (JIRA)

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

Forrest Xia commented on GERONIMO-5318:
---

Interesting thing is if running ejb-tests itself, there is no failure, but if 
running the enterprise testsuite, the ejb-tests will fail. An exception like 
this:

[INFO] [INFO] Starting module: 
org.apache.geronimo.testsuite/ejb-ear/2.2.1-SNAPSHOT/ear
[WARNING] Deployer operation failed: start of 
org.apache.geronimo.testsuite/ejb-ear/2.2.1-SNAPSHOT/ear failed
[WARNING] org.apache.geronimo.kernel.config.LifecycleException: start of 
org.apache.geronimo.testsuite/ejb-ear/2.2.1-SNAPSHOT/ear failed
[WARNING]   at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562)
[WARNING]   at 
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
[WARNING]   at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
[WARNING]   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[WARNING]   at java.lang.reflect.Method.invoke(Method.java:597)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851)
[WARNING]   at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
[WARNING]   at 
org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
[WARNING]   at sun.reflect.GeneratedMethodAccessor146.invoke(Unknown Source)
[WARNING]   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[WARNING]   at java.lang.reflect.Method.invoke(Method.java:597)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
[WARNING]   at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851)
[WARNING]   at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
[WARNING]   at 
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
[WARNING]   at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
[WARNING]   at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
[WARNING]   at 
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
[WARNING]   at 
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
[WARNING]   at 
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
[WARNING]   at java.security.AccessController.doPrivileged(Native Method)
[WARNING]   at 
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
[WARNING]   at 
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
[WARNING]   at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown Source)
[WARNING]   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[WARNING]   at java.lang.reflect.Method.invoke(Method.java:597)
[WARNING]   at 
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
[WARNING]   at sun.rmi.transport.Transport$1.run(Transport.java:159)
[WARNING]   at java.security.AccessController.doPrivileged(Native Method)
[WARNING]   at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
[WARNING]   at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
[WARNING]   at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
[WARNING]   at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
[WARNING]   at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[WARNING]   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[WARNING]   at java.lang.Thread.run(Thread.java:619)
[WARNING] Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: 
Unknown start exception
[WARNING]   at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522)
[WARNING]   at 
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:493)
[WARNING]   at