date:20090903

the state is stopping when i click disable query of a running jmx server 
-

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


1、add a jmx server and its state is stopped
2、i click enable query  and the state is running
3、i click disable query  but the state is stopped

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

[jira] Closed: (GERONIMO-4829) can't install Geronimo Plugins, Monitoring :: Agent JMX CAR from http://geronimo.apache.org/plugins/geronimo-2.2/


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

Bin He closed GERONIMO-4829.



 can't install Geronimo Plugins, Monitoring :: Agent JMX CAR  from 
 http://geronimo.apache.org/plugins/geronimo-2.2/
 --

 Key: GERONIMO-4829
 URL: https://issues.apache.org/jira/browse/GERONIMO-4829
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: buildsystem
Affects Versions: 2.2
 Environment: jdk6
 windows sp2
Reporter: Bin He
Assignee: Shawn Jiang
Priority: Blocker

 1、start server
 2、click  plugins porlet
 3、choose http://geronimo.apache.org/plugins/geronimo-2.2/;  ,and click Show 
 Plugins in selected repository
 4、so the plugins listed at http://geronimo.apache.org/plugins/geronimo-2.2/ 
 is present.And choose Geronimo Plugins, Monitoring :: Agent JMX CAR  to 
 install . 
 5、But when I click intall,it showd :(I think if this problem can't be 
 solved,we can't do the work related to jmx)
 Current file being operated on... 
 Downloading 
 org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.2-SNAPSHOT/car
 A problem has occured: 
 java.lang.IllegalArgumentException: Could not find 
 org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.2-SNAPSHOT/car in any 
 repo: 
 [org.apache.geronimo.system.plugin.RemoteSourceRepository:http://geronimo.apache.org/plugins/geronimo-2.2/,
  
 org.apache.geronimo.system.plugin.RemoteSourceRepository:http://repo1.maven.org/maven2/,
  
 org.apache.geronimo.system.plugin.RemoteSourceRepository:http://people.apache.org/repo/m2-snapshot-repository/,
  
 org.apache.geronimo.system.plugin.RemoteSourceRepository:http://people.apache.org/repo/m2-incubating-repository/]

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

[jira] Updated: (GERONIMO-4843) the state is stopping when i click disable query of a running jmx server


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

Bin He updated GERONIMO-4843:
-

Description: 
1、add a localhost jmx server and its state is stopped
2、i click enable query  and the state is running
3、i click disable query  but the state is stopping

Another problem  :
When I  delete this stopping server ,I want to create a  localhost jmx server 
again .The state is also stopping.

So I think jmx has a big problem.

  was:
1、add a jmx server and its state is stopped
2、i click enable query  and the state is running
3、i click disable query  but the state is stopped


 the state is stopping when i click disable query of a running jmx server 
 -

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

 1、add a localhost jmx server and its state is stopped
 2、i click enable query  and the state is running
 3、i click disable query  but the state is stopping
 Another problem  :
 When I  delete this stopping server ,I want to create a  localhost jmx server 
 again .The state is also stopping.
 So I think jmx has a big problem.

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

[jira] Closed: (GERONIMO-4837) Cannot monitor the local server via

2009-09-03 Thread Ivan (JIRA)


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

Ivan closed GERONIMO-4837.
--

Resolution: Cannot Reproduce

Could not reproduce it :-(
If you found it is still an issue, please reopen it, thanks !

 Cannot monitor the local server via 
 

 Key: GERONIMO-4837
 URL: https://issues.apache.org/jira/browse/GERONIMO-4837
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: OS:Windows XP
 Server: G 2.2 snapshot
 JDK:1.6
Reporter: Lu Jiang

 When create a new instance to monitor the localhost Server.The status is 
 always offline.
 But when the  monitor can connect to a remote server and its status is online.

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

[jira] Closed: (GERONIMO-4843) the state is stopping when i click disable query of a running jmx server

2009-09-03 Thread Ivan (JIRA)


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

Ivan closed GERONIMO-4843.
--

Resolution: Duplicate

Should be the same issue with Geronimo-4822 
https://issues.apache.org/jira/browse/GERONIMO-4822
If I missed anything, please help to reopen it, thanks !

 the state is stopping when i click disable query of a running jmx server 
 -

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

 1、add a localhost jmx server and its state is stopped
 2、i click enable query  and the state is running
 3、i click disable query  but the state is stopping
 Another problem  :
 When I  delete this stopping server ,I want to create a  localhost jmx server 
 again .The state is also stopping.
 So I think jmx has a big problem.

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

[jira] Commented: (GERONIMO-4837) Cannot monitor the local server via

2009-09-03 Thread Victor Fang (JIRA)


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

Victor Fang commented on GERONIMO-4837:
---

I can't reproduce it, too.

 Cannot monitor the local server via 
 

 Key: GERONIMO-4837
 URL: https://issues.apache.org/jira/browse/GERONIMO-4837
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: OS:Windows XP
 Server: G 2.2 snapshot
 JDK:1.6
Reporter: Lu Jiang

 When create a new instance to monitor the localhost Server.The status is 
 always offline.
 But when the  monitor can connect to a remote server and its status is online.

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

[DISCUSS] Release Geronimo components 2.2 (tx manager / connector)

A long time ago, I've made those two jars available as OSGi bundles, but
they haven't been released yet because I did that in trunk.
I'd really like to have those as bundles, so I can backport the pom changes
in the branch and release from the branch or release trunk.
Not sure what the exact status for this component is.  I've seen djencks
made some changes in the branch that are not available in trunk, but trunk
also has some changes.
Please advise what would be the best way to proceed here.

-- 
Cheers,
Guillaume Nodet

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

Open Source SOA
http://fusesource.com

[jira] Closed: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a complete redeploy of a WAR

2009-09-03 Thread Delos Dai (JIRA)


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

Delos Dai closed GERONIMODEVTOOLS-580.
--


Verified it, All the problems have been resolved,so close it.

 Servlet/JSP update forces a complete redeploy of a WAR
 --

 Key: GERONIMODEVTOOLS-580
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580
 Project: Geronimo-Devtools
  Issue Type: Improvement
Affects Versions: 2.0.x, 2.2.0
Reporter: Kevan Miller
Assignee: Tim McConnell
 Fix For: 2.1.5, 2.2.0

 Attachments: 580.patch


 I've had several users comment to me that application development with GEP is 
 not as fast as it should be. Basic scenario is create an application, deploy, 
 test, update, test, update, etc... IIUC, for each update, GEP is repackaging 
 the WAR and running a redeploy. Repackaging/redeploy can take some time (for 
 large apps  30 seconds). IIUC, we could be updating the appropriate 
 JSP/Servlet classes directly and greatly improving this behavior. I don't 
 know how this works, however. Anybody interested in looking at this? I'd like 
 to see this improved in 2.2. If it's something that could be fixed in 2.1.x, 
 that would be great. But that might depend on how extensive the changes 
 are...  

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

[jira] Resolved: (GERONIMODEVTOOLS-575) GEP errors that are logged to the Eclipse error log are not always seen by end-user

2009-09-03 Thread Delos Dai (JIRA)


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

Delos Dai resolved GERONIMODEVTOOLS-575.


   Resolution: Fixed
Fix Version/s: 2.2.0
   2.1.5

For this jira, we re-organize the error messages for starting/stoping server, 
deployment/undeployment/redeployment and using invalid user id/password.  
All these error messages are visible to users now. 

 GEP errors that are logged to the Eclipse error log are not always seen by 
 end-user
 ---

 Key: GERONIMODEVTOOLS-575
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-575
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.4, 2.2.0
Reporter: Tim McConnell
Assignee: Tim McConnell
 Fix For: 2.1.5, 2.2.0

 Attachments: 575.patch, 575_new.patch, 575_startserver.patch, 
 575_stopserver.patch


 For example, when deploying an erroneous war file to the Geronimo server will 
 result in the following to the Eclispe.log that the end-user may not likely 
 see.
 !ENTRY org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE Distribution of module failed.  See log for details.
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE Unable to resolve resource reference 'jdbc/users' (Could not 
 auto-map to resource.  Try adding a resource-ref mapping to your Geronimo 
 deployment plan.
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE Search conducted in current module and dependencies:
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE )
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE org.apache.geronimo.common.DeploymentException: Unable to resolve 
 resource reference 'jdbc/users' (Could not auto-map to resource.  Try adding 
 a resource-ref mapping to your Geronimo deployment plan.
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE Search conducted in current module and dependencies:
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/tomcat6/2.1.4/car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [CLASSES: org.apache.geronimo.configs/openejb//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/axis//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/axis2//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE [ALL: org.apache.geronimo.configs/openjpa//car]
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE )
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE  at 
 org.apache.geronimo.connector.deployment.ResourceRefBuilder.buildNaming(ResourceRefBuilder.java:216)
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE  at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53)
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE  at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:842)
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE  at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:347)
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE  at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
 !SUBENTRY 1 org.apache.geronimo.st.core 4 0 2009-05-31 15:09:17.859
 !MESSAGE

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

2009-09-03 Thread Delos Dai (JIRA)


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

Delos Dai resolved GERONIMODEVTOOLS-579.


   Resolution: Fixed
Fix Version/s: 2.2.0
   2.1.5

revision #810806 for trunk; revision  #810827 for 2.1.5 branch.



 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-4804) Fail to set up Tomcat Cluster

2009-09-03 Thread Chi Runhua (JIRA)


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

Chi Runhua commented on GERONIMO-4804:
--

Thanks Shawn for the solution. I removed the security constraints and realm 
info from both web.xml and deployment plan.

Now the application can be deployed on G2.2 but with the following warning in 
the log

2009-09-03 17:22:12,276 WARN  [TomcatModuleBuilder] No clustering builders 
configured: app will not be clustered
2009-09-03 17:22:12,824 WARN  [SimpleTcpCluster] setManagerClassName is 
deprecated, use nested Manager element inside the Cluster element instead, 
this request will be ignored.



Jeff C

 Fail to set up Tomcat Cluster 
 --

 Key: GERONIMO-4804
 URL: https://issues.apache.org/jira/browse/GERONIMO-4804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 2.2
 Environment: OS:win2003
Reporter: viola.lu
Assignee: Shawn Jiang
Priority: Minor
 Attachments: servlet-examples-cluster-plan.xml, 
 servlet-examples-cluster-server1.war


 1.Modify server.xml under var/catalina/ as tomcat how-to-cluster doc as below:
 Engine name=Catalina defaultHost=${ServerHostname} jvmRoute=node2 
 channelSendOptions=8
 Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster
 Manager className=org.apache.catalina.ha.session.DeltaManager
expireSessionsOnShutdown=false
notifyListenersOnReplication=true/
   Channel className=org.apache.catalina.tribes.group.GroupChannel
 Membership 
 className=org.apache.catalina.tribes.membership.McastService
 address=228.0.0.4
 port=45564
 frequency=500
 dropTime=3000/
 Receiver 
 className=org.apache.catalina.tribes.transport.nio.NioReceiver
   address=auto
   port=4000
   autoBind=100
   selectorTimeout=5000
   maxThreads=6/
 Sender 
 className=org.apache.catalina.tribes.transport.ReplicationTransmitter
   Transport 
 className=org.apache.catalina.tribes.transport.nio.PooledParallelSender/
 /Sender
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.TcpFailureDetector/
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor/
   /Channel
   Valve className=org.apache.catalina.ha.tcp.ReplicationValve
  filter=/
   Valve 
 className=org.apache.catalina.ha.session.JvmRouteBinderValve/
   Deployer className=org.apache.catalina.ha.deploy.FarmWarDeployer
 tempDir=/tmp/war-temp/
 deployDir=/tmp/war-deploy/
 watchDir=/tmp/war-listen/
 watchEnabled=false/
   ClusterListener 
 className=org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener/
   ClusterListener 
 className=org.apache.catalina.ha.session.ClusterSessionListener/
   /Cluster
 
 /Engine
 2.And deploy web apps whose web.xml containing distributable element 
 succesfully
 3.Configure Apache http server with mod_jk, but errors in mod_jk.log
 [error] jk_ajp_common.c (1011): (NODE2) can't receive the response message 
 from tomcat, network problems or tomcat (9.186.10.167:8009) is down (errno=60)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [error] jk_ajp_common.c (1766): 
 (NODE2) Tomcat is down or refused connection. No response has been sent to 
 the client (yet)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [info] jk_ajp_common.c (2186): (NODE2) 
 sending request to tomcat failed (recoverable),  (attempt=1)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1011): 
 (NODE1) can't receive the response message from tomcat, network problems or 
 tomcat (9.186.10.67:8009) is down (errno=60)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1766): 
 (NODE1) Tomcat is down or refused connection. No response has been sent to 
 the client (yet)
 If i follow tomcat cluster steps used in g 2.1.*  to work on G 2.2 snapshot, 
 it does't work also, when deploy web app, there is an error:
 org.apache.geronimo.common.DeploymentException: Unable to resolve reference 
 NextValve

-- 
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-4804) Fail to set up Tomcat Cluster

2009-09-03 Thread Chi Runhua (JIRA)


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

Chi Runhua edited comment on GERONIMO-4804 at 9/3/09 2:33 AM:
--

Thanks Shawn for the solution. I also removed the security constraints and 
realm info from both web.xml and deployment plan.

Now the application can be deployed on G2.2 using GBean method but with the 
following warning in the log

2009-09-03 17:22:12,276 WARN  [TomcatModuleBuilder] No clustering builders 
configured: app will not be clustered
2009-09-03 17:22:12,824 WARN  [SimpleTcpCluster] setManagerClassName is 
deprecated, use nested Manager element inside the Cluster element instead, 
this request will be ignored.



Jeff C

  was (Author: chi runhua):
Thanks Shawn for the solution. I removed the security constraints and realm 
info from both web.xml and deployment plan.

Now the application can be deployed on G2.2 but with the following warning in 
the log

2009-09-03 17:22:12,276 WARN  [TomcatModuleBuilder] No clustering builders 
configured: app will not be clustered
2009-09-03 17:22:12,824 WARN  [SimpleTcpCluster] setManagerClassName is 
deprecated, use nested Manager element inside the Cluster element instead, 
this request will be ignored.



Jeff C
  
 Fail to set up Tomcat Cluster 
 --

 Key: GERONIMO-4804
 URL: https://issues.apache.org/jira/browse/GERONIMO-4804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 2.2
 Environment: OS:win2003
Reporter: viola.lu
Assignee: Shawn Jiang
Priority: Minor
 Attachments: servlet-examples-cluster-plan.xml, 
 servlet-examples-cluster-server1.war


 1.Modify server.xml under var/catalina/ as tomcat how-to-cluster doc as below:
 Engine name=Catalina defaultHost=${ServerHostname} jvmRoute=node2 
 channelSendOptions=8
 Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster
 Manager className=org.apache.catalina.ha.session.DeltaManager
expireSessionsOnShutdown=false
notifyListenersOnReplication=true/
   Channel className=org.apache.catalina.tribes.group.GroupChannel
 Membership 
 className=org.apache.catalina.tribes.membership.McastService
 address=228.0.0.4
 port=45564
 frequency=500
 dropTime=3000/
 Receiver 
 className=org.apache.catalina.tribes.transport.nio.NioReceiver
   address=auto
   port=4000
   autoBind=100
   selectorTimeout=5000
   maxThreads=6/
 Sender 
 className=org.apache.catalina.tribes.transport.ReplicationTransmitter
   Transport 
 className=org.apache.catalina.tribes.transport.nio.PooledParallelSender/
 /Sender
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.TcpFailureDetector/
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor/
   /Channel
   Valve className=org.apache.catalina.ha.tcp.ReplicationValve
  filter=/
   Valve 
 className=org.apache.catalina.ha.session.JvmRouteBinderValve/
   Deployer className=org.apache.catalina.ha.deploy.FarmWarDeployer
 tempDir=/tmp/war-temp/
 deployDir=/tmp/war-deploy/
 watchDir=/tmp/war-listen/
 watchEnabled=false/
   ClusterListener 
 className=org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener/
   ClusterListener 
 className=org.apache.catalina.ha.session.ClusterSessionListener/
   /Cluster
 
 /Engine
 2.And deploy web apps whose web.xml containing distributable element 
 succesfully
 3.Configure Apache http server with mod_jk, but errors in mod_jk.log
 [error] jk_ajp_common.c (1011): (NODE2) can't receive the response message 
 from tomcat, network problems or tomcat (9.186.10.167:8009) is down (errno=60)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [error] jk_ajp_common.c (1766): 
 (NODE2) Tomcat is down or refused connection. No response has been sent to 
 the client (yet)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [info] jk_ajp_common.c (2186): (NODE2) 
 sending request to tomcat failed (recoverable),  (attempt=1)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1011): 
 (NODE1) can't receive the response message from tomcat, network problems or 
 tomcat (9.186.10.67:8009) is down (errno=60)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1766): 
 (NODE1) Tomcat is

[jira] Created: (GERONIMO-4844) There is an error after undeploy the application and deploy the application again when configure WADI clustering,

2009-09-03 Thread liangkun (JIRA)

There is an error after undeploy the application and  deploy the application 
again when configure WADI clustering,
--

 Key: GERONIMO-4844
 URL: https://issues.apache.org/jira/browse/GERONIMO-4844
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Clustering
Affects Versions: 2.2
 Environment: windows:sp2
jdk1.6
Reporter: liangkun


I deploy the application cviewer.war after undeploy it when configure the WADI 
clustering ,the there is an error:


org.apache.geronimo.common.DeploymentException: Unable to deploy 
cviewer-2.1.1.2.war: Module com.ibm.wasce.samples/cviewer/2.1.1.2/car already 
exists in the server.  Try to undeploy it first or use the redeploy command.

at 
org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:45)
at 
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:139)
at 
org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:125)
at 
org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:168)
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.deployer.DeployerCLI.main(DeployerCLI.java:31)

However,actually,there are no any module in the server.


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

[jira] Commented: (GERONIMO-4804) Fail to set up Tomcat Cluster

2009-09-03 Thread Shawn Jiang (JIRA)


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

Shawn Jiang commented on GERONIMO-4804:
---

The warning should be OK,  please ignore it to see if the clustering is really 
working.  Thanks.

 Fail to set up Tomcat Cluster 
 --

 Key: GERONIMO-4804
 URL: https://issues.apache.org/jira/browse/GERONIMO-4804
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 2.2
 Environment: OS:win2003
Reporter: viola.lu
Assignee: Shawn Jiang
Priority: Minor
 Attachments: servlet-examples-cluster-plan.xml, 
 servlet-examples-cluster-server1.war


 1.Modify server.xml under var/catalina/ as tomcat how-to-cluster doc as below:
 Engine name=Catalina defaultHost=${ServerHostname} jvmRoute=node2 
 channelSendOptions=8
 Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster
 Manager className=org.apache.catalina.ha.session.DeltaManager
expireSessionsOnShutdown=false
notifyListenersOnReplication=true/
   Channel className=org.apache.catalina.tribes.group.GroupChannel
 Membership 
 className=org.apache.catalina.tribes.membership.McastService
 address=228.0.0.4
 port=45564
 frequency=500
 dropTime=3000/
 Receiver 
 className=org.apache.catalina.tribes.transport.nio.NioReceiver
   address=auto
   port=4000
   autoBind=100
   selectorTimeout=5000
   maxThreads=6/
 Sender 
 className=org.apache.catalina.tribes.transport.ReplicationTransmitter
   Transport 
 className=org.apache.catalina.tribes.transport.nio.PooledParallelSender/
 /Sender
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.TcpFailureDetector/
 Interceptor 
 className=org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor/
   /Channel
   Valve className=org.apache.catalina.ha.tcp.ReplicationValve
  filter=/
   Valve 
 className=org.apache.catalina.ha.session.JvmRouteBinderValve/
   Deployer className=org.apache.catalina.ha.deploy.FarmWarDeployer
 tempDir=/tmp/war-temp/
 deployDir=/tmp/war-deploy/
 watchDir=/tmp/war-listen/
 watchEnabled=false/
   ClusterListener 
 className=org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener/
   ClusterListener 
 className=org.apache.catalina.ha.session.ClusterSessionListener/
   /Cluster
 
 /Engine
 2.And deploy web apps whose web.xml containing distributable element 
 succesfully
 3.Configure Apache http server with mod_jk, but errors in mod_jk.log
 [error] jk_ajp_common.c (1011): (NODE2) can't receive the response message 
 from tomcat, network problems or tomcat (9.186.10.167:8009) is down (errno=60)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [error] jk_ajp_common.c (1766): 
 (NODE2) Tomcat is down or refused connection. No response has been sent to 
 the client (yet)
 [Wed Aug 19 14:01:45 2009] [6828:5876] [info] jk_ajp_common.c (2186): (NODE2) 
 sending request to tomcat failed (recoverable),  (attempt=1)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1011): 
 (NODE1) can't receive the response message from tomcat, network problems or 
 tomcat (9.186.10.67:8009) is down (errno=60)
 [Wed Aug 19 14:02:03 2009] [6828:1212] [error] jk_ajp_common.c (1766): 
 (NODE1) Tomcat is down or refused connection. No response has been sent to 
 the client (yet)
 If i follow tomcat cluster steps used in g 2.1.*  to work on G 2.2 snapshot, 
 it does't work also, when deploy web app, there is an error:
 org.apache.geronimo.common.DeploymentException: Unable to resolve reference 
 NextValve

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

[jira] Updated: (DAYTRADER-68) A version of daytrader for Tomcat 6

2009-09-03 Thread Forrest Xia (JIRA)


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

Forrest Xia updated DAYTRADER-68:
-

Attachment: daytrader-webonly-updated.patch

Except the 5th item, all of remained todo items are done with the new patch 
daytrader-webonly-updated.patch:
1. Remove unnecessary dependencies of daytrader web only version
2. Update README to better decribe the differences from the formal version
3. Add two plugins for Tomcat and Jetty respectively for web only version
4. Update daytrader trunk to use Jetty7

Please check and help commit, thanks!

 A version of daytrader for Tomcat 6
 ---

 Key: DAYTRADER-68
 URL: https://issues.apache.org/jira/browse/DAYTRADER-68
 Project: DayTrader
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: Web Tier
Affects Versions: 2.2
 Environment: Tomcat 6.0.18
Reporter: Forrest Xia
Assignee: Joe Bohn
 Fix For: 2.2

 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, 
 daytrader-webonly-updated.patch, daytrader-webonly.patch


 I have a trimmed version of daytrader for tomcat 6, and want to contribute to 
 daytrader trunk, please help review and commit. thanks!

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

[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6

2009-09-03 Thread Joe Bohn (JIRA)


[ 
https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751011#action_12751011
 ] 

Joe Bohn commented on DAYTRADER-68:
---

Forrest,
Is this a patch for trunk?  Was it created after the most recent structure 
changes?  I believe that the /daytrader-webonly/ directory and it's contents 
are all but physically removed from svn now and has been replaced with 
/assemblies/web/daytrader-web-jdbc/
Joe

 A version of daytrader for Tomcat 6
 ---

 Key: DAYTRADER-68
 URL: https://issues.apache.org/jira/browse/DAYTRADER-68
 Project: DayTrader
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: Web Tier
Affects Versions: 2.2
 Environment: Tomcat 6.0.18
Reporter: Forrest Xia
Assignee: Joe Bohn
 Fix For: 2.2

 Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, 
 daytrader-webonly-updated.patch, daytrader-webonly.patch


 I have a trimmed version of daytrader for tomcat 6, and want to contribute to 
 daytrader trunk, please help review and commit. thanks!

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

Geronimo Revision: 810750 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/unit-test-reports
 
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 3 source files to 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@501c501c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@5c145c14
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/target/surefire-reports

---
 T E S T S
---
There are no tests to run.

Results :

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

[INFO] [jar:jar]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/target/geronimo-activemq-management-3.0-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-activemq-management-3.0-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/activemq/geronimo-activemq-management/target/geronimo-activemq-management-3.0-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-activemq-management/3.0-SNAPSHOT/geronimo-activemq-management-3.0-SNAPSHOT.jar
[INFO] 
[INFO] Building Geronimo Plugins, ActiveMQ v5 :: Core
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking for 
updates from codehaus.snapshots
[INFO] snapshot org.apache.activemq:activemq-core:5.3-SNAPSHOT: checking for 
updates from apache.snapshots
Downloading: 
http://snapshots.repository.codehaus.org/org/apache/activemq/activemq-core/5.3-SNAPSHOT/activemq-core-5.3-SNAPSHOT.pom
Downloading: 
http://repository.apache.org/snapshots/org/apache/activemq/activemq-core/5.3-SNAPSHOT/activemq-core-5.3-SNAPSHOT.pom
24K downloaded
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@501c501c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@5c145c14
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@501c501c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@5c145c14
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@501c501c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@5c145c14
[INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT: checking for 
updates from codehaus.snapshots
[INFO] snapshot org.apache.activemq:activemq-parent:5.3-SNAPSHOT: checking for 
updates from apache.snapshots
Downloading: 
http://snapshots.repository.codehaus.org/org/apache/activemq/activemq-parent/5.3-SNAPSHOT/activemq-parent-5.3-SNAPSHOT.pom
Downloading: 
http://repository.apache.org/snapshots/org/apache/activemq

Re: [DISCUSS] Release Geronimo components 2.2 (tx manager / connector)

2009-09-03 Thread David Jencks



On Sep 3, 2009, at 1:20 AM, Guillaume Nodet wrote:

A long time ago, I've made those two jars available as OSGi bundles,  
but they haven't been released yet because I did that in trunk.
I'd really like to have those as bundles, so I can backport the pom  
changes in the branch and release from the branch or release trunk.
Not sure what the exact status for this component is.  I've seen  
djencks made some changes in the branch that are not available in  
trunk, but trunk also has some changes.


Can you be more specific about the changes and which svn urls you are  
talking about?


https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk   
uses connector 1.6 spec, so I don't think we will release it until we  
have some idea that we are fairly OK with the ee6 tck, and also that  
it works with whatever osgi stuff we end up with in g. trunk.


https://svn.apache.org/repos/asf/geronimo/components/txmanager/branches/geronimo-txmanager-parent-2.1 
 uses connector 1.5 and we need to release it for g. 2.2 as it has  
some important bug fixes.


Making sure both of these are osgi-workable would be great.  I thought  
I'd merged all the bug fixes both ways between these branches, if you  
see a problem please let me know!


I'm hoping to get to releasing some specs and other sub-projects for  
2.2 this week, so if you can make sure the 2.1 branch is acceptable  
that would be really great!


thanks
david jencks



Please advise what would be the best way to proceed here.

--
Cheers,
Guillaume Nodet

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

Open Source SOA
http://fusesource.com

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

Geronimo Revision: 810735 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090902/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090902
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 54 seconds
[INFO] Finished at: Wed Sep 02 20:46:55 EDT 2009
[INFO] Final Memory: 438M/1013M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090902/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:48.931
[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:26.832) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:38.954) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:46.131) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:23.504) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:41.616) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:40.768) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:08.668) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:58.203) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:24.617) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:52.795) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:38.214) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:36.383) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:40.596) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:16.124) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:20.811) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:58.775) 
[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS (0:00:34.978) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:01:20.090) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:57.089) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:35.986) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:34.614) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO]

Re: [DISCUSS] Release Geronimo components 2.2 (tx manager / connector)

I'd like this commit [1] to be releases somehow.
I'll backport it to the 2.1 branch asap.

[1] http://svn.apache.org/viewvc?view=revrevision=615758

On Thu, Sep 3, 2009 at 18:00, David Jencks david_jen...@yahoo.com wrote:


 On Sep 3, 2009, at 1:20 AM, Guillaume Nodet wrote:

 A long time ago, I've made those two jars available as OSGi bundles, but
 they haven't been released yet because I did that in trunk.
 I'd really like to have those as bundles, so I can backport the pom changes
 in the branch and release from the branch or release trunk.
 Not sure what the exact status for this component is.  I've seen djencks
 made some changes in the branch that are not available in trunk, but trunk
 also has some changes.


 Can you be more specific about the changes and which svn urls you are
 talking about?

 https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk  uses
 connector 1.6 spec, so I don't think we will release it until we have some
 idea that we are fairly OK with the ee6 tck, and also that it works with
 whatever osgi stuff we end up with in g. trunk.


 https://svn.apache.org/repos/asf/geronimo/components/txmanager/branches/geronimo-txmanager-parent-2.1uses
  connector 1.5 and we need to release it for g. 2.2 as it has some
 important bug fixes.

 Making sure both of these are osgi-workable would be great.  I thought I'd
 merged all the bug fixes both ways between these branches, if you see a
 problem please let me know!

 I'm hoping to get to releasing some specs and other sub-projects for 2.2
 this week, so if you can make sure the 2.1 branch is acceptable that would
 be really great!

 thanks
 david jencks


 Please advise what would be the best way to proceed here.

 --
 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: [DISCUSS] Release Geronimo components 2.2 (tx manager / connector)

2009-09-03 Thread David Jencks

I thought I had already bundleized 2.1 since we are using the  
2.0.0 bundle plugin a direct merge or [1] won't work.  In the  
interests of my learning how to set this stuff up I just committed a  
bundleization of 2.1.  Can you please check it?  In particular, should  
the import of javax.resource in txmanager be optional?


thanks
david jencks

On Sep 3, 2009, at 9:18 AM, Guillaume Nodet wrote:


I'd like this commit [1] to be releases somehow.
I'll backport it to the 2.1 branch asap.

[1] http://svn.apache.org/viewvc?view=revrevision=615758

On Thu, Sep 3, 2009 at 18:00, David Jencks david_jen...@yahoo.com  
wrote:


On Sep 3, 2009, at 1:20 AM, Guillaume Nodet wrote:

A long time ago, I've made those two jars available as OSGi  
bundles, but they haven't been released yet because I did that in  
trunk.
I'd really like to have those as bundles, so I can backport the pom  
changes in the branch and release from the branch or release trunk.
Not sure what the exact status for this component is.  I've seen  
djencks made some changes in the branch that are not available in  
trunk, but trunk also has some changes.


Can you be more specific about the changes and which svn urls you  
are talking about?


https://svn.apache.org/repos/asf/geronimo/components/txmanager/ 
trunk  uses connector 1.6 spec, so I don't think we will release it  
until we have some idea that we are fairly OK with the ee6 tck, and  
also that it works with whatever osgi stuff we end up with in g.  
trunk.


https://svn.apache.org/repos/asf/geronimo/components/txmanager/branches/geronimo-txmanager-parent-2.1 
 uses connector 1.5 and we need to release it for g. 2.2 as it has  
some important bug fixes.


Making sure both of these are osgi-workable would be great.  I  
thought I'd merged all the bug fixes both ways between these  
branches, if you see a problem please let me know!


I'm hoping to get to releasing some specs and other sub-projects for  
2.2 this week, so if you can make sure the 2.1 branch is acceptable  
that would be really great!


thanks
david jencks



Please advise what would be the best way to proceed here.

--
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: [DISCUSS] Release Geronimo components 2.2 (tx manager / connector)

I've slightly enhanced what you did.
Mostly, I've added the following lines:


Import-Package!org.apache.geronimo.connector*,*/Import-Package

_versionpolicy[$(version;==;$(@)),$(version;+;$(@)))/_versionpolicy

The first line is to ensure that the bundle won't import the package it
exports.  Such a thing is ok for an api, but not for an implementation /
library as you certainly don't want to use classes from another version of
the bundle.
The second line makes sure the version uses ranges by default such as
[2.1,3.0), meaning any version = 2.1 and  3.0.  This assume backward
compatibility between minor releases.  FWIW, if you don't put anything, it
would be [2.1,), meaning anything = 2.1.

For the javax.resource package, it can't really be optional, as the
GeronimoTransactionManager implements javax.resource.spi.XATerminator.
If we want to not import this package, we could add this only class to the
bundle and not export the package.  That would mean the maven dependency
could be removed altogether ...

On Thu, Sep 3, 2009 at 19:04, David Jencks david_jen...@yahoo.com wrote:

 I thought I had already bundleized 2.1 since we are using the 2.0.0
 bundle plugin a direct merge or [1] won't work.  In the interests of my
 learning how to set this stuff up I just committed a bundleization of 2.1.
  Can you please check it?  In particular, should the import of
 javax.resource in txmanager be optional?
 thanks
 david jencks

 On Sep 3, 2009, at 9:18 AM, Guillaume Nodet wrote:

 I'd like this commit [1] to be releases somehow.
 I'll backport it to the 2.1 branch asap.

 [1] http://svn.apache.org/viewvc?view=revrevision=615758

 On Thu, Sep 3, 2009 at 18:00, David Jencks david_jen...@yahoo.com wrote:


 On Sep 3, 2009, at 1:20 AM, Guillaume Nodet wrote:

 A long time ago, I've made those two jars available as OSGi bundles, but
 they haven't been released yet because I did that in trunk.
 I'd really like to have those as bundles, so I can backport the pom
 changes in the branch and release from the branch or release trunk.
 Not sure what the exact status for this component is.  I've seen djencks
 made some changes in the branch that are not available in trunk, but trunk
 also has some changes.


 Can you be more specific about the changes and which svn urls you are
 talking about?

 https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk  uses
 connector 1.6 spec, so I don't think we will release it until we have some
 idea that we are fairly OK with the ee6 tck, and also that it works with
 whatever osgi stuff we end up with in g. trunk.


 https://svn.apache.org/repos/asf/geronimo/components/txmanager/branches/geronimo-txmanager-parent-2.1uses
  connector 1.5 and we need to release it for g. 2.2 as it has some
 important bug fixes.

 Making sure both of these are osgi-workable would be great.  I thought I'd
 merged all the bug fixes both ways between these branches, if you see a
 problem please let me know!

 I'm hoping to get to releasing some specs and other sub-projects for 2.2
 this week, so if you can make sure the 2.1 branch is acceptable that would
 be really great!

 thanks
 david jencks


 Please advise what would be the best way to proceed here.

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






-- 
Cheers,
Guillaume Nodet

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

Open Source SOA
http://fusesource.com

Apache Karaf info

2009-09-03 Thread Jarek Gawor

Hey,

Apache Karaf was mentioned a couple times on this list as something we
want to consider for using in/for Geronimo 3.0. So, I've been looking
at it for last few days to get a better understanding how it works,
what it does, etc. and thought maybe others want to know what I
learned about it. Overall, I think it fits pretty well for what we
want to do with Geronimo.

What does Karaf have?

- JMX (rfc 139): it actually uses the RI from OSGi Alliance
- Blueprint (rfc 124): it uses Geronimo implementation. It actually
uses Blueprint to deploy and configure all of the services it
provides. For example, the JMX connector, rmi registry, mbean server,
gshell commands, all are configured via Blueprint. It also uses the
Blueprint features that were deleted from the official spec but we
still kept it in the Geronimo impl - i.e. the Configuration Admin
service support and namespace handler extensions.
- GShell: provides commands for osgi operations (install bundle,
uninstall bundle, stop, start, etc.), adding/changing/deleting
configurations (for Configuration Admin service support), some basic
shell commands (exec, grep, etc)., some commands for creating Karaf
instances (same idea as in Geronimo), some for inspecting logs, and
some ssh commands. I think you can install ssh daemon and ssh into the
console but I have not tried that.
- Logging service: provided by Pax Logging, exposes all the logging
API (slf4j, commons logging, etc.)
- Additional url handlers for mvn and wrap urls. That's provided by
Pax Url bundles. The mvn: url handler allow you to specify a url in
mvn://group/artifacts/version/type format, and the handler will go out
to a specified set of repositories (local or remote) and resolve the
bundle and install it. The wrap: url handler allows transform and
install non OSGi jar files into OSGi bundles. See Pax Url for more
details.
- It also comes with Preference Service and Configuration Admin
Service - both provided by Felix.
- File Install bundle provided by Felix. It provides hot
deployment/update functionality. For example, you can drop bundles
into the deploy directory and they will be automatically deployed
(just like in Geronimo) and also, it can watch configuration files
(those in etc directory) and update the corresponding Configuration
objects (from Configuration Admin service). More on this below.
- Some JAAS security support which I haven't looked at yet.

How does it work?

Karaf can work on top of any OSGi framework and in fact comes with
Equinox and Felix jars but by default it boots Felix. Karaf starts by
instantiating the OSGi framework and than reads etc/startup.properties
file which contains an ordered list of bundles (and their run level)
to start. The bundles in the startup.properties file are specified in
mvn format. That's one of the places where Pax Url is used. Pax Url is
actually configured (see etc/org.ops4j.pax.url.mvn.cfg) to use the
system directory as a default local maven repo. It's also configured
with a few remote repos. The system directory is in mvn layout and
has all the bundles that Karaf needs (mentioned above). However,
during startup Karaf actually installs the bundles from the system
bundle into the framework. And with Felix, when you install a bundle
it actually copies the bundle jar file into its own data directory.
So after starting Karaf for the first time, you pretty much will have
the jars in the system directory duplicated in the data directory.
I guess that's the price for being OSGI framework independent. But we
might be able to improve it. Also, if you install a bundle
dynamically, it goes into the Felix's data directory and not the
system directory.

After all the bundles are installed and framework started, all the
rest of the work is done via Blueprint.

Configuration

In OSGi things are configured via Configuration Admin service.
ConfigAdmin service provides Configuration objects which basically
have multiple name=value properties and each Configuration object has
an unique id. In Karaf and with the help of File Install bundle
these Configuration objects are represented as simple text
configuration files under the etc directory with .cfg extension.
The name of the file corresponds to the id of the Configuration
object. And if you change the .cfg file at runtime the Configuration
object should be updated as well. Geronimo Blueprint implementation
has Configuration Admin support so all this nicely integrates
together.

Features

Karaf has this concept of features. Features can have dependencies
on other features, they contain a list of bundles, and can have some
configuration data. So installing a feature, can trigger installation
of multiple bundles. For example, installing http feature installs
Geronimo Servlet spec jar bundle, Jetty bundle, and Pax Web bundle.
All are automatically downloaded from the maven repos specified in
etc/org.ops4j.pax.url.mvn.cfg.

There is also a webconsole feature that installs Felix's webconsole
bundle and some Karaf

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

Geronimo Revision: 811060 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090903/build-1400.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090903
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 48 minutes 14 seconds
[INFO] Finished at: Thu Sep 03 14:53:18 EDT 2009
[INFO] Final Memory: 402M/1014M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090903/logs-1400-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:47.215
[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.034) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:39.033) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:47.608) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:24.238) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:40.931) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:41.397) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:09.254) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:57.185) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:05.848) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:54.311) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:38.447) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:36.509) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:41.197) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:23.492) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:24.119) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:00.179) 
[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS (0:00:34.960) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:01:00.812) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:58.096) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:36.562) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:35.642) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test

[BUILD] trunk: Failed for Revision: 811080

Geronimo Revision: 811080 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 43 minutes 26 seconds
[INFO] Finished at: Thu Sep 03 15:45:34 EDT 2009
[INFO] Final Memory: 473M/849M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/logs-1500-tomcat/
 
 
[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:03.000) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  FAILURE (0:00:18.839) Java 
returned: 1
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   FAILURE (0:00:31.880) Java 
returned: 1
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.714) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  FAILURE (0:00:05.239) Java 
returned: 1
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:33.664) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:59.468) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   FAILURE (0:00:48.129) Java 
returned: 1
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  FAILURE (0:00:01.997) Java 
returned: 1
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:58.519) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.352) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:36.978) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:41.203) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests FAILURE (0:00:01.004) Java 
returned: 1
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests FAILURE (0:01:02.537) Java 
returned: 1
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests FAILURE (0:00:02.013) Java 
returned: 1
[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS (0:00:29.675) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:01:03.617) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:54.890) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.798) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:36.604) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:34.551) 
[INFO] web-testsuite/test-tomcat  RUNNING
[INFO] web-testsuite/test-tomcat  SUCCESS (0:00:25.300) 
[INFO] web-testsuite/test-web-forward RUNNING
[INFO] web-testsuite/test-web-forward SUCCESS (0:00:43.834) 
[INFO] web-testsuite/test-web-references  RUNNING
[INFO] web-testsuite/test-web-references  FAILURE (0:00:02.683) Java 
returned: 1
[INFO] webservices-testsuite/jaxb-tests   RUNNING
[INFO] webservices-testsuite/jaxb-tests   SUCCESS (0:01:04.192) 
[INFO] webservices-testsuite/jaxr-tests   RUNNING
[INFO] webservices-testsuite/jaxr-tests   SUCCESS (0:01:05.024) 
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   RUNNING
[INFO] webservices-testsuite/jaxrpc-jaxws-tests   FAILURE (0:00:26.008) Java 
returned: 1
[INFO] webservices-testsuite/jaxrpc-tests RUNNING
[INFO] webservices-testsuite/jaxrpc-tests SUCCESS (0:00:53.122) 
[INFO

xbean pom parent genesis?

2009-09-03 Thread David Jencks

We need to release a new xbean for geronimo 2.2.  Early on genesis  
might have been regarded (although not by me) as possibly a little  
unstable and overcomplicated but IMO with genesis 2 its pretty simple,  
bare-bones, and useful.  In particular I would rather not duplicate  
stuff in genesis that results in compliant releases.


So, unless someone objects with a coherent argument I'm planning to  
change the xbean pom parent to genesis 2 in preparation for a 3.6  
release.


many thanks
david jencks

Re: xbean pom parent genesis?

Sounds good to me.

On Thu, Sep 3, 2009 at 23:24, David Jencks david_jen...@yahoo.com wrote:

 We need to release a new xbean for geronimo 2.2.  Early on genesis might
 have been regarded (although not by me) as possibly a little unstable and
 overcomplicated but IMO with genesis 2 its pretty simple, bare-bones, and
 useful.  In particular I would rather not duplicate stuff in genesis that
 results in compliant releases.

 So, unless someone objects with a coherent argument I'm planning to change
 the xbean pom parent to genesis 2 in preparation for a 3.6 release.

 many thanks
 david jencks




-- 
Cheers,
Guillaume Nodet

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

Open Source SOA
http://fusesource.com

Re: xbean pom parent genesis?

2009-09-03 Thread Kevan Miller



On Sep 3, 2009, at 5:24 PM, David Jencks wrote:

We need to release a new xbean for geronimo 2.2.  Early on genesis  
might have been regarded (although not by me) as possibly a little  
unstable and overcomplicated but IMO with genesis 2 its pretty  
simple, bare-bones, and useful.  In particular I would rather not  
duplicate stuff in genesis that results in compliant releases.


So, unless someone objects with a coherent argument I'm planning to  
change the xbean pom parent to genesis 2 in preparation for a 3.6  
release.


Sounds like a good plan to me.

--kevan

[jira] Updated: (GERONIMO-4827) it says javax.portlet.PortletException when I click monitoring portlet after I drop table graph in database MonitoringClientDB


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

Bin He updated GERONIMO-4827:
-

Priority: Major  (was: Critical)

 it says  javax.portlet.PortletException  when I click monitoring portlet  
 after I drop table graph in database MonitoringClientDB
 ---

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

 1、start server
 2、click monitoting porlet
 3、create server、view、graph，so it create MonitoringClientDB database 
 automatically
 4、click DB Manager porlet ,and input drop table graph; as sql command  
 using DB MonitoringClientDB .
 5、run sql and the graph table is deleted normally
 6、click monitoting porlet again it says:(But when I restart server ,the 
 monitoring porlet runs well)
 javax.portlet.PortletException
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.addAllViewsAttribute(MonitoringPortlet.java:495)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:451)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
   at 
 org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
   at 
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
   at 
 org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:151)
   at

[BUILD] trunk: Failed for Revision: 811196

Geronimo Revision: 811196 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090903/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@1c001c
[WARNING] Component returned which is not the same manager

[jira] Created: (GERONIMO-4845) the view is also existed after I delete the server in monitoting portlet

the view is also existed after I delete the server in monitoting portlet


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


1、create server、view、graph
2、i delete the server ,and the graphs which belong to the server are all 
deleted .But the related views are also existed. So i think it's a problem

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

[jira] Commented: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root

2009-09-03 Thread Rodger Zhang (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751276#action_12751276
]

Rodger Zhang commented on GERONIMODEVTOOLS-283:
---

The rename item is bond with a action, and probably there is no extension
point to modify the action's wizard. Like wtp's rename , its wizard does not
provide a check box for changing display-name/ in web.xml. It is possible to
implement this tiny feature but with a large effort, because the rename is
not implemented by GEP.

Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id
context root
-

Key: GERONIMODEVTOOLS-283
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283
Project: Geronimo-Devtools
Issue Type: Wish
Components: eclipse-plugin
Reporter: Shiva Kumar H R
Priority: Minor
Fix For: 2.2.0

When a Dynamic Web Project with name say tt is created, a Geronimo
deployment plan geronimo-web.xml will get created with module-id as
default/tt-1.0.car and context-root as /tt.
When this project is re-factored to say tz, the module-id will still be the
same default/tt-1.0.car (note that artifact id is not re-factored from tt
to tz). The context-root also remains the same /tt.
Although this doesn't pose any problem, wouldn't it be better to refactor the
artifact-id context-root to match the project name?

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

[jira] Updated: (GERONIMO-4845) the view is also existed after I delete the server in monitoting portlet


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

Bin He updated GERONIMO-4845:
-

Affects Version/s: (was: 2.2)
   2.1.5

 the view is also existed after I delete the server in monitoting portlet
 

 Key: GERONIMO-4845
 URL: https://issues.apache.org/jira/browse/GERONIMO-4845
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.1.4, 2.1.5
 Environment: jdk6
 window  xp sp2
Reporter: Bin He

 1、create server、view、graph
 2、i delete the server ,and the graphs which belong to the server are all 
 deleted .But the related views are also existed. So i think it's a problem

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

[jira] Closed: (XBEAN-134) If you have a package-info.java in a package, then ClassFinder throws a ClassCastException when calling the findInheritedAnnotatedClasses

2009-09-03 Thread David Blevins (JIRA)


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

David Blevins closed XBEAN-134.
---

Resolution: Fixed
  Assignee: karan singh malhi

$ svn ci 
Sending
xbean-finder/src/main/java/org/apache/xbean/finder/ClassFinder.java
Transmitting file data .
Committed revision 811210.


 If you have a package-info.java in a package, then ClassFinder throws a 
 ClassCastException when calling the findInheritedAnnotatedClasses
 -

 Key: XBEAN-134
 URL: https://issues.apache.org/jira/browse/XBEAN-134
 Project: XBean
  Issue Type: Bug
  Components: finder
Affects Versions: 3.6
Reporter: karan singh malhi
Assignee: karan singh malhi
 Attachments: ClassFinder_Patch.txt


 Running com.abc.xbean.ClassFinderTest
 java.lang.ClassCastException: org.apache.xbean.finder.ClassFinder$PackageInfo 
 cannot be cast to org.apache.xbean.finder.ClassFinder$ClassInfo
   at 
 org.apache.xbean.finder.ClassFinder.findInheritedAnnotatedClasses(ClassFinder.java:264)
   at 
 com.abc.xbean.ClassFinderTest.testFindInheritedAnnotatedClasses(ClassFinderTest.java:67)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
   at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
   at 
 org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
   at 
 org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
   at 
 org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
   at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
   at 
 org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)

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

[jira] Commented: (GERONIMO-4833) javax.resource.ResourseException in too many graphs in one view after disable server