[jira] Resolved: (GERONIMO-4873) Unable creating a new JMS Resource Group via "For another JMS provider... " under IE

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4873.


   Resolution: Fixed
Fix Version/s: 3.0
   2.2

Commit changes to 2.2 At revision: 815169 and trunk At revision: 815170.
By default, ActiveMQ is the default provider, and we could create it with the 
link 'For ActiveMQ', I removed the it from other provider list, currently, no 
option could be selected in the list if we do not install any other providers

> Unable creating a new JMS Resource Group via "For another JMS provider... " 
> under IE
> 
>
> Key: GERONIMO-4873
> URL: https://issues.apache.org/jira/browse/GERONIMO-4873
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
>Reporter: Shiny Cheng
> Fix For: 2.2, 3.0
>
>
> Click on "For another JMS provider" when creating a new JMS Resource Group 
> via admin console. Select the existed 
> org.apache.geronimo.modules/geronimo-activemq-ra/2.2-SNAPSHOT/rar and click 
> on "Next". 
> If your current browser is IE series, you will see warning like "The focussed 
> field must not be empty" and unable to do following steps. However, you won't 
> meet this problem under Firefox.

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

[jira] Commented: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.

[Shawn Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755394#action_12755394
 ] 

Shawn Jiang commented on GERONIMO-4850:
---

When node-A (main node) is shutdown.
BasicClusterConfigurationController.doStop() get executed, it will stop the 
cviewer configuration on each node in clustering.

When configuration cviewer in node-B is getting stopped by

LocalAttributeManager.stopConfiguration(Artifact){
.
  configuration.setLoad(false);

}

The cviewer configuration is set to "load=false".  To fix it is not hard, but 
I'm wondering if it's working as design case.

> WADI clustering: the application no node B will not start up when start up 
> the node B. 
> ---
>
> Key: GERONIMO-4850
> URL: https://issues.apache.org/jira/browse/GERONIMO-4850
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
>Assignee: Shawn Jiang
>
> 1.I configuration two nodes A and B following the WADI clustering and deploy 
> the cviewer.war on the node A the no the node B there is cviewer.war also and 
> they work well on 2 nodes.
> 2.shutdown A node first and then shutdown B node, I find that the cviewer.war 
> load is set false in the config.xml of node B.
> 3 .start A and B, the cviewer.war on the node B can not start automatically.

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

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[Shawn Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755391#action_12755391
 ] 

Shawn Jiang commented on GERONIMO-4855:
---

Session Sticky does not resolve the failed login info replication problem.  
They are totally different problems from each other.


 As Ben stated above, Tomcat native clustering support login info replication 
while Geronimo can't.

> Clustering can not work when the application needs login information
> 
>
> Key: GERONIMO-4855
> URL: https://issues.apache.org/jira/browse/GERONIMO-4855
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
> Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war
>
>
> When I using WADI clustering and tomcat native clustering there are the same 
> problem:
> If the application on the different node needs the security information to 
> access some page then firefox gives the following error information:
> HTTP Status 404 - /demo/protect/j_security_check
> type Status report
> message /demo/protect/j_security_check
> description The requested resource (/demo/protect/j_security_check) is not 
> available.
> so it is likely clustering can not access any resource which need security 
> check.

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

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[viola.lu (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755386#action_12755386
 ] 

viola.lu commented on GERONIMO-4855:


hi, jeff, pls update your doc 
http://cwiki.apache.org/GMOxDOC22/tomcat-native-clustering.html about session 
affinity

  
name=Geronimo
jvmRoute=nodeId
  

This doesn't work in geronimo 2.2. Should modify server.xml to implement 
session affinity


uncommnet out this line to enable it or add jvmRoute attribute to enable it.
 



> Clustering can not work when the application needs login information
> 
>
> Key: GERONIMO-4855
> URL: https://issues.apache.org/jira/browse/GERONIMO-4855
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
> Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war
>
>
> When I using WADI clustering and tomcat native clustering there are the same 
> problem:
> If the application on the different node needs the security information to 
> access some page then firefox gives the following error information:
> HTTP Status 404 - /demo/protect/j_security_check
> type Status report
> message /demo/protect/j_security_check
> description The requested resource (/demo/protect/j_security_check) is not 
> available.
> so it is likely clustering can not access any resource which need security 
> check.

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

[jira] Updated: (GERONIMO-4876) "java.lang.Exception" when I shutdown the server

[Bin He (JIRA)]

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

Bin He updated GERONIMO-4876:
-

Priority: Minor  (was: Major)

> "java.lang.Exception"  when I shutdown the server
> -
>
> Key: GERONIMO-4876
> URL: https://issues.apache.org/jira/browse/GERONIMO-4876
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector
>Affects Versions: 2.2
> Environment: jdk6
> windows xp sp2
>Reporter: Bin He
>Priority: Minor
>
> start server
> shutdown server using "shutdown.bat"
> It shows an error:
> 2009-09-15 13:07:51,367 WARN  [ConnectorGBean] TomcatWebConnector connector 
> failed
> 2009-09-15 13:07:51,445 ERROR [GBeanInstanceState] Error while stopping; 
> GBean is now in the FAILED state: 
> abstractName="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebConnector"
> java.lang.Exception: Problem while updaing the persistent value of attibute: 
> Attribute Name: keystoreFile, Type: class java.lang.String, GBeanInstance: 
> Tomcat Connector HTTP BIO
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1080)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638)
>   at org.apache.geronimo.kernel.KernelGBean.shutdown(KernelGBean.java:382)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.reflect.Method.invoke(Method.java:599)
>   at 
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
>   at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275)
>   at 
> java.security.AccessController.doPrivileged(AccessController.java:284)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1377)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.re

[jira] Assigned: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.

[Shawn Jiang (JIRA)]

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

Shawn Jiang reassigned GERONIMO-4850:
-

Assignee: Shawn Jiang

> WADI clustering: the application no node B will not start up when start up 
> the node B. 
> ---
>
> Key: GERONIMO-4850
> URL: https://issues.apache.org/jira/browse/GERONIMO-4850
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
>Assignee: Shawn Jiang
>
> 1.I configuration two nodes A and B following the WADI clustering and deploy 
> the cviewer.war on the node A the no the node B there is cviewer.war also and 
> they work well on 2 nodes.
> 2.shutdown A node first and then shutdown B node, I find that the cviewer.war 
> load is set false in the config.xml of node B.
> 3 .start A and B, the cviewer.war on the node B can not start automatically.

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

[jira] Assigned: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector

[Shawn Jiang (JIRA)]

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

Shawn Jiang reassigned GERONIMO-4877:
-

Assignee: Shawn Jiang

> Modification to keystoreFile doesn't work for HTTPS connector
> -
>
> Key: GERONIMO-4877
> URL: https://issues.apache.org/jira/browse/GERONIMO-4877
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 2.2
> Environment: win server 2008, jdk 1.6
>Reporter: Shiny Cheng
>Assignee: Shawn Jiang
>
> Once I tried to edit a created HTTPS connector, either BIO or NIO, I found 
> that the modification to value of keystoreFile didn't work. After I saved my 
> modification and re-click on "edit" to check my setting, its value still 
> remained as the one I input at the first time. 

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

[jira] Created: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector

[Shiny Cheng (JIRA)]

Modification to keystoreFile doesn't work for HTTPS connector
-

 Key: GERONIMO-4877
 URL: https://issues.apache.org/jira/browse/GERONIMO-4877
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tomcat
Affects Versions: 2.2
 Environment: win server 2008, jdk 1.6
Reporter: Shiny Cheng


Once I tried to edit a created HTTPS connector, either BIO or NIO, I found that 
the modification to value of keystoreFile didn't work. After I saved my 
modification and re-click on "edit" to check my setting, its value still 
remained as the one I input at the first time. 

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

[jira] Resolved: (GERONIMODEVTOOLS-504) advanced security section does not allow setting of credential store

[Delos Dai (JIRA)]

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

Delos Dai resolved GERONIMODEVTOOLS-504.


   Resolution: Fixed
Fix Version/s: 2.1.5
 Assignee: Delos Dai

Since credential store is a type of gbean, the attributes of it can be modified 
in gbean wizard. For this JIRA, I revise the UI to let user select deployed 
credential store and its default subjects. If it needs more improvement, 
another JIRA can be created.

revision #815007 for trunk; revision #815051 for 2.1.5 branch.

Thanks!

> advanced security section does not allow setting of credential store
> 
>
> Key: GERONIMODEVTOOLS-504
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-504
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
> Environment: Ganymede on Windows 
>Reporter: B.J. Reed
>Assignee: Delos Dai
> Fix For: 2.1.5, 2.2.0
>
>
> When editing the Web deployment plan (and probably the application and EJB as 
> well), clicking the Credential Store Edit button does nothing.  Have traced 
> through the code and when the button is selected, a call to 
> getCredentialStoreRefWizard is made in SecurityAdvancedSection.java.  This 
> method simply returns null without bringing up a dialog and setting the 
> field.  With this function disabled, most of the rest of the advanced 
> security options are also disabled.

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

[jira] Closed: (GERONIMODEVTOOLS-579) java specs are not included into G server runtime by default

[viola.lu (JIRA)]

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

viola.lu closed GERONIMODEVTOOLS-579.
-


Fixed in latest build.Close it.

> java specs are not included into G server runtime by default
> 
>
> Key: GERONIMODEVTOOLS-579
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.2.0
> Environment: os:win2003
>Reporter: viola.lu
>Assignee: Tim McConnell
>Priority: Minor
> Fix For: 2.1.5, 2.2.0
>
> Attachments: 579.patch
>
>
> 1.Create a web dynamic project ,and add <%@ taglib 
> uri="http://java.sun.com/jsf/core"; prefix='f' %> to a jsp file
> 2.But can't recognize this taglib
> In 
> $GEPsrc\plugins\org\apache\geronimo\st\core\GeronimoServerRuntimeTargetHandler.java
>  file, no support for 2.2 target runtime, so myface spec, javamail spec  
> are not included by default.

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

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755362#action_12755362
 ] 

Rex Wang commented on GERONIMO-4855:


Thanks Viola for pointing out this, so it looks like a configuration problem 
and not a bug to me. Ben, please re-test it and update the document if needed.

-Rex

> Clustering can not work when the application needs login information
> 
>
> Key: GERONIMO-4855
> URL: https://issues.apache.org/jira/browse/GERONIMO-4855
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
> Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war
>
>
> When I using WADI clustering and tomcat native clustering there are the same 
> problem:
> If the application on the different node needs the security information to 
> access some page then firefox gives the following error information:
> HTTP Status 404 - /demo/protect/j_security_check
> type Status report
> message /demo/protect/j_security_check
> description The requested resource (/demo/protect/j_security_check) is not 
> available.
> so it is likely clustering can not access any resource which need security 
> check.

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

[jira] Commented: (GERONIMO-4876) "java.lang.Exception" when I shutdown the server

[Shawn Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755355#action_12755355
 ] 

Shawn Jiang commented on GERONIMO-4876:
---

can't recreate this, please be more specific on the reproducing steps.

> "java.lang.Exception"  when I shutdown the server
> -
>
> Key: GERONIMO-4876
> URL: https://issues.apache.org/jira/browse/GERONIMO-4876
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector
>Affects Versions: 2.2
> Environment: jdk6
> windows xp sp2
>Reporter: Bin He
>
> start server
> shutdown server using "shutdown.bat"
> It shows an error:
> 2009-09-15 13:07:51,367 WARN  [ConnectorGBean] TomcatWebConnector connector 
> failed
> 2009-09-15 13:07:51,445 ERROR [GBeanInstanceState] Error while stopping; 
> GBean is now in the FAILED state: 
> abstractName="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebConnector"
> java.lang.Exception: Problem while updaing the persistent value of attibute: 
> Attribute Name: keystoreFile, Type: class java.lang.String, GBeanInstance: 
> Tomcat Connector HTTP BIO
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1080)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638)
>   at org.apache.geronimo.kernel.KernelGBean.shutdown(KernelGBean.java:382)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.reflect.Method.invoke(Method.java:599)
>   at 
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
>   at 
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275)
>   at 
> java.security.AccessController.doPrivileged(AccessController.java:284)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1377)
>   at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccesso

[jira] Closed: (GERONIMO-4854) The protocol option will be reset after testing connection when addint server

[Rex Wang (JIRA)]

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

Rex Wang closed GERONIMO-4854.
--


> The protocol option will be reset after testing connection when addint server
> -
>
> Key: GERONIMO-4854
> URL: https://issues.apache.org/jira/browse/GERONIMO-4854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Affects Versions: 2.2
> Environment: windows sp3
>Reporter: Siqi Du
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: monitoring.patch
>
>
> In the addServer portlet 
> 1 fill the blank with the protocal option set to jmx
> 2 test connection
> 3 protocol option is reset to ejb but other info remains

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

[jira] Commented: (GERONIMO-4790) Migrate debug-views code to base on the up-to-date dojo

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755351#action_12755351
 ] 

Rex Wang commented on GERONIMO-4790:


All the sub tasks have been resolved. Will close it if there is no further 
issues.
-Rex

> Migrate debug-views code to base on the up-to-date dojo
> ---
>
> Key: GERONIMO-4790
> URL: https://issues.apache.org/jira/browse/GERONIMO-4790
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2
>
> Attachments: classloader-viewer.jpg, dependency-viewer.jpg, 
> jmx-viewer.jpg, JNDI-viewer.jpg, ldap-viewer.jpg
>
>
> ref http://www.nabble.com/Re%3A-Which-dojo--p24293149s134.html
> Currently, our console depends on two different versions of dojo library. One 
> is 1.3.0, which is used by EJB portlet and just updated from 1.2.1 
> (GERONIMO-4723) and fixed a bug(GERONIMO-4746). I hope we can go on updating 
> it to the latest version 1.3.2.
> The other one is 0.4.3, the legacy lib, which has not been supported  by dojo 
> team, but used by our debug-view portlets, I prefer to update it to the 
> latest lib, and the advantage are as follows:
> 1. keep consistent in the portlet page style with the EJB portlet
> 2. reduce a bit to the geronimo footprint size
> 3. Although we have ported the dojo-legacy to build the source in 
> external(GERONIMO-4750), with this update, we don't need that as well.
> 4. will be more easy to maintainance the program logic by using the unified 
> dojo lib.
> 5. the doc of 1.3.x is good and easy to find.
> There are also some risks:
> 1. There has been so much changes between the dojo versions that the effort 
> might be 1-2 week to complete.
> 2. I did not find any documents for the old dojo lib, so it might be easier 
> to re-write the whole pages to base on 1.3.x and dwr 3.0.x(we have upgrade 
> the dwr successfully in GERONIMO-4753), but I not sure.
> Any thoughts?
> -Rex

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

[jira] Resolved: (GERONIMO-4832) Modify EJB portlets to fit the new APIs of Tree and TreeEntry

[Rex Wang (JIRA)]

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

Rex Wang resolved GERONIMO-4832.


   Resolution: Fixed
Fix Version/s: 3.0
   2.2

rev 814996 for trunk

> Modify EJB portlets to fit the new APIs of Tree and TreeEntry
> -
>
> Key: GERONIMO-4832
> URL: https://issues.apache.org/jira/browse/GERONIMO-4832
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2, 3.0
>
>


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

[jira] Created: (GERONIMO-4876) "java.lang.Exception" when I shutdown the server

[Bin He (JIRA)]

"java.lang.Exception"  when I shutdown the server
-

 Key: GERONIMO-4876
 URL: https://issues.apache.org/jira/browse/GERONIMO-4876
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: connector
Affects Versions: 2.2
 Environment: jdk6
windows xp sp2
Reporter: Bin He


start server
shutdown server using "shutdown.bat"
It shows an error:

2009-09-15 13:07:51,367 WARN  [ConnectorGBean] TomcatWebConnector connector 
failed
2009-09-15 13:07:51,445 ERROR [GBeanInstanceState] Error while stopping; GBean 
is now in the FAILED state: 
abstractName="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebConnector"
java.lang.Exception: Problem while updaing the persistent value of attibute: 
Attribute Name: keystoreFile, Type: class java.lang.String, GBeanInstance: 
Tomcat Connector HTTP BIO
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1080)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546)
at 
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421)
at 
org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339)
at 
org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661)
at 
org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638)
at org.apache.geronimo.kernel.KernelGBean.shutdown(KernelGBean.java:382)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at 
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
at 
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
at 
org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
at 
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437)
at 
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)
at 
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275)
at 
java.security.AccessController.doPrivileged(AccessController.java:284)
at 
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1377)
at 
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:310)
at sun.rmi.transport.Transport$1.run(Transport.java:171)
at 
java.security.AccessController.doPrivileged(AccessController.java:284)
at sun.rmi.transport.Transport.serviceCall(Transport.java:167)
at 
sun.rmi.transp

[jira] Commented: (GERONIMO-4832) Modify EJB portlets to fit the new APIs of Tree and TreeEntry

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755349#action_12755349
 ] 

Rex Wang commented on GERONIMO-4832:


rev814992 for branch 2.2

> Modify EJB portlets to fit the new APIs of Tree and TreeEntry
> -
>
> Key: GERONIMO-4832
> URL: https://issues.apache.org/jira/browse/GERONIMO-4832
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Reporter: Rex Wang
>Assignee: Rex Wang
>


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

[jira] Updated: (GERONIMODEVTOOLS-456) Add Security Realm Wizard to GEP to deploy security realm directly from GEP

[Rodger Zhang (JIRA)]

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

Rodger Zhang updated GERONIMODEVTOOLS-456:
--

Attachment: updated_security_realm.patch

replace the patch "wizard_for_add_security_realm_to_plan.patch", improved.


> Add Security Realm Wizard to GEP to deploy security realm directly from GEP
> ---
>
> Key: GERONIMODEVTOOLS-456
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 2.1.3
>Reporter: Saurabh Sharma
>Assignee: Saurabh Sharma
> Fix For: 2.2.0
>
> Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, 
> updated_security_realm.patch, wizard_for_add_security_realm_to_plan.patch
>
>


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

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[viola.lu (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755336#action_12755336
 ] 

viola.lu commented on GERONIMO-4855:


First, pls add  element to your app web.xml
Second:modify  Engine setting in you server.xml under $G_Dir/var/catalina/ with 
below:


Make sure your mod_jk or mod_proxy server node name same as jvmRoute 
definition, which is used to enable sticky session.
After that, your login page will sticky to one server, no 404 error.Login 
Verification is a built-in process, not relation with Servlet or JSP.

> Clustering can not work when the application needs login information
> 
>
> Key: GERONIMO-4855
> URL: https://issues.apache.org/jira/browse/GERONIMO-4855
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
>Reporter: liangkun
> Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war
>
>
> When I using WADI clustering and tomcat native clustering there are the same 
> problem:
> If the application on the different node needs the security information to 
> access some page then firefox gives the following error information:
> HTTP Status 404 - /demo/protect/j_security_check
> type Status report
> message /demo/protect/j_security_check
> description The requested resource (/demo/protect/j_security_check) is not 
> available.
> so it is likely clustering can not access any resource which need security 
> check.

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

[jira] Updated: (GERONIMO-4831) stop building dojo-0.4.3 from ext

[Rex Wang (JIRA)]

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

Rex Wang updated GERONIMO-4831:
---

Description: cause we don't need dojo-legacy ever.  (was: we don't need 
dojo-legacy that with these changes .)
Summary: stop building dojo-0.4.3 from ext  (was: remove dojo-legacy 
from our code base.)

> stop building dojo-0.4.3 from ext
> -
>
> Key: GERONIMO-4831
> URL: https://issues.apache.org/jira/browse/GERONIMO-4831
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2, 3.0
>
>
> cause we don't need dojo-legacy ever.

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

[jira] Resolved: (GERONIMO-4831) stop building dojo-0.4.3 from ext

[Rex Wang (JIRA)]

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

Rex Wang resolved GERONIMO-4831.


   Resolution: Fixed
Fix Version/s: 3.0

> stop building dojo-0.4.3 from ext
> -
>
> Key: GERONIMO-4831
> URL: https://issues.apache.org/jira/browse/GERONIMO-4831
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2, 3.0
>
>
> cause we don't need dojo-legacy ever.

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

[jira] Commented: (GERONIMO-4831) remove dojo-legacy from our code base.

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755325#action_12755325
 ] 

Rex Wang commented on GERONIMO-4831:


rev 814985

remove the ext/trunk/geronimo-dojo-0.4.3

> remove dojo-legacy from our code base.
> --
>
> Key: GERONIMO-4831
> URL: https://issues.apache.org/jira/browse/GERONIMO-4831
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2
>
>
> we don't need dojo-legacy that with these changes .

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

[jira] Resolved: (GERONIMO-4830) Commit new debug-view portlets codes

[Rex Wang (JIRA)]

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

Rex Wang resolved GERONIMO-4830.


   Resolution: Fixed
Fix Version/s: 3.0

rev814983 for trunk

> Commit new debug-view portlets codes
> 
>
> Key: GERONIMO-4830
> URL: https://issues.apache.org/jira/browse/GERONIMO-4830
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2, 3.0
>
>
> commit new codes to branch 2.2 and  trunk.

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

[jira] Commented: (GERONIMODEVTOOLS-261) Incorporate maven-remote-resources-plugin

[Delos Dai (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755320#action_12755320
 ] 

Delos Dai commented on GERONIMODEVTOOLS-261:


I'm not quite clear about what you mean by "geronimo-crypto". 

Currently, the license file and notice file in GEP contains not only the 
"Apache" license content but also some other licenses. So I'm afraid it may be 
troublesome to incorporate maven-remote-resources-plugin only for GEP.  

Suggest to incorporate maven-remote-resources-plugin once Geronimo server start 
to make use of maven-remote-resources-plugin.

> Incorporate maven-remote-resources-plugin 
> --
>
> Key: GERONIMODEVTOOLS-261
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-261
> Project: Geronimo-Devtools
>  Issue Type: Improvement
>  Components: eclipse-plugin
>Affects Versions: 2.1.2
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.2.0
>
>


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

[jira] Created: (GERONIMO-4875) "edit" button shows under "Created" label when i create a new view

[Bin He (JIRA)]

"edit" button shows under "Created"  label  when  i create a new view
-

 Key: GERONIMO-4875
 URL: https://issues.apache.org/jira/browse/GERONIMO-4875
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
 Environment: jdk6
windows xp sp2
Reporter: Bin He
Priority: Minor


Start server
Click monitoring porlet
Create a new view and you can see that  the "edit" button is under "Created" 
label.and there is nothing under "Modified" label and "Actions" label.
In geronomo 2114 and geronimo 2115 ,under "Created" and "Modified" is  some 
time ,under "Actions" is the Edit button.

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

Re: There's still hope for 2.2...

[Jack Cai]

I finished the patch for the console filter to improve its performance:
https://issues.apache.org/jira/browse/GERONIMO-4874

Hopefully someone could review it...

-Jack

On Mon, Sep 14, 2009 at 10:53 PM, Forrest Xia  wrote:

>
>
> On Mon, Sep 14, 2009 at 10:48 PM, Donald Woods  wrote:
>
>> I'm still working on Daytrader 2.2, but could use some help updating and
>> testing the Daytrader plugins and plans.
>>
>>
>> -Donald
>
>
> Donald, once you roll out all of changes on daytrader 2.2, I will have a
> testing on it.
>

[BUILD] branches/2.2: Failed for Revision: 814941

[gawor]

Geronimo Revision: 814941 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 4 seconds
[INFO] Finished at: Mon Sep 14 20:44:23 EDT 2009
[INFO] Final Memory: 331M/894M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/logs-2000-tomcat/
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:49.722
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:24.118) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:39.176) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:47.899) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:23.867) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:37.500) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:41.341) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:07.908) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:57.247) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:37.002) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:52.674) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:37.942) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.907) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:40.159) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:19.178) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:23.116) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:58.503) 
[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS (0:00:34.711) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:01:00.808) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:57.571) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.650) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:33.918) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test

