[jira] Created: (GERONIMO-4632) Enable Geronimo to support IPv6 addresses
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 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.
[jira] Created: (GERONIMO-4633) extra semicolon in code.
extra semicolon in code. Key: GERONIMO-4633 URL: https://issues.apache.org/jira/browse/GERONIMO-4633 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Clustering Affects Versions: 2.2 Environment: xp + sun jdk 1.5 Reporter: Shawn Jiang Priority: Trivial extra semicolon in code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4633) extra semicolon in code.
[ https://issues.apache.org/jira/browse/GERONIMO-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4633: -- Attachment: extra_semicolon.patch see patch for details. > extra semicolon in code. > > > Key: GERONIMO-4633 > URL: https://issues.apache.org/jira/browse/GERONIMO-4633 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 > Environment: xp + sun jdk 1.5 >Reporter: Shawn Jiang >Priority: Trivial > Attachments: extra_semicolon.patch > > > extra semicolon in code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4633) extra semicolon in code.
[ https://issues.apache.org/jira/browse/GERONIMO-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4633: -- Patch Info: [Patch Available] > extra semicolon in code. > > > Key: GERONIMO-4633 > URL: https://issues.apache.org/jira/browse/GERONIMO-4633 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 > Environment: xp + sun jdk 1.5 >Reporter: Shawn Jiang >Priority: Trivial > Attachments: extra_semicolon.patch > > > extra semicolon in code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4633) extra semicolon in code.
[ https://issues.apache.org/jira/browse/GERONIMO-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4633. Resolution: Fixed Fix Version/s: 2.2 Commit changes to rev 775134 , thanks Shawn for the patch ! > extra semicolon in code. > > > Key: GERONIMO-4633 > URL: https://issues.apache.org/jira/browse/GERONIMO-4633 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 > Environment: xp + sun jdk 1.5 >Reporter: Shawn Jiang >Priority: Trivial > Fix For: 2.2 > > Attachments: extra_semicolon.patch > > > extra semicolon in code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4626) Tomcat Clustering with WADI - JSESSIONID with jvmRoute to support mod_jk routing
[ https://issues.apache.org/jira/browse/GERONIMO-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4626: --- Fix Version/s: 2.2 2.1.5 > Tomcat Clustering with WADI - JSESSIONID with jvmRoute to support mod_jk > routing > > > Key: GERONIMO-4626 > URL: https://issues.apache.org/jira/browse/GERONIMO-4626 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.1.4 >Reporter: Gianny Damour >Assignee: Gianny Damour > Fix For: 2.1.5, 2.2 > > > It is not possible to fulfill session affinity with Apache mod_jk as the > value of the JSESSIONID cookie does not embed a jvmRoute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned DAYTRADER-68: - Assignee: Joe Bohn (was: Forrest Xia) > A version of daytrader for Tomcat 6 > --- > > Key: DAYTRADER-68 > URL: https://issues.apache.org/jira/browse/DAYTRADER-68 > Project: DayTrader > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Web Tier >Affects Versions: 2.2 > Environment: Tomcat 6.0.18 >Reporter: Forrest Xia >Assignee: Joe Bohn > Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, > daytrader-webonly.patch > > > I have a trimmed version of daytrader for tomcat 6, and want to contribute to > daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved DAYTRADER-68. --- Resolution: Fixed Fix Version/s: 2.2 > A version of daytrader for Tomcat 6 > --- > > Key: DAYTRADER-68 > URL: https://issues.apache.org/jira/browse/DAYTRADER-68 > Project: DayTrader > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Web Tier >Affects Versions: 2.2 > Environment: Tomcat 6.0.18 >Reporter: Forrest Xia >Assignee: Joe Bohn > Fix For: 2.2 > > Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, > daytrader-webonly.patch > > > I have a trimmed version of daytrader for tomcat 6, and want to contribute to > daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709873#action_12709873 ] Joe Bohn commented on DAYTRADER-68: --- I decided to go ahead and checkin the code so that further collaboration could take place in svn. I added the missing headers, fixed the build, included commons-logging in the war (not included in tomcat 6 and decided it was better in the war than manually pulling it into tomcat) and beautified some code. Included in trunk rev. 775187 Still needed is to create plugins for Geronimo jetty and tomcat. We also need to reconcile the datasource issues for Geronimo (perhaps we can share a common datasource with the full sample). > A version of daytrader for Tomcat 6 > --- > > Key: DAYTRADER-68 > URL: https://issues.apache.org/jira/browse/DAYTRADER-68 > Project: DayTrader > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Web Tier >Affects Versions: 2.2 > Environment: Tomcat 6.0.18 >Reporter: Forrest Xia >Assignee: Joe Bohn > Fix For: 2.2 > > Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, > daytrader-webonly.patch > > > I have a trimmed version of daytrader for tomcat 6, and want to contribute to > daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709907#action_12709907 ] Donald Woods commented on DAYTRADER-68: --- Forrest, can you describe how this version of Daytrader differs from the normal one? What changes did you make to remove the EJB/JPA dependencies? Any thoughts of using non-container managed JPA w/o the need for EJBs for the DB access? > A version of daytrader for Tomcat 6 > --- > > Key: DAYTRADER-68 > URL: https://issues.apache.org/jira/browse/DAYTRADER-68 > Project: DayTrader > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Web Tier >Affects Versions: 2.2 > Environment: Tomcat 6.0.18 >Reporter: Forrest Xia >Assignee: Joe Bohn > Fix For: 2.2 > > Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, > daytrader-webonly.patch > > > I have a trimmed version of daytrader for tomcat 6, and want to contribute to > daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6
[ https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709912#action_12709912 ] Donald Woods commented on DAYTRADER-68: --- Wondering why there are dependencies like openjpa, geronimo specs, ... in the pom.xml, but none are pulled into the created WAR file? Also, please update the README with instructions on how to deploy to Tomcat and Little-G. Thanks. > A version of daytrader for Tomcat 6 > --- > > Key: DAYTRADER-68 > URL: https://issues.apache.org/jira/browse/DAYTRADER-68 > Project: DayTrader > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Web Tier >Affects Versions: 2.2 > Environment: Tomcat 6.0.18 >Reporter: Forrest Xia >Assignee: Joe Bohn > Fix For: 2.2 > > Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, > daytrader-webonly.patch > > > I have a trimmed version of daytrader for tomcat 6, and want to contribute to > daytrader trunk, please help review and commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 775402
Geronimo Revision: 775402 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090515/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090515
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 27 seconds
[INFO] Finished at: Fri May 15 21:39:35 EDT 2009
[INFO] Final Memory: 669M/991M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090515/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-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:40.759
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.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:01.244)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.240)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:32.976)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.993)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:29.355)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:28.634)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:54.265)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:50.391)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:53.884)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:43.708)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.226)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.479)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.956)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:04.764)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.325)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.708)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.798)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:50.607)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.680) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.872)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
