[jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.
[ http://issues.apache.org/jira/browse/GERONIMO-2577?page=comments#action_12459700 ] Dave Colasurdo commented on GERONIMO-2577: -- 1) Is node c (the failing node) always the same physical machine? 2) Are you 100% certain that all three nodes are on the same subnet? This is extremely important.. Applying the subnet mask to each nodes IP address should yield the exact same network portion of the IP address. 3) Have you added the distributable tag to the web.xml for each clustered app? 4) Can you please elaborate on the following statement ...When replication module is SimpleTcpReplicationManager, the geronimo cluster can continue the process. What exactly does that mean? What replication module are you using? Thanks Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down. --- Key: GERONIMO-2577 URL: http://issues.apache.org/jira/browse/GERONIMO-2577 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat, Clustering Affects Versions: 1.1, 1.1.1 Environment: JDK - Sun java version 1_5_0_09(32bit) OS- Red Hat Enterprise Linux ES4 update4(32bit) Http Server - Apache 2.0.59 +mod_jk 1.2.19 Reporter: Kaoru Matsumura Attachments: geronimo-web.xml We run Geronimo cluster with three nodes. In our environment, with DeltaManager set for replication module, we found that the last node cound not continue the processes when the other nodes is intentionally halted in order. We recognize Tomcat 5.5.15 is OK with the same configuration and operations. Test Application The Web application program, which was used for the test, simply reads the number of access count, and then write the count to HttpSession object. Configuration?Files == We refer http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html * config.xml We add the following parameters to the standard configuration. gbean name=TomcatEngine attribute name=initParamsname=Geronimo jvmRoute=nodeA/attribute /gbean Operations === 1 Have browser access to Test Application , and reload several times.(*1) HttpSession object is created on the nodeA. 2 And then, We kill the process of geronimo on the nodeA with $kill -9 Process ID.(*2) 3 Reload the browser at one time. The node changes to nodeB.(*3) 4 Reload the browser several times.(*4) 5 And then, We kill the process of geronimo on the nodeB with $kill -9 Process ID.(*5) 6 Reload the browser at one time.(And then, We expect that the process continues at the nodeC.) But the HttpSessionID of the HttpSession object is changed to another ID and the counter value is back to 1.(*6) As a result, the geronimo cluster cannot continue the process. For avoidance === When replication module is SimpleTcpReplicationManager, the geronimo cluster can continue the process. Debug levels logs == (*1) nodeA -- 20:06:17,736 DEBUG [CoyoteAdapter] Requested cookie session id is 7160C8614D20687D3548E8488AB65AC3.nodeA 20:06:17,736 DEBUG [JvmRouteBinderValve] Found Cluster DeltaManager [EMAIL PROTECTED] at /ClusterCheck 20:06:17,736 DEBUG [JvmRouteBinderValve] Turnover Check time 0 msec 20:06:17,737 DEBUG [MsgContext] COMMIT 20:06:17,737 DEBUG [JkInputStream] COMMIT sending headers [EMAIL PROTECTED] === MimeHeaders === 20:06:17,737 DEBUG [MsgContext] CLOSE 20:06:17,738 DEBUG [REQ_TIME] Time pre=0/ service=2 242 /ClusterCheck/counter 20:06:17,738 DEBUG [ReplicationValve] Invoking replication request on /ClusterCheck/counter 20:06:17,738 DEBUG [DeltaManager] Manager [/ClusterCheck]: create session message [7160C8614D20687D3548E8488AB65AC3.nodeA] delta request. 20:06:17,757 DEBUG [McastService] Mcast receive ping from member org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.3:4001,catalina,192.168.1.3,4001, alive=58960] --- nodeC --- 20:06:17,655 DEBUG [SimpleTcpCluster] Assuming clocks are synched: Replication for 7160C8614D20687D3548E8488AB65AC3.nodeA-1162811177738 took=-83 ms. 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: Received SessionMessage of type=(SESSION-DELTA) from [org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.1:4001,catalina,192.168.1.1,4001, alive=130441]] 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: received session [7160C8614D20687D3548E8488AB65AC3.nodeA] delta. --- (*2) nodeB (same as nodeC) --- 20:06:39,817 INFO [SimpleTcpCluster] Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.1:4001,catalina,192.168.1.1,4001, alive=149288] 20:06:39,818
[jira] Commented: (GERONIMO-2577) Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down.
[ http://issues.apache.org/jira/browse/GERONIMO-2577?page=comments#action_12459757 ] Dave Colasurdo commented on GERONIMO-2577: -- I have seen clustering fail in multicast mode when the physical machines were not on the same subnet... Even when you plug machines into adjacent wallports, oftentimes the subnets are different. That would be my first guess.. Lots more questions :) 5) I've heard that this same scenario works for you when using Tomcat w/o Geronimo. Did you run the tomcat test on the same exact same three machines as the geronimo test? 6) Are you certain that config.xml has a unique nodename (i.e jvmRoute)for each of the three nodes? 7) Are you certain that the IP addresses are unique (and correct) in the deployment plan for each node? 8) Can you provide all three deployment plans (one for each node)? 9) Any particular reason you set useDirtyFlag=true? 10) I see that you removed the mcastBindAddress setting in the deployment plan. I've heard differing information on whether or not this is needed. Have you tried setting this field in each of the nodes? 11) Have you tried removing waitForAck=true and using ackTimeout for the test? Thanks -Dave- Geronimo cluster (Tomcat Version)cannot continue the HttpSession when current node is down. --- Key: GERONIMO-2577 URL: http://issues.apache.org/jira/browse/GERONIMO-2577 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat, Clustering Affects Versions: 1.1, 1.1.1 Environment: JDK - Sun java version 1_5_0_09(32bit) OS- Red Hat Enterprise Linux ES4 update4(32bit) Http Server - Apache 2.0.59 +mod_jk 1.2.19 Reporter: Kaoru Matsumura Attachments: geronimo-web.xml We run Geronimo cluster with three nodes. In our environment, with DeltaManager set for replication module, we found that the last node cound not continue the processes when the other nodes is intentionally halted in order. We recognize Tomcat 5.5.15 is OK with the same configuration and operations. Test Application The Web application program, which was used for the test, simply reads the number of access count, and then write the count to HttpSession object. Configuration?Files == We refer http://cwiki.apache.org/GMOxDOC11/clustering-sample-application.html * config.xml We add the following parameters to the standard configuration. gbean name=TomcatEngine attribute name=initParamsname=Geronimo jvmRoute=nodeA/attribute /gbean Operations === 1 Have browser access to Test Application , and reload several times.(*1) HttpSession object is created on the nodeA. 2 And then, We kill the process of geronimo on the nodeA with $kill -9 Process ID.(*2) 3 Reload the browser at one time. The node changes to nodeB.(*3) 4 Reload the browser several times.(*4) 5 And then, We kill the process of geronimo on the nodeB with $kill -9 Process ID.(*5) 6 Reload the browser at one time.(And then, We expect that the process continues at the nodeC.) But the HttpSessionID of the HttpSession object is changed to another ID and the counter value is back to 1.(*6) As a result, the geronimo cluster cannot continue the process. For avoidance === When replication module is SimpleTcpReplicationManager, the geronimo cluster can continue the process. Debug levels logs == (*1) nodeA -- 20:06:17,736 DEBUG [CoyoteAdapter] Requested cookie session id is 7160C8614D20687D3548E8488AB65AC3.nodeA 20:06:17,736 DEBUG [JvmRouteBinderValve] Found Cluster DeltaManager [EMAIL PROTECTED] at /ClusterCheck 20:06:17,736 DEBUG [JvmRouteBinderValve] Turnover Check time 0 msec 20:06:17,737 DEBUG [MsgContext] COMMIT 20:06:17,737 DEBUG [JkInputStream] COMMIT sending headers [EMAIL PROTECTED] === MimeHeaders === 20:06:17,737 DEBUG [MsgContext] CLOSE 20:06:17,738 DEBUG [REQ_TIME] Time pre=0/ service=2 242 /ClusterCheck/counter 20:06:17,738 DEBUG [ReplicationValve] Invoking replication request on /ClusterCheck/counter 20:06:17,738 DEBUG [DeltaManager] Manager [/ClusterCheck]: create session message [7160C8614D20687D3548E8488AB65AC3.nodeA] delta request. 20:06:17,757 DEBUG [McastService] Mcast receive ping from member org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.1.3:4001,catalina,192.168.1.3,4001, alive=58960] --- nodeC --- 20:06:17,655 DEBUG [SimpleTcpCluster] Assuming clocks are synched: Replication for 7160C8614D20687D3548E8488AB65AC3.nodeA-1162811177738 took=-83 ms. 20:06:17,655 DEBUG [DeltaManager] Manager [/ClusterCheck]: Received SessionMessage of type=(SESSION-DELTA) from
[jira] Commented: (GERONIMO-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=comments#action_12416199 ] Dave Colasurdo commented on GERONIMO-2112: -- I believe the following changes are still required: License.txt - add licenses for castor and possibly antlr Notice.txt - add notices for castor and xpp3 Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Assignee: Kevan Miller Priority: Blocker Fix For: 1.1 Attachments: LICENSE.txt, NOTICE.txt, NOTICE.txt, NOTICES-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft2.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=all ] Dave Colasurdo updated GERONIMO-2112: - Attachment: NOTICE.txt LICENSE.txt Here is the initial pass at the LICENSE.TXT and NOTICE.TXT files for Geronimo 1.1.. Still need input on Openejb and stax-api .. and of course a thorough review of all content.. Note that antlr contains two licenses.. I suspect only the first one is needed but included both so that you could see them. Thanks -Dave- Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 Attachments: LICENSE.txt, NOTICE.txt, NOTICES-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft1.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2112) Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file
[ http://issues.apache.org/jira/browse/GERONIMO-2112?page=comments#action_12416113 ] Dave Colasurdo commented on GERONIMO-2112: -- That was the format I used in the original LICENSE.TXT and NOTICE.txt that I attached (separating licenses from attributions). I suspect tweaking those files with updated info may be the way to go.. -Dave- Place required attrtibutions in the NOTICES.txt file or a license included in the LICENSE.txt file -- Key: GERONIMO-2112 URL: http://issues.apache.org/jira/browse/GERONIMO-2112 Project: Geronimo Type: Task Security: public(Regular issues) Components: documentation Versions: 1.1 Reporter: John Sisson Priority: Blocker Fix For: 1.1 Attachments: LICENSE.txt, NOTICE.txt, NOTICE.txt, NOTICES-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft1.txt, geronimo-1.1-RC-licenses-attributions-draft2.txt I have collated a list of components in the attached file indicating whether IMHO they require an attribution in the NOTICES.txt file or a license included in the LICENSE.txt file. See http://www.apache.org/dev/apply-license.html#new for information on license files. See http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE for an example of a LICENSE file containing other licenses. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=comments#action_12402408 ] Dave Colasurdo commented on GERONIMO-2006: -- Thanks for looking at this issue.. I originally created the pblm on a build that was done just prior to the cut-over to moduleId. So the original reported failures weren't related to configId -vs- moduleId.. though that pblm is also worth investigation. Concerning the non-functioning web app WARs panel .. The failure was pretty solid.. Perhaps this has gone away. I will try to recreate after getting a clean build. Though may be a bit delayed as I have been encountering connection errors ( svn: PROPFIND of '/openejb/branches/v2_1/openejb2': could not connect to server (https://svn.codehaus.org)) with maven m:fresh-checkout all day :( -Dave- Deploying an application with an incorrect deployment plan results in non-functional admin console panel Key: GERONIMO-2006 URL: http://issues.apache.org/jira/browse/GERONIMO-2006 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment, console Versions: 1.1 Reporter: Dave Colasurdo Assignee: Aaron Mulder Priority: Blocker Fix For: 1.1 Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning Show Web App Wars panel. The console Deploy Applications panel reports application installed and started successfully. However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA. From then on, the Web App Wars console panel shows portlet error and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the Web App War panel function correctly. The console should be able to report the true status of the deploy/start and recover from deploying a bad plan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2006) Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
Deploying an application with an incorrect depolyment plan results in non-functional admin console panel Key: GERONIMO-2006 URL: http://issues.apache.org/jira/browse/GERONIMO-2006 Project: Geronimo Type: Bug Security: public (Regular issues) Components: console Versions: 1.1 Reporter: Dave Colasurdo Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning Show Web App Wars panel. The console Deploy Applications panel reports application installed and started successfully. However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA. From then on, the Web App Wars console panel shows portlet error and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the Web App War panel function correctly. The console should be able to report the true status of the deploy/start and recover from deploying a bad plan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2006) Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ] Dave Colasurdo updated GERONIMO-2006: - Attachment: stackTrace.log badPlan.xml Myapp.war Deploying an application with an incorrect depolyment plan results in non-functional admin console panel Key: GERONIMO-2006 URL: http://issues.apache.org/jira/browse/GERONIMO-2006 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.1 Reporter: Dave Colasurdo Attachments: Myapp.war, badPlan.xml, stackTrace.log Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning Show Web App Wars panel. The console Deploy Applications panel reports application installed and started successfully. However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA. From then on, the Web App Wars console panel shows portlet error and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the Web App War panel function correctly. The console should be able to report the true status of the deploy/start and recover from deploying a bad plan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2006) Deploying an application with an incorrect depolyment plan results in non-functional admin console panel
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ] Dave Colasurdo updated GERONIMO-2006: - Attachment: badPlan2.xml Here is another bad plan (badPlan2) that results in a slightly different error (i.e the deploy panel doesn't refresh and returns a blank page). Deploying an application with an incorrect depolyment plan results in non-functional admin console panel Key: GERONIMO-2006 URL: http://issues.apache.org/jira/browse/GERONIMO-2006 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.1 Reporter: Dave Colasurdo Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning Show Web App Wars panel. The console Deploy Applications panel reports application installed and started successfully. However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA. From then on, the Web App Wars console panel shows portlet error and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the Web App War panel function correctly. The console should be able to report the true status of the deploy/start and recover from deploying a bad plan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2006) Deploying an application with an incorrect deployment plan results in non-functional admin console panel
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ] Dave Colasurdo updated GERONIMO-2006: - Summary: Deploying an application with an incorrect deployment plan results in non-functional admin console panel (was: Deploying an application with an incorrect depolyment plan results in non-functional admin console panel) Deploying an application with an incorrect deployment plan results in non-functional admin console panel Key: GERONIMO-2006 URL: http://issues.apache.org/jira/browse/GERONIMO-2006 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.1 Reporter: Dave Colasurdo Attachments: Myapp.war, badPlan.xml, badPlan2.xml, stackTrace.log Deploying myApp.war using badPlan.xml (both attached) results in a non-functioning Show Web App Wars panel. The console Deploy Applications panel reports application installed and started successfully. However, the application did not startup succesfully. The badPlan file is actually missing tcpListenerAddress=auto which causes TomcatReceiver Gbean to fail startup. I've attached the stacktrace to the JIRA. From then on, the Web App Wars console panel shows portlet error and there is no way to uninstall the bad application via the console. The server must be stopped and restarted in order to have the Web App War panel function correctly. The console should be able to report the true status of the deploy/start and recover from deploying a bad plan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1976) Change Welcome Application for G1.1
Change Welcome Application for G1.1 --- Key: GERONIMO-1976 URL: http://issues.apache.org/jira/browse/GERONIMO-1976 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: usability Versions: 1.1 Reporter: Dave Colasurdo Update the G1.1 welcome app.. - Unclutter the initial welcome screen - Moved replace url information to backup page - Moved slimmer geronimo info to backup page - Updated replace url user deployment xml to G1.1 format - Geronimo-1900 adds a graphic that can be used on the new panels. The graphic is referenced though commented out for now. It can be uncommented when Geronimo-1900 patch is committed. Also, the writeup for slimmer Geronimo still needs to evaluated in light of the new little-G offering and Plugin capabilities. I suspect we should reference all three on the slimmerG page. Thoughts? Thanks -Dave- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1976) Change Welcome Application for G1.1
[ http://issues.apache.org/jira/browse/GERONIMO-1976?page=all ] Dave Colasurdo updated GERONIMO-1976: - Attachment: welcome-app.patch Change Welcome Application for G1.1 --- Key: GERONIMO-1976 URL: http://issues.apache.org/jira/browse/GERONIMO-1976 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: usability Versions: 1.1 Reporter: Dave Colasurdo Attachments: welcome-app.patch Update the G1.1 welcome app.. - Unclutter the initial welcome screen - Moved replace url information to backup page - Moved slimmer geronimo info to backup page - Updated replace url user deployment xml to G1.1 format - Geronimo-1900 adds a graphic that can be used on the new panels. The graphic is referenced though commented out for now. It can be uncommented when Geronimo-1900 patch is committed. Also, the writeup for slimmer Geronimo still needs to evaluated in light of the new little-G offering and Plugin capabilities. I suspect we should reference all three on the slimmerG page. Thoughts? Thanks -Dave- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1976) Change Welcome Application for G1.1
[ http://issues.apache.org/jira/browse/GERONIMO-1976?page=comments#action_12377630 ] Dave Colasurdo commented on GERONIMO-1976: -- BTW, the patch should get applied to /applications/welcome/src/webapp/ Thanks Change Welcome Application for G1.1 --- Key: GERONIMO-1976 URL: http://issues.apache.org/jira/browse/GERONIMO-1976 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: usability Versions: 1.1 Reporter: Dave Colasurdo Attachments: welcome-app.patch Update the G1.1 welcome app.. - Unclutter the initial welcome screen - Moved replace url information to backup page - Moved slimmer geronimo info to backup page - Updated replace url user deployment xml to G1.1 format - Geronimo-1900 adds a graphic that can be used on the new panels. The graphic is referenced though commented out for now. It can be uncommented when Geronimo-1900 patch is committed. Also, the writeup for slimmer Geronimo still needs to evaluated in light of the new little-G offering and Plugin capabilities. I suspect we should reference all three on the slimmerG page. Thoughts? Thanks -Dave- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1900) Sample app links on welcome app are broken by default
[ http://issues.apache.org/jira/browse/GERONIMO-1900?page=comments#action_12377441 ] Dave Colasurdo commented on GERONIMO-1900: -- I still have a general uneasy feeling about this overall approach for the default examples. Prasad has done a good job given the current requirements/assumptions/restrictions of this JIRA. However, I question the assumptions. The flow is currently: 1) User hits the welcome page and selects servlets-examples 2) The would you like to install examples page is presented 3) User selects yes and is brought to the admin console logon page 4) After logging on, the plugins page is displayed 5) User selects the plugin server and chooses search 6) User is presented with list of plugins (apachds, various examples, ldap-realm) 7) User selects servlets-examples for the appropriate web container 8) Servlets-examples is magically installed along with any dependencies 9) User is presented with panel to start servlets-examples 10) User selects start and is returned to the plugins menu The major problems I have with this approach is: a) The user that is trying to run a few simple examples is tossed into the middle of the admin console. b) First time users should be gently introduced to the console via the front welcome page c) Users will be exposed to many other plugins (the list is growing) that are useful but not particulary pertinent to the task of installing examples c) The user is left stranded in the plugins page of the admin console without any path back to the original thing they wanted to do (i.e. run the samples).. They either have to retype the original url or hit the back button several times.. Any chance of either pre-installing the samples (like G1.0) or installing the samples with one click (perhaps cmdline plugin under the covers) and automatically redirecting the user to the samples with minimal user intervention? Are we trying to showcase the plugin technology user interface or are we trying to provide a mechanism to quickly let the user run the samples? Perhaps there should be a separate plugins link from the welcome page to showcase the plugin technology. Thanks -Dave- Sample app links on welcome app are broken by default - Key: GERONIMO-1900 URL: http://issues.apache.org/jira/browse/GERONIMO-1900 Project: Geronimo Type: Bug Security: public(Regular issues) Components: usability, sample apps Versions: 1.1 Reporter: Aaron Mulder Assignee: Aaron Mulder Priority: Blocker Fix For: 1.1 Attachments: welcome-2.patch, welcome-3.patch, welcome.patch It would be nice to take users to a page that would prompt them to install the sample if they click a link to it and it's not present. However, automating this would require us to be able to construct a link into a portlet, which does not seem easy. For now, the welcome app can include pages at the locations where the sample apps will be bound, with text to the effect of: This sample has not yet been installed. To install it, visit the (URL)console(/URL) and select the Plugins page, click the Search for Plugins button, and select the (NAME HERE) sample to install. Then visit this same URL again to view the (NAME HERE) example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1955) Move user applications out of Geronimo repo
Move user applications out of Geronimo repo --- Key: GERONIMO-1955 URL: http://issues.apache.org/jira/browse/GERONIMO-1955 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: usability Versions: 1.1 Reporter: Dave Colasurdo User applications should be moved out of the Geronimo repository (i.e. /Geronimo-1.1/repository/geronimo ).. This may be as simple as changing the sample/default deployment plans to contain a common groupid name. I'd recommend a short simple groupid name of user-apps or possibly user-applications.. Alternately Matt has suggested installedJ2EEApps. Whatever groupid name is chosen, the following should be changed: -Change documentation to specify the default deployment location (groupid in the deployment plans) and other references in the doc. -Consider creating this as an empty directory in the distributions. -Change the deployment plans for the available examples to use this groupid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1884) Samples not installed properly in G1.1 - several issues
[ http://issues.apache.org/jira/browse/GERONIMO-1884?page=comments#action_12376249 ] Dave Colasurdo commented on GERONIMO-1884: -- Reopened ...so that most recent comments won't get lost.. -Dave- Samples not installed properly in G1.1 - several issues --- Key: GERONIMO-1884 URL: http://issues.apache.org/jira/browse/GERONIMO-1884 Project: Geronimo Type: Bug Security: public(Regular issues) Components: sample apps Versions: 1.1 Reporter: Dave Colasurdo Assignee: Aaron Mulder Priority: Critical Fix For: 1.1 IT appears that the Geronimo samples have recently been removed from the default distributions and replaced with the ability to download them through the admin console. There are several issues that need to be addressed: 1) The Sample links on the Geronimo welcome page are dead.. This needs to be updated with instructions on how to download, start and access the samples.. 2) Assuming that the admin console plugins is the correct spot to download the samples.. 2a) The initial panel presented to the user is a bit confusing and is missing the ldap-demo.. 2b) After downloading the jsp or servlet examples.. The user is presented with a start examples box.. Selecting this does not work and results in an exception (attached below) 2c) start examples box does not return any status 2d) Manually starting the example via the command line also does not work. and results in an exception... Exception for 2b Geronimo Application Server started # Installed configuration # id = geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car # location = /home/davecola/geronimo-1.1-041906/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/repository/geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/jsp-examples-tomcat-1.1-SNAPSHOT.car 14:12:04,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car?configurationName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car java.lang.ClassCastException at org.apache.geronimo.kernel.config.Configuration.buildClassPath(Configuration.java:380) at org.apache.geronimo.kernel.config.Configuration.createConfigurationClasssLoader(Configuration.java:322) at org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:267) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:932) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:376) at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:143) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:267) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:210) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:111) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at
[jira] Commented: (GERONIMO-1884) Samples not installed properly in G1.1 - several issues
[ http://issues.apache.org/jira/browse/GERONIMO-1884?page=comments#action_12376064 ] Dave Colasurdo commented on GERONIMO-1884: -- Thanks Aaron!! The servlet and jsp examples seem to install and start fine with the latest build.. A few comments: - Is it possible to suppress the missing web containers examples (e.g. suppress jetty examples in the tomcat distribution and vice versa). There presence seems awkward.. - There seems to be a mismatch in terminology.. Title reads import/export configurations.. the details talk about installing a plugin.. - The Ldap example is missing from the list. - It would be nice if there were a few words documenting how to uninstall the config/plugin. Perhaps just a simple statement imported configurations can be removed by uninstalling the appropriate application It wasn't clear to me at first if the term plugin implied some uninstall step beyond a simple application uninstall. Thanks -Dave- Samples not installed properly in G1.1 - several issues --- Key: GERONIMO-1884 URL: http://issues.apache.org/jira/browse/GERONIMO-1884 Project: Geronimo Type: Bug Security: public(Regular issues) Components: sample apps Versions: 1.1 Reporter: Dave Colasurdo Assignee: Aaron Mulder Priority: Critical Fix For: 1.1 IT appears that the Geronimo samples have recently been removed from the default distributions and replaced with the ability to download them through the admin console. There are several issues that need to be addressed: 1) The Sample links on the Geronimo welcome page are dead.. This needs to be updated with instructions on how to download, start and access the samples.. 2) Assuming that the admin console plugins is the correct spot to download the samples.. 2a) The initial panel presented to the user is a bit confusing and is missing the ldap-demo.. 2b) After downloading the jsp or servlet examples.. The user is presented with a start examples box.. Selecting this does not work and results in an exception (attached below) 2c) start examples box does not return any status 2d) Manually starting the example via the command line also does not work. and results in an exception... Exception for 2b Geronimo Application Server started # Installed configuration # id = geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car # location = /home/davecola/geronimo-1.1-041906/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/repository/geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/jsp-examples-tomcat-1.1-SNAPSHOT.car 14:12:04,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car?configurationName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car java.lang.ClassCastException at org.apache.geronimo.kernel.config.Configuration.buildClassPath(Configuration.java:380) at org.apache.geronimo.kernel.config.Configuration.createConfigurationClasssLoader(Configuration.java:322) at org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:267) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:932) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:376) at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:143) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:267) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:210) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:111) at
[jira] Created: (GERONIMO-1884) Samples not installed properly in G1.1 - several issues
Samples not installed properly in G1.1 - several issues --- Key: GERONIMO-1884 URL: http://issues.apache.org/jira/browse/GERONIMO-1884 Project: Geronimo Type: Bug Security: public (Regular issues) Components: sample apps Versions: 1.1 Reporter: Dave Colasurdo Priority: Critical IT appears that the Geronimo samples have recently been removed from the default distributions and replaced with the ability to download them through the admin console. There are several issues that need to be addressed: 1) The Sample links on the Geronimo welcome page are dead.. This needs to be updated with instructions on how to download, start and access the samples.. 2) Assuming that the admin console plugins is the correct spot to download the samples.. 2a) The initial panel presented to the user is a bit confusing and is missing the ldap-demo.. 2b) After downloading the jsp or servlet examples.. The user is presented with a start examples box.. Selecting this does not work and results in an exception (attached below) 2c) start examples box does not return any status 2d) Manually starting the example via the command line also does not work. and results in an exception... Exception for 2b Geronimo Application Server started # Installed configuration # id = geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car # location = /home/davecola/geronimo-1.1-041906/assemblies/j2ee-tomcat-server/target/geronimo-1.1-SNAPSHOT/repository/geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/jsp-examples-tomcat-1.1-SNAPSHOT.car 14:12:04,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car?configurationName=geronimo/jsp-examples-tomcat/1.1-SNAPSHOT/car java.lang.ClassCastException at org.apache.geronimo.kernel.config.Configuration.buildClassPath(Configuration.java:380) at org.apache.geronimo.kernel.config.Configuration.createConfigurationClasssLoader(Configuration.java:322) at org.apache.geronimo.kernel.config.Configuration.init(Configuration.java:267) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:932) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:376) at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:143) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:267) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:235) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:210) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:111) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGLIB$$a14ba351.loadConfiguration(generated) at org.apache.geronimo.console.car.ResultsHandler.actionAfterView(ResultsHandler.java:75) at org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:116) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at
[jira] Commented: (GERONIMO-1577) Installer - User Interface changes
[ http://issues.apache.org/jira/browse/GERONIMO-1577?page=comments#action_12365077 ] Dave Colasurdo commented on GERONIMO-1577: -- The Izpack guy(s) are looking into item 1 (dependencies and indentation) and will get back to us on Monday. Their initial feedback looks promising. Installer - User Interface changes -- Key: GERONIMO-1577 URL: http://issues.apache.org/jira/browse/GERONIMO-1577 Project: Geronimo Type: Improvement Components: installer Versions: 1.0.1, 1.1 Reporter: Dave Colasurdo The Installer should consider changing the following: 1) Represent the PacksPanel dependencies visually in a hierarchical tree (I'm awaiting a rsp on ipack mailing list to see if this is possible) 2) Suppress the dependencies box on the PacksPanel (I'm awaiting rsp on iPack mailing list to see if this is possible) 3) The Configuration Checkpoint page should include a list of all the selected options and a summary of their combined sizes. Title on this page ahould be updated to Install Confirmation Panel 4) The Processing Panel - this panel shows up and executes afterit appears that the install has already completed. Would be nice to have a better description title on the page Installing configurations and Applications and a better indication of success when the install completes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1577) Installer - User Interface changes
Installer - User Interface changes -- Key: GERONIMO-1577 URL: http://issues.apache.org/jira/browse/GERONIMO-1577 Project: Geronimo Type: Improvement Components: installer Versions: 1.0.1, 1.1 Reporter: Dave Colasurdo The Installer should consider changing the following: 1) Represent the PacksPanel dependencies visually in a hierarchical tree (I'm awaiting a rsp on ipack mailing list to see if this is possible) 2) Suppress the dependencies box on the PacksPanel (I'm awaiting rsp on iPack mailing list to see if this is possible) 3) The Configuration Checkpoint page should include a list of all the selected options and a summary of their combined sizes. Title on this page ahould be updated to Install Confirmation Panel 4) The Processing Panel - this panel shows up and executes afterit appears that the install has already completed. Would be nice to have a better description title on the page Installing configurations and Applications and a better indication of success when the install completes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[
http://issues.apache.org/jira/browse/GERONIMO-1540?page=comments#action_12364086
]
Dave Colasurdo commented on GERONIMO-1540:
--
It appears the corruption of the war file was a temporary JIRA problem. The
same war file looks fine today. Please publish the war and the patch at your
convenience..
Thanks
-Dave-
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.1, 1.0.1
Reporter: Dave Colasurdo
Attachments: geronimo-jsp-examples-tomcat-5.5.15-plus.war, jsp-examples.patch
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1540) Fix security vulnerability in jsp-examples
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Reporter: Dave Colasurdo
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[ http://issues.apache.org/jira/browse/GERONIMO-1540?page=all ]
Dave Colasurdo updated GERONIMO-1540:
-
Component: sample apps
Version: 1.0.1
1.1
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0.1, 1.1
Reporter: Dave Colasurdo
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[
http://issues.apache.org/jira/browse/GERONIMO-1540?page=comments#action_12364003
]
Dave Colasurdo commented on GERONIMO-1540:
--
The Tomcat team has fixed this in their open builds (but *not* in Tomcat
5.5.15). I've extracted the latest Tomcat source and built it to get the
latest binary image of the jsp-examples.
Tomcat info:
Path: .
URL: http://svn.apache.org/repos/asf/tomcat/current/tc5.5.x
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 372275
Node Kind: directory
Schedule: normal
Last Changed Author: remm
Last Changed Rev: 344145
Last Changed Date: 2005-11-14 10:19:03 -0500 (Mon, 14 Nov 2005)
Properties Last Updated: 2006-01-25 12:21:02 -0500 (Wed, 25 Jan 2006)
Also, merged our custom geronimo changes to the war file and change the
geronimo build to pickup the new warfile.
I've provided a geronimo patch for the 1.0 branch and anupdated war file.
The attached warfile needs to get published to
http://svn.apache.org/repository/geronimo-samples/wars/ prior to committing the
patch.
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0.1, 1.1
Reporter: Dave Colasurdo
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[ http://issues.apache.org/jira/browse/GERONIMO-1540?page=all ]
Dave Colasurdo updated GERONIMO-1540:
-
Attachment: jsp-examples.patch
geronimo-jsp-examples-tomcat-5.5.15-plus.war
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0.1, 1.1
Reporter: Dave Colasurdo
Attachments: geronimo-jsp-examples-tomcat-5.5.15-plus.war, jsp-examples.patch
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[ http://issues.apache.org/jira/browse/GERONIMO-1540?page=all ]
Dave Colasurdo updated GERONIMO-1540:
-
Geronimo Info: [Patch Available]
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0.1, 1.1
Reporter: Dave Colasurdo
Attachments: geronimo-jsp-examples-tomcat-5.5.15-plus.war, jsp-examples.patch
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1540) Fix security vulnerability in jsp-examples
[
http://issues.apache.org/jira/browse/GERONIMO-1540?page=comments#action_12364012
]
Dave Colasurdo commented on GERONIMO-1540:
--
The original warfile that I've attached seems to work fine on my machine (and
another) though appears to be corrupted when I re-download it from JIRA. It
seems the JIRA system is having problems and I am receiving lots of garbled
info when viewing items. Not yet certain if the two issues are related
though please hold off on publishing the war until the issue is resolved.
Thanks..
-Dave-
Fix security vulnerability in jsp-examples
--
Key: GERONIMO-1540
URL: http://issues.apache.org/jira/browse/GERONIMO-1540
Project: Geronimo
Type: Bug
Components: sample apps
Versions: 1.0.1, 1.1
Reporter: Dave Colasurdo
Attachments: geronimo-jsp-examples-tomcat-5.5.15-plus.war, jsp-examples.patch
Oliver Karow has reported a cross-site scripting vulnerability in the Tomcat
jsp-examples that are included in Geronimo. It fails on both Jetty and
Tomcat.
This can be reproduced with the following urls:
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert('Gotcha')/script
http://localhost:8080/jsp-examples/cal/cal2.jsp?time=/scriptalert(document.cookie)/script
This JIRA does not address a related problem in the admin console. That
problem is addressed in GERONIMO-1474.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1424) Correct Additional Samples redirect url
Correct Additional Samples redirect url -- Key: GERONIMO-1424 URL: http://issues.apache.org/jira/browse/GERONIMO-1424 Project: Geronimo Type: Bug Reporter: Dave Colasurdo Priority: Minor The Geronimo Welcome page links to additional samples. This link points to the geronimo website that redirects to the actual spot. The actual spot has moved, hence the redirection needs to be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1424) Correct Additional Samples redirect url
[ http://issues.apache.org/jira/browse/GERONIMO-1424?page=all ] Dave Colasurdo updated GERONIMO-1424: - Attachment: sampleRedirect.patch Correct Additional Samples redirect url - Key: GERONIMO-1424 URL: http://issues.apache.org/jira/browse/GERONIMO-1424 Project: Geronimo Type: Bug Reporter: Dave Colasurdo Priority: Minor Attachments: sampleRedirect.patch The Geronimo Welcome page links to additional samples. This link points to the geronimo website that redirects to the actual spot. The actual spot has moved, hence the redirection needs to be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1371) Geronimo startup/shutdown issues
[ http://issues.apache.org/jira/browse/GERONIMO-1371?page=all ] Dave Colasurdo updated GERONIMO-1371: - Attachment: simple.patch Attached simple.patch for part 1.. Geronimo startup/shutdown issues Key: GERONIMO-1371 URL: http://issues.apache.org/jira/browse/GERONIMO-1371 Project: Geronimo Type: Bug Versions: 1.0 Environment: Windows Reporter: Dave Colasurdo Fix For: 1.0, 1.x Attachments: simple.patch Noticed two separate issues when using the latest v1 candidate build (12/15/05) on a windows platform... 1) When issuing startup.bat, lots of debug messages appear in the primary window.. Suspect this is just a missing @echo off 2) Seeing the following warning in the secondary window and the log for various shutdowns... a) startup.bat followed by shutdown.bat b) geronimo.bat start followed by shutdown.bat 13:36:31,052 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.commit(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setAutoCommit(Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.setAutoCommit(Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionStart(ManagedXAConnection.java:89) at org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.begin(AbstractManagedConnection.java:188) at org.tranql.connector.jdbc.ConnectionHandle.setAutoCommit(ConnectionHandle.java:161) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:126) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.store.PersistenceAdapter$$EnhancerByCGLIB$$98dcaa17.beginTransaction(generated) at org.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:158) at org.activemq.util.TransactionTemplate.run(TransactionTemplate.java:38) at org.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:227) at org.activemq.store.journal.JournalPersistenceAdapter$3.run(JournalPersistenceAdapter.java:357) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source) at java.lang.Thread.run(Thread.java:534) 13:36:31,062 ERROR [JournalPersistenceAdapter] Failed to checkpoint a message store: javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. at org.activemq.util.JMSExceptionHelper.newJMSException(JMSExceptionHelper.java:49) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:130) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
[jira] Created: (GERONIMO-1377) Startup Warning - unknown host - tomcat
Startup Warning - unknown host - tomcat --- Key: GERONIMO-1377 URL: http://issues.apache.org/jira/browse/GERONIMO-1377 Project: Geronimo Type: Bug Versions: 1.0 Environment: Geronimo w/ tomcat. Seeing warning on both windows and linux. Reporter: Dave Colasurdo The following Wanings are in the log during startup. [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost It appears that content does get served correctly from the tomcat web container. Jeff G has indicated this is potentially a race condition. Not sure if/how it is related to JIRA 1372.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1377) Startup Warning on tomcat - unknown default host
[ http://issues.apache.org/jira/browse/GERONIMO-1377?page=all ] Dave Colasurdo updated GERONIMO-1377: - Summary: Startup Warning on tomcat - unknown default host (was: Startup Warning - unknown host - tomcat) Startup Warning on tomcat - unknown default host Key: GERONIMO-1377 URL: http://issues.apache.org/jira/browse/GERONIMO-1377 Project: Geronimo Type: Bug Versions: 1.0 Environment: Geronimo w/ tomcat. Seeing warning on both windows and linux. Reporter: Dave Colasurdo The following Wanings are in the log during startup. [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost It appears that content does get served correctly from the tomcat web container. Jeff G has indicated this is potentially a race condition. Not sure if/how it is related to JIRA 1372.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1371) Geronimo startup/shutdown issues
Geronimo startup/shutdown issues Key: GERONIMO-1371 URL: http://issues.apache.org/jira/browse/GERONIMO-1371 Project: Geronimo Type: Bug Versions: 1.0 Environment: Windows Reporter: Dave Colasurdo Noticed two separate issues when using the latest v1 candidate build (12/15/05) on a windows platform... 1) When issuing startup.bat, lots of debug messages appear in the primary window.. Suspect this is just a missing @echo off 2) Seeing the following warning in the secondary window and the log for various shutdowns... a) startup.bat followed by shutdown.bat b) geronimo.bat start followed by shutdown.bat 13:36:31,052 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.commit(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setAutoCommit(Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.setAutoCommit(Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionStart(ManagedXAConnection.java:89) at org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.begin(AbstractManagedConnection.java:188) at org.tranql.connector.jdbc.ConnectionHandle.setAutoCommit(ConnectionHandle.java:161) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:126) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.store.PersistenceAdapter$$EnhancerByCGLIB$$98dcaa17.beginTransaction(generated) at org.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:158) at org.activemq.util.TransactionTemplate.run(TransactionTemplate.java:38) at org.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:227) at org.activemq.store.journal.JournalPersistenceAdapter$3.run(JournalPersistenceAdapter.java:357) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source) at java.lang.Thread.run(Thread.java:534) 13:36:31,062 ERROR [JournalPersistenceAdapter] Failed to checkpoint a message store: javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. at org.activemq.util.JMSExceptionHelper.newJMSException(JMSExceptionHelper.java:49) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:130) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.activemq.store.PersistenceAdapter$$EnhancerByCGLIB$$98dcaa17.beginTransaction(generated) at org.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:158) at
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360528 ] Dave Colasurdo commented on GERONIMO-1372: -- Just noticed the default JRE on the machine is set to 1.4.2_06.. Will retry with 1.4.2_10... Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [ ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create(generated) at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke(generated) at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create(generated) at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360529 ] Dave Colasurdo commented on GERONIMO-1372: -- Same exception with 1.4.2_10 JRE.. Is anyone else seeing this exception? Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [ ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create(generated) at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke(generated) at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create(generated) at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at
[jira] Updated: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=all ] Dave Colasurdo updated GERONIMO-1372: - Attachment: geronimo.log Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Attachments: geronimo.log Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [ ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create(generated) at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke(generated) at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create(generated) at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360539 ] Dave Colasurdo commented on GERONIMO-1372: -- Retried one more time and the exception during shutdown doesn't seem pertinent to the TradeEJB exception.. 1) ./geronimo.sh - worked fine CTL-C shutdown - worked fine 2) ./geronimo.sh - TradeEJB Exception Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Attachments: geronimo.log Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [ ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create(generated) at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke(generated) at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create(generated) at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360553 ] Dave Colasurdo commented on GERONIMO-1372: -- I'm sorry to say that I'm still seeing this same intermittent exception on the proposed-final-3 build. :( It fails intermittently during startup.. Sometimes the first time, sometimes the third time.. sometimes the third and fourth time. It does not fail only once after a fresh install. In other words, it often fails on multiple subsequent startups. Can anyone else confirm? Environment is linux and tomcat. with JDK 1.4.2_10 Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Attachments: geronimo.log Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [* ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [* ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [ ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create(generated) at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke(generated) at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create(generated) at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at
[jira] Updated: (GERONIMO-1274) Cannot install an application on Geronimo using the admin console
[ http://issues.apache.org/jira/browse/GERONIMO-1274?page=all ] Dave Colasurdo updated GERONIMO-1274: - Summary: Cannot install an application on Geronimo using the admin console (was: Cannot install an application on Tomcat using the admin console) Description: Attempted to install applications in a Tomcat-only environment using the admin console and simple deployment plans. The app install fails w/o any error in the admin console. However, there are exceptions in the log. Will attach them to this JIRA. The same scenario works fine when deploying via the cmdline. 12/07/05 Update: Now seeing the same failure on Jetty. was: Attempted to install applications in a Tomcat-only environment using the admin console and simple deployment plans. The app install fails w/o any error in the admin console. However, there are exceptions in the log. Will attach them to this JIRA. The same scenario works fine when deploying via the cmdline. Also, the same apps install fine on Jetty using the admin console. Cannot install an application on Geronimo using the admin console - Key: GERONIMO-1274 URL: http://issues.apache.org/jira/browse/GERONIMO-1274 Project: Geronimo Type: Bug Components: console Versions: 1.0 Reporter: Dave Colasurdo Attachments: geronimo.save.log Attempted to install applications in a Tomcat-only environment using the admin console and simple deployment plans. The app install fails w/o any error in the admin console. However, there are exceptions in the log. Will attach them to this JIRA. The same scenario works fine when deploying via the cmdline. 12/07/05 Update: Now seeing the same failure on Jetty. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
Refresh servlet-examples and jsp-examples war files --- Key: GERONIMO-1299 URL: http://issues.apache.org/jira/browse/GERONIMO-1299 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor There are several aspects of the Tomcat examples that are inappropriate for Jetty. Have updated the examples as follows: Updates to geronimo-servlet-examples-tomcat-5.5.12-1.war: -index.html - removed Please refer to the iREADME/i file provide with this Tomcat release regarding how to configure and start the provided web server. -WEB-INF/web.xml - Commented out filter-mapping filter-nameServlet Mapped Filter/filter-name servlet-nameinvoker/servlet-name /filter-mapping Updates to geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples: -index.html - removed of course, we recommend a href=http://jakarta.apache.org/tomcat/;Tomcat/a. Also updated the dependencies relating to the war revision id.. Will include a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
[ http://issues.apache.org/jira/browse/GERONIMO-1299?page=all ] Dave Colasurdo updated GERONIMO-1299: - Attachment: geronimo-jsp-examples-tomcat-5.5.12-1.war geronimo-servlet-examples-tomcat-5.5.12-1.war newexamples-12-06-05.patch Attached 2 new war files. They need to get published to: http://www.ibiblio.org/maven/geronimo/wars/ Also have attached a patch to update the dependencies that rely on the wars. Refresh servlet-examples and jsp-examples war files --- Key: GERONIMO-1299 URL: http://issues.apache.org/jira/browse/GERONIMO-1299 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor Attachments: geronimo-jsp-examples-tomcat-5.5.12-1.war, geronimo-servlet-examples-tomcat-5.5.12-1.war, newexamples-12-06-05.patch There are several aspects of the Tomcat examples that are inappropriate for Jetty. Have updated the examples as follows: Updates to geronimo-servlet-examples-tomcat-5.5.12-1.war: -index.html - removed Please refer to the iREADME/i file provide with this Tomcat release regarding how to configure and start the provided web server. -WEB-INF/web.xml - Commented out filter-mapping filter-nameServlet Mapped Filter/filter-name servlet-nameinvoker/servlet-name /filter-mapping Updates to geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples: -index.html - removed of course, we recommend a href=http://jakarta.apache.org/tomcat/;Tomcat/a. Also updated the dependencies relating to the war revision id.. Will include a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1258) Introduce Tomcat examples - using new build structure
[ http://issues.apache.org/jira/browse/GERONIMO-1258?page=all ] Dave Colasurdo updated GERONIMO-1258: - Attachment: examples-120305-good.patch Here is an updated verion of the examples patch (examples-120305-good.patch) It replaces the old patches examples.patch and welcome.patch.. Introduce Tomcat examples - using new build structure - Key: GERONIMO-1258 URL: http://issues.apache.org/jira/browse/GERONIMO-1258 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Assignee: Matt Hogstrom Priority: Minor Attachments: examples-120305-good.patch, examples.patch, welcome.patch Add the Tomcat Examples (jsp-examples, servlet-examples) to the server images for Tomcat and Jetty. The patch uses the new build structure (/config and /assemblies) and installs the examples as default started applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1274) Cannot install an application on Tomcat using the admin console
Cannot install an application on Tomcat using the admin console --- Key: GERONIMO-1274 URL: http://issues.apache.org/jira/browse/GERONIMO-1274 Project: Geronimo Type: Bug Components: console Versions: 1.0 Reporter: Dave Colasurdo Attempted to install applications in a Tomcat-only environment using the admin console and simple deployment plans. The app install fails w/o any error in the admin console. However, there are exceptions in the log. Will attach them to this JIRA. The same scenario works fine when deploying via the cmdline. Also, the same apps install fine on Jetty using the admin console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1276) Installing an application into Jetty - started state not retained after a restart
Installing an application into Jetty - started state not retained after a restart --- Key: GERONIMO-1276 URL: http://issues.apache.org/jira/browse/GERONIMO-1276 Project: Geronimo Type: Bug Versions: 1.0 Reporter: Dave Colasurdo I installed an application into the Jetty web container using the admin console and checking the start application box. The app installs and starts fine. However, the started state for the application is not retained over a server restart. Tryed this using the cmdline via: java -jar deployer.jar deploy c:\Example_WARs-from-ibiblio\geronimo-servlet-examples-tomcat-5.5.12 .war c:\Example_WARs-from-ibiblio\servlets-jetty-plan.xml java -jar deployer.jar start geronimo/servlets-examples/1.0-SNAPSHOT/war Again the app installed and started fine. The started state did not survive a server restart. This works fine when installing via cmdline for Tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1274) Cannot install an application on Tomcat using the admin console
[ http://issues.apache.org/jira/browse/GERONIMO-1274?page=all ] Dave Colasurdo updated GERONIMO-1274: - Attachment: geronimo.save.log Here is the geronimo log. I believe the failure starts at 11:05:45 in the log.. Cannot install an application on Tomcat using the admin console --- Key: GERONIMO-1274 URL: http://issues.apache.org/jira/browse/GERONIMO-1274 Project: Geronimo Type: Bug Components: console Versions: 1.0 Reporter: Dave Colasurdo Attachments: geronimo.save.log Attempted to install applications in a Tomcat-only environment using the admin console and simple deployment plans. The app install fails w/o any error in the admin console. However, there are exceptions in the log. Will attach them to this JIRA. The same scenario works fine when deploying via the cmdline. Also, the same apps install fine on Jetty using the admin console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1258) Introduce Tomcat examples - using new build structure
[ http://issues.apache.org/jira/browse/GERONIMO-1258?page=all ] Dave Colasurdo updated GERONIMO-1258: - Attachment: welcome.patch Updated Welcome page to link to examples. Introduce Tomcat examples - using new build structure - Key: GERONIMO-1258 URL: http://issues.apache.org/jira/browse/GERONIMO-1258 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor Attachments: examples.patch, welcome.patch Add the Tomcat Examples (jsp-examples, servlet-examples) to the server images for Tomcat and Jetty. The patch uses the new build structure (/config and /assemblies) and installs the examples as default started applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1258) Introduce Tomcat examples - using new build structure
Introduce Tomcat examples - using new build structure - Key: GERONIMO-1258 URL: http://issues.apache.org/jira/browse/GERONIMO-1258 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor Add the Tomcat Examples (jsp-examples, servlet-examples) to the server images for Tomcat and Jetty. The patch uses the new build structure (/config and /assemblies) and installs the examples as default started applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1258) Introduce Tomcat examples - using new build structure
[ http://issues.apache.org/jira/browse/GERONIMO-1258?page=all ] Dave Colasurdo updated GERONIMO-1258: - Attachment: examples.patch Patch attached. Introduce Tomcat examples - using new build structure - Key: GERONIMO-1258 URL: http://issues.apache.org/jira/browse/GERONIMO-1258 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor Attachments: examples.patch Add the Tomcat Examples (jsp-examples, servlet-examples) to the server images for Tomcat and Jetty. The patch uses the new build structure (/config and /assemblies) and installs the examples as default started applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1258) Introduce Tomcat examples - using new build structure
[ http://issues.apache.org/jira/browse/GERONIMO-1258?page=all ] Dave Colasurdo updated GERONIMO-1258: - Geronimo Info: [Patch Available] Introduce Tomcat examples - using new build structure - Key: GERONIMO-1258 URL: http://issues.apache.org/jira/browse/GERONIMO-1258 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Priority: Minor Attachments: examples.patch Add the Tomcat Examples (jsp-examples, servlet-examples) to the server images for Tomcat and Jetty. The patch uses the new build structure (/config and /assemblies) and installs the examples as default started applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1224) shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool
[ http://issues.apache.org/jira/browse/GERONIMO-1224?page=comments#action_12358403 ] Dave Colasurdo commented on GERONIMO-1224: -- If an are you sure prompt is added to shutdown, then there should also be a way to suppress the prompt (perhaps the use of the -port keyword itself). This will be useful for user written scripts that call to the geronimo shutdown scripts. shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool Key: GERONIMO-1224 URL: http://issues.apache.org/jira/browse/GERONIMO-1224 Project: Geronimo Type: Bug Components: startup/shutdown Versions: 1.0 Reporter: John Sisson Fix For: 1.0 The shutdown command line processing should be consistent with the deploy tool processing, such as: * specifying a URI as an argument (therefore allowing connections to remote hosts) * using the same file that the deployer uses for storing the username and password for the URI (see the .geronimo-deployer file used by the ServerConnection class) We should also consider outputting the domain and server name to the user when they request a shutdown and prompt them to confirm that is the system they really want to shut down. The reason for this is the shutdown processing defaults the port to 1099 if a port isn't supplied. This could be dangerous in the future if a number of geronimos processes are running on a single system because one of them ( e.g. the production system) could be using the default port whilst the others (e.g test systems) could be using customised port numbers. It would be easy for a user to shut down the wrong system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1087) Add Tomcat servlets-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1087?page=all ] Dave Colasurdo updated GERONIMO-1087: - Geronimo Info: (was: [Patch Available]) Do not checkin these patches.. This will be Dupped to a new JIRA. Add Tomcat servlets-examples to geronimo Key: GERONIMO-1087 URL: http://issues.apache.org/jira/browse/GERONIMO-1087 Project: Geronimo Type: New Feature Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: WelcomePage_withExamples.patch, servlets-examples.war, tomcat-servlets-examples-source.zip, tomcat_example.patch Add the Tomcat servlets-examples to the geronimo default distributions. Also update the Geronimo welcome page to include links to the examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1088) Add Tomcat jsp-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1088?page=all ] Dave Colasurdo updated GERONIMO-1088: - Geronimo Info: (was: [Patch Available]) Do not checkin these patches.. This will be Dupped to a new JIRA Add Tomcat jsp-examples to geronimo --- Key: GERONIMO-1088 URL: http://issues.apache.org/jira/browse/GERONIMO-1088 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: jsp-examples.war, tomcat-jsp-examples-source.zip, tomcat_jsp_example.patch Introduce the tomcat jsp-examples into geronimo.. This is a follow-on to GERONIMO-1087.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1166) Enhance Startup scripts to allow process to be launched in background
[ http://issues.apache.org/jira/browse/GERONIMO-1166?page=all ] Dave Colasurdo updated GERONIMO-1166: - Attachment: startup.sh.patch Here is the patch for unix environments. Enhance Startup scripts to allow process to be launched in background - Key: GERONIMO-1166 URL: http://issues.apache.org/jira/browse/GERONIMO-1166 Project: Geronimo Type: Improvement Components: startup/shutdown Versions: 1.0 Reporter: Dave Colasurdo Attachments: startup.patch, startup.sh.patch Add new keywords to startup scripts that control whether the process gets launched in the current window/process or in a separate background window/process. New keywords are: -foreground (or -fg) -background (or -bg) default is for a background session For windows platform: Will launch process in a separate window. For unix platforms: Will launch as a background process -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1166) Enhance Startup scripts to allow process to be launched in background
Enhance Startup scripts to allow process to be launched in background - Key: GERONIMO-1166 URL: http://issues.apache.org/jira/browse/GERONIMO-1166 Project: Geronimo Type: Improvement Components: startup/shutdown Versions: 1.0 Reporter: Dave Colasurdo Add new keywords to startup scripts that control whether the process gets launched in the current window/process or in a separate background window/process. New keywords are: -foreground (or -fg) -background (or -bg) default is for a background session For windows platform: Will launch process in a separate window. For unix platforms: Will launch as a background process -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1166) Enhance Startup scripts to allow process to be launched in background
[ http://issues.apache.org/jira/browse/GERONIMO-1166?page=all ] Dave Colasurdo updated GERONIMO-1166: - Attachment: startup.patch Attached is the patch for the windows platform.. Still need to investigate unix platforms.. Enhance Startup scripts to allow process to be launched in background - Key: GERONIMO-1166 URL: http://issues.apache.org/jira/browse/GERONIMO-1166 Project: Geronimo Type: Improvement Components: startup/shutdown Versions: 1.0 Reporter: Dave Colasurdo Attachments: startup.patch Add new keywords to startup scripts that control whether the process gets launched in the current window/process or in a separate background window/process. New keywords are: -foreground (or -fg) -background (or -bg) default is for a background session For windows platform: Will launch process in a separate window. For unix platforms: Will launch as a background process -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1166) Enhance Startup scripts to allow process to be launched in background
[ http://issues.apache.org/jira/browse/GERONIMO-1166?page=all ] Dave Colasurdo updated GERONIMO-1166: - Geronimo Info: [Patch Available] Enhance Startup scripts to allow process to be launched in background - Key: GERONIMO-1166 URL: http://issues.apache.org/jira/browse/GERONIMO-1166 Project: Geronimo Type: Improvement Components: startup/shutdown Versions: 1.0 Reporter: Dave Colasurdo Attachments: startup.patch Add new keywords to startup scripts that control whether the process gets launched in the current window/process or in a separate background window/process. New keywords are: -foreground (or -fg) -background (or -bg) default is for a background session For windows platform: Will launch process in a separate window. For unix platforms: Will launch as a background process -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1088) Add Tomcat jsp-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1088?page=all ] Dave Colasurdo updated GERONIMO-1088: - Geronimo Info: [Patch Available] Add Tomcat jsp-examples to geronimo --- Key: GERONIMO-1088 URL: http://issues.apache.org/jira/browse/GERONIMO-1088 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: jsp-examples.war, tomcat-jsp-examples-source.zip, tomcat_jsp_example.patch Introduce the tomcat jsp-examples into geronimo.. This is a follow-on to GERONIMO-1087.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1087) Add Tomcat servlets-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1087?page=all ] Dave Colasurdo updated GERONIMO-1087: - Attachment: tomcat-servlets-examples-source.zip servlets-examples.war WelcomePage_withExamples.patch Please ignore the previous patch file (tomcat_example.patch) as it was an invalid format for some of the updates. New attachments include: -the source changes for servlets-examples in zip format. It needs to be applied to geronimo/applications -changes to the welcome page -the generated warfile for servlets-examples (in case you want to test them out) Add Tomcat servlets-examples to geronimo Key: GERONIMO-1087 URL: http://issues.apache.org/jira/browse/GERONIMO-1087 Project: Geronimo Type: New Feature Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: WelcomePage_withExamples.patch, servlets-examples.war, tomcat-servlets-examples-source.zip, tomcat_example.patch Add the Tomcat servlets-examples to the geronimo default distributions. Also update the Geronimo welcome page to include links to the examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1088) Add Tomcat jsp-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1088?page=all ] Dave Colasurdo updated GERONIMO-1088: - Attachment: tomcat-jsp-examples-source.zip jsp-examples.war Please ignore the early patch file (tomcat_jsp_example.patch) as it was an invalid format for some of the updates. New attachments include: -the source changes for jsp-examples in zip format. It needs to be applied to geronimo/applications -the generated warfile for jsp-examples (in case you want to test them out) Add Tomcat jsp-examples to geronimo --- Key: GERONIMO-1088 URL: http://issues.apache.org/jira/browse/GERONIMO-1088 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: jsp-examples.war, tomcat-jsp-examples-source.zip, tomcat_jsp_example.patch Introduce the tomcat jsp-examples into geronimo.. This is a follow-on to GERONIMO-1087.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1087) Add Tomcat servlets-examples to geronimo
Add Tomcat servlets-examples to geronimo Key: GERONIMO-1087 URL: http://issues.apache.org/jira/browse/GERONIMO-1087 Project: Geronimo Type: New Feature Components: sample apps Versions: 1.0-M5 Reporter: Dave Colasurdo Add the Tomcat servlets-examples to the geronimo default distributions. Also update the Geronimo welcome page to include links to the examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1087) Add Tomcat servlets-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1087?page=all ] Dave Colasurdo updated GERONIMO-1087: - Attachment: tomcat_example.patch This patch should be applied to the /geronimo/applications/ directory. It includes: -Changes to welcome page for examples - creating a warfile from the servlets-examples source This example should be predeployed to the geronimo binary distributions. I suspect a minor tweak is needed (perhaps in maven.xml?) to cause it to predeploy..How to predeploy? Manual installation of the war works fine.. Add Tomcat servlets-examples to geronimo Key: GERONIMO-1087 URL: http://issues.apache.org/jira/browse/GERONIMO-1087 Project: Geronimo Type: New Feature Components: sample apps Versions: 1.0-M5 Reporter: Dave Colasurdo Attachments: tomcat_example.patch Add the Tomcat servlets-examples to the geronimo default distributions. Also update the Geronimo welcome page to include links to the examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1088) Add Tomcat jsp-examples to geronimo
Add Tomcat jsp-examples to geronimo Key: GERONIMO-1088 URL: http://issues.apache.org/jira/browse/GERONIMO-1088 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Introduce the tomcat jsp-examples into geronimo.. This is a follow-on to GERONIMO-1087.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1088) Add Tomcat jsp-examples to geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-1088?page=all ] Dave Colasurdo updated GERONIMO-1088: - Attachment: tomcat_jsp_example.patch Same general comments as GERONIMO-1087 except for JSPs.. Add Tomcat jsp-examples to geronimo --- Key: GERONIMO-1088 URL: http://issues.apache.org/jira/browse/GERONIMO-1088 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.0 Reporter: Dave Colasurdo Attachments: tomcat_jsp_example.patch Introduce the tomcat jsp-examples into geronimo.. This is a follow-on to GERONIMO-1087.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-762) Improve manageability by adding a web based management console
[ http://issues.apache.org/jira/browse/GERONIMO-762?page=comments#action_12315917 ] Dave Colasurdo commented on GERONIMO-762: - There is a README.txt available in /geronimo-console/trunk/ that describes how to build/install the console. Also, note that the donation is currently pulling dependencies (e.g. pluto, portlet-api) from the Gluecode maven repository. This needs to be updated such that these dependencies are downloaded from the Apache maven repository. Improve manageability by adding a web based management console -- Key: GERONIMO-762 URL: http://issues.apache.org/jira/browse/GERONIMO-762 Project: Geronimo Type: New Feature Components: management Reporter: David Klavon Attachments: console.zip Geronimo should provide a way to administer the server via the web. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-762) Improve manageability by adding a web based management console
[ http://issues.apache.org/jira/browse/GERONIMO-762?page=comments#action_12315918 ] Dave Colasurdo commented on GERONIMO-762: - Of course, the README step to download the source (i.e. Check out the geronimo-console svn co https://svn.gluecode.com/repos/geronimo-console;) are no longer relevant as the console is available as an attachment in this JIRA entry. Improve manageability by adding a web based management console -- Key: GERONIMO-762 URL: http://issues.apache.org/jira/browse/GERONIMO-762 Project: Geronimo Type: New Feature Components: management Reporter: David Klavon Attachments: console.zip Geronimo should provide a way to administer the server via the web. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
