[jira] Commented: (GERONIMO-4632) Enable Geronimo to support IPv6 addresses
[ https://issues.apache.org/jira/browse/GERONIMO-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12727936#action_12727936 ] Shawn Jiang commented on GERONIMO-4632: --- A related JIRA. https://issues.apache.org/jira/browse/GERONIMO-2567 A related FAQ item: http://cwiki.apache.org/confluence/display/GMOxKB/Remote+admin+using+deployer.jar+fails+to+connect+when+IPv6+is+used Enable Geronimo to support IPv6 addresses - Key: GERONIMO-4632 URL: https://issues.apache.org/jira/browse/GERONIMO-4632 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Wish List Affects Versions: 2.1.5, 2.2 Reporter: Forrest Xia Assignee: Shawn Jiang Currently, geronimo only accepts IPv4 addresses to function. For IPv6 addresses, such as ::, ::1, Geronimo does not provide support. Can we enable this in geronimo 2.2 release or certain future release? Thanks! I opened a discussion session in the mailing list, please check http://www.nabble.com/Does-geronimo-support-IPv6--td22801389s134.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Certify Geronimo with Harmony!
I got a few positive responses from people in the jcp-open list on this topic [1] - certify Geronimo with Harmony as a JEE server. Sounds cool, doesn't it? Obviously there are already known problems mostly in the Harmony side, like the -javaagent option support, CXF issue, etc. Do we have enough people interested in this work (again)? There need some Harmony committers to sign a NDA as Kevan suggested and work directly with the JEE TCK. Hopefully the Geronimo community can offer some help to get the Harmoniers started. -Jack [1] http://markmail.org/message/ovx6zlrevy4bh57m?q=%22Certify+Geronimo+with+Harmony%22page=1refer=3xmwwbgvaacxrd2i
Web app clustering with WADI in Geronimo Tomcat 2.1.4 broken?
I am trying to deploy a clustered web application in Geronimo Tomcat 2.1.4. I have added distributable/ in web.xml and clustering-wadi/ in geronimo-web.xml. When I deploy the application, I am getting the following deployment error: xml problem for web app . org.apache.geronimo.common.DeploymentException: xml problem for web app . at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:318) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:207) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:179) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:94) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:307) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:227) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.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:595) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.2.4a: Expected elements 'work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http://geronimo.apache.org/xml/ns/deployment-1.2 persiste...@http://java.sun.com/xml/ns/persistence' instead of 'clustering-w...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: xml-fragment xmlns:tom=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1; !--web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1; xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0-- dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:moduleId dep:groupIdpackt-samples/dep:groupId dep:artifactIdhelloworld-cluster/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ /dep:environment tom:context-root/helloworld-cluster/tom:context-root tom:clustering-wadi/ /xml-fragment at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD(XmlBeansUtil.java:187) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:312) ... 17 more Appears like the deployer is not liking the tag clustering-wadi/. I do have org.apache.geronimo.configs/tomcat6-clustering-wadi/2.1.4/car and org.apache.geronimo.configs/tomcat6-clustering-builder-wadi/2.1.4/car configurations started before deploying the web application. I tried deploying the same application in Geronimo Tomcat 2.2-SNAPSHOT server and got the same error. Is the WADI clustering broken in Geronimo Tomcat 2.1.4 and 2.2-SNAPSHOT? The application deploys and runs as expected in Geronimo Jetty 2.1.4.
Re: problem with Bound on all IP address
Seeing this mail by chance. Actually, this is a Defect and had been fixed in
latest geronimo 2.1.4 release.
See: https://issues.apache.org/jira/browse/GERONIMO-4442
marco75 wrote:
I'am using geronimo 2.1.2. I have modified the
/config/config-substitutions.properties and changed all the localhost
with a specific IP address. After i have modified the config.xml and add
the host properties in this section:
module name=org.apache.geronimo.framework/rmi-naming/2.1.2/car
gbean name=RMIRegistry
attribute name=host${ServerHostname}/attribute
attribute name=port${NamingPort + PortOffset}/attribute
/gbean
after that when i start the istance i get the following message:
Starting Geronimo Application Server v2.1.2
[] 100% 19s Startup complete
Listening on Ports:
0 1.5.36.37 Derby Connector
1050 1.5.36.37 CORBA Naming Service
1099 1.5.36.37 RMI Naming
2001 1.5.36.37 OpenEJB ORB Adapter
4201 1.5.36.37 OpenEJB Daemon
6882 1.5.36.37 OpenEJB ORB Adapter
8009 1.5.36.37 Tomcat Connector AJP AJP
8080 1.5.36.37 Tomcat Connector HTTP BIO HTTP
8443 1.5.36.37 Tomcat Connector HTTPS BIO HTTPS
1.5.36.37 JMX Remoting Connector
61613 1.5.36.37 ActiveMQ Transport Connector
61616 1.5.36.37 ActiveMQ Transport Connector
it's all ok? No because if i use the lsof command (i'am on linux system) i
found that this java process bound all IP address for some ports:
java9590 root5u IPv6 87466915 TCP *:1099 (LISTEN)
java9590 root8u IPv6 87466917 TCP *: (LISTEN)
java9590 root 17u IPv6 87466936 TCP
lxi18l.intra.infocamere.it:1527 (LISTEN)
java9590 root 53u IPv6 87467168 TCP
lxi18l.intra.infocamere.it:61616 (LISTEN)
java9590 root 54u IPv6 87467170 TCP
lxi18l.intra.infocamere.it:61613 (LISTEN)
java9590 root 55u IPv6 87467172 TCP
lxi18l.intra.infocamere.it:4201 (LISTEN)
java9590 root 56u IPv6 87467175 TCP *:1050 (LISTEN)
java9590 root 57u IPv6 87467179 TCP *:24842
(LISTEN)
java9590 root 58u IPv6 87467183 TCP *:2001 (LISTEN)
java9590 root 59u IPv6 87467186 TCP *:6882 (LISTEN)
java9590 root 62u IPv6 87467189 TCP
lxi18l.intra.infocamere.it:webcache (LISTEN)
java9590 root 63u IPv6 87467191 TCP
lxi18l.intra.infocamere.it:8009 (LISTEN)
java9590 root 64u IPv6 87467193 TCP
lxi18l.intra.infocamere.it:8443 (LISTEN)
lxi18l.intra.infocamere.it=1.5.36.37
what's the problem?
thank you
Marco
-
-Shawn
--
View this message in context:
http://www.nabble.com/problem-with-Bound-on-all-IP-address-tp19683535s134p24368274.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Trunk Builds
Sorry, Are we using the same trunk build ? I downloaded the tomcat trunk
build here:
*
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090703/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
*
When accessing http://localhost:8080/*dojo/dojo/*dojo.js , I got it's
content:
/*
Copyright (c) 2004-2008, The Dojo Foundation All Rights Reserved.
Available via Academic Free License = 2.1 OR the modified BSD license.
see: http://dojotoolkit.org/license for details
*/
(function(){var _1=null;if((_1||(typeof
djConfig!=undefineddjConfig.scopeMap))(typeo
When accessing http://localhost:8080/*dojo/dojo/dojo*/dojo.js, I got this:
HTTP Status 404
I also tried to revert ConfirmMessageTag.java to dojo/dojo/dojo.js from
dojo/dojo/dojo/dojo.js. The dialog poped up and the test suite passed.
So , can anyone else help verify this ?
On Tue, Jul 7, 2009 at 1:09 AM, Jarek Gawor jga...@gmail.com wrote:
Shawn,
I recently modified ConfirmMessageTag.java so that it points to the
right locations for dojo resources. It used to point to
http://localhost:8080/dojo/dojo/dojo.js (which does not work) but now
points to http://localhost:8080/dojo/dojo/dojo/dojo.js (which does
work). That made the confirmation box to display again. The
confirmation box does display now when you use the web browser and
follow the steps of the test but somehow it fails in our automatic
tests. The test does pass for me when I execute it on my machine in
the same way as the automatic tests do... so that's why I thought it
was a timing issue. But there might be something else going on, I'm
not sure.
Jarek
On Fri, Jul 3, 2009 at 10:53 AM, Shawn Jianggenspr...@gmail.com wrote:
On Fri, Jul 3, 2009 at 2:53 AM, Jarek Gawor jga...@gmail.com wrote:
Shawn,
The one failure in console/advanced on Tomcat is caused by fixing that
prompting issue in the console. I'm hoping it's just a timing issue
It's not a timing issue. This is caused by a modification on
ConfirmMessageTag.java recently .
After that change, dojo.js can't be found so that the prompting dialog
can't be display anymore.
Revert the bvt change and update the code
private static final String DOJO_BASE = /dojo/dojo
to
private static final String DOJO_BASE = /dojo
can fix this.
since its takes a bit of time to load all the Dojo stuff for the first
time. So I just increased the wait time for the window to show up in
that test.
Jarek
On Wed, Jul 1, 2009 at 9:31 PM, Shawn Jianggenspr...@gmail.com wrote:
I can't recreate the same console/advanced failure in my local
machine.
But I do find another console testsuite bug and filed a JIRA:
https://issues.apache.org/jira/browse/GERONIMO-4720 (patch
provided)
The failure of enterprise-testsuite/sec-tests is related to
run-as propagation from a servlet to another servlet. I'm looking
into
it and will provide a patch.
On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor jga...@gmail.com
wrote:
Based on running the testsuite yesterday and with fixes committed
last
night I *think* we should be passing all tests on Tomcat and fail
enterprise-testsuite/sec-tests and webservices-testsuite/jaxws-tests
on Jetty. The webservices-testsuite/jaxws-tests fails because of
GERONIMO-4645. Not sure what's going on with
enterprise-testsuite/sec-tests.
Jarek
On Thu, Jun 25, 2009 at 11:00 AM, Kevan Miller
kevan.mil...@gmail.com
wrote:
A search of emails shows that our last successful automated build
of
trunk
was on May 26th. I know that there have been increasing frustration
with
these recent build issues. We seem to be closing in on getting
these
issues
resolved. I built last night. I built successfully, last night, but
had
7
testsuite failures -- 3 jetty, 4 tomcat.
I think it would do us a lot of good to have a concerted effort to
get
these
final issues resolved. Here are the test failures that I'm seeing:
3 common errors:
[INFO] The following tests failed:
[INFO] * console-testsuite/advanced -
/Users/kevan/geronimo/server/trunk/testsuite/console-testsuite/advanced/build.log
[INFO] * enterprise-testsuite/sec-tests -
/Users/kevan/geronimo/server/trunk/testsuite/enterprise-testsuite/sec-tests/build.log
[INFO] * webservices-testsuite/jaxws-tests -
/Users/kevan/geronimo/server/trunk/testsuite/webservices-testsuite/jaxws-tests/build.log
1 Tomcat unique failure:
[INFO] * web-testsuite/test-tomcat -
/Users/kevan/geronimo/server/trunk/testsuite/web-testsuite/test-tomcat/build.log
Is this consistent with what others are seeing?
--kevan
--
Shawn
--
Shawn
--
Shawn
[BUILD] trunk: Failed for Revision: 791712
Geronimo Revision: 791712 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 44 minutes 11 seconds
[INFO] Finished at: Tue Jul 07 03:48:24 EDT 2009
[INFO] Final Memory: 434M/1013M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-0300-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/trunk/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/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.609
[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.427)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:34.644)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.440)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.746)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:36.718)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:03:58.451) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:08.150)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:55.210)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:55.971)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:46.614)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.724)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:36.020)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.672)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:13.884)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.491)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:55.294)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.046)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:54.732)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.625)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.790)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.437)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
[jira] Created: (GERONIMO-4728) Can't access EJB Server portlet with IPV6 address.
Can't access EJB Server portlet with IPV6 address. -- Key: GERONIMO-4728 URL: https://issues.apache.org/jira/browse/GERONIMO-4728 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Environment: tomcat geronimo server 2.2_2009-07-03 + windows XP Reporter: Shawn Jiang Priority: Minor 1, enable ipv6 in windows 2, start server 3, ipconfig to find ipv6 address of host server. My ip is: 2002:97b:e933::97b:e933 4, use http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server to access EJB Server. Result: EJB server portlet can't be displayed. Swith to http://localhost:8080/console/portal/Server/EJB%20Server , the portlet is working well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4728) Can't access EJB Server portlet with IPV6 address.
[
https://issues.apache.org/jira/browse/GERONIMO-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4728:
--
Description:
1, enable ipv6 in windows
2, start server
3, ipconfig to find ipv6 address of host server. My ip is:
2002:97b:e933::97b:e933
4, use
{noformat}http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server
{noformat} to access EJB Server.
Result: EJB server portlet can't be displayed.
After swicthing to http://localhost:8080/console/portal/Server/EJB%20Server ,
the portlet is working well.
was:
1, enable ipv6 in windows
2, start server
3, ipconfig to find ipv6 address of host server. My ip is:
2002:97b:e933::97b:e933
4, use http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server
to access EJB Server.
Result: EJB server portlet can't be displayed.
Swith to http://localhost:8080/console/portal/Server/EJB%20Server , the portlet
is working well.
Environment: tomcat geronimo server 2.2_2009-07-03 + windows XP + firefox
3.5 (was: tomcat geronimo server 2.2_2009-07-03 + windows XP)
Can't access EJB Server portlet with IPV6 address.
--
Key: GERONIMO-4728
URL: https://issues.apache.org/jira/browse/GERONIMO-4728
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2
Environment: tomcat geronimo server 2.2_2009-07-03 + windows XP +
firefox 3.5
Reporter: Shawn Jiang
Priority: Minor
1, enable ipv6 in windows
2, start server
3, ipconfig to find ipv6 address of host server. My ip is:
2002:97b:e933::97b:e933
4, use
{noformat}http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server
{noformat} to access EJB Server.
Result: EJB server portlet can't be displayed.
After swicthing to http://localhost:8080/console/portal/Server/EJB%20Server ,
the portlet is working well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4632) Enable Geronimo to support IPv6 addresses
[ https://issues.apache.org/jira/browse/GERONIMO-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728011#action_12728011 ] Shawn Jiang commented on GERONIMO-4632: --- Need to monitor IPV6 defects in components that Geronimo are using. Key Summary GERONIMO-1078 org.openejb.client.ServerMetadata does not handle IPv6 addresses DERBY-526 Network Client URL cannot take the IP Address as host name for IPV6 machines DERBY-283 On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . AXIS-2710 ipv6 address in endpoint url AXIS-2784 Having a host name as an ipv6 address (ex : [2001::2002] on which a web service is running) causes problems in Axis DERBY-4082 Cannot shutdown Network Server on IPv6 machine 'host: loopback6.xxx.xxx.xxx.com is not local to the server' GERONIMO-4632 Enable Geronimo to support IPv6 addresses NET-61 [net] FTPClient.listFiles() hangs on Red Hat Linux http://activemq.apache.org/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.html Multicast - Watch out for IPV6 vs IPV4 support on your operating system or distribution or network Enable Geronimo to support IPv6 addresses - Key: GERONIMO-4632 URL: https://issues.apache.org/jira/browse/GERONIMO-4632 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Wish List Affects Versions: 2.1.5, 2.2 Reporter: Forrest Xia Assignee: Shawn Jiang Currently, geronimo only accepts IPv4 addresses to function. For IPv6 addresses, such as ::, ::1, Geronimo does not provide support. Can we enable this in geronimo 2.2 release or certain future release? Thanks! I opened a discussion session in the mailing list, please check http://www.nabble.com/Does-geronimo-support-IPv6--td22801389s134.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Web app clustering with WADI in Geronimo Tomcat 2.1.4 broken?
Hi Vamsi, In the case of tomcat, you need to use the node tomcat-clustering-wadi / instead of clustering-wadi / I wonder if it would not be better to uniformise node names across Jetty and Tomcat to prevent confusion. Thanks, Gianny On 07/07/2009, at 4:57 PM, Vamsavardhana Reddy wrote: I am trying to deploy a clustered web application in Geronimo Tomcat 2.1.4. I have added distributable/ in web.xml and clustering-wadi/ in geronimo-web.xml. When I deploy the application, I am getting the following deployment error: xml problem for web app . org.apache.geronimo.common.DeploymentException: xml problem for web app . at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWeb App(TomcatModuleBuilder.java:318) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule (TomcatModuleBuilder.java:207) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createMo dule(AbstractWebModuleBuilder.java:179) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModul e(SwitchingModuleBuilder.java:94) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan (EARConfigBuilder.java:307) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:227) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.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.doDe ploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run (DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.2.4a: Expected elements 'work-...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http:// geronimo.apache.org/xml/ns/j2ee/application-2.0 web- contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 abstract-naming-en...@http:// geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http:// geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http:// geronimo.apache.org/xml/ns/naming-1.2 service-...@http:// geronimo.apache.org/xml/ns/naming-1.2 resource-...@http:// geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http:// geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http:// geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http:// geronimo.apache.org/xml/ns/deployment-1.2 persiste...@http:// java.sun.com/xml/ns/persistence' instead of 'clustering-w...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: xml-fragment xmlns:tom=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 !--web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/ application-2.0-- dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/ deployment-1.2 dep:moduleId dep:groupIdpackt-samples/dep:groupId dep:artifactIdhelloworld-cluster/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ /dep:environment tom:context-root/helloworld-cluster/tom:context-root tom:clustering-wadi/ /xml-fragment at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD (XmlBeansUtil.java:187) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWeb App(TomcatModuleBuilder.java:312) ... 17 more Appears like the deployer is not liking the tag clustering-wadi/. I do have org.apache.geronimo.configs/tomcat6-clustering-wadi/ 2.1.4/car and org.apache.geronimo.configs/tomcat6-clustering- builder-wadi/2.1.4/car configurations started before deploying the web application. I tried deploying the same application in Geronimo Tomcat
Re: Setup a Geonimo FAQ ?
So... go to town... or am I missing something? --jason On Jul 7, 2009, at 12:42 PM, Shawn Jiang wrote: OK, I also noticed that Knowledge Base page can be found as FAQ in geronimo homepage. FAQ Browse SpaceAdd Page View Edit Attachments (0) Info Added by Jason Dillon, last edited by Jason Dillon on Jun 22, 2006 (view change) Labels: (None) EDIT --- Seems it has not been updated from 2006. We need to 1, Remove some stale content. 2, Add some new FAQ there. Hope that can reduce FAQ questions in mailing list. On Tue, Jul 7, 2009 at 1:08 PM, Jason Dillon ja...@planet57.com wrote: The Knowledge Base was intended to be the home for FAQ-ish thingys. --jason On Jul 7, 2009, at 12:04 PM, Shawn Jiang wrote: Obviously, there are really some FAQ in the mailing list such as 1, Lib conflict including myface, spring 2, Log4j 3, JPA JTA/Non-JTA DS requirement. 4, web-service out of memory 5, Classloading problem caused by bad EAR package structure. .. We need a formal page to record these FAQ. (only found two related page [1] and [2] with google). [1]http://docs.huihoo.com/apache/geronimo/1.1/geronimo-eclipse-plugin-faq.html [2]http://cwiki.apache.org/GMOxKB/index.html -- Shawn -- Shawn
[BUILD] trunk: Failed for Revision: 791807
Geronimo Revision: 791807 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 58 seconds
[INFO] Finished at: Tue Jul 07 09:45:29 EDT 2009
[INFO] Final Memory: 403M/1013M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-0900-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/trunk/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/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:46.939
[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.058)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.369)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.417)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.983)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:40.176)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:03:46.151) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:01.566)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:55.472)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:04.168)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.444)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.402)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:37.393)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.981)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:13.481)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.264)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:52.007)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.090)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:55.199)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.752)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.412)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.990)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
Re: Trunk Builds
Shawn,
Looks like my copy of dojo-release-1.1.1-mini.zip was outdated and
files were wrapped in an extra dojo directory. Once I updated it the
extra dojo directory disappeared. I updated the DOJO_BASE in
ConfirmMessageTag.java.
Thanks,
Jarek
On Tue, Jul 7, 2009 at 3:38 AM, Shawn Jianggenspr...@gmail.com wrote:
Sorry, Are we using the same trunk build ? I downloaded the tomcat trunk
build here:
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090703/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
When accessing http://localhost:8080/dojo/dojo/dojo.js , I got it's
content:
/*
Copyright (c) 2004-2008, The Dojo Foundation All Rights Reserved.
Available via Academic Free License = 2.1 OR the modified BSD license.
see: http://dojotoolkit.org/license for details
*/
(function(){var _1=null;if((_1||(typeof
djConfig!=undefineddjConfig.scopeMap))(typeo
When accessing http://localhost:8080/dojo/dojo/dojo/dojo.js, I got this:
HTTP Status 404
I also tried to revert ConfirmMessageTag.java to dojo/dojo/dojo.js from
dojo/dojo/dojo/dojo.js. The dialog poped up and the test suite passed.
So , can anyone else help verify this ?
On Tue, Jul 7, 2009 at 1:09 AM, Jarek Gawor jga...@gmail.com wrote:
Shawn,
I recently modified ConfirmMessageTag.java so that it points to the
right locations for dojo resources. It used to point to
http://localhost:8080/dojo/dojo/dojo.js (which does not work) but now
points to http://localhost:8080/dojo/dojo/dojo/dojo.js (which does
work). That made the confirmation box to display again. The
confirmation box does display now when you use the web browser and
follow the steps of the test but somehow it fails in our automatic
tests. The test does pass for me when I execute it on my machine in
the same way as the automatic tests do... so that's why I thought it
was a timing issue. But there might be something else going on, I'm
not sure.
Jarek
On Fri, Jul 3, 2009 at 10:53 AM, Shawn Jianggenspr...@gmail.com wrote:
On Fri, Jul 3, 2009 at 2:53 AM, Jarek Gawor jga...@gmail.com wrote:
Shawn,
The one failure in console/advanced on Tomcat is caused by fixing that
prompting issue in the console. I'm hoping it's just a timing issue
It's not a timing issue. This is caused by a modification on
ConfirmMessageTag.java recently .
After that change, dojo.js can't be found so that the prompting dialog
can't be display anymore.
Revert the bvt change and update the code
private static final String DOJO_BASE = /dojo/dojo
to
private static final String DOJO_BASE = /dojo
can fix this.
since its takes a bit of time to load all the Dojo stuff for the first
time. So I just increased the wait time for the window to show up in
that test.
Jarek
On Wed, Jul 1, 2009 at 9:31 PM, Shawn Jianggenspr...@gmail.com wrote:
I can't recreate the same console/advanced failure in my local
machine.
But I do find another console testsuite bug and filed a JIRA:
https://issues.apache.org/jira/browse/GERONIMO-4720 (patch
provided)
The failure of enterprise-testsuite/sec-tests is related to
run-as propagation from a servlet to another servlet. I'm looking
into
it and will provide a patch.
On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor jga...@gmail.com
wrote:
Based on running the testsuite yesterday and with fixes committed
last
night I *think* we should be passing all tests on Tomcat and fail
enterprise-testsuite/sec-tests and webservices-testsuite/jaxws-tests
on Jetty. The webservices-testsuite/jaxws-tests fails because of
GERONIMO-4645. Not sure what's going on with
enterprise-testsuite/sec-tests.
Jarek
On Thu, Jun 25, 2009 at 11:00 AM, Kevan
Millerkevan.mil...@gmail.com
wrote:
A search of emails shows that our last successful automated build
of
trunk
was on May 26th. I know that there have been increasing
frustration
with
these recent build issues. We seem to be closing in on getting
these
issues
resolved. I built last night. I built successfully, last night,
but
had
7
testsuite failures -- 3 jetty, 4 tomcat.
I think it would do us a lot of good to have a concerted effort to
get
these
final issues resolved. Here are the test failures that I'm seeing:
3 common errors:
[INFO] The following tests failed:
[INFO] * console-testsuite/advanced -
/Users/kevan/geronimo/server/trunk/testsuite/console-testsuite/advanced/build.log
[INFO] * enterprise-testsuite/sec-tests -
/Users/kevan/geronimo/server/trunk/testsuite/enterprise-testsuite/sec-tests/build.log
[INFO] * webservices-testsuite/jaxws-tests -
/Users/kevan/geronimo/server/trunk/testsuite/webservices-testsuite/jaxws-tests/build.log
1 Tomcat unique failure:
[INFO] * web-testsuite/test-tomcat -
[BUILD] trunk: Failed for Revision: 791924
Geronimo Revision: 791924 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 11 seconds
[INFO] Finished at: Tue Jul 07 15:45:54 EDT 2009
[INFO] Final Memory: 403M/1009M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-1500-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-1500-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:49.701
[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:15.592)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.727)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:39.793)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.679)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:24.690)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:34.448)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:08.051)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:51.662)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:10.269)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:49.000)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:35.201)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.164)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.706)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.330)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.466)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.290)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.402)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.130) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:51.263)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:35.207)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.210)
[INFO] web-testsuite/test-jetty
Re: Setup a Geonimo FAQ ?
Hi Shawn, Besides Knowledge Base page, which might require different set of write permission, we have one section for trouble shooting[1] in G2.2 doc, targeting at version-specific problems. And your contribution will be highly appreciated. Jeff C On Tue, Jul 7, 2009 at 7:49 PM, Jason Dillon ja...@planet57.com wrote: So... go to town... or am I missing something? --jason On Jul 7, 2009, at 12:42 PM, Shawn Jiang wrote: OK, I also noticed that Knowledge Base page can be found as FAQ in geronimo homepage. FAQhttp://cwiki.apache.org/confluence/pages/listpages.action?key=GMOxKB Browse Spacehttp://cwiki.apache.org/confluence/spaces/browsespace.action?key=GMOxKB http://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=GMOxKBfromPageId=7513 Add Pagehttp://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=GMOxKBfromPageId=7513 - *V*iew http://cwiki.apache.org/confluence/display/GMOxKB/FAQ - *E*dithttp://cwiki.apache.org/confluence/pages/editpage.action?pageId=7513 - *A*ttachments (0)http://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=7513 - *I*nfohttp://cwiki.apache.org/confluence/pages/pageinfo.action?pageId=7513 Added by Jason Dillonhttp://cwiki.apache.org/confluence/display/%7Ejdillon, last edited by Jason Dillonhttp://cwiki.apache.org/confluence/display/%7Ejdillon on Jun 22, 2006 (view changehttp://cwiki.apache.org/confluence/pages/diffpages.action?pageId=7513originalId=7552 )Labels: (None) EDIT http://cwiki.apache.org/confluence/display/GMOxKB/FAQ --- Seems it has not been updated from 2006. We need to 1, Remove some stale content. 2, Add some new FAQ there. Hope that can reduce FAQ questions in mailing list. On Tue, Jul 7, 2009 at 1:08 PM, Jason Dillon ja...@planet57.com wrote: The Knowledge Base was intended to be the home for FAQ-ish thingys. --jason On Jul 7, 2009, at 12:04 PM, Shawn Jiang wrote: Obviously, there are really some FAQ in the mailing list such as 1, Lib conflict including myface, spring 2, Log4j 3, JPA JTA/Non-JTA DS requirement. 4, web-service out of memory 5, Classloading problem caused by bad EAR package structure. .. We need a formal page to record these FAQ. (only found two related page [1] and [2] with google). [1] http://docs.huihoo.com/apache/geronimo/1.1/geronimo-eclipse-plugin-faq.html [2]http://cwiki.apache.org/GMOxKB/index.html -- Shawn -- Shawn
Re: Web app clustering with WADI in Geronimo Tomcat 2.1.4 broken?
Hi all, Doc updated for both 2.1 and 2.2 by now. If you are using a Tomcat assembly of Geronimo distribution, replace clustering-wadi/ with tomcat-clustering-wadi/ element in the deployment plan. (1) http://cwiki.apache.org/confluence/display/GMOxDOC21/WADI+Clustering+Support (2) http://cwiki.apache.org/confluence/display/GMOxDOC22/WADI+Clustering And one more question, is there any reason that the schema file (ie. geronimo-tomcat-clustering-wadi-X.xsd ) was not extracted to geronimo_home/schema after build. Thanks. Jeff C On Tue, Jul 7, 2009 at 6:58 PM, Gianny Damour gianny.dam...@optusnet.com.au wrote: Hi Vamsi, In the case of tomcat, you need to use the node tomcat-clustering-wadi / instead of clustering-wadi / I wonder if it would not be better to uniformise node names across Jetty and Tomcat to prevent confusion. Thanks, Gianny On 07/07/2009, at 4:57 PM, Vamsavardhana Reddy wrote: I am trying to deploy a clustered web application in Geronimo Tomcat 2.1.4. I have added distributable/ in web.xml and clustering-wadi/ in geronimo-web.xml. When I deploy the application, I am getting the following deployment error: xml problem for web app . org.apache.geronimo.common.DeploymentException: xml problem for web app . at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:318) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:207) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:179) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:94) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:307) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:227) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.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:595) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.2.4a: Expected elements 'work-...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http:// geronimo.apache.org/xml/ns/j2ee/application-2.0 web-container@ http://geronimo.apache.org/xml/ns/naming-1.2 h...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-context@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cookies@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-chain@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-chain@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-realm@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 manager@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster@ http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-ref @http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http:// geronimo.apache.org/xml/ns/naming-1.2 resource-...@http:// geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http:// geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http:// geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http:// geronimo.apache.org/xml/ns/deployment-1.2 persiste...@http:// java.sun.com/xml/ns/persistence' instead of 'clustering-w...@http:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: xml-fragment xmlns:tom=http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 !--web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1; xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0-- dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/ deployment-1.2 dep:moduleId dep:groupIdpackt-samples/dep:groupId dep:artifactIdhelloworld-cluster/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ /dep:environment
[jira] Created: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties
Duplicate clusterName value sets in config-subsitious.properties
Key: GERONIMO-4729
URL: https://issues.apache.org/jira/browse/GERONIMO-4729
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: Any
Reporter: Chi Runhua
Look into *config-subsitions.properties* file, there are 2 places to set
clustername as following:
{code}
ClusterName=DEFAULT_CLUSTER
...
clusterName=CLUSTER_NAME
...
{code}
which will confuse users when they are going to set up a clustering/farming
environment.
Can we improve this?
Jeff
--
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: 792003
Geronimo Revision: 792003 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 51 seconds
[INFO] Finished at: Tue Jul 07 21:44:33 EDT 2009
[INFO] Final Memory: 464M/835M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-2100-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090707/logs-2100-jetty/
[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:44.818
[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.525)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:33.183)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:36.778)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.762)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:26.674)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:34.128)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:04.217)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.274)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:50.486)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.570)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.309)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.296)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.880)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.146)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.679)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.247)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.335)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.905) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:46.845) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.886)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:33.434)
[INFO] web-testsuite/test-jetty RUNNING
[INFO] web-testsuite/test-jetty SUCCESS (0:00:26.425
[jira] Commented: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties
[
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728478#action_12728478
]
Rex Wang commented on GERONIMO-4729:
agree, I'd like improve this
-Rex
Duplicate clusterName value sets in config-subsitious.properties
Key: GERONIMO-4729
URL: https://issues.apache.org/jira/browse/GERONIMO-4729
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: Any
Reporter: Chi Runhua
Look into *config-subsitions.properties* file, there are 2 places to set
clustername as following:
{code}
ClusterName=DEFAULT_CLUSTER
...
clusterName=CLUSTER_NAME
...
{code}
which will confuse users when they are going to set up a clustering/farming
environment.
Can we improve this?
Jeff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties
[
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang reassigned GERONIMO-4729:
--
Assignee: Rex Wang
Duplicate clusterName value sets in config-subsitious.properties
Key: GERONIMO-4729
URL: https://issues.apache.org/jira/browse/GERONIMO-4729
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
Look into *config-subsitions.properties* file, there are 2 places to set
clustername as following:
{code}
ClusterName=DEFAULT_CLUSTER
...
clusterName=CLUSTER_NAME
...
{code}
which will confuse users when they are going to set up a clustering/farming
environment.
Can we improve this?
Jeff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Duplicate clustername value sets in config-subsititions file
Well, I see your jira opened against it and also rename the clusterNodeName to farmingClusterNodeName? any thoughts? -Rex 2009/7/6 chi runhua chirun...@gmail.com 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] Created: (GERONIMO-4730) Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle.
Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle. -- Key: GERONIMO-4730 URL: https://issues.apache.org/jira/browse/GERONIMO-4730 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.2 Environment: TranQL XA Resource Adapter for DB2 Reporter: Kan Ogawa Assignee: Kan Ogawa Fix For: 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4730) Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle.
[ https://issues.apache.org/jira/browse/GERONIMO-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4730: Component/s: console Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle. -- Key: GERONIMO-4730 URL: https://issues.apache.org/jira/browse/GERONIMO-4730 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: TranQL XA Resource Adapter for DB2 Reporter: Kan Ogawa Assignee: Kan Ogawa Fix For: 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4730) Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle.
[ https://issues.apache.org/jira/browse/GERONIMO-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4730: Attachment: dbpoolwizard-db2.png Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle. -- Key: GERONIMO-4730 URL: https://issues.apache.org/jira/browse/GERONIMO-4730 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: TranQL XA Resource Adapter for DB2 Reporter: Kan Ogawa Assignee: Kan Ogawa Fix For: 2.2 Attachments: dbpoolwizard-db2.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4730) Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle.
[ https://issues.apache.org/jira/browse/GERONIMO-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728515#action_12728515 ] viola.lu commented on GERONIMO-4730: this is duplicate with https://issues.apache.org/jira/browse/GERONIMO-4706, thanks. Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle. -- Key: GERONIMO-4730 URL: https://issues.apache.org/jira/browse/GERONIMO-4730 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: TranQL XA Resource Adapter for DB2 Reporter: Kan Ogawa Assignee: Kan Ogawa Fix For: 2.2 Attachments: dbpoolwizard-db2.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties
[
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4729:
---
Attachment: Geronimo-4729-trunk.patch
patch for trunk.
Duplicate clusterName value sets in config-subsitious.properties
Key: GERONIMO-4729
URL: https://issues.apache.org/jira/browse/GERONIMO-4729
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
Attachments: Geronimo-4729-trunk.patch
Look into *config-subsitions.properties* file, there are 2 places to set
clustername as following:
{code}
ClusterName=DEFAULT_CLUSTER
...
clusterName=CLUSTER_NAME
...
{code}
which will confuse users when they are going to set up a clustering/farming
environment.
Can we improve this?
Jeff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties
[
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4729:
---
Attachment: Geronimo-4729-b21.patch
patch for branch 2.1
Duplicate clusterName value sets in config-subsitious.properties
Key: GERONIMO-4729
URL: https://issues.apache.org/jira/browse/GERONIMO-4729
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch
Look into *config-subsitions.properties* file, there are 2 places to set
clustername as following:
{code}
ClusterName=DEFAULT_CLUSTER
...
clusterName=CLUSTER_NAME
...
{code}
which will confuse users when they are going to set up a clustering/farming
environment.
Can we improve this?
Jeff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4730) Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle.
[ https://issues.apache.org/jira/browse/GERONIMO-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa closed GERONIMO-4730. --- Resolution: Invalid Some messages in dbpool wizard are undefined in the sysdb portlet resource bundle. -- Key: GERONIMO-4730 URL: https://issues.apache.org/jira/browse/GERONIMO-4730 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: TranQL XA Resource Adapter for DB2 Reporter: Kan Ogawa Assignee: Kan Ogawa Fix For: 2.2 Attachments: dbpoolwizard-db2.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
