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

2009-05-16 Thread Forrest Xia (JIRA)

[ 
https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710173#action_12710173
 ] 

Forrest Xia commented on DAYTRADER-68:
--

Joe, Donald, thank you for your review, commit, and comments for next step. I 
know there is more work to do :-)

Summarizing the comments from Joe and Donald, here is my understanding about 
what to do next:
1. Revise the pom.xml to remove the dependencies like openjpa, geronimo specs, 
etc.
2. Have a generic version of daytrader-webonly for both tomcat and jetty
3. Have two plugins of daytrader-webonly, one for geronimo tomcat version, 
another for geronimo jetty version
4. More doc work
4.1 about difference between daytrader-webonly version and the normal one
4.2 about how to deploy to tomcat and little-g
5. Investigate non-container managed JPA for db access

I will try best to followup this list asap. If anything I misundertood or 
missed, feel free to comment on this jira. 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.



Struts 2 very slow in 2.1.3

2009-05-16 Thread Geronimo 2.1.4

Hello,

We are building a struts based application, using Geronimo 2.1.3 as the
application server. In all the JSP pages we are using struts tags. The pages
are rendered very slowly. Even after pre-compilation there was no
significant change, the pages are painted very slow.

I also noticed a known issue in 2.1.2 regarding this GERONIMO-3890 has this
been resolved in any of the later Geronimo versions?


Regards
Shanmu


-- 
View this message in context: 
http://www.nabble.com/Struts-2-very-slow-in-2.1.3-tp23580106s134p23580106.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.



[BUILD] trunk: Failed for Revision: 775570

2009-05-16 Thread gawor
Geronimo Revision: 775570 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090516/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090516
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 5 seconds
[INFO] Finished at: Sat May 16 21:40:17 EDT 2009
[INFO] Final Memory: 710M/994M
[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/20090516/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:41.688
[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.330) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:28.392) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:33.004) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.026) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:29.943) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:28.467) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:53.895) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:50.726) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:10.121) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:45.659) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:29.385) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.447) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:33.402) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:03.035) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:56.225) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:54.388) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.368) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:50.463) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:38.394) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:31.177) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5

[jira] Resolved: (GERONIMO-4626) Tomcat Clustering with WADI - JSESSIONID with jvmRoute to support mod_jk routing

2009-05-16 Thread Gianny Damour (JIRA)

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

Gianny Damour resolved GERONIMO-4626.
-

   Resolution: Fixed
Fix Version/s: (was: 2.2)

Fix has been checked in and integration tested with mod_jk.

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