Re: The setting of LoginDomainName attribute of the LoginModuleGBean

[chi runhua]

I think this is the page that David mentioned:

http://cwiki.apache.org/GMOxDOC22/configuring-login-modules.html

Jeff C

On Tue, Sep 15, 2009 at 4:56 AM, Quintin Beukes wrote:

> For interest sake, how would you use this to implement the below?
>
> If you have a doc specifying this, can you send me the link. This
> explanation made it sound interesting, as I myself have wondered about
> the WrappingLoginModule.
>
> Q
>
> On Mon, Sep 14, 2009 at 6:42 PM, David Jencks 
> wrote:
> >
> > On Sep 14, 2009, at 12:51 AM, Ivan wrote:
> >
> >> Hi
> >>  In the LoginModuleGBean, there is an attribute named loginDomainName, I
> >> went through the codes, just found that while the WrappingLoginModule is
> >> turned on, those domainNames are used in the Subject as DomainPrincipal.
> >> Except for this, is there any use for those loginDomainNames ? And, I
> did
> >> not found any example for WrappingLoginModule, so when we would use it ?
> >>  Thanks !
> >
> > I thought this was documented somewhere, but I could easily be wrong, and
> > the explanation might not include enough info for anyone to know why...
> >
> > Most people use the simplest form of principal-role mapping, where you
> > specify the class and name of the actual Principal from the login module
> you
> > specify.  However, it's possible to think up more complicated scenarios
> > where this is not enough to identify the principal for the principal-role
> > mapping.
> >
> > lets suppose you have an ejb app C with 2 web apps A and B in front of
> it.
> >  Your ejb app has 2 roles r1 and r2.  You have two legacy security
> systems
> > S1 and S2 with proprietary login modules that both happen to supply the
> same
> > principal class.  You need to use S1 with A and S2 with B.  S1 and S2
> both
> > provide principals with names "g1" and "g2" but the meaning is
> opposite.
> > you need
> >
> > For S1 and A,
> > "g1" > r1
> > "g2" > r2
> >
> > but for S2 and B,
> > "g1" > r2
> > "g2" > r1
> >
> > So, you need more information to distinguish the principals so you can
> map
> > them to the correct roles.  Geronimo lets you wrap the original
> principals
> > with a wrapper that contains a name of the login module "loginDomainName"
> > and the name of the security realm, and the principal-role mapping can
> > specify these as well.  You'd use the loginDomainName if you set up a
> single
> > security realm that includes the login modules for S1 and S2, and the
> > security realm if you set up two separate security realms.
> >
> > I don't know if anyone has used this or ever will, but we thought we'd be
> > thorough.
> >
> > thanks
> > david jencks
> >
> >> --
> >> Ivan
> >
> >
>
>
>
> --
> Quintin Beukes
>

[jira] Commented: (GERONIMO-4874) Improve the console filter performance

[Jack Cai (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755301#action_12755301
 ] 

Jack Cai commented on GERONIMO-4874:


Forgot to mention, the below two files can be removed if the attached patch is 
applied.

plugins/console/console-filter/src/main/java/org/apache/geronimo/console/filter/FilterResponseWrapper.java
plugins/console/console-filter/src/main/java/org/apache/geronimo/console/filter/ResponseOutputStream.java


> Improve the console filter performance
> --
>
> Key: GERONIMO-4874
> URL: https://issues.apache.org/jira/browse/GERONIMO-4874
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
> Environment: All
>Reporter: Jack Cai
>Priority: Minor
> Attachments: GERONIMO-4874.patch
>
>
> Current console filter for blocking XSRF attack does not scale well as it 
> need to read all the output into a string and then do some text replacement. 
> This will use a lot of memory in extreme cases. See the discussion [1].
> [1] http://www.nabble.com/XSRFHandler-question-td24545409s134.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-4874) Improve the console filter performance

[Jack Cai (JIRA)]

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

Jack Cai updated GERONIMO-4874:
---

Attachment: GERONIMO-4874.patch

I use the nio buffers and charset decoders to do the text scan and replacement 
in a stream-style. The performance is improved in two aspects -

1. Less memory consumption. The output is written out as it comes in. No need 
to hold a big chunk of data in memory.
2. Less charset decoding/encoding overhead. The original filter will encode 
text into byte array and then decode again. The patch will scan text directly.

I tested the new filter with the admin console by clicking through most of the 
pages. Everything looks good.

The patch can be applied to branch 2.1, branch 2.2 and trunk.

> Improve the console filter performance
> --
>
> Key: GERONIMO-4874
> URL: https://issues.apache.org/jira/browse/GERONIMO-4874
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
> Environment: All
>Reporter: Jack Cai
>Priority: Minor
> Attachments: GERONIMO-4874.patch
>
>
> Current console filter for blocking XSRF attack does not scale well as it 
> need to read all the output into a string and then do some text replacement. 
> This will use a lot of memory in extreme cases. See the discussion [1].
> [1] http://www.nabble.com/XSRFHandler-question-td24545409s134.html

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

Re: documentation is important too

[chi runhua]

Yes, I agree that documentation is really important to the success of
Geronimo.

We have lots of changes in terms of security, web container integration
mechanism as well as GEP improvements for G2.2, and we know some of
information are not well documented yet. For the current status of G2.2 doc
development, you may refer to

http://cwiki.apache.org/GMOxDOC22/apache-geronimo-v22-documentation-development-status.html

Beyond these items listed, I believe there are lots of topics to be updated
such as new samples, screenshots and so on. Therefore, we would appreciate
any individual who can contribute to the documents and especially for those
who has successful experiences with configuration of certain components.

As for the examples that you mentioned, in my understanding,  G Doc already
has certain topics for those:
1. Database security realm, you may refer to
http://cwiki.apache.org/GMOxDOC22/database-sql-realm.html
2. Real samples, we have sample applications for test and evaluation, you
may refer to
http://cwiki.apache.org/GMOxDOC22/sample-applications.html#Sampleapplications-AvailableSampleApplicationsor
WAS CE samples which can be deployed on Geronimo as well
3. Tutorial for various applications' development, which might not cover
every corner by now but it would be
applaudable**if we could have more
and more tutorials on website. For this part, you may
refer to
   http://cwiki.apache.org/GMOxDOC22/developing-web-applications.html
   http://cwiki.apache.org/GMOxDOC22/developing-ejb-applications.html
   http://cwiki.apache.org/GMOxDOC22/developing-jpa-applications.html
   http://cwiki.apache.org/GMOxDOC22/developing-application-clients.html
   http://cwiki.apache.org/GMOxDOC22/developing-web-services.html

We'd like to hear more about your comments to the document such as the
documents are not well-orgnized? what kind of topics are missing? Or you can
share your experience briefly, we can help to document? I think more details
will do more help.

Thanks alot.

Jeff C




On Tue, Sep 15, 2009 at 5:27 AM, Radim Kolar  wrote:

>
>
> Quintin Beukes-2 wrote:
> >
> > They're all small errors, and I listed them because they can
> > potentially damage Geronimo's image by complicating a user's
> > experience. User experience is the biggest factor in a product's
> > success.
> >
> I see it that biggest problem with Geronimo is lack of good documentation,
> mainly good documentation on security is still missing. After reading users
> mailing list for a while people asks for documents about:
>
> How to secure internal derby database from connections into geronimo from
> outside? They want to have something like: for database XYZ user X and Y
> can
> connect. it can be probably done by binding security realm into database.
> it
> would be great if we can click it in gui.
>
> same thing for message queues.
>
> oh and deployment plans are another topic. There are some samples on doc
> website but i would really like to see some real world example for example
> web application with more modules, jpa and message queues. it took me
> almost
> entire day until i managed to write it correctly myself.
> --
> View this message in context:
> http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25443963.html
> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
>
>

[jira] Created: (GERONIMO-4874) Improve the console filter performance

[Jack Cai (JIRA)]

Improve the console filter performance
--

 Key: GERONIMO-4874
 URL: https://issues.apache.org/jira/browse/GERONIMO-4874
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0
 Environment: All
Reporter: Jack Cai
Priority: Minor


Current console filter for blocking XSRF attack does not scale well as it need 
to read all the output into a string and then do some text replacement. This 
will use a lot of memory in extreme cases. See the discussion [1].

[1] http://www.nabble.com/XSRFHandler-question-td24545409s134.html

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

[jira] Issue Comment Edited: (GERONIMO-4830) Commit new debug-view portlets codes

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755298#action_12755298
 ] 

Rex Wang edited comment on GERONIMO-4830 at 9/14/09 6:42 PM:
-

rev814960 for branch 2.2
submit the new debug-views codes and delete the dojo-legacy from server.

-Rex


  was (Author: rwonly):
rev814960
submit the new debug-views codes and delete the dojo-legacy from server.

-Rex

  
> Commit new debug-view portlets codes
> 
>
> Key: GERONIMO-4830
> URL: https://issues.apache.org/jira/browse/GERONIMO-4830
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2
>
>
> commit new codes to branch 2.2 and  trunk.

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

[jira] Commented: (GERONIMO-4830) Commit new debug-view portlets codes

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755298#action_12755298
 ] 

Rex Wang commented on GERONIMO-4830:


rev814960
submit the new debug-views codes and delete the dojo-legacy from server.

-Rex


> Commit new debug-view portlets codes
> 
>
> Key: GERONIMO-4830
> URL: https://issues.apache.org/jira/browse/GERONIMO-4830
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2
>
>
> commit new codes to branch 2.2 and  trunk.

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

[gawor]

Geronimo Revision: 814948 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@341c341c
[WARNING] Component returned which is not the same manager. Ignored. 
component

Re: [VOTE] txmanager 2.1.3 2nd try

[Kevan Miller]

+1

--kevan
On Sep 13, 2009, at 3:58 AM, David Jencks wrote:


I fixed the build problem where we weren't building the test jars.

I've set up a release candidate for the transaction manager and  
connector code 2.1.3, needed for geronimo 2.2:


https://repository.apache.org/content/repositories/geronimo-staging-012/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/

There are some problems with the site (non-existent extra modules)  
but I'd rather fix them by hand if necessary than try to decipher  
how to get the site build to work automatically.


This includes mostly some bug fixes in the pooling code that make  
tying a connection to a thread work.  This should make it a lot  
easier to make cases where you open several connections and then  
start a user transaction work properly, as they can now share the  
same managed connection.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 don't release

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

[Kevan Miller]

+1

--kevan
On Sep 11, 2009, at 12:38 PM, Guillaume Nodet wrote:


I've uploaded another 1.0.0 release of the blueprint project.
I think I've addressed all the issues raised in the discussion thread.

The staging repository is available at:
https://repository.apache.org/content/repositories/geronimo-staging-005/

The corresponding tag is available at
 
http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/

Please review and vote:
[  ] +1 Release
[  ] -1 Do not release

The vote will remain open for 72 hours.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: [VOTE] geronimo-jacc_1.1_spec version 1.0.2

[Kevan Miller]

+1

--kevan
On Sep 10, 2009, at 8:16 PM, David Jencks wrote:


I've built a release candidate for the jacc spec jar:

https://repository.apache.org/content/repositories/geronimo-staging-002/

Site is staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/

Along with a bunch of build improvements this includes these fixes:

GERONIMO-4357 don't double escape pre-escaped colons in web  
permissions


GERONIMO-4587 fix EJBMethodPermission construction problem when a  
method param is an array, patch (slightly modified) from Shawn Jiang


r788107 ensure HTTPMethodSpec.getActions() returns right information  
- otherwise reserialized permission objects could loose some vital  
information. Also, add serialVersionUID constants


GERONIMO-4721 represent 'all http methods' with '' rather than '\!'  
when computing the actions string in web permissions


GERONIMO-4735 serialize EJBMethodPermissionCollection contents only  
once


GERONIMO-4734 fix web permissions HTTPMethodSpec equals method

GERONIMO-4766, sort of.  Use generics and make policy context  
handler registration slightly more thread safe.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 Don't release it

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] release jaspic implementation component 1.0

[Kevan Miller]

Spot check of checksums looks good. Here's my +1. Thanks David!

--kevan
On Sep 10, 2009, at 10:08 PM, David Jencks wrote:

It's time for the first release of our jaspic implementation for  
inclusion in g. 2.2.


Release artifacts staged here:

https://repository.apache.org/content/repositories/geronimo-staging-003/

Site staged here:

http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/

When used in geronimo with tomcat or jetty, this passed the jaspic  
tck web profile.  So far we don't try to implement the soap profile  
in geornimo; this implementation should support  both.



[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.

Vote open for 72 hours.

thanks
david jencks

Re: [VOTE] release jaspic implementation component 1.0

[Kevan Miller]

On Sep 14, 2009, at 5:41 PM, David Jencks wrote:

This turned out to be because I was inadvertently using maven 2.2  
for these releases, which has a problem with uploading files twice  
to nexus, and calculating the checksum on the doubled file.


Good to know.



John Casey regenerated the checksums on all the staging repos for  
me.  I checked a couple and they match my local checksums.  Do you  
have a moderately automated way to check these or should I go  
through and verify them all one by one?


I find staging at repository.apache.org difficult to deal with in that  
regard. It may be that somebody may have an automated technique, but I  
don't... ;-)




I'm hoping that since the actual artfifacts didn't change, just the  
derived checksums, we won't need to reroll the staging and vote.   
WDYT?


Agreed.

--kevan

Re: [VOTE] geronimo-jacc_1.1_spec version 1.0.2

[David Jencks]

I guess I missed fixing that one. I think that may be in all the  
individual spec jar LICENSE files.


I think we should fix this in svn for the next release but not redo  
the vote for this problem.


thanks
david jencks

On Sep 14, 2009, at 1:00 PM, Kevan Miller wrote:

The license file contains a W3C license for XMLSchema.dtd. However,  
the generated jar file does not contain the license. AFAICT, there's  
no need for this license. Am I missing something?


--kevan
On Sep 10, 2009, at 8:16 PM, David Jencks wrote:


I've built a release candidate for the jacc spec jar:

https://repository.apache.org/content/repositories/geronimo-staging-002/

Site is staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/

Along with a bunch of build improvements this includes these fixes:

GERONIMO-4357 don't double escape pre-escaped colons in web  
permissions


GERONIMO-4587 fix EJBMethodPermission construction problem when a  
method param is an array, patch (slightly modified) from Shawn Jiang


r788107 ensure HTTPMethodSpec.getActions() returns right  
information - otherwise reserialized permission objects could loose  
some vital information. Also, add serialVersionUID constants


GERONIMO-4721 represent 'all http methods' with '' rather than '\!'  
when computing the actions string in web permissions


GERONIMO-4735 serialize EJBMethodPermissionCollection contents only  
once


GERONIMO-4734 fix web permissions HTTPMethodSpec equals method

GERONIMO-4766, sort of.  Use generics and make policy context  
handler registration slightly more thread safe.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 Don't release it

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] release jaspic implementation component 1.0

[David Jencks]

This turned out to be because I was inadvertently using maven 2.2 for  
these releases, which has a problem with uploading files twice to  
nexus, and calculating the checksum on the doubled file.


John Casey regenerated the checksums on all the staging repos for me.   
I checked a couple and they match my local checksums.  Do you have a  
moderately automated way to check these or should I go through and  
verify them all one by one?


I'm hoping that since the actual artfifacts didn't change, just the  
derived checksums, we won't need to reroll the staging and vote.  WDYT?


thanks
david jencks


On Sep 14, 2009, at 11:56 AM, Kevan Miller wrote:


Dave,
It looks like the md5 and sha1 checksums are bad on all of your  
release votes. I'm now -1 until resolved.


--kevan
On Sep 10, 2009, at 10:08 PM, David Jencks wrote:

It's time for the first release of our jaspic implementation for  
inclusion in g. 2.2.


Release artifacts staged here:

https://repository.apache.org/content/repositories/geronimo-staging-003/

Site staged here:

http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/

When used in geronimo with tomcat or jetty, this passed the jaspic  
tck web profile.  So far we don't try to implement the soap profile  
in geornimo; this implementation should support  both.



[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.

Vote open for 72 hours.

thanks
david jencks

documentation is important too

[Radim Kolar]

Quintin Beukes-2 wrote:
> 
> They're all small errors, and I listed them because they can
> potentially damage Geronimo's image by complicating a user's
> experience. User experience is the biggest factor in a product's
> success.
> 
I see it that biggest problem with Geronimo is lack of good documentation,
mainly good documentation on security is still missing. After reading users
mailing list for a while people asks for documents about:

How to secure internal derby database from connections into geronimo from
outside? They want to have something like: for database XYZ user X and Y can
connect. it can be probably done by binding security realm into database. it
would be great if we can click it in gui.

same thing for message queues.

oh and deployment plans are another topic. There are some samples on doc
website but i would really like to see some real world example for example
web application with more modules, jpa and message queues. it took me almost
entire day until i managed to write it correctly myself.
-- 
View this message in context: 
http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25443963.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: The setting of LoginDomainName attribute of the LoginModuleGBean

[Quintin Beukes]

For interest sake, how would you use this to implement the below?

If you have a doc specifying this, can you send me the link. This
explanation made it sound interesting, as I myself have wondered about
the WrappingLoginModule.

Q

On Mon, Sep 14, 2009 at 6:42 PM, David Jencks  wrote:
>
> On Sep 14, 2009, at 12:51 AM, Ivan wrote:
>
>> Hi
>>  In the LoginModuleGBean, there is an attribute named loginDomainName, I
>> went through the codes, just found that while the WrappingLoginModule is
>> turned on, those domainNames are used in the Subject as DomainPrincipal.
>> Except for this, is there any use for those loginDomainNames ? And, I did
>> not found any example for WrappingLoginModule, so when we would use it ?
>>  Thanks !
>
> I thought this was documented somewhere, but I could easily be wrong, and
> the explanation might not include enough info for anyone to know why...
>
> Most people use the simplest form of principal-role mapping, where you
> specify the class and name of the actual Principal from the login module you
> specify.  However, it's possible to think up more complicated scenarios
> where this is not enough to identify the principal for the principal-role
> mapping.
>
> lets suppose you have an ejb app C with 2 web apps A and B in front of it.
>  Your ejb app has 2 roles r1 and r2.  You have two legacy security systems
> S1 and S2 with proprietary login modules that both happen to supply the same
> principal class.  You need to use S1 with A and S2 with B.  S1 and S2 both
> provide principals with names "g1" and "g2" but the meaning is opposite.
> you need
>
> For S1 and A,
> "g1" > r1
> "g2" > r2
>
> but for S2 and B,
> "g1" > r2
> "g2" > r1
>
> So, you need more information to distinguish the principals so you can map
> them to the correct roles.  Geronimo lets you wrap the original principals
> with a wrapper that contains a name of the login module "loginDomainName"
> and the name of the security realm, and the principal-role mapping can
> specify these as well.  You'd use the loginDomainName if you set up a single
> security realm that includes the login modules for S1 and S2, and the
> security realm if you set up two separate security realms.
>
> I don't know if anyone has used this or ever will, but we thought we'd be
> thorough.
>
> thanks
> david jencks
>
>> --
>> Ivan
>
>



-- 
Quintin Beukes

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

[Guillaume Nodet]

Added.

On Mon, Sep 14, 2009 at 20:37, Kevan Miller  wrote:
> Guillaume,
> Your PGP key is missing from the Geronimo KEYS file --
> https://svn.apache.org/repos/asf/geronimo/KEYS
>
> --kevan
> On Sep 11, 2009, at 12:38 PM, Guillaume Nodet wrote:
>
>> I've uploaded another 1.0.0 release of the blueprint project.
>> I think I've addressed all the issues raised in the discussion thread.
>>
>> The staging repository is available at:
>> https://repository.apache.org/content/repositories/geronimo-staging-005/
>>
>> The corresponding tag is available at
>>
>>  http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/
>>
>> Please review and vote:
>> [  ] +1 Release
>> [  ] -1 Do not release
>>
>> The vote will remain open for 72 hours.
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> 
>> Blog: http://gnodet.blogspot.com/
>> 
>> Open Source SOA
>> http://fusesource.com
>
>



-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: [VOTE] txmanager 2.1.3 2nd try

[Kevan Miller]

Changing my vote to -1 until the checksum issues are resolved.
--kevan
On Sep 13, 2009, at 1:45 PM, Kevan Miller wrote:


+1

Source, build, and generated binaries look good.

There's a problem with the staging and site links in your note,  
however. The text of the links is correct. However, both hrefs refer  
to an invalid url (eg. http://people.apache.org/~djencks/staging-site/maven/txmanager/2.1.3/ 
 ), which does not exist.


--kevan

On Sep 13, 2009, at 3:58 AM, David Jencks wrote:


I fixed the build problem where we weren't building the test jars.

I've set up a release candidate for the transaction manager and  
connector code 2.1.3, needed for geronimo 2.2:


https://repository.apache.org/content/repositories/geronimo-staging-012/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/

There are some problems with the site (non-existent extra modules)  
but I'd rather fix them by hand if necessary than try to decipher  
how to get the site build to work automatically.


This includes mostly some bug fixes in the pooling code that make  
tying a connection to a thread work.  This should make it a lot  
easier to make cases where you open several connections and then  
start a user transaction work properly, as they can now share the  
same managed connection.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 don't release

Vote open for 72 hours

thanks
david jencks

Re: Geronimo branches/2.2 build failure

[Kevan Miller]

On Sep 14, 2009, at 4:14 PM, Jason Warner wrote:

The automated TCK tests are failing when building the geronimo  
server from the branches/2.2 source with a missing artifact error[1].


This was caused by the tests jar problem that David recently fixed.  
I've deployed a fixed version of 2.1.3-SNAPSHOT. It should take care  
of the problem.


--kevan

Geronimo branches/2.2 build failure

[Jason Warner]

The automated TCK tests are failing when building the geronimo server from
the branches/2.2 source with a missing artifact error[1].

Missing: --
 1)
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.geronimo.components
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
  1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
  2)
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

 --
 1 required artifact is missing.

 for artifact:
  org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT

 from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)

~Jason Warner

Re: [VOTE] geronimo-jacc_1.1_spec version 1.0.2

[Kevan Miller]

The license file contains a W3C license for XMLSchema.dtd. However,  
the generated jar file does not contain the license. AFAICT, there's  
no need for this license. Am I missing something?


--kevan
On Sep 10, 2009, at 8:16 PM, David Jencks wrote:


I've built a release candidate for the jacc spec jar:

https://repository.apache.org/content/repositories/geronimo-staging-002/

Site is staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/

Along with a bunch of build improvements this includes these fixes:

GERONIMO-4357 don't double escape pre-escaped colons in web  
permissions


GERONIMO-4587 fix EJBMethodPermission construction problem when a  
method param is an array, patch (slightly modified) from Shawn Jiang


r788107 ensure HTTPMethodSpec.getActions() returns right information  
- otherwise reserialized permission objects could loose some vital  
information. Also, add serialVersionUID constants


GERONIMO-4721 represent 'all http methods' with '' rather than '\!'  
when computing the actions string in web permissions


GERONIMO-4735 serialize EJBMethodPermissionCollection contents only  
once


GERONIMO-4734 fix web permissions HTTPMethodSpec equals method

GERONIMO-4766, sort of.  Use generics and make policy context  
handler registration slightly more thread safe.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 Don't release it

Vote open for 72 hours

thanks
david jencks

[BUILD] trunk: Failed for Revision: 814776

[gawor]

Geronimo Revision: 814776 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/unit-test-reports
 
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 117 source files to 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[101,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[102,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatEJBWebServiceContext.java:[244,20]
 [deprecation] setStatus(int,java.lang.String) in 
org.apache.catalina.connector.Response has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatServerGBean.java:[103,20]
 [deprecation] setServer(javax.management.MBeanServer) in 
org.apache.tomcat.util.modeler.Registry has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/HostGBean.java:[171,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/EngineGBean.java:[137,24]
 [deprecation] setServer(javax.management.MBeanServer) in 
org.apache.tomcat.util.modeler.Registry has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/ManagerGBean.java:[93,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 9 source files to 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/test-classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/AbstractWebModuleTest.java:[110,107]
 [deprecation] toURL() in java.io.File has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/ApplicationTest.java:[34,88]
 [deprecation] toURL() in java.io.File has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/StatTest.java:[39,79]
 [deprecation] toURL() in java.io.File has been deprecated

[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.tomcat.ContainerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.667 sec
Running org.apache.geronimo.tomcat.BasicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec
Running org.apache.geronimo.tomcat.TomcatServerGBeanTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.05 sec <<< 
FAILURE!
Running org.apache.geronimo.tomcat.ApplicationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.819 sec
Running org.apache.geronimo.tomcat.JAASSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.937 sec
Running org.apache.geronimo.tomcat.StatTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.703 sec
Running org.apache.geronimo.tomcat.JACCSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.866 sec

Results :

Tests in error: 

Tests run: 8, Failures: 0, Errors: 2, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[

Re: [VOTE] release jaspic implementation component 1.0

[Kevan Miller]

Dave,
It looks like the md5 and sha1 checksums are bad on all of your  
release votes. I'm now -1 until resolved.


--kevan
On Sep 10, 2009, at 10:08 PM, David Jencks wrote:

It's time for the first release of our jaspic implementation for  
inclusion in g. 2.2.


Release artifacts staged here:

https://repository.apache.org/content/repositories/geronimo-staging-003/

Site staged here:

http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/

When used in geronimo with tomcat or jetty, this passed the jaspic  
tck web profile.  So far we don't try to implement the soap profile  
in geornimo; this implementation should support  both.



[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.

Vote open for 72 hours.

thanks
david jencks

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

[Kevan Miller]

Guillaume,
Your PGP key is missing from the Geronimo KEYS file -- 
https://svn.apache.org/repos/asf/geronimo/KEYS

--kevan
On Sep 11, 2009, at 12:38 PM, Guillaume Nodet wrote:


I've uploaded another 1.0.0 release of the blueprint project.
I think I've addressed all the issues raised in the discussion thread.

The staging repository is available at:
https://repository.apache.org/content/repositories/geronimo-staging-005/

The corresponding tag is available at
 
http://svn.apache.org/repos/asf/geronimo/components/blueprint/tags/blueprint-1.0.0/

Please review and vote:
[  ] +1 Release
[  ] -1 Do not release

The vote will remain open for 72 hours.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

[BUILD] branches/2.2: Failed for Revision: 814753

[gawor]

Geronimo Revision: 814753 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3 
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3 
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
2) 
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: 
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
--
1) org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3 
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components 
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3 
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
2) 
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT

from the specified remote repositories:
  ibiblio.org (http://repo.exist.com/maven2),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324

Re: [VOTE] release jaspic implementation component 1.0

[Kevan Miller]

+1

source, build, and binaries all look good

--kevan

On Sep 10, 2009, at 10:08 PM, David Jencks wrote:

It's time for the first release of our jaspic implementation for  
inclusion in g. 2.2.


Release artifacts staged here:

https://repository.apache.org/content/repositories/geronimo-staging-003/

Site staged here:

http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/

When used in geronimo with tomcat or jetty, this passed the jaspic  
tck web profile.  So far we don't try to implement the soap profile  
in geornimo; this implementation should support  both.



[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.

Vote open for 72 hours.

thanks
david jencks

Re: [VOTE] txmanager 2.1.3 2nd try

[Vamsavardhana Reddy]

+1


On Sun, Sep 13, 2009 at 1:28 PM, David Jencks wrote:

> I fixed the build problem where we weren't building the test jars.
>
> I've set up a release candidate for the transaction manager and connector
> code 2.1.3, needed for geronimo 2.2:
>
> https://repository.apache.org/content/repositories/geronimo-staging-012/
>
> Site staged at:
>
>
> http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/
>
> There are some problems with the site (non-existent extra modules) but I'd
> rather fix them by hand if necessary than try to decipher how to get the
> site build to work automatically.
>
> This includes mostly some bug fixes in the pooling code that make tying a
> connection to a thread work.  This should make it a lot easier to make cases
> where you open several connections and then start a user transaction work
> properly, as they can now share the same managed connection.
>
> [ ] +1 release it
> [ ] 0 dunno
> [ ] -1 don't release
>
> Vote open for 72 hours
>
> thanks
> david jencks
>
>


-- 
Vamsi

Re: [VOTE] xbean 3.6 3rd try

[David Jencks]

On Sep 13, 2009, at 6:44 PM, Jack Cai wrote:

Can we also include the fix for XBEAN-122? It fixes important  
problems in

the naming module.


According to JIRA this was committed back in march.  Can you verify  
this and set the Fix version in the jira issue if appropriate?


thanks
david jencks



I thought that usually all the fixes will make into a new release. :-)

-Jack

Re: [VOTE] txmanager 2.1.3 2nd try

[David Jencks]

+1

david jencks

On Sep 13, 2009, at 12:58 AM, David Jencks wrote:


I fixed the build problem where we weren't building the test jars.

I've set up a release candidate for the transaction manager and  
connector code 2.1.3, needed for geronimo 2.2:


https://repository.apache.org/content/repositories/geronimo-staging-012/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/

There are some problems with the site (non-existent extra modules)  
but I'd rather fix them by hand if necessary than try to decipher  
how to get the site build to work automatically.


This includes mostly some bug fixes in the pooling code that make  
tying a connection to a thread work.  This should make it a lot  
easier to make cases where you open several connections and then  
start a user transaction work properly, as they can now share the  
same managed connection.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 don't release

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] geronimo-jacc_1.1_spec version 1.0.2

[David Jencks]

+1

david jencks

On Sep 10, 2009, at 5:16 PM, David Jencks wrote:


I've built a release candidate for the jacc spec jar:

https://repository.apache.org/content/repositories/geronimo-staging-002/

Site is staged here:

http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/

Along with a bunch of build improvements this includes these fixes:

GERONIMO-4357 don't double escape pre-escaped colons in web  
permissions


GERONIMO-4587 fix EJBMethodPermission construction problem when a  
method param is an array, patch (slightly modified) from Shawn Jiang


r788107 ensure HTTPMethodSpec.getActions() returns right information  
- otherwise reserialized permission objects could loose some vital  
information. Also, add serialVersionUID constants


GERONIMO-4721 represent 'all http methods' with '' rather than '\!'  
when computing the actions string in web permissions


GERONIMO-4735 serialize EJBMethodPermissionCollection contents only  
once


GERONIMO-4734 fix web permissions HTTPMethodSpec equals method

GERONIMO-4766, sort of.  Use generics and make policy context  
handler registration slightly more thread safe.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 Don't release it

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] release jaspic implementation component 1.0

[David Jencks]

+1

david jencks

On Sep 10, 2009, at 7:08 PM, David Jencks wrote:

It's time for the first release of our jaspic implementation for  
inclusion in g. 2.2.


Release artifacts staged here:

https://repository.apache.org/content/repositories/geronimo-staging-003/

Site staged here:

http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/

When used in geronimo with tomcat or jetty, this passed the jaspic  
tck web profile.  So far we don't try to implement the soap profile  
in geornimo; this implementation should support  both.



[ ] +1 release this
[ ] 0 dunno
[ ] -1 don't release this.

Vote open for 72 hours.

thanks
david jencks

Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?

[David Jencks]

On Sep 14, 2009, at 8:41 AM, Shawn Jiang wrote:




On Mon, Sep 14, 2009 at 11:26 PM, Kevan Miller  
 wrote:


On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:

Right,  I'm planing to ship both of them but mark ejb agent as  
"load=false".  So that the user will use JMX as default monitoring  
agent.


When the users do not need EJB, they can create a EJB free assembly  
easily  without breaking the monitoring.


Does anyone have any other comments ?

Agreed that this would be more convenient for most users. I don't  
recall any specific reason why agent-jmx wasn't included. Vaguely  
recall that ejb support was developed first because MEJB support is  
required per the EE spec.
Does it mean that we still have to keep ejb agent on by default to  
meet the EE spec ?


no, the monitoring is not part of the spec so we can use anything we  
want.


thanks
david jencks



--kevan



--
Shawn

Re: The setting of LoginDomainName attribute of the LoginModuleGBean

[David Jencks]

On Sep 14, 2009, at 12:51 AM, Ivan wrote:


Hi
  In the LoginModuleGBean, there is an attribute named  
loginDomainName, I went through the codes, just found that while the  
WrappingLoginModule is turned on, those domainNames are used in the  
Subject as DomainPrincipal. Except for this, is there any use for  
those loginDomainNames ? And, I did not found any example for  
WrappingLoginModule, so when we would use it ?

 Thanks !


I thought this was documented somewhere, but I could easily be wrong,  
and the explanation might not include enough info for anyone to know  
why...


Most people use the simplest form of principal-role mapping, where you  
specify the class and name of the actual Principal from the login  
module you specify.  However, it's possible to think up more  
complicated scenarios where this is not enough to identify the  
principal for the principal-role mapping.


lets suppose you have an ejb app C with 2 web apps A and B in front of  
it.  Your ejb app has 2 roles r1 and r2.  You have two legacy security  
systems S1 and S2 with proprietary login modules that both happen to  
supply the same principal class.  You need to use S1 with A and S2  
with B.  S1 and S2 both provide principals with names "g1" and "g2"  
but the meaning is opposite. you need


For S1 and A,
"g1" > r1
"g2" > r2

but for S2 and B,
"g1" > r2
"g2" > r1

So, you need more information to distinguish the principals so you can  
map them to the correct roles.  Geronimo lets you wrap the original  
principals with a wrapper that contains a name of the login module  
"loginDomainName" and the name of the security realm, and the  
principal-role mapping can specify these as well.  You'd use the  
loginDomainName if you set up a single security realm that includes  
the login modules for S1 and S2, and the security realm if you set up  
two separate security realms.


I don't know if anyone has used this or ever will, but we thought we'd  
be thorough.


thanks
david jencks


--
Ivan

Re: [VOTE] geronimo-jacc_1.1_spec version 1.0.2

[Jarek Gawor]

+1

Jarek

On Thu, Sep 10, 2009 at 8:16 PM, David Jencks  wrote:
> I've built a release candidate for the jacc spec jar:
>
> https://repository.apache.org/content/repositories/geronimo-staging-002/
>
> Site is staged here:
>
> http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/
>
> Along with a bunch of build improvements this includes these fixes:
>
> GERONIMO-4357 don't double escape pre-escaped colons in web permissions
>
> GERONIMO-4587 fix EJBMethodPermission construction problem when a method
> param is an array, patch (slightly modified) from Shawn Jiang
>
> r788107 ensure HTTPMethodSpec.getActions() returns right information -
> otherwise reserialized permission objects could loose some vital
> information. Also, add serialVersionUID constants
>
> GERONIMO-4721 represent 'all http methods' with '' rather than '\!' when
> computing the actions string in web permissions
>
> GERONIMO-4735 serialize EJBMethodPermissionCollection contents only once
>
> GERONIMO-4734 fix web permissions HTTPMethodSpec equals method
>
> GERONIMO-4766, sort of.  Use generics and make policy context handler
> registration slightly more thread safe.
>
> [ ] +1 release it
> [ ] 0 dunno
> [ ] -1 Don't release it
>
> Vote open for 72 hours
>
> thanks
> david jencks
>
>

Re: [VOTE] release jaspic implementation component 1.0

[Jarek Gawor]

+1

Jarek

On Thu, Sep 10, 2009 at 10:08 PM, David Jencks  wrote:
> It's time for the first release of our jaspic implementation for inclusion
> in g. 2.2.
>
> Release artifacts staged here:
>
> https://repository.apache.org/content/repositories/geronimo-staging-003/
>
> Site staged here:
>
> http://people.apache.org/~djencks/staging-site/maven/components/geronimo-jaspi/1.0/
>
> When used in geronimo with tomcat or jetty, this passed the jaspic tck web
> profile.  So far we don't try to implement the soap profile in geornimo;
> this implementation should support  both.
>
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 don't release this.
>
> Vote open for 72 hours.
>
> thanks
> david jencks
>
>

Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?

[Shawn Jiang]

On Mon, Sep 14, 2009 at 11:26 PM, Kevan Miller wrote:

>
> On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:
>
>  Right,  I'm planing to ship both of them but mark ejb agent as
>> "load=false".  So that the user will use JMX as default monitoring agent.
>>
>> When the users do not need EJB, they can create a EJB free assembly easily
>>  without breaking the monitoring.
>>
>> Does anyone have any other comments ?
>>
>
> Agreed that this would be more convenient for most users. I don't recall
> any specific reason why agent-jmx wasn't included. Vaguely recall that ejb
> support was developed first because MEJB support is required per the EE
> spec.
>
Does it mean that we still have to keep ejb agent on by default to meet the
EE spec ?

>
> --kevan
>



-- 
Shawn

[jira] Commented: (GERONIMO-4836) Default Pluto URL parser could not hanle semicolon in the parameter values

[Ivan (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755024#action_12755024
 ] 

Ivan commented on GERONIMO-4836:


Yes, this class is configurable in the xml file, we could use our own in 
Geronimo.
I recreated a patch, and once it is accepted, I will do the change in Geronimo 
2.2.
Thanks !

> Default Pluto URL parser could not hanle semicolon in the parameter values
> --
>
> Key: GERONIMO-4836
> URL: https://issues.apache.org/jira/browse/GERONIMO-4836
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console, Tomcat
>Affects Versions: 2.2
>Reporter: Ivan
> Fix For: 2.2
>
>
> While the input parameter contains semicolon, there will be some issues while 
> handlering those parameters. Seem that Pluto would ignore those parameters 
> after the semicolon.

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

Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?

[Kevan Miller]

On Sep 14, 2009, at 2:52 AM, Shawn Jiang wrote:

Right,  I'm planing to ship both of them but mark ejb agent as  
"load=false".  So that the user will use JMX as default monitoring  
agent.


When the users do not need EJB, they can create a EJB free assembly  
easily  without breaking the monitoring.


Does anyone have any other comments ?


Agreed that this would be more convenient for most users. I don't  
recall any specific reason why agent-jmx wasn't included. Vaguely  
recall that ejb support was developed first because MEJB support is  
required per the EE spec.


--kevan 

Re: There's still hope for 2.2...

[Forrest Xia]

On Mon, Sep 14, 2009 at 10:48 PM, Donald Woods  wrote:

> I'm still working on Daytrader 2.2, but could use some help updating and
> testing the Daytrader plugins and plans.
>
>
> -Donald


Donald, once you roll out all of changes on daytrader 2.2, I will have a
testing on it.

Re: There's still hope for 2.2...

[Forrest Xia]

Hope someone could look into
https://issues.apache.org/jira/browse/GERONIMO-4222. It's an important
reliability issue about db connectivity.

[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?

[Kevan Miller (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755016#action_12755016
 ] 

Kevan Miller commented on GERONIMO-4871:


That's good, I guess, but strange. I'm on Mac OS. kill -3 works just fine on G 
2.1 (both java 5 and 6), but doesn't work on G 2.2. I'm using geronimo.sh to 
start (in case that makes a difference).

> Something blocking 'kill -3' signals?
> -
>
> Key: GERONIMO-4871
> URL: https://issues.apache.org/jira/browse/GERONIMO-4871
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Kevan Miller
> Fix For: 2.2
>
>
> I occasionally use 'kill -3' to cause a java process to dump all thread 
> stacks. For some reason, this isn't working on Geronimo 2.2

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

Re: There's still hope for 2.2...

[Donald Woods]

I'm still working on Daytrader 2.2, but could use some help updating and 
testing the Daytrader plugins and plans.



-Donald


Forrest Xia wrote:
I am working on G 2.2 samples. Basically, I hope the existing G 2.2 
samples plugins could be installable and runable on G 2.2 server.
 
I will post my results here soon.

[jira] Commented: (GERONIMO-4871) Something blocking 'kill -3' signals?

[Jarek Gawor (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755004#action_12755004
 ] 

Jarek Gawor commented on GERONIMO-4871:
---

Works for me on Ubuntu (with Sun Java 5).





> Something blocking 'kill -3' signals?
> -
>
> Key: GERONIMO-4871
> URL: https://issues.apache.org/jira/browse/GERONIMO-4871
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Kevan Miller
> Fix For: 2.2
>
>
> I occasionally use 'kill -3' to cause a java process to dump all thread 
> stacks. For some reason, this isn't working on Geronimo 2.2

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

Re: [VOTE] txmanager 2.1.3 2nd try

[Donald Woods]

+1


Donald

David Jencks wrote:

I fixed the build problem where we weren't building the test jars.

I've set up a release candidate for the transaction manager and 
connector code 2.1.3, needed for geronimo 2.2:


https://repository.apache.org/content/repositories/geronimo-staging-012/ 



Site staged at:

http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/ 



There are some problems with the site (non-existent extra modules) but 
I'd rather fix them by hand if necessary than try to decipher how to get 
the site build to work automatically.


This includes mostly some bug fixes in the pooling code that make tying 
a connection to a thread work.  This should make it a lot easier to make 
cases where you open several connections and then start a user 
transaction work properly, as they can now share the same managed 
connection.


[ ] +1 release it
[ ] 0 dunno
[ ] -1 don't release

Vote open for 72 hours

thanks
david jencks

Re: [VOTE] txmanager 2.1.3 2nd try

[Jarek Gawor]

+1

Jarek

On Sun, Sep 13, 2009 at 3:58 AM, David Jencks  wrote:
> I fixed the build problem where we weren't building the test jars.
> I've set up a release candidate for the transaction manager and connector
> code 2.1.3, needed for geronimo 2.2:
>
> https://repository.apache.org/content/repositories/geronimo-staging-012/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/components/txmanager/2.1.3/
>
> There are some problems with the site (non-existent extra modules) but I'd
> rather fix them by hand if necessary than try to decipher how to get the
> site build to work automatically.
>
> This includes mostly some bug fixes in the pooling code that make tying a
> connection to a thread work.  This should make it a lot easier to make cases
> where you open several connections and then start a user transaction work
> properly, as they can now share the same managed connection.
>
> [ ] +1 release it
> [ ] 0 dunno
> [ ] -1 don't release
>
> Vote open for 72 hours
>
> thanks
> david jencks
>
>

Re: There's still hope for 2.2...

[Forrest Xia]

I am working on G 2.2 samples. Basically, I hope the existing G 2.2 samples
plugins could be installable and runable on G 2.2 server.

I will post my results here soon.

Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?

[Forrest Xia]

Good to see that happen :-)

Re: Request for editor access for G docs

[chi runhua]

Hi Kevan,  I think Ellen has filed her ICLA cause I saw her name was in
unlisted CLA group with name Tang Lei.

http://people.apache.org/~jim/committers.html

Please help to confirm.

Thanks alot.

Jeff Chi

On Mon, Sep 14, 2009 at 8:27 PM, Kevan Miller wrote:

>
> On Sep 13, 2009, at 10:34 PM, Ellen Tang wrote:
>
> Hi,
>>
>> I am a technical writer. I would like to apply for the editor access for
>> geronimo related docs.
>>
>
> Hi Ellen,
> That would be great! To insure that our documentation is appropriately
> Apache Licensed, we require an ICLA to be on file, before we can give you
> access to our Wiki. I don't see your name in the iclas file. Let us know if
> you think it should be there. Here's the form --
> http://www.apache.org/licenses/icla.pdf You can mail, fax, or email a
> scanned copy to secret...@apache.org.
>
> --kevan
>
>
>

Re: There's still hope for 2.2...

[Ivan]

 Is there an approximate date of Geronimo 2.2 release ? I remembered that
last time, what I got is in the early October.
Thanks !

2009/9/14 Jack Cai 

> I'm working on improving the console filter performance. Will open a
> JIRA...
>
> -Jack
>
>
> On Fri, Sep 11, 2009 at 6:11 PM, Quintin Beukes wrote:
>
>> There are some bugs I reported regarding adding/removing connectors. I
>> seriously think they need to be addressed. They are:
>> https://issues.apache.org/jira/browse/GERONIMO-4867
>> https://issues.apache.org/jira/browse/OPENEJB-1070
>> https://issues.apache.org/jira/browse/GERONIMO-4860
>> https://issues.apache.org/jira/browse/GERONIMO-4861
>>
>> The last one is a regression of sorts (in other words is wasn't present in
>> 2.1).
>>
>> They're all small errors, and I listed them because they can
>> potentially damage Geronimo's image by complicating a user's
>> experience. User experience is the biggest factor in a product's
>> success.
>>
>> Q
>>
>> On Fri, Sep 11, 2009 at 11:49 AM, Ivan  wrote:
>> > Sorry, I make a mistaken, I did not mean
>> > https://issues.apache.org/jira/browse/GERONIMO-4603, I mean
>> GERONIMO-4625
>> >
>> >
>> > 2009/9/11 Ivan 
>> >>
>> >> I wish those JIRAs to be included in Geronimo 2.2
>> >>
>> >> https://issues.apache.org/jira/browse/GERONIMO-4801
>> >> Please check my comment, I think we could just ignore the
>> alreadyexisted
>> >> exception
>> >>
>> >> https://issues.apache.org/jira/browse/GERONIMO-4821
>> >> Please check my comment, I need more help on it :-(
>> >>
>> >> https://issues.apache.org/jira/browse/GERONIMO-4836
>> >> If anyone could help to check the patch in the current pluto snapshot,
>> >> that will be fine. or, I wish to fix it in Geronimo 2.2 firstly
>> >>
>> >> https://issues.apache.org/jira/browse/GERONIMO-4493
>> >> I am working on it, and it will be finished soon
>> >>
>> >> https://issues.apache.org/jira/browse/GERONIMO-4603
>> >> I am working on it, and it will be finished soon
>> >>
>> >> Thanks !
>> >>
>> >> 2009/9/11 David Jencks 
>> >>>
>> >>> We may be able to release 2.2 soon.  Activemq has fixed the last bug
>> we
>> >>> had problems with and is fast approaching a release, openejb is
>> getting very
>> >>> close to a release for 2.2, and I've started votes on a number of our
>> >>> snapshot dependencies.
>> >>>
>> >>> At this point I'd like anyone who is working on something they'd like
>> to
>> >>> get into 2.2 to reply to this with a description of what they are
>> working on
>> >>> and an estimate for completion.
>> >>>
>> >>> Also, if there is something you think is really necessary to get into
>> 2.2
>> >>> please reply and describe what you'd like.
>> >>>
>> >>> many thanks
>> >>> david jencks
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Ivan
>> >
>> >
>> >
>> > --
>> > Ivan
>> >
>>
>>
>>
>> --
>> Quintin Beukes
>>
>
>


-- 
Ivan

[BUILD] branches/2.2: Failed for Revision: 813529

[gawor]

Geronimo Revision: 813529 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090914/unit-test-reports
 
[INFO]   Geronimo Plugins, Tomcat :: Clustering over WADI Core
[INFO]   Geronimo Plugins, Tomcat :: Clustering over WADI
[INFO]   Geronimo Plugins, Tomcat :: Clustering Builder for WADI Core
[INFO]   Geronimo Plugins, Tomcat :: Clustering Builder for WADI
[INFO]   Geronimo Plugin Groups
[INFO]   Geronimo Plugin Group :: Client
[INFO]   Geronimo Plugin Group :: WADI Clustering Jetty
[INFO]   Geronimo Plugin Group :: WADI Clustering Tomcat
[INFO]   Geronimo Plugin Group :: EJB
[INFO]   Geronimo Plugin Group :: Persistence
[INFO]   Geronimo Plugin Group :: Web Little-G Jetty
[INFO]   Geronimo Plugin Group :: Web Services Axis2
[INFO]   Geronimo Plugin Group :: Web Services CXF
[INFO]   Geronimo Plugin Group :: Java EE 5 Jetty
[INFO]   Geronimo Plugin Group ::  Web Little-G Tomcat
[INFO]   Geronimo Plugin Group :: Java EE 5 Tomcat
[INFO]   Geronimo Assemblies
[INFO]   Geronimo Assemblies :: Minimal + Jetty7
[INFO]   Geronimo Assemblies :: JavaEE 5 + Jetty7
[INFO]   Geronimo Assemblies :: Minimal + Tomcat
[INFO]   Geronimo Assemblies :: JavaEE 5 + Tomcat
[INFO] snapshot org.apache.geronimo.buildsupport:car-maven-plugin:2.2-SNAPSHOT: 
checking for updates from apache.snapshots
Full thread dump Java HotSpot(TM) Server VM (1.5.0_18-b02 mixed mode):

"Low Memory Detector" daemon prio=1 tid=0x081230f8 nid=0x2473 runnable 
[0x..0x]

"CompilerThread1" daemon prio=1 tid=0x08121c78 nid=0x2472 waiting on condition 
[0x..0x60b6b208]

"CompilerThread0" daemon prio=1 tid=0x08120c20 nid=0x2471 waiting on condition 
[0x..0x60bec248]

"AdapterThread" daemon prio=1 tid=0x0811fb98 nid=0x2470 waiting on condition 
[0x..0x]

"Signal Dispatcher" daemon prio=1 tid=0x0811ed38 nid=0x246f waiting on 
condition [0x..0x]

"Finalizer" daemon prio=1 tid=0x08115cf8 nid=0x246e in Object.wait() 
[0x60d6f000..0x60d6fea0]
at java.lang.Object.wait(Native Method)
- waiting on <0x715422a0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:120)
- locked <0x715422a0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:136)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=1 tid=0x08114670 nid=0x246d in Object.wait() 
[0x60df..0x60df0e20]
at java.lang.Object.wait(Native Method)
- waiting on <0x715401e0> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x715401e0> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x0805cca0 nid=0x2463 runnable [0xbfffc000..0xbfffd898]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
- locked <0xaa616368> (a java.io.BufferedInputStream)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:681)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:626)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:972)
- locked <0xaa60bff8> (a sun.net.www.protocol.http.HttpURLConnection)
at 
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:475)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:371)
at 
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97)
at 
org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65)
at 
org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:63)
at 
org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java

[BUILD] trunk: Failed for Revision: 814623

[gawor]

Geronimo Revision: 814623 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@14141414
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@14141414
[INFO] [surefire:test]
[WARNING] Component returned which is not the same manager. Ignored. 
component

Re: Request for editor access for G docs

[Kevan Miller]

On Sep 13, 2009, at 10:34 PM, Ellen Tang wrote:


Hi,

I am a technical writer. I would like to apply for the editor access  
for geronimo related docs.


Hi Ellen,
That would be great! To insure that our documentation is appropriately  
Apache Licensed, we require an ICLA to be on file, before we can give  
you access to our Wiki. I don't see your name in the iclas file. Let  
us know if you think it should be there. Here's the form -- http://www.apache.org/licenses/icla.pdf 
 You can mail, fax, or email a scanned copy to secret...@apache.org.


--kevan

Re: Miss org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT dependency when build g2.2 branch

[Shawn Jiang]

On Mon, Sep 14, 2009 at 5:46 PM, Rex Wang  wrote:

> Yes, I also met this, Shawn has pointed that these days looks like the
> branch 22 are not built autoly.
> Might be the reason..
>

David Jencks is releasing txmanager 2.1.3.  After that,upgrading the
dependency to geronimo-connector:jar:tests:2.1.3 should resolve this
problem.

>
> -Rex
>
> 2009/9/14 viola lu 
>
> Hi,
>>  When build g2.2 branch plugins/connector, there is an error :
>> Missing:
>> --
>> 1)
>> org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT
>>
>>   Try downloading the file manually from the project website.
>>
>>   Then, install it using the command:
>>   mvn install:install-file -DgroupId=org.apache.geronimo.components
>> -DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
>> -Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file
>>
>>   Alternatively, if you host your own repository you can deploy the file
>> there:
>>   mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components
>> -DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
>> -Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
>> -DrepositoryId=[id]
>>
>>   Path to dependency:
>> 1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
>> 2)
>> org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT
>>
>> --
>> 1 required artifact is missing.
>>
>> for artifact:
>>   org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
>>
>> Where to get this module and compile?And what does "classifier" do in
>> 
>> org.apache.geronimo.components
>> geronimo-connector
>>tests
>> 
>> ?
>>
>> Thanks.
>> --
>> viola
>>
>
>


-- 
Shawn

[jira] Resolved: (GERONIMO-4798) can't start server because of an error of Http11AprProtocol

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4798.


   Resolution: Fixed
Fix Version/s: 3.0

Commit changes to 2.2 At revision: 814548 and trunk At revision: 814547

> can't start server  because of an error of   Http11AprProtocol
> --
>
> Key: GERONIMO-4798
> URL: https://issues.apache.org/jira/browse/GERONIMO-4798
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.2
> Environment: windows xp sp3
> jdk6
>Reporter: Bin He
>Assignee: Shawn Jiang
> Fix For: 2.2, 3.0
>
> Attachments: apr.7z
>
>
> 1、move three attached files ：openssl.exe、tcnative.dll、tcnative_ipv4.dll  into 
> C:\WINDOWS\system32 
> 2、click "gsh.bat"  in /bin
> 3、input  geronimo/start-server  but  the server can't  start   and it says :
> 2009-08-18 13:42:21,859 INFO  [Http11AprProtocol] Initializing Coyote 
> HTTP/1.1 on http-8080
> 2009-08-18 13:42:21,859 ERROR [Http11AprProtocol] Error initializing endpoint
> java.lang.Exception: Invalid Server SSL Protocol
>   at org.apache.tomcat.jni.SSLContext.make(Native Method)
>   at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:693)
>   at 
> org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107)
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1058)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:677)
>   at 
> org.apache.catalina.core.StandardService.init(StandardService.java:689)
>   at 
> org.apache.catalina.core.StandardService.start(StandardService.java:503)
>   at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
>   at 
> org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:135)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
>   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:538)
>   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.GeneratedMethodAccessor29.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.reflect.Method.invoke(Method.java:599)
>   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:815)
>   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$$2c2ce3ed.startConfiguration()
>   at 
> org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
>   at 
> org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
>   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)
> 2009-08-18 13:42:21,875 ERROR [StandardService] Service initializing at 
> Catalina failed
> LifecycleException:  Protocol handler initialization failed: 
> java.lang.Exception: Invalid Server SSL Protocol
>   at 
> org.apache.catalina.connector.Connector.initialize(Connector.java:1060)
>   at 
> org.apache.catalina.core.StandardService.initialize(StandardService.java:677)
>   at 
> org.apache.catalina.core.StandardService.init(StandardService.java:689)
>   at 
> org.apache.catalina.core

Re: Miss org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT dependency when build g2.2 branch

[Rex Wang]

Yes, I also met this, Shawn has pointed that these days looks like the
branch 22 are not built autoly.
Might be the reason..

-Rex

2009/9/14 viola lu 

> Hi,
>  When build g2.2 branch plugins/connector, there is an error :
> Missing:
> --
> 1)
> org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.apache.geronimo.components
> -DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
> -Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file
>
>   Alternatively, if you host your own repository you can deploy the file
> there:
>   mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components
> -DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
> -Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
>   Path to dependency:
> 1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
> 2)
> org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT
>
> --
> 1 required artifact is missing.
>
> for artifact:
>   org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
>
> Where to get this module and compile?And what does "classifier" do in
> 
> org.apache.geronimo.components
> geronimo-connector
>tests
> 
> ?
>
> Thanks.
> --
> viola
>

Miss org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT dependency when build g2.2 branch

[viola lu]

Hi,
 When build g2.2 branch plugins/connector, there is an error :
Missing:
--
1)
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.geronimo.components
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file
there:
  mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components
-DartifactId=geronimo-connector -Dversion=2.1.3-20090910.160808-3
-Dclassifier=tests -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

  Path to dependency:
1) org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT
2)
org.apache.geronimo.components:geronimo-connector:jar:tests:2.1.3-SNAPSHOT

--
1 required artifact is missing.

for artifact:
  org.apache.geronimo.modules:geronimo-connector:jar:2.2-SNAPSHOT

Where to get this module and compile?And what does "classifier" do in

org.apache.geronimo.components
geronimo-connector
   tests

?

Thanks.
-- 
viola

[jira] Commented: (GERONIMO-4647) welcome files with servlet mappings

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754894#action_12754894
 ] 

Rex Wang commented on GERONIMO-4647:


This has been applied to tomcat trunk, so should we applied it to our internal 
tomcat 6 build?

-
Tim Funk  2009-08-31 07:02:01 PDT

Applied this to trunk - so it should make its way into tomcat7
http://svn.apache.org/viewvc?rev=809596&view=rev

I am not proposing this for backport to tomcat 6. But wouldn't be against it if
it were proposed. So I'm moving this to enhancement.
-

> welcome files with servlet mappings
> ---
>
> Key: GERONIMO-4647
> URL: https://issues.apache.org/jira/browse/GERONIMO-4647
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 2.1.4
> Environment: JRE 1.5.0_06, Windows XP
>Reporter: Bobby Lawrence
>Assignee: Rex Wang
> Fix For: 2.2
>
> Attachments: GERONIMO-4647.patch, sampleapp.war, sampleapp.war
>
>
> When you specify welcome files in web.xml Geronimo throws 404 errors if the 
> welcome file isn't a valid file resource.
> Values that are URL mappings to a servlet are ignored by the app server even 
> through they are valid.
> This means that I can't have a welcome file of "/index.jsf" or "/index.do" or 
> "/someservlet".
> The only welcome files that Geronimo seems to not throw a 404 Not Found error 
> are actual files found in the web application.

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

[jira] Created: (GERONIMO-4873) Unable creating a new JMS Resource Group via "For another JMS provider... " under IE

[Shiny Cheng (JIRA)]

Unable creating a new JMS Resource Group via "For another JMS provider... " 
under IE


 Key: GERONIMO-4873
 URL: https://issues.apache.org/jira/browse/GERONIMO-4873
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
 Environment: winxp sp3, jdk 1.6
Reporter: Shiny Cheng


Click on "For another JMS provider" when creating a new JMS Resource Group via 
admin console. Select the existed 
org.apache.geronimo.modules/geronimo-activemq-ra/2.2-SNAPSHOT/rar and click on 
"Next". 

If your current browser is IE series, you will see warning like "The focussed 
field must not be empty" and unable to do following steps. However, you won't 
meet this problem under Firefox.

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

Re: What's the reason why didn't agent-car-jmx get shipped with geronimo server by default ?

[Jack Cai]

Then we would also need to change the default option when creating a server
to monitor in the monitoring console. Current default is EJB.

-Jack

On Mon, Sep 14, 2009 at 2:52 PM, Shawn Jiang  wrote:

> Right,  I'm planing to ship both of them but mark ejb agent as
> "load=false".  So that the user will use JMX as default monitoring agent.
>
> When the users do not need EJB, they can create a EJB free assembly easily
> without breaking the monitoring.
>
> Does anyone have any other comments ?
>
>
> On Mon, Sep 14, 2009 at 9:56 AM, Jack Cai  wrote:
>
>> So looks like it's a random choice...
>>
>> If there's no particular reasons (like performance etc.), I'd recommend
>> that we use JMX agent as the default instead of the EJB agent, as the latter
>> has a dependency on the EJB container.
>>
>> -Jack
>>
>>
>>
>> On Thu, Sep 10, 2009 at 1:19 PM, Shawn Jiang  wrote:
>>
>>> Whenever a user wants to use jmx monitor, he/she needs to install
>>> agent-car-jmx plugin firstly.   Why not to ship this plugin with geronimo
>>> while keep it "load=false" in config.xml by default ?
>>>
>>> IMO, this size of agent-car-jmx plugin is only 13Kb.   It's not a problem
>>> to bundle it with geronimo server as long as we make it "load=false" by
>>> default.
>>>
>>> Any ideas ?
>>>
>>> --
>>> Shawn
>>>
>>
>>
>
>
> --
> Shawn
>

Re: [jira] Commented: (GERONIMO-4849) Such warning will be shown after deleted a remote monitoring server via JMX

[Siqi Du]

mrc.dispose() is used to close jmx connection, I have check all the code
used mrc to ensure  every possible jmx connection is closed.
I create the patch from branch 2.2 and it seems that 2.1 has not been tested
according to the bug description.

-Siqi
On Mon, Sep 14, 2009 at 3:20 PM, Shawn Jiang (JIRA)  wrote:

>
>[
> https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754849#action_12754849]
>
> Shawn Jiang commented on GERONIMO-4849:
> ---
>
> Does 21 branch have the same problem ?
>
> > Such warning will be shown after deleted a remote monitoring server via
> JMX
> >
> ---
> >
> > Key: GERONIMO-4849
> > URL: https://issues.apache.org/jira/browse/GERONIMO-4849
> > Project: Geronimo
> >  Issue Type: Bug
> >  Security Level: public(Regular issues)
> >  Components: monitoring
> >Affects Versions: 2.2
> > Environment: winxp sp3, jdk 1.6
> >Reporter: Shiny Cheng
> > Fix For: 2.2
> >
> > Attachments: monitoring_jmx.patch
> >
> >
> > The following warning will be shown after these steps.
> > First, create a remote monitoring server via JMX and meanwhile, start the
> remote server. Then, you delete the monitoring server and stop the remote
> server. You will see the following information via log or command line.
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.ConnectException: Connection refused: connect]
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.ConnectException: Connection refused: connect]
> > WARN  [rmi] Failed to call the method close():java.rmi.ConnectException:
> Connection refused to host: 9.123.233.70; nested exception is:
> >   java.net.ConnectException: Connection refused: connect
> > WARN  [misc] Failed to check connection: java.net.ConnectException:
> Connection refused: connect
> > WARN  [misc] stopping
> > WARN  [rmi] Failed to call the method close():java.rmi.ConnectException:
> Connection refused to host: 9.123.233.70; nested exception is:
> >   java.net.ConnectException: Connection refused: connect
> > WARN  [misc] Failed to check connection: java.net.ConnectException:
> Connection refused: connect
> > WARN  [misc] stopping
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.ConnectException: Connection refused: connect]
> > WARN  [rmi] Failed to call the method close():java.rmi.ConnectException:
> Connection refused to host: 9.123.233.70; nested exception is:
> >   java.net.ConnectException: Connection refused: connect
> > WARN  [misc] Failed to check connection: java.net.ConnectException:
> Connection refused: connect
> > WARN  [misc] stopping
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.ConnectException: Connection refused: connect]
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.ConnectException: Connection refused: connect]
> > WARN  [rmi] Failed to call the method close():java.rmi.ConnectException:
> Connection refused to host: 9.123.233.70; nested exception is:
> >   java.net.ConnectException: Connection refused: connect
> > WARN  [misc] Failed to check connection: java.net.ConnectException:
> Connection refused: connect
> > WARN  [misc] stopping
> > WARN  [rmi] Failed to call the method close():java.rmi.ConnectException:
> Connection refused to host: 9.123.233.70; nested exception is:
> >   java.net.ConnectException: Connection refused: connect
> > WARN  [misc] Failed to check connection: java.net.ConnectException:
> Connection refused: connect
> > WARN  [misc] stopping
> > WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI
> stub: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested
> exception is:
> >   java.net.Connec

[jira] Commented: (GERONIMO-4790) Migrate debug-views code to base on the up-to-date dojo

[Rex Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754861#action_12754861
 ] 

Rex Wang commented on GERONIMO-4790:


Hi David, My account has been created finally.. I will commit it tomorrow once 
Kaven adds me to geronimo group. :-)

-Rex

> Migrate debug-views code to base on the up-to-date dojo
> ---
>
> Key: GERONIMO-4790
> URL: https://issues.apache.org/jira/browse/GERONIMO-4790
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.2
>
> Attachments: classloader-viewer.jpg, dependency-viewer.jpg, 
> jmx-viewer.jpg, JNDI-viewer.jpg, ldap-viewer.jpg
>
>
> ref http://www.nabble.com/Re%3A-Which-dojo--p24293149s134.html
> Currently, our console depends on two different versions of dojo library. One 
> is 1.3.0, which is used by EJB portlet and just updated from 1.2.1 
> (GERONIMO-4723) and fixed a bug(GERONIMO-4746). I hope we can go on updating 
> it to the latest version 1.3.2.
> The other one is 0.4.3, the legacy lib, which has not been supported  by dojo 
> team, but used by our debug-view portlets, I prefer to update it to the 
> latest lib, and the advantage are as follows:
> 1. keep consistent in the portlet page style with the EJB portlet
> 2. reduce a bit to the geronimo footprint size
> 3. Although we have ported the dojo-legacy to build the source in 
> external(GERONIMO-4750), with this update, we don't need that as well.
> 4. will be more easy to maintainance the program logic by using the unified 
> dojo lib.
> 5. the doc of 1.3.x is good and easy to find.
> There are also some risks:
> 1. There has been so much changes between the dojo versions that the effort 
> might be 1-2 week to complete.
> 2. I did not find any documents for the old dojo lib, so it might be easier 
> to re-write the whole pages to base on 1.3.x and dwr 3.0.x(we have upgrade 
> the dwr successfully in GERONIMO-4753), but I not sure.
> Any thoughts?
> -Rex

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

The setting of LoginDomainName attribute of the LoginModuleGBean

[Ivan]

Hi
  In the LoginModuleGBean, there is an attribute named loginDomainName, I
went through the codes, just found that while the WrappingLoginModule is
turned on, those domainNames are used in the Subject as DomainPrincipal.
Except for this, is there any use for those loginDomainNames ? And, I did
not found any example for WrappingLoginModule, so when we would use it ?
 Thanks !
-- 
Ivan

[jira] Created: (GERONIMO-4872) plugin "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP " doesn't exist in http://geronimo.apache.org/plugins/geronimo-2.2

[Bin He (JIRA)]

plugin  "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP "   doesn't 
exist in http://geronimo.apache.org/plugins/geronimo-2.2
-

 Key: GERONIMO-4872
 URL: https://issues.apache.org/jira/browse/GERONIMO-4872
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Plugins
Affects Versions: 2.2
 Environment: jdk6
windows xp sp2
Reporter: Bin He
Priority: Minor


http://cwiki.apache.org/GMOxDOC22/ldap-realm.html

Login into the Geronimo Administration Console. 
Click on Plugins. 
Click on Update Repository List (optional if you are already pointing to 
http://geronimo.apache.org/plugins/geronimo-2.2). 
Click on Show Plugins in selected repository. 
 "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP" doesn't exist .

I think we need update this doc and first make this plugin exist in the 
Repository.




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

[jira] Resolved: (GERONIMO-4854) The protocol option will be reset after testing connection when addint server

[Shawn Jiang (JIRA)]

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

Shawn Jiang resolved GERONIMO-4854.
---

   Resolution: Fixed
Fix Version/s: 2.1.5
 Assignee: Shawn Jiang

Patch commited to 21, 22, trunk.  Thanks Siqi for the patch.

> The protocol option will be reset after testing connection when addint server
> -
>
> Key: GERONIMO-4854
> URL: https://issues.apache.org/jira/browse/GERONIMO-4854
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Affects Versions: 2.2
> Environment: windows sp3
>Reporter: Siqi Du
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: monitoring.patch
>
>
> In the addServer portlet 
> 1 fill the blank with the protocal option set to jmx
> 2 test connection
> 3 protocol option is reset to ejb but other info remains

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

[gawor]

Geronimo Revision: 814499 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090914/unit-test-reports
 
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 117 source files to 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[101,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/LifecycleListenerGBean.java:[102,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatEJBWebServiceContext.java:[244,20]
 [deprecation] setStatus(int,java.lang.String) in 
org.apache.catalina.connector.Response has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/TomcatServerGBean.java:[103,20]
 [deprecation] setServer(javax.management.MBeanServer) in 
org.apache.tomcat.util.modeler.Registry has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/HostGBean.java:[171,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/EngineGBean.java:[137,24]
 [deprecation] setServer(javax.management.MBeanServer) in 
org.apache.tomcat.util.modeler.Registry has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/main/java/org/apache/geronimo/tomcat/ManagerGBean.java:[93,19]
 [deprecation] addOperation(java.lang.String) in 
org.apache.geronimo.gbean.GBeanInfoBuilder has been deprecated

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 9 source files to 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/test-classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/AbstractWebModuleTest.java:[110,107]
 [deprecation] toURL() in java.io.File has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/ApplicationTest.java:[34,88]
 [deprecation] toURL() in java.io.File has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/src/test/java/org/apache/geronimo/tomcat/StatTest.java:[39,79]
 [deprecation] toURL() in java.io.File has been deprecated

[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/tomcat/geronimo-tomcat6/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.tomcat.ContainerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.64 sec
Running org.apache.geronimo.tomcat.BasicTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.233 sec
Running org.apache.geronimo.tomcat.TomcatServerGBeanTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 4.031 sec <<< 
FAILURE!
Running org.apache.geronimo.tomcat.ApplicationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.761 sec
Running org.apache.geronimo.tomcat.JAASSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.942 sec
Running org.apache.geronimo.tomcat.StatTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.677 sec
Running org.apache.geronimo.tomcat.JACCSecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.923 sec

Results :

Tests in error: 

Tests run: 8, Failures: 0, Errors: 2, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[

[jira] Commented: (GERONIMO-4849) Such warning will be shown after deleted a remote monitoring server via JMX

[Shawn Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754849#action_12754849
 ] 

Shawn Jiang commented on GERONIMO-4849:
---

Does 21 branch have the same problem ?

> Such warning will be shown after deleted a remote monitoring server via JMX
> ---
>
> Key: GERONIMO-4849
> URL: https://issues.apache.org/jira/browse/GERONIMO-4849
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
>Reporter: Shiny Cheng
> Fix For: 2.2
>
> Attachments: monitoring_jmx.patch
>
>
> The following warning will be shown after these steps.
> First, create a remote monitoring server via JMX and meanwhile, start the 
> remote server. Then, you delete the monitoring server and stop the remote 
> server. You will see the following information via log or command line.
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> I wonder mayb

[jira] Commented: (GERONIMO-4849) Such warning will be shown after deleted a remote monitoring server via JMX

[Shawn Jiang (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754848#action_12754848
 ] 

Shawn Jiang commented on GERONIMO-4849:
---

1, I noticed you only added mrc.dispose() at part of finally blocks. Shouldn't 
mrc.dispose() be added to all finally blocks ?

2, Please identify from which branch your patch is created.



> Such warning will be shown after deleted a remote monitoring server via JMX
> ---
>
> Key: GERONIMO-4849
> URL: https://issues.apache.org/jira/browse/GERONIMO-4849
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
>Reporter: Shiny Cheng
> Fix For: 2.2
>
> Attachments: monitoring_jmx.patch
>
>
> The following warning will be shown after these steps.
> First, create a remote monitoring server via JMX and meanwhile, start the 
> remote server. Then, you delete the monitoring server and stop the remote 
> server. You will see the following information via log or command line.
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refused: connect
> WARN  [misc] Failed to check connection: java.net.ConnectException: 
> Connection refused: connect
> WARN  [misc] stopping
> WARN  [misc] Failed to restart: java.io.IOException: Failed to get a RMI 
> stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested 
> exception is: 
>   java.net.ConnectException: Connection refused: connect]
> WARN  [rmi] Failed to call the method close():java.rmi.ConnectException: 
> Connection refused to host: 9.123.233.70; nested exception is: 
>   java.net.ConnectException: Connection refuse