[BUILD] trunk: Failed for Revision: 793279

2009-07-12 Thread gawor
Geronimo Revision: 793279 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 43 minutes 19 seconds
[INFO] Finished at: Sun Jul 12 03:47:37 EDT 2009
[INFO] Final Memory: 432M/972M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/logs-0300-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/logs-0300-jetty/
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/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.781
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/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:17.259) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:37.124) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:41.077) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.559) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:25.507) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:22.705) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:12.771) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:54.412) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:32.486) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:48.132) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.209) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.033) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:35.894) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.939) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.541) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.686) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.953) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.986) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:50.761) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.621) 
[INFO] web-testsuite/test-2.5

Re: Duplicate clustername value sets in config-subsititions file

2009-07-12 Thread Jack Cai
I used to think that server farm is from management point of view
(start/stop, deploy, monitor, etc.), and server cluster is from runtime
point of view (fail-over, load-balancing, etc.). But after a little search,
it seems that many people regard them as the same thing. Some people also
has an interesting distinguishing between them. e.g, [1] classifies clusters
into server farm and server pack. A farm shares the same applications and
services but do not share the same repository of data, while a pack shares
the data too.

-Jack

[1] http://www.certmag.com/read.php?in=1477

On Fri, Jul 10, 2009 at 10:28 AM, Rex Wang rwo...@gmail.com wrote:

 Thanks! So IIUC, farm provide system Load balancing, while Cluster add the
 ability of failover, is that right?:-)

 -Rex

 2009/7/9 Gianny Damour gianny.dam...@optusnet.com.au

 I would say the other way around. A cluster is a type of farm.

 I see a farm as a set of independent instances. I see a cluster as a set
 of collaborating instances. You can deploy a non clustered application to a
 farm whereby you do not have resilience in case of service failure. And you
 can deploy a clustered application to a farm to increase service resiliency
 if necessary.

 Thanks,
 Gianny


 On 09/07/2009, at 12:49 PM, Rex Wang wrote:

  well, Gianny, is a server farm not a type of cluster?

 -Rex

 2009/7/8 Gianny Damour gianny.dam...@optusnet.com.au
 Hi,

 It seems to me that farmName would be better than farmingClusterName as
 there is a clear distinction between a farm and a cluster.

 Thanks,
 Gianny


 On 06/07/2009, at 7:47 PM, chi runhua wrote:

 Hi all,

 I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in
 config-substitions.properties.  My understanding of them is one for WADI
 clustering and another for farming.

 Can we using different keywords to identify them? ie.  farmingClusterName
 and WADIClusterName or sth. like that.


 Jeff  C







[jira] Assigned: (GERONIMO-4739) create a monitoring server when using a JMX protocol in G2.2 and the server status is offline??

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang reassigned GERONIMO-4739:
-

Assignee: Shawn Jiang

 create a monitoring server when using a JMX protocol in G2.2 and the server 
 status is offline??
 ---

 Key: GERONIMO-4739
 URL: https://issues.apache.org/jira/browse/GERONIMO-4739
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: XP sp2
 JRE 1.6
Reporter: liangkun
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.2


 Steps:
 1.start the server.
 2.click the monitoring link.
 3.add a new server
 4.input the server name with local system, input the ip with localhost 
 ,select JMX protocol and input the password with manager
 5.click the save and you will return the home page.
 Problem:
 the new server's status is Offline and can not enable query.

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



[jira] Assigned: (GERONIMO-4733) Unable to starting to configure Apache mod_jk

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang reassigned GERONIMO-4733:
-

Assignee: Shawn Jiang

 Unable to starting to configure Apache mod_jk 
 --

 Key: GERONIMO-4733
 URL: https://issues.apache.org/jira/browse/GERONIMO-4733
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Windows XP SP2, IE6.0
Reporter: Shiny Cheng
Assignee: Shawn Jiang
 Fix For: 2.2


 From Console Navigation, click Apache HTTP and then Get Started. The 
 following exception will appear, which means this function doesn't work 
 correctly.
 java.lang.ClassCastException: 
 [Lorg.apache.geronimo.tomcat.connector.TomcatWebConnector; cannot be cast to 
 [Lorg.apache.geronimo.management.geronimo.WebConnector;
   
 org.apache.geronimo.console.apache.jk.AJPHandler.actionBeforeView(AJPHandler.java:62)
   
 org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:112)
   org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   
 org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
   
 org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
   
 org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:65)
   
 org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125)

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



[jira] Assigned: (GERONIMO-4539) Deployment failed if JPA PU jar in web module

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang reassigned GERONIMO-4539:
-

Assignee: Shawn Jiang

 Deployment failed if JPA PU jar in web module
 -

 Key: GERONIMO-4539
 URL: https://issues.apache.org/jira/browse/GERONIMO-4539
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.1.4, 2.2
Reporter: Forrest Xia
Assignee: Shawn Jiang
 Attachments: my-ear-1.0-SNAPSHOT_PUjarinwebclasses_ejbjarinweblib.ear


 If putting JPA persistence unit jar and JPA entity bean jar in web module 
 WEB-INF/lib, then to deploy it as part of ear, a deployment exception as 
 follows:
 At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 org.apache.geronimo.common.DeploymentException: At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 at 
 org.apache.geronimo.persistence.builder.PersistenceUnitRefBuilder.buildNaming(PersistenceUnitRefBuilder.java:154)
 at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53)
 at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:842)
 at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:347)
 at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
 at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
 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:124)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
 at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
 at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
 at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
 at java.lang.Thread.run(Thread.java:735)

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



Quarterly Board Report

2009-07-12 Thread Kevan Miller
Many thanks to Jay McHugh for generating this Quarter's Board report  
-- http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2009-07+-+July 
 I've made some editorial updates. Any updates need to be in by  
Monday morning.


--kevan


[jira] Commented: (GERONIMO-4739) create a monitoring server when using a JMX protocol in G2.2 and the server status is offline??

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang commented on GERONIMO-4739:
---

You might want to install agent-car-jmx plugin before enable JMX protocol 
monitoring server.  

 create a monitoring server when using a JMX protocol in G2.2 and the server 
 status is offline??
 ---

 Key: GERONIMO-4739
 URL: https://issues.apache.org/jira/browse/GERONIMO-4739
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: XP sp2
 JRE 1.6
Reporter: liangkun
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.2


 Steps:
 1.start the server.
 2.click the monitoring link.
 3.add a new server
 4.input the server name with local system, input the ip with localhost 
 ,select JMX protocol and input the password with manager
 5.click the save and you will return the home page.
 Problem:
 the new server's status is Offline and can not enable query.

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



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

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang reassigned GERONIMO-4647:
--

Assignee: Rex Wang

 welcome files with servlet url-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
 Attachments: 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] Updated: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4217:
---

Attachment: GERONIMO-4217-trunk.patch

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



Re: Quarterly Board Report

2009-07-12 Thread Kevan Miller


On Jul 12, 2009, at 11:19 PM, Kevan Miller wrote:

Many thanks to Jay McHugh for generating this Quarter's Board report  
-- http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2009-07+-+July 
 I've made some editorial updates. Any updates need to be in by  
Monday morning.


Oops. That should have said Many thanks to Jay McHugh and David  
Jencks.


--kevan


[jira] Resolved: (GERONIMO-4539) Deployment failed if JPA PU jar in web module

2009-07-12 Thread Ivan (JIRA)

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

Ivan resolved GERONIMO-4539.


   Resolution: Fixed
Fix Version/s: 2.2
   2.1.5

Commit changes to 2.1 At revision: 793447, trunk At revision: 793448. Thanks 
for the patch, Shawn Jiang.

 Deployment failed if JPA PU jar in web module
 -

 Key: GERONIMO-4539
 URL: https://issues.apache.org/jira/browse/GERONIMO-4539
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.1.4, 2.2
Reporter: Forrest Xia
Assignee: Shawn Jiang
 Fix For: 2.1.5, 2.2

 Attachments: G4539_g21.patch, G4539_trunk.patch, 
 my-ear-1.0-SNAPSHOT_PUjarinwebclasses_ejbjarinweblib.ear


 If putting JPA persistence unit jar and JPA entity bean jar in web module 
 WEB-INF/lib, then to deploy it as part of ear, a deployment exception as 
 follows:
 At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 org.apache.geronimo.common.DeploymentException: At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 at 
 org.apache.geronimo.persistence.builder.PersistenceUnitRefBuilder.buildNaming(PersistenceUnitRefBuilder.java:154)
 at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53)
 at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:842)
 at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:347)
 at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
 at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
 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:124)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
 at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
 at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
 at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
 at java.lang.Thread.run(Thread.java:735)

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



[jira] Updated: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4217:
---

Fix Version/s: 2.2
   2.1.5

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Fix For: 2.1.5, 2.2

 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Commented: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang commented on GERONIMO-4217:


Can anyone help review this?
-Rex

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Fix For: 2.1.5, 2.2

 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Updated: (GERONIMO-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4732:
---


I think it should check whether or not there is any existing graphs related to 
the server before deleting it.
-Rex

 click monitoring and delete the server localhost and there is an Error 
 rendering portlet.
 -

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
 JRE 1.6
Reporter: liangkun
Assignee: viola.lu
 Fix For: 2.2


 steps:
 1.click the porlet and add a server localhost.
 2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
 3.view the graphs and they run well.
 4 Delete the server and there is an error:rendering portlet.
 Error rendering portlet.
 java.lang.NullPointerException
   at 
 jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
   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.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
   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 
 

Re: The scope and schedule for G 2.2 samples release

2009-07-12 Thread Forrest_Xia

Let me try to sort out what we will do next:
1. Add one sample which uses popular application framework, such as struts,
spring.
2. Update and release a new version of daytrader with G 2.2 sample release
3. Add or update a sample to configure EJB security via annotation
4. Add or update a sample to demo JTA
5. Add a new sample to demo the support of using tomcat server.xml directly
6. Add a sample to demo how to build a CSA via car-maven-plugin, ActiveMQ
server could be the sample.
7. Figure out a way to release JEE application ear/war balls of G samples.
8. Ensure G 2.1.2 samples plugins installable and functionable on G 2.2
server.

I am going to work on this list and open a JIRA to track it, and will post
my progress to this thread from time to time. Welcome any comments!

Regards, Forrest
-- 
View this message in context: 
http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24455766.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.



[jira] Created: (GERONIMO-4741) Make a new samples release with G 2.2 server

2009-07-12 Thread Forrest Xia (JIRA)
Make a new samples release with G 2.2 server


 Key: GERONIMO-4741
 URL: https://issues.apache.org/jira/browse/GERONIMO-4741
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: sample apps
Affects Versions: 2.2
Reporter: Forrest Xia
Assignee: Forrest Xia


To do list:
1. Add one sample which uses popular application framework, such as struts, 
spring.
2. Update and release a new version of daytrader with G 2.2 sample release
3. Add or update a sample to configure EJB security via annotation
4. Add or update a sample to demo JTA
5. Add a new sample to demo the support of using tomcat server.xml directly
6. Add a sample to demo how to build a CSA via car-maven-plugin, ActiveMQ 
server could be the sample.
7. Figure out a way to release JEE application ear/war balls of G samples.
8. Ensure G 2.1.2 samples plugins installable and functionable on G 2.2 server. 

Check forum thread 
http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-td24177645s134.html#a24455766
 for details.

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

2009-07-12 Thread gawor
Geronimo Revision: 793437 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 39 minutes 13 seconds
[INFO] Finished at: Sun Jul 12 21:43:51 EDT 2009
[INFO] Final Memory: 466M/941M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/logs-2100-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090712/logs-2100-jetty/
 
 
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.612
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/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:02.661) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:33.533) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:36.178) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.816) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:18.565) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:20.247) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:06.822) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:51.794) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:58.471) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.160) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.952) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.998) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:38.198) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.072) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.660) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.682) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.030) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:52.621) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:46.566) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.547) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:34.003) 
[INFO] web

[jira] Updated: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4217:
---

Attachment: (was: Geronimo-4729-trunk.patch)

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Updated: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4217:
---

Attachment: Geronimo-4729-trunk.patch

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Attachments: GERONIMO-4217-b21.patch, Geronimo-4729-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Updated: (GERONIMO-4539) Deployment failed if JPA PU jar in web module

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4539:
--

Attachment: G4539_g21.patch
G4539_trunk.patch

This patch will narrow the PU ref search scope in WAR if the PU is defined in 
WAR.

 Deployment failed if JPA PU jar in web module
 -

 Key: GERONIMO-4539
 URL: https://issues.apache.org/jira/browse/GERONIMO-4539
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 2.1.4, 2.2
Reporter: Forrest Xia
Assignee: Shawn Jiang
 Attachments: G4539_g21.patch, G4539_trunk.patch, 
 my-ear-1.0-SNAPSHOT_PUjarinwebclasses_ejbjarinweblib.ear


 If putting JPA persistence unit jar and JPA entity bean jar in web module 
 WEB-INF/lib, then to deploy it as part of ear, a deployment exception as 
 follows:
 At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 org.apache.geronimo.common.DeploymentException: At least one deployment 
 problem:org.apache.geronimo.common.DeploymentException: Could not resolve 
 reference at deploy time for query 
 com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear?J2EEApplication=com.heilgeist.testcase.geronimo.jarfile/my-ear/1.0-SNAPSHOT/ear,PersistenceUnitModule=WEB-INF/lib/my-pu-1.0-SNAPSHOT_inclasses.jar,WebModule=my-war-1.0-SNAPSHOT.war,j2eeType=PersistenceUnit,name=myPU#.
  No GBean references found.
 at 
 org.apache.geronimo.persistence.builder.PersistenceUnitRefBuilder.buildNaming(PersistenceUnitRefBuilder.java:154)
 at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:53)
 at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:842)
 at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:347)
 at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)
 at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
 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:124)
 at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
 at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
 at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
 at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
 at java.lang.Thread.run(Thread.java:735)

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



[jira] Updated: (GERONIMO-4733) Unable to starting to configure Apache mod_jk

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4733:
--

Attachment: G4733_trunk.patch
G4733_21.patch

Uploading the patches to fix this JIRA.

 Unable to starting to configure Apache mod_jk 
 --

 Key: GERONIMO-4733
 URL: https://issues.apache.org/jira/browse/GERONIMO-4733
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Windows XP SP2, IE6.0
Reporter: Shiny Cheng
Assignee: Shawn Jiang
 Fix For: 2.2

 Attachments: G4733_21.patch, G4733_trunk.patch


 From Console Navigation, click Apache HTTP and then Get Started. The 
 following exception will appear, which means this function doesn't work 
 correctly.
 java.lang.ClassCastException: 
 [Lorg.apache.geronimo.tomcat.connector.TomcatWebConnector; cannot be cast to 
 [Lorg.apache.geronimo.management.geronimo.WebConnector;
   
 org.apache.geronimo.console.apache.jk.AJPHandler.actionBeforeView(AJPHandler.java:62)
   
 org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:112)
   org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   
 org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
   
 org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
   
 org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:65)
   
 org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125)

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



[jira] Resolved: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Ivan (JIRA)

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

Ivan resolved GERONIMO-4217.


Resolution: Fixed

Commit changes to trunk At revision: 793450, 2.1.5 At revision: 793453.
Thanks for the patch, Rex !

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Fix For: 2.1.5, 2.2

 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Commented: (GERONIMO-4733) Unable to starting to configure Apache mod_jk

2009-07-12 Thread Shawn Jiang (JIRA)

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

Shawn Jiang commented on GERONIMO-4733:
---

This did not happen before because if there's a valid ajp connector GBean.  The 
error code(AJPHandler.java:62) did not get executed at all. In the latest 
tomcat trunk build.  There's not ajp connector GBean by default.  which results 
in this JIRA.

You can also recreate this on 2.1 branch by deleting AJP connector before 
access Apache HTTP---Get Started.


About the patch:

1, TomcatWebConnector inherits NetworkConnector but not WebConnector.   We 
should use NetworkConnector since there's only NetworkConnector method 
getPort()  needed here.

2, Somehow, the webmanager.getConnectors() might return a connector array that 
only contains null elements.  So we need to check null for connectors[0].

3, After fixing the problems above, there will be another EL parsing error.  
Can't find property configId in 
org.apache.geronimo.console.apache.jk.BaseApacheHandler.WebAppData.   
Actually, there's only parentConfigId in 
org.apache.geronimo.console.apache.jk.BaseApacheHandler.WebAppData but not 
configId.I just correct configId to parentconfigId to resolve this.







 Unable to starting to configure Apache mod_jk 
 --

 Key: GERONIMO-4733
 URL: https://issues.apache.org/jira/browse/GERONIMO-4733
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
 Environment: Windows XP SP2, IE6.0
Reporter: Shiny Cheng
Assignee: Shawn Jiang
 Fix For: 2.2

 Attachments: G4733_21.patch, G4733_trunk.patch


 From Console Navigation, click Apache HTTP and then Get Started. The 
 following exception will appear, which means this function doesn't work 
 correctly.
 java.lang.ClassCastException: 
 [Lorg.apache.geronimo.tomcat.connector.TomcatWebConnector; cannot be cast to 
 [Lorg.apache.geronimo.management.geronimo.WebConnector;
   
 org.apache.geronimo.console.apache.jk.AJPHandler.actionBeforeView(AJPHandler.java:62)
   
 org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:112)
   org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   
 org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
   
 org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
   
 org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:65)
   
 org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125)

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



[jira] Commented: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang commented on GERONIMO-4217:


Thanks! Ivan:-)

 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Fix For: 2.1.5, 2.2

 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



[jira] Closed: (GERONIMO-4217) Check for all data primitive types when shortcutting to the primordial classloader

2009-07-12 Thread Rex Wang (JIRA)

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

Rex Wang closed GERONIMO-4217.
--


 Check for all data primitive types when shortcutting to the primordial 
 classloader
 --

 Key: GERONIMO-4217
 URL: https://issues.apache.org/jira/browse/GERONIMO-4217
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: kernel
Affects Versions: 2.1.2, 2.2
Reporter: Kevan Miller
Assignee: Rex Wang
 Fix For: 2.1.5, 2.2

 Attachments: GERONIMO-4217-b21.patch, GERONIMO-4217-trunk.patch


 Make sure that MultiParentClassLoader checks for all data primitive types 
 when deciding if the primordial ClassLoader should be invoked

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



Re: The scope and schedule for G 2.2 samples release

2009-07-12 Thread Rex Wang
Great! FYI, I can provide you a JTA sample coz I have ever implemented one
for a ppt demo.

-Rex

2009/7/13 Forrest_Xia forres...@gmail.com


 Let me try to sort out what we will do next:
 1. Add one sample which uses popular application framework, such as struts,
 spring.
 2. Update and release a new version of daytrader with G 2.2 sample release
 3. Add or update a sample to configure EJB security via annotation
 4. Add or update a sample to demo JTA
 5. Add a new sample to demo the support of using tomcat server.xml directly
 6. Add a sample to demo how to build a CSA via car-maven-plugin, ActiveMQ
 server could be the sample.
 7. Figure out a way to release JEE application ear/war balls of G samples.
 8. Ensure G 2.1.2 samples plugins installable and functionable on G 2.2
 server.

 I am going to work on this list and open a JIRA to track it, and will post
 my progress to this thread from time to time. Welcome any comments!

 Regards, Forrest
 --
 View this message in context:
 http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24455766.html
 Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.




Re: Possible for G to directly consume a Tomcat server config w/o changes?

2009-07-12 Thread Ivan
2009/6/23 David Jencks david_jen...@yahoo.com


 On Jun 22, 2009, at 9:27 PM, Ivan wrote:

 After checking the current changes to the realm, in the past, we will set
 the geronimo-admin for the Engine, which means that all the web-apps belong
 to the Engine will use the realm setting from its parent if no setting is
 set for those web-apps. Currently, the realm for the Engine is remained for
 Tomcat's default setting, which uses users.xml.
 So far, I did not see any effect to our existing console applications, I am
 not sure whether we need to recover it. IMO, keep the current way is better.
 Any comment ?


 Unless I've forgotten something only the jacc realms that are specifically
 configured for a particular application hook into the geronimo security
 system.  So I don't expect anyone to use any other realms, and what the
 default realm is doesn't make a lot of difference.

 thanks
 david jencks

 Ivan

 2009/6/22 Ivan xhh...@gmail.com



 2009/6/22 David Jencks david_jen...@yahoo.com


 On Jun 21, 2009, at 10:20 PM, Ivan wrote:



 2009/6/22 David Jencks david_jen...@yahoo.com


 On Jun 19, 2009, at 9:18 PM, Ivan wrote:

 Currently, what I can see are
 1. Recover those configurations that we used  for Tomcat in the
 server.xml


 For connectors, I may have done most of this in my work for (3)
 could use some checking.  I'd also like to see if I can make the tomcat
 connectors use our thread pool -- a new feature I've wanted for years :-)

 2. Update the console codes, and decide whether we need to keep the
 functions like add/remove connectors. If keep, the way we do it is to
 add/remove ConnectorGBean or to marshall/remarshall server.xml.

 Hi, David, do you still work on this ?




 3. Make those settings in the server.xml not hardcoded.


 I implemented this here, not sure if I'll get it committed today or
 tomorrow


 I committed this in rev 787153.  I exposed the replacement code the local
 attribute manager uses.  I'm thinking of modifying the activemq integration
 to use this method instead of spring property substitution.


Native support from Geronimo for the subsitution is better, for
 ActiveMQ integration, IIRC, maybe a bit extra work needs, for i add some
 extra properties to the property configuration, which are not contained in
 the config-substitution.



 4. Recover those GBeans that console/other components used, such as
 AccessLogValve etc.


 Maybe the AccessLogValve can fish its valve out of the server like the
 engine gbean now does?


I will try to do it, Valve is a bit different with the Engine, for it
 has no name attribute, and Engine/Host all could hold to a list of them.
My way is to use the seq to identify it, like what it is done by its
 object name.


 Looking forward to seeing this!


DONE with At revision: 787174.
BTW, I guess that we also need to look at the realm setting for Tomcat.



 thanks
 david jencks


 thanks
 david jencks


 I would like to work at parts of them, if we have decided to import this
 feature in 2.2. And I suggest that we open a JIRA for each of them, so that
 we could track them clearly.
 Thanks !
 Ivan

 2009/6/20 David Jencks david_jen...@yahoo.com

 After fixing the HostGBean in web app plan problem I don't have a very
 clear idea of what's missing here.  If one of you do could you please list
 in detail what needs to be done?
 thanks
 david jencks

 On Jun 19, 2009, at 8:51 AM, Ivan wrote:

 It is easy to add the SSL connector, the things that Jack concens is
 that, how do the changes affect other components, I think.
 Ivan

 2009/6/19 Kevan Miller kevan.mil...@gmail.com


 On Jun 19, 2009, at 2:31 AM, Jack Cai wrote:

  Looks like this is going be a piece of non-trivial work. Considering
 that we are going for a 2.2 release, should we re-evaluate whether this
 feature should be in 2.2? My gut feeling is no. We should really 
 stablize
 the code and resovle TCK issues.


 If it's *hard* to add the SSL connector configuration, then something
 is clearly wrong. Personally, I'd be pretty interested in seeing this 
 type
 of support in 2.2. The more Tomcat apps/configurations that just run on
 Geronimo, the better off we are...

 --kevan




 --
 Ivan





 --
 Ivan





 --
 Ivan





 --
 Ivan




 --
 Ivan





-- 
Ivan