Fwd: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync
And now I'm getting these... :-( --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: January 18, 2008 6:22:11 PM PST To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ build-2000.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/enterprise-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/console-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/web-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/webservices-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-2000-tomcat/corba-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-
[jira] Created: (GERONIMODEVTOOLS-270) Support import of GEP features as feature projects in Eclipse
Support import of GEP features as feature projects in Eclipse - Key: GERONIMODEVTOOLS-270 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-270 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-260) Branding for 2.1.0 WTP server adapter
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560647#action_12560647 ] Tim McConnell commented on GERONIMODEVTOOLS-260: branding provided in revision 613350 > Branding for 2.1.0 WTP server adapter > - > > Key: GERONIMODEVTOOLS-260 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-260 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 2.1.0 >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-260) Branding for 2.1.0 WTP server adapter
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell resolved GERONIMODEVTOOLS-260. Resolution: Fixed Feature branding is now provided for the org.apache.geronimo.v21.feature (i.e., 2.10 WTP server adapter) via the org.apache.geronimo.st.v21.core plugin. Thus, the Geronimo server adapter feature and all associated plugins will now be viewable via the Help --> About dialogs. > Branding for 2.1.0 WTP server adapter > - > > Key: GERONIMODEVTOOLS-260 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-260 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 2.1.0 >Reporter: Tim McConnell >Assignee: Tim McConnell > Fix For: 2.1.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-269) Use released version of all Eclipse WTP artifacts
Use released version of all Eclipse WTP artifacts - Key: GERONIMODEVTOOLS-269 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-269 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-268) Synchronize version of OpenEJB with Geronimo Server
Synchronize version of OpenEJB with Geronimo Server --- Key: GERONIMODEVTOOLS-268 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-268 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-267) Remove all non-released artifacts
Remove all non-released artifacts -- Key: GERONIMODEVTOOLS-267 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-267 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-266) GEP automation testsuite
GEP automation testsuite Key: GERONIMODEVTOOLS-266 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-266 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-265) Remove 1.0 runtime
Remove 1.0 runtime -- Key: GERONIMODEVTOOLS-265 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-265 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-263) Support 2.1 Geronimo deployment plans
Support 2.1 Geronimo deployment plans - Key: GERONIMODEVTOOLS-263 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-263 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-264) Port Classpath Containers 2.0 code to 2.1.0
Port Classpath Containers 2.0 code to 2.1.0 --- Key: GERONIMODEVTOOLS-264 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-264 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-262) Create 2.1.0 update site
Create 2.1.0 update site Key: GERONIMODEVTOOLS-262 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-262 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-261) Incorporate rat-maven-plugin
Incorporate rat-maven-plugin Key: GERONIMODEVTOOLS-261 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-261 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-98) NotFoundException when trying to use non-builtin commands in full assembly
[ https://issues.apache.org/jira/browse/GSHELL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner closed GSHELL-98. -- Resolution: Invalid After a quick chat with Jason Dillon, it became apparent I was just using GShell wrong. The path for the command I was using was incomplete. Things are working as intended. > NotFoundException when trying to use non-builtin commands in full assembly > -- > > Key: GSHELL-98 > URL: https://issues.apache.org/jira/browse/GSHELL-98 > Project: GShell > Issue Type: Bug > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.0-alpha-2 >Reporter: Jason Warner >Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > Attachments: GShell-98.patch > > > The full assembly of gshell includes all the available commands by default. > When trying to use one of the commands included outside of builtins, a > NotFoundException is received. This seems to be caused by the groupings in > the layout.xml file. When the groupings were removed, all the commands could > be used successfully. Ideally, we'd like to be able to keep the groupings, > though. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-260) Branding for 2.1.0 WTP server adapter
Branding for 2.1.0 WTP server adapter - Key: GERONIMODEVTOOLS-260 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-260 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-259) GEP 2.1.0 Tasklist
GEP 2.1.0 Tasklist -- Key: GERONIMODEVTOOLS-259 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-259 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3762) Web Applications displayed during server startup include "system" console plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560571#action_12560571 ] David Jencks commented on GERONIMO-3762: I think we should show all the console plugins that have started. How about changing the context roots so they are all o the form console-*? > Web Applications displayed during server startup include "system" console > plugins > - > > Key: GERONIMO-3762 > URL: https://issues.apache.org/jira/browse/GERONIMO-3762 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1 >Reporter: Kevan Miller > Fix For: 2.1 > > > During server startup, the following web applications are displayed. > Web Applications: > / > /CAHelper > /activemq > /console > /console-base > /debug-views > /dojo > /dojo/1.0 > /juddi > /monitoring > /plan-creator > /plugin > /remote-deploy > /system-database > In 2.0.2, they were: > Web Applications: > / > /console > /console-standard > /dojo > /remote-deploy > Is it possible to filter these system apps (e.g. activemq, CAHelper, etc.)? > Or group in some way to make them more intuitive? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync
Kay, thx :-) --jason On Jan 18, 2008, at 1:42 PM, Jarek Gawor wrote: My fault, this should be fixed now. I changed the location where the the test reports and the binaries are published and forgot about the permission settings. Jarek On Jan 18, 2008 4:29 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: Um, anyone know what happened to the site perms? --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: January 18, 2008 1:18:41 PM PST To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ build-0200.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ geronimo-tomcat6-jee5-2.0.3-SNAPSHOT-bin.zip: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ geronimo-jetty6-jee5-2.0.3-SNAPSHOT-bin.zip: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/enterprise-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/console-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3- SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/web-testsuite: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var/log: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT/var: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6- jee5-2.0.3-SNAPSHOT: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite/target: Operation not permitted chmod: /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/ logs-0200-tomcat/webservices-testsuite: Operation not permitted
Re: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync
My fault, this should be fixed now. I changed the location where the the test reports and the binaries are published and forgot about the permission settings. Jarek On Jan 18, 2008 4:29 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: > Um, anyone know what happened to the site perms? > > --jason > > > Begin forwarded message: > > From: [EMAIL PROTECTED] (Cron Daemon) > Date: January 18, 2008 1:18:41 PM PST > To: [EMAIL PROTECTED] > Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync > > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/build-0200.log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT-bin.zip: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/geronimo-jetty6-jee5-2.0.3-SNAPSHOT-bin.zip: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite/target: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/enterprise-testsuite: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite/target: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/console-testsuite: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite/target: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/web-testsuite: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log/geronimo.log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var/log: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/var: > Operation not permitted > chmod: > /www/geronimo.apache.org/maven/server/binaries/2.0/20080118/logs-0200-tomcat/webservices-testsuite/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT: > Operation not permitted > chmod: > /www/g
[BUILD] 2.1: Failed for Revision: 613251
Geronimo Revision: 613251 built with tests included
See the full build-1500.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/build-1500.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080118
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 30 minutes 31 seconds
[INFO] Finished at: Fri Jan 18 15:37:44 EST 2008
[INFO] Final Memory: 307M/1011M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/logs-1500-tomcat/test.log
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-ear/2.1-SNAPSHOT/car
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-client/2.1-SNAPSHOT/car
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] 15:47:52,008 WARN [AbstractGBeanReference] GBean references are
not using proxies
[INFO] [INFO] 15:47:53,563 INFO [Log4jService]
--
[INFO] [INFO] 15:47:53,563 INFO [Log4jService] Started Logging Service
[INFO] [INFO] 15:47:53,563 INFO [Log4jService] Runtime Information:
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] Install Directory =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] JVM in use = Sun Microsystems
Inc. Java 1.5.0_12
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] Java Information:
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property
[java.runtime.name] = Java(TM) 2 Runtime Environment, Standard Edition
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property
[java.runtime.version] = 1.5.0_12-b04
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property [os.name]
= Linux
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property [os.version]
= 2.6.18-8.el5
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property
[sun.os.patch.level] = unknown
[INFO] [INFO] 15:47:53,564 INFO [Log4jService] System property [os.arch]
= i386
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.class.version] = 49.0
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property [locale]
= en_US
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[unicode.encoding]= UnicodeLittle
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[file.encoding] = ANSI_X3.4-1968
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.vm.name]= Java HotSpot(TM) Server VM
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.vm.vendor] = Sun Microsystems Inc.
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.vm.version] = 1.5.0_12-b04
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.vm.info]= mixed mode
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property [java.home]
= /usr/lib/jvm/jdk1.5.0_12/jre
[INFO] [INFO] 15:47:53,565 INFO [Log4jService] System property
[java.classpath] = null
[INFO] [INFO] 15:47:53,566 INFO [Log4jService] System property
[java.library.path] =
/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/server:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386
[INFO] [INFO] 15:47:53,566 INFO [Log4jService] System property
[java.endorsed.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed:/usr/lib/jvm/jdk1.5.0_12/jre/lib/endorsed
[INFO] [INFO] 15:47:53,566 INFO [Log4jService] System property
[java.ext.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/ext:/usr/lib/jvm/jdk1.5.0_12/jre/lib/ext
[INFO] [INFO] 15:47:53,566 INFO [Log4jService] System property
[sun.boot.class.path] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-spec-corba-1.0-incubating-r602900.jar:/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-rmi-spec-1.0-incubating-r602900.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/rt.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i18n.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.5.0_12/jre
Re: [BUILD] 2.1: Failed for Revision: 613167
This should be fixed now, I missed a plan in GERONIMO-3758
david jencks
On Jan 18, 2008, at 7:09 AM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 613167 built with tests included
See the full build-0900.log file at http://geronimo.apache.org/
maven/server/binaries/trunk/20080118/build-0900.log
Download the binaries from http://geronimo.apache.org/maven/server/
binaries/trunk/20080118
[INFO] BUILD SUCCESSFUL
[INFO]
--
--
[INFO] Total time: 35 minutes
[INFO] Finished at: Fri Jan 18 09:41:03 EST 2008
[INFO] Final Memory: 303M/1016M
[INFO]
--
--
TESTSUITE RESULTS (Failures only)
=
See detailed results at http://geronimo.apache.org/maven/server/
testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at http://geronimo.apache.org/maven/
server/binaries/trunk/20080118/logs-0900-tomcat/test.log
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0] org.apache.geronimo.testsuite/corba-marshal-
ear/2.1-SNAPSHOT/car
[INFO] [INFO] [0] org.apache.geronimo.testsuite/corba-
marshal-client/2.1-SNAPSHOT/car
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home: /home/geronimo/geronimo/trunk/
testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] 09:51:18,363 WARN [AbstractGBeanReference] GBean
references are not using proxies
[INFO] [INFO] 09:51:19,939 INFO [Log4jService]
--
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Started Logging
Service
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Runtime Information:
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Install Directory
= /home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/
geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] JVM in use = Sun
Microsystems Inc. Java 1.5.0_12
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] Java Information:
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.name] = Java(TM) 2 Runtime Environment, Standard
Edition
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[os.name] = Linux
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[os.version] = 2.6.18-8.el5
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[sun.os.patch.level] = unknown
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[os.arch] = i386
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.class.version] = 49.0
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[locale] = en_US
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[unicode.encoding]= UnicodeLittle
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[file.encoding] = ANSI_X3.4-1968
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.vm.name]= Java HotSpot(TM) Server VM
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.vendor] = Sun Microsystems Inc.
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.info]= mixed mode
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.home] = /usr/lib/jvm/jdk1.5.0_12/jre
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.classpath] = null
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.library.path] = /usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/
server:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/
jdk1.5.0_12/jre/../lib/i386
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.endorsed.dirs] = /home/geronimo/geronimo/trunk/testsuite/
corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/
endorsed:/usr/lib/jvm/jdk1.5.0_12/jre/lib/endorsed
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.ext.dirs] = /home/geronimo/geronimo/trunk/testsuite/
corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/
ext:/usr/lib/jvm/jdk1.5.0_12/jre/lib/ext
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[sun.boot.class.path] = /home/geronimo/geronimo/trunk/testsuite/
corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/
endorsed/yoko-spec-corba-1.0-incubating-r602900.jar:/home/geronimo/
geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-
javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-rmi-spec
[jira] Commented: (GERONIMO-3758) put our default jacc provider implementation into a different package than the required container stuff.
[ https://issues.apache.org/jira/browse/GERONIMO-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560542#action_12560542 ] David Jencks commented on GERONIMO-3758: Missed a plan, rev 613267 > put our default jacc provider implementation into a different package than > the required container stuff. > > > Key: GERONIMO-3758 > URL: https://issues.apache.org/jira/browse/GERONIMO-3758 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.1 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.1 > > > It's too hard to tell which jacc classes are the container framework and > which are our default jacc provider implementation. Putting the latter into > a separate package should help people figure out how to integrate other jacc > providers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Does deploy.sh make use of org.apache.geronimo.system.plugin?
Yes, it uses the code in the plugin jar. thanks david jencks On Jan 18, 2008, at 11:48 AM, Joseph Leong wrote: Hi all, Does anyone know if the $deploy.sh search-plugins eventually make use of the org.apache.geronimo.system.plugin to do it's installations? Or is there a separate package governing that. the best, Joseph Leong
Re: Site Broken?
Also it looks like the snippit macro isn't working on the published site: Working cwiki page: http://cwiki.apache.org/confluence/display/XB/Custom+XML Broken site page: http://geronimo.apache.org/xbean/custom-xml.html Anyone have ideas on how to fix this? -dain On Jan 18, 2008, at 10:27 AM, Dain Sundstrom wrote: Looks like we have been a bit lax lately about adding the releases to the site. David or Alan (not sure who is carrying the ball right now) can you add a blurb to the site http://geronimo.apache.org/xbean/ Thanks, -dain
[jira] Created: (GERONIMO-3762) Web Applications displayed during server startup include "system" console plugins
Web Applications displayed during server startup include "system" console plugins - Key: GERONIMO-3762 URL: https://issues.apache.org/jira/browse/GERONIMO-3762 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1 Reporter: Kevan Miller Fix For: 2.1 During server startup, the following web applications are displayed. Web Applications: / /CAHelper /activemq /console /console-base /debug-views /dojo /dojo/1.0 /juddi /monitoring /plan-creator /plugin /remote-deploy /system-database In 2.0.2, they were: Web Applications: / /console /console-standard /dojo /remote-deploy Is it possible to filter these system apps (e.g. activemq, CAHelper, etc.)? Or group in some way to make them more intuitive? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Does deploy.sh make use of org.apache.geronimo.system.plugin?
Hi all, Does anyone know if the $deploy.sh search-plugins eventually make use of the org.apache.geronimo.system.plugin to do it's installations? Or is there a separate package governing that. the best, Joseph Leong
Site?
Looks like we have been a bit lax lately about adding the releases to the site. David or Alan (not sure who is carrying the ball right now) can you add a blurb to the site http://geronimo.apache.org/xbean/ Thanks, -dain
[jira] Updated: (GERONIMO-3761) Add data collection and instrumentation to the AsyncHttpClient
[ https://issues.apache.org/jira/browse/GERONIMO-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-3761: --- Attachment: GERONIMO-3761.patch This is a proof of concept of the monitoring support. There are some additional details that probably need to be worked out. > Add data collection and instrumentation to the AsyncHttpClient > -- > > Key: GERONIMO-3761 > URL: https://issues.apache.org/jira/browse/GERONIMO-3761 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: AsyncHttpClient >Reporter: Rick McGuire > Attachments: GERONIMO-3761.patch > > > There's been some discussion on the dev list about adding some > instrumentation to the AsyncHttpClient. This is for tracking these > additions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3761) Add data collection and instrumentation to the AsyncHttpClient
Add data collection and instrumentation to the AsyncHttpClient -- Key: GERONIMO-3761 URL: https://issues.apache.org/jira/browse/GERONIMO-3761 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: AsyncHttpClient Reporter: Rick McGuire There's been some discussion on the dev list about adding some instrumentation to the AsyncHttpClient. This is for tracking these additions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Is there a caching order problem with authentication challenges?
Yeah, I think caching the session before calling sendRequest() is a slightly
better idea. I don't think it's a major difference however.
The difference would be noticed only if the current connection is the *only*
active connection to the host. If there are more active connections for the
given host, the subsequent sendRequest() call will happily pick up the
connection that's at the front of the queue and start. Note the session
cache employs a queue, so the behavior is FIFO. But I do agree that in the
case described above, caching it before sendRequest() would work better.
Thanks!
Regards,
Sangjin
On Jan 18, 2008 7:39 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> While working through the code looking to add hooks for signaling the
> monitoring events, I noticed the following bit of code in the
> ResponseFuture:
>
>//Authenticate
>int authCount = request.getAuthCount() + 1;
>if (authCount <= 3) {
>request.setAuthCount(authCount);
>client.sendRequest(request);
>
>// if we've been provided with a cache, put this session
> into
>// the cache.
>SessionCache cache = getSessionCache();
>if (cache != null) {
>// cache the session before we return
>cache.cacheSession(ioSession);
>}
>return;
>}
>
>
> This is sending the challenge response back to the server, but returning
> the connection to the cache AFTER the request is sent back. Shouldn't
> the connection be returned to the cache BEFORE the challenge response is
> sent to allow the connection to be reused?
>
> Rick
>
[BUILD] 2.1: Failed for Revision: 613094
Geronimo Revision: 613094 built with tests included
See the full build-0300.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/build-0300.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080118
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 29 minutes 54 seconds
[INFO] Finished at: Fri Jan 18 03:36:16 EST 2008
[INFO] Final Memory: 310M/608M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/logs-0300-tomcat/test.log
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-ear/2.1-SNAPSHOT/car
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-client/2.1-SNAPSHOT/car
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] 03:46:15,014 WARN [AbstractGBeanReference] GBean references are
not using proxies
[INFO] [INFO] 03:46:16,947 INFO [Log4jService]
--
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] Started Logging Service
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] Runtime Information:
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] Install Directory =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] JVM in use = Sun Microsystems
Inc. Java 1.5.0_12
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] Java Information:
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] System property
[java.runtime.name] = Java(TM) 2 Runtime Environment, Standard Edition
[INFO] [INFO] 03:46:16,948 INFO [Log4jService] System property
[java.runtime.version] = 1.5.0_12-b04
[INFO] [INFO] 03:46:16,949 INFO [Log4jService] System property [os.name]
= Linux
[INFO] [INFO] 03:46:16,949 INFO [Log4jService] System property [os.version]
= 2.6.18-8.el5
[INFO] [INFO] 03:46:16,949 INFO [Log4jService] System property
[sun.os.patch.level] = unknown
[INFO] [INFO] 03:46:16,949 INFO [Log4jService] System property [os.arch]
= i386
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property
[java.class.version] = 49.0
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property [locale]
= en_US
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property
[unicode.encoding]= UnicodeLittle
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property
[file.encoding] = ANSI_X3.4-1968
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property
[java.vm.name]= Java HotSpot(TM) Server VM
[INFO] [INFO] 03:46:16,950 INFO [Log4jService] System property
[java.vm.vendor] = Sun Microsystems Inc.
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.vm.version] = 1.5.0_12-b04
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.vm.info]= mixed mode
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property [java.home]
= /usr/lib/jvm/jdk1.5.0_12/jre
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.classpath] = null
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.library.path] =
/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/server:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.endorsed.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed:/usr/lib/jvm/jdk1.5.0_12/jre/lib/endorsed
[INFO] [INFO] 03:46:16,951 INFO [Log4jService] System property
[java.ext.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/ext:/usr/lib/jvm/jdk1.5.0_12/jre/lib/ext
[INFO] [INFO] 03:46:16,952 INFO [Log4jService] System property
[sun.boot.class.path] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-spec-corba-1.0-incubating-r602900.jar:/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-rmi-spec-1.0-incubating-r602900.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/rt.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i18n.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.5.0_12/jre
[BUILD] 2.1: Failed
Geronimo Revision: 613167 built with tests included
See the full build-0900.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/build-0900.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080118
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes
[INFO] Finished at: Fri Jan 18 09:41:03 EST 2008
[INFO] Final Memory: 303M/1016M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/logs-0900-tomcat/test.log
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-ear/2.1-SNAPSHOT/car
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-client/2.1-SNAPSHOT/car
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] 09:51:18,363 WARN [AbstractGBeanReference] GBean references are
not using proxies
[INFO] [INFO] 09:51:19,939 INFO [Log4jService]
--
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Started Logging Service
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Runtime Information:
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Install Directory =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] JVM in use = Sun Microsystems
Inc. Java 1.5.0_12
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] Java Information:
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.name] = Java(TM) 2 Runtime Environment, Standard Edition
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property [os.name]
= Linux
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property [os.version]
= 2.6.18-8.el5
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[sun.os.patch.level] = unknown
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property [os.arch]
= i386
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.class.version] = 49.0
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property [locale]
= en_US
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[unicode.encoding]= UnicodeLittle
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[file.encoding] = ANSI_X3.4-1968
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.vm.name]= Java HotSpot(TM) Server VM
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.vendor] = Sun Microsystems Inc.
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.info]= mixed mode
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property [java.home]
= /usr/lib/jvm/jdk1.5.0_12/jre
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.classpath] = null
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.library.path] =
/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/server:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.endorsed.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed:/usr/lib/jvm/jdk1.5.0_12/jre/lib/endorsed
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.ext.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/ext:/usr/lib/jvm/jdk1.5.0_12/jre/lib/ext
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[sun.boot.class.path] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-spec-corba-1.0-incubating-r602900.jar:/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-rmi-spec-1.0-incubating-r602900.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/rt.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i18n.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib
[BUILD] 2.1: Failed for Revision: 613167
Geronimo Revision: 613167 built with tests included
See the full build-0900.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/build-0900.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080118
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes
[INFO] Finished at: Fri Jan 18 09:41:03 EST 2008
[INFO] Final Memory: 303M/1016M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080118/logs-0900-tomcat/test.log
[INFO] [INFO] Started module(s):
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-ear/2.1-SNAPSHOT/car
[INFO] [INFO] [0]
org.apache.geronimo.testsuite/corba-marshal-client/2.1-SNAPSHOT/car
[INFO] [INFO] [geronimo:run-client {execution: run-client}]
[INFO] [INFO] Geronimo Home:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] Starting Geronimo client...
[INFO] [INFO] 09:51:18,363 WARN [AbstractGBeanReference] GBean references are
not using proxies
[INFO] [INFO] 09:51:19,939 INFO [Log4jService]
--
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Started Logging Service
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Runtime Information:
[INFO] [INFO] 09:51:19,939 INFO [Log4jService] Install Directory =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] JVM in use = Sun Microsystems
Inc. Java 1.5.0_12
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] Java Information:
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.name] = Java(TM) 2 Runtime Environment, Standard Edition
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property
[java.runtime.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property [os.name]
= Linux
[INFO] [INFO] 09:51:19,940 INFO [Log4jService] System property [os.version]
= 2.6.18-8.el5
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[sun.os.patch.level] = unknown
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property [os.arch]
= i386
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.class.version] = 49.0
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property [locale]
= en_US
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[unicode.encoding]= UnicodeLittle
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[file.encoding] = ANSI_X3.4-1968
[INFO] [INFO] 09:51:19,941 INFO [Log4jService] System property
[java.vm.name]= Java HotSpot(TM) Server VM
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.vendor] = Sun Microsystems Inc.
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.version] = 1.5.0_12-b04
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.vm.info]= mixed mode
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property [java.home]
= /usr/lib/jvm/jdk1.5.0_12/jre
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.classpath] = null
[INFO] [INFO] 09:51:19,942 INFO [Log4jService] System property
[java.library.path] =
/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386/server:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i386:/usr/lib/jvm/jdk1.5.0_12/jre/../lib/i386
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.endorsed.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed:/usr/lib/jvm/jdk1.5.0_12/jre/lib/endorsed
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[java.ext.dirs] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/ext:/usr/lib/jvm/jdk1.5.0_12/jre/lib/ext
[INFO] [INFO] 09:51:19,943 INFO [Log4jService] System property
[sun.boot.class.path] =
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-spec-corba-1.0-incubating-r602900.jar:/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/lib/endorsed/yoko-rmi-spec-1.0-incubating-r602900.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/rt.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/i18n.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.5.0_12/jre/lib
ignore
test please ignore
Is there a caching order problem with authentication challenges?
While working through the code looking to add hooks for signaling the
monitoring events, I noticed the following bit of code in the
ResponseFuture:
//Authenticate
int authCount = request.getAuthCount() + 1;
if (authCount <= 3) {
request.setAuthCount(authCount);
client.sendRequest(request);
// if we've been provided with a cache, put this session
into
// the cache.
SessionCache cache = getSessionCache();
if (cache != null) {
// cache the session before we return
cache.cacheSession(ioSession);
}
return;
}
This is sending the challenge response back to the server, but returning
the connection to the cache AFTER the request is sent back. Shouldn't
the connection be returned to the cache BEFORE the challenge response is
sent to allow the connection to be reused?
Rick
[jira] Closed: (GERONIMO-1265) Preserve comments added by users in the config.xml file
[ https://issues.apache.org/jira/browse/GERONIMO-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh closed GERONIMO-1265. --- > Preserve comments added by users in the config.xml file > --- > > Key: GERONIMO-1265 > URL: https://issues.apache.org/jira/browse/GERONIMO-1265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: startup/shutdown, usability >Affects Versions: 1.0-M5, 1.0, 1.1, 2.1 >Reporter: John Sisson >Assignee: Jay D. McHugh > Fix For: 2.1 > > Attachments: geronimo-1265.patch > > > Currently if a user adds comments to the config.xml file, they will be lost > when Geronimo re-generates the file if a configuration change is made (e.g. > through the web console). > As a temporary measure, the code that re-generates the XML will place a > warning at the top of the file warning users not to place comments in it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-1265) Preserve comments added by users in the config.xml file
[ https://issues.apache.org/jira/browse/GERONIMO-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay D. McHugh resolved GERONIMO-1265. - Resolution: Fixed Fix Version/s: 2.1 No one has commented that they wanted the additional functionality that I had been holding this issue open for. So I am closing it. We can create a new JIRA or reopen this one later if anyone decides that we want that (or some other) comment functionality later. > Preserve comments added by users in the config.xml file > --- > > Key: GERONIMO-1265 > URL: https://issues.apache.org/jira/browse/GERONIMO-1265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: startup/shutdown, usability >Affects Versions: 1.0-M5, 1.0, 1.1, 2.1 >Reporter: John Sisson >Assignee: Jay D. McHugh > Fix For: 2.1 > > Attachments: geronimo-1265.patch > > > Currently if a user adds comments to the config.xml file, they will be lost > when Geronimo re-generates the file if a configuration change is made (e.g. > through the web console). > As a temporary measure, the code that re-generates the XML will place a > warning at the top of the file warning users not to place comments in it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [YOKO] premature tools deletion?
By the time we release it, it will be renamed to o.a.cxf.something. Right now, I'm leaving the package name alone as I merge in some patches that IONA has internally to update it to work with the latest CXF (and latest CXF dependencies like the newer XmlSchema and such). If the package names change, those patches won't apply cleanly. Once it all builds and tests cleanly, the package names will change. Dan On Friday 18 January 2008, Lars Kühne wrote: > I assume tools will also live in CXF for the IDL<->WSDL compilers. If > we keep our own copy (which I think is a good idea) we need to make > sure that our package name is different from theirs. I assume they > will eventually use o.a.cxf.something, but currently they are not: > http://svn.apache.org/viewvc/incubator/cxf/trunk/tools/corba/src/main/ >java/org/apache/yoko/tools/ > > On Jan 17, 2008 7:47 PM, Matt Hogstrom wrote: > > Keep 'em around, we can always whack them later. > > > > On Jan 17, 2008, at 1:51 AM, Alan D. Cabrera wrote: > > > I was wondering if we prematurely deleted tools. It would be nice > > > to have our own IDL compiler. I was thinking that we could move > > > tools to a dir in the sandbox for someone to pick up. Thoughts? > > > > > > > > > Regards, > > > Alan -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
RE: Geronimo 2.0.2 starts on Harmony!
> What do you mean by "HTTP interface works badly"? Slow? Exceptions? It only shows the left frame. The HTML source of the page seems truncated at some point. I couldn't find any entries in the log concerning this problem, I'd investigate further. > What platform are you using? Linux or Windows? Windows XP Pro on my notebook. > As far as I understood you already got a patch for GERONIMO-3757. > If so could you please attach it to the issue? :) What I have now is not a patch, but a hotfix workaround. Sure, I'll try to make a valid patch out of it. What I'm not sure is how should I check the patch before it can be considered valid - sure I can run GUT on Sun and Harmony, but otherwise there's so many Geronimo release bundles and platforms that it would be difficult to make sure I didn't break anything in complex Geronimo structure. > I also think that it would be nice to add the list of Harmony > and Geronimo issues related to Geronimo on Harmony to the wiki page > you have created. Well, I have all the actual issues mentioned there. Do you mean it makes sense to have a separate listing of JIRA numbers somewhere? Do you mean only actual open issues, or fixed/closed also? Vasily -Original Message- From: Alexey Petrenko [mailto:[EMAIL PROTECTED] Sent: Friday, January 18, 2008 2:57 AM To: dev@geronimo.apache.org Subject: Re: Geronimo 2.0.2 starts on Harmony! Great news, Vasily! What do you mean by "HTTP interface works badly"? Slow? Exceptions? What platform are you using? Linux or Windows? As far as I understood you already got a patch for GERONIMO-3757. If so could you please attach it to the issue? :) I also think that it would be nice to add the list of Harmony and Geronimo issues related to Geronimo on Harmony to the wiki page you have created. Thanks in advance. SY, Alexey 2008/1/18, Zakharov, Vasily M <[EMAIL PROTECTED]>: > Hi, all, > > Well, finally I can say Geronimo 2.0.2 starts and works on Apache > Harmony! > Some steps yet need to be taken for that to happen - see [1] for > details. > > Some issues were overcome, some workarounded, and some just hotfixed and > wait for their proper resolution, like GERONIMO-3757. > > Three important problems that still need investigation are: > - HTTP interface works badly (HTTPS works fine). > - The application takes up all the CPU resources on both cores I have > available so the machine is 100% busy. > - The application takes up all the memory specified in -Xms option. > > Otherwise, I was able to browse the console freely and even deploy > SPECjAppServer2004. > No serious load was tested however. > > Vasily Zakharov > Intel ESSD > > [1] http://cwiki.apache.org/confluence/display/GMOxDOC20/Apache+Harmony > >
[jira] Created: (GERONIMO-3760) Geronimo Tomcat Clustering - Support for disabling multicasting and adding only static members
Geronimo Tomcat Clustering - Support for disabling multicasting and adding only static members -- Key: GERONIMO-3760 URL: https://issues.apache.org/jira/browse/GERONIMO-3760 Project: Geronimo Issue Type: Wish Security Level: public (Regular issues) Components: Clustering Reporter: Shiva Kumar H R Fix For: Wish List This is opened as a feature request on Tomcat bug tracker: http://issues.apache.org/bugzilla/show_bug.cgi?id=44264 Once it is supported in Tomcat, check to see if any configuration elements need to be added in Geronimo's config.xml to expose this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Geronimo 2.0.2 starts on Harmony!
It's not the latest, but rather recent - I used r610339. Hmm, good idea, thanks! :) Vasily -Original Message- From: Jarek Gawor [mailto:[EMAIL PROTECTED] Sent: Friday, January 18, 2008 2:49 AM To: dev@geronimo.apache.org Subject: Re: Geronimo 2.0.2 starts on Harmony! Cool! Is this with latest Harmony snapshot? Also, if you rename or remove the bin/jpa.jar you should be able to use the Geronimo scripts to start up the server. Jarek On Jan 17, 2008 6:15 PM, Zakharov, Vasily M <[EMAIL PROTECTED]> wrote: > Hi, all, > > Well, finally I can say Geronimo 2.0.2 starts and works on Apache > Harmony! > Some steps yet need to be taken for that to happen - see [1] for > details. > > Some issues were overcome, some workarounded, and some just hotfixed and > wait for their proper resolution, like GERONIMO-3757. > > Three important problems that still need investigation are: > - HTTP interface works badly (HTTPS works fine). > - The application takes up all the CPU resources on both cores I have > available so the machine is 100% busy. > - The application takes up all the memory specified in -Xms option. > > Otherwise, I was able to browse the console freely and even deploy > SPECjAppServer2004. > No serious load was tested however. > > Vasily Zakharov > Intel ESSD > > [1] http://cwiki.apache.org/confluence/display/GMOxDOC20/Apache+Harmony > > Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
[jira] Created: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
Geronimo Tomcat Clustering - No GBeans for adding Static Members Key: GERONIMO-3759 URL: https://issues.apache.org/jira/browse/GERONIMO-3759 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Clustering Reporter: Shiva Kumar H R Fix For: 2.1 Tomcat uses multicasting for discovering cluster members. It also supports static memberships using the StaticMembershipInterceptor if you want to extend your membership to points beyond multicasting, using configuration as below: http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html However, to add this configuration in Geronimo's config.xml, we don't have the required GBeans for element. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2435) Shutdown doesn't require valid credentials
[ https://issues.apache.org/jira/browse/GERONIMO-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2435. -- Resolution: Cannot Reproduce Assignee: David Jencks we have 3 people who can't reproduce this time to close it. > Shutdown doesn't require valid credentials > -- > > Key: GERONIMO-2435 > URL: https://issues.apache.org/jira/browse/GERONIMO-2435 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security, startup/shutdown >Affects Versions: 1.2 > Environment: [EMAIL PROTECTED] /cygdrive/c/oss/geronimo > $ svn info > Path: . > URL: https://svn.apache.org/repos/asf/geronimo/server/trunk > Repository Root: https://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 449803 > Node Kind: directory > Schedule: normal > Last Changed Author: djencks > Last Changed Rev: 449797 > Last Changed Date: 2006-09-25 22:05:13 +0200 (Mon, 25 Sep 2006) > Properties Last Updated: 2006-09-13 16:27:07 +0200 (Wed, 13 Sep 2006) >Reporter: Jacek Laskowski >Assignee: David Jencks > > 1/ Run geronimo-tomcat-j2ee with ./bin/startup.sh > 2/ Run ./bin/shutdown.sh. When asked about Username and password enter > whatever comes to your mind, say x/x > 3/ Notice that although the credenatials are wrong, the server shutdown > procedure begins (@see var/log/geronimo.out) > Server shutdown begun > ... > Server shutdown completed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3467) Confusing security exception thrown while authenticating using JMX with a just starting server
[
https://issues.apache.org/jira/browse/GERONIMO-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560307#action_12560307
]
David Jencks commented on GERONIMO-3467:
I'm not sure we should be doing anything differently. We've generally tried to
avoid exporting any information on just why authentication failed. How is this
a bug?
> Confusing security exception thrown while authenticating using JMX with a
> just starting server
> --
>
> Key: GERONIMO-3467
> URL: https://issues.apache.org/jira/browse/GERONIMO-3467
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
>Affects Versions: 2.0.2, 2.0.x, 2.1
>Reporter: Shiva Kumar H R
> Fix For: 2.0.x, 2.1
>
>
> Scenario is as below:
> Let's say server is starting and
> org.apache.geronimo.configs/rmi-naming/2.0.1/car has started, but
> org.apache.geronimo.configs/j2ee-security/2.0.1/car hasn't yet started. If an
> external entity (like Geronimo Eclipse Plug-in) now tries to connect to the
> kernel remotely through JMX, although rmi connection succeeds, authenticate
> will fail (because security realm has not yet been started).
> In this case, org.apache.geronimo.jmxremoting.Authenticator.authenticate() is
> getting a LoginException with error
> "javax.security.auth.login.LoginException: No LoginModules configured for
> geronimo-admin". However this exception is not propogated, but rather is
> thrown back as a 'SecurityException("Invalid login")'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2446) Creating sql security realm fails in Geronimo 1.1.1
[
https://issues.apache.org/jira/browse/GERONIMO-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560304#action_12560304
]
David Jencks commented on GERONIMO-2446:
At some point I added some code to try to avoid the jdbc classloader
weirdness I wonder if that code fixed this problem?
> Creating sql security realm fails in Geronimo 1.1.1
> ---
>
> Key: GERONIMO-2446
> URL: https://issues.apache.org/jira/browse/GERONIMO-2446
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
>Affects Versions: 1.1.1
> Environment: Geronimo 1.1.1 Jetty version with J2SDK 1.4.1_11
> running von Windows 2003 Server
>Reporter: Markus Hanecke
>
> In opposite to Geronimo 1.0 it is not possible to create an SQL-based
> security realm in Geronimo 1.1.1
> In the last step where I can test the new ream I'll always get the result
> "Login failed".
> The logfile (geronimo.log) says:
> 07:33:15,193 WARN [SecurityRealmPortlet] Testing with options
> {dataSourceName=testpool, dataSourceApplication=null,
> org.apache.geronimo.security.realm.GenericSecurityRealm.CLASSLOADER=[org.apache.geronimo.kernel.classloader.JarFileClassLoader
> id=geronimo/webconsole-jetty_standard.war/1.1.1/car], groupSelect=select
> userid, groupname
> from groups where userid=?, userSelect=select userid, password from users
> where userid=?}
> 07:34:19,159 WARN [SecurityRealmPortlet] Test login failed
> javax.security.auth.login.LoginException: SQL error
> at
> org.apache.geronimo.security.realm.providers.SQLLoginModule.login(SQLLoginModule.java:238)
> at
> org.apache.geronimo.console.util.KernelManagementHelper.testLoginModule(KernelManagementHelper.java:414)
> at
> org.apache.geronimo.console.util.PortletManager.testLoginModule(PortletManager.java:159)
> at
> org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.actionAttemptLogin(SecurityRealmPortlet.java:316)
> at
> org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.processAction(SecurityRealmPortlet.java:200)
> at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
> at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
> at
> org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:104)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
> at
> org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
> at
> org.apache.geronimo.jetty.JettyWebApplicationHandler.dispatch(JettyWebApplicationHandler.java:59)
> at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:283)
> at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:163)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120)
> at
> org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68)
> at
> org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164)
> at
> org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82)
> at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
> at
> org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:104)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
> at
> org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
> at
> org.apache.geronimo.jetty.JettyWebApplicationHandler.dispatch(JettyWebApplicationHandler.java:59)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl
[jira] Closed: (GERONIMO-3486) GBean order makes security work?
[ https://issues.apache.org/jira/browse/GERONIMO-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3486. -- Resolution: Won't Fix Fix Version/s: 2.1 Assignee: David Jencks The CredentialStore is using the test-realm to log in the stuff it knows about, so the test-realm needs to be set up. A better way to do this would be to use a gbean-dependency between the credential store and the security realm. I don't see a good way to fix this generically. The security realm might be in a different module and there might be several security realms used in a credential store. > GBean order makes security work? > > > Key: GERONIMO-3486 > URL: https://issues.apache.org/jira/browse/GERONIMO-3486 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.0.2, 2.0.x, 2.1 >Reporter: Jarek Gawor >Assignee: David Jencks > Fix For: 2.1 > > > I was trying to fix the testsuite/enterprise-testsuite/sec-tests tests. > Initially, the test were failing with > "javax.security.auth.login.LoginException: No LoginModules configured". After > trying a few things, I switched the order of GBeans in the deployment plan > and that made the tests pass. See > http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/enterprise-testsuite/sec-tests/sec-ejb/src/main/resources/META-INF/openejb-jar.xml?r1=560771&r2=579469. > > I'm not sure if this is a bug or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3076) Request to add Security Realm dependencies from the web console
[ https://issues.apache.org/jira/browse/GERONIMO-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-3076: --- Component/s: (was: security) console I think this is a request that the security realm wizard should generate a new plan and allow you to select whatever dependencies you want for it. It doesn't really have anything to do with security per se. > Request to add Security Realm dependencies from the web console > --- > > Key: GERONIMO-3076 > URL: https://issues.apache.org/jira/browse/GERONIMO-3076 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.0-M4 > Environment: all >Reporter: Bill Brown > > Greetings: > I am not sure if this has already been requested. I have a custom jaas > security realm I use for authentication. The realm depends on a library in > the common lib. When the server is down I can add the dependency tag in the > gbean for the realm in the config.xml file. I think it would be a neat > feature to be able to add this and other dependencies to the realm from > within the web console while the server is running without having to edit the > config.xml server when the server is stopped. > Thanks for the consideration. > Bill. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2617) Custom Authorization
[ https://issues.apache.org/jira/browse/GERONIMO-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2617. -- Resolution: Incomplete Assignee: David Jencks I can't tell well enough what you want here. I think you may want to implement a custom jacc implementation. You might want something like triplesec. But without much clearer goals we won't get too far. > Custom Authorization > > > Key: GERONIMO-2617 > URL: https://issues.apache.org/jira/browse/GERONIMO-2617 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: security >Reporter: Diego L Espineira >Assignee: David Jencks > > Apache Geronimo to enable the developer to implement custom and complex > security models, such as role hierarchies and permission inheritance between > roles. This can be accomplished by adding an optional parameter to the > security realm options specifying some class to intercept and handle the > authorization to EJBs, WebServices and web content (JSP, html etc) by > applying custom and application specific authorization based on information > stored in somewhere else (like a DBMS). > This enables an application to allow its users to change the EJB methods and > content permissions through the application itself. The authentication and > authorization settings is widely wrongly assigned to deployment time, while > it must be assigned much of it to run time. > An example of this is the JBoss SX approach to this subject. An application > security realm is configured to use an "authorization manager", which is a > class that implements org.jboss.security.SecurityProxy. And it handles the > requests to all the resources like EJBs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2336) JSR 196: JavaTM Authentication Service Provider Interface for Containers API
[ https://issues.apache.org/jira/browse/GERONIMO-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560298#action_12560298 ] David Jencks commented on GERONIMO-2336: umm, its a dup of 3417. > JSR 196: JavaTM Authentication Service Provider Interface for Containers API > > > Key: GERONIMO-2336 > URL: https://issues.apache.org/jira/browse/GERONIMO-2336 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: security >Reporter: Alan Cabrera >Assignee: David Jencks > > JSR196 API in geronimo/specs/brances/jsr196 > (http://jcp.org/en/jsr/detail?id=196) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2336) JSR 196: JavaTM Authentication Service Provider Interface for Containers API
[ https://issues.apache.org/jira/browse/GERONIMO-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2336. -- Resolution: Duplicate Assignee: David Jencks Closing the earlier of the duplicate issues to pretend we are not letting our jiras drag on so long :-) > JSR 196: JavaTM Authentication Service Provider Interface for Containers API > > > Key: GERONIMO-2336 > URL: https://issues.apache.org/jira/browse/GERONIMO-2336 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: security >Reporter: Alan Cabrera >Assignee: David Jencks > > JSR196 API in geronimo/specs/brances/jsr196 > (http://jcp.org/en/jsr/detail?id=196) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2301) Missing features in Keystore interface
[ https://issues.apache.org/jira/browse/GERONIMO-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2301. -- Resolution: Fixed Fix Version/s: 2.1 Assignee: David Jencks I don't know when they were added but these methods (with appropriate password arguments) are in the current KeystoreInstance interface. > Missing features in Keystore interface > -- > > Key: GERONIMO-2301 > URL: https://issues.apache.org/jira/browse/GERONIMO-2301 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: security >Affects Versions: 1.1 >Reporter: Guillaume Nodet >Assignee: David Jencks > Fix For: 2.1 > > > To provide ws-security for outbound messages while leveraging Geronimo > keystores, a few methods are missing on the KeystoreInstance interface: > > String getCertificateAlias(Certificate cert); > Certificate[] getCertificateChain(String alias); > PrivateKey getPrivateKey(String alias); > These methods are needed to implement > http://ws.apache.org/wss4j/apidocs/org/apache/ws/security/components/crypto/Crypto.html > See an abstract base class that could be used to implement this interface on > top of geronimo Keystores > > http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-soap/src/main/java/org/apache/servicemix/soap/handlers/security/BaseCrypto.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1747) HTTP-methods checks
[ https://issues.apache.org/jira/browse/GERONIMO-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-1747. -- Resolution: Fixed Fix Version/s: 2.1 Assignee: David Jencks I think the problem was an incorrect regular expression in the servlet schema. I believe its been fixed. > HTTP-methods checks > --- > > Key: GERONIMO-1747 > URL: https://issues.apache.org/jira/browse/GERONIMO-1747 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 1.0 > Environment: Windows 2003, java 1.4 >Reporter: Ilya Platonov >Assignee: David Jencks > Fix For: 2.1 > > Attachments: slide.war, web.xml > > > I'm tring to run jakarta-slide web-application on geronimo application > server. Slide provides WebDAV support. > When security constrain is not set, everything works fine exept some minor > issues but when I put some security constraints for servlets I got following > error in server.log. > 15:43:58,132 ERROR [CoyoteAdapter] An exception or error occurred in the > container during the request processing > java.lang.IllegalArgumentException: Invalid HTTPMethodSpec > at javax.security.jacc.HTTPMethodSpec.(HTTPMethodSpec.java:114) > at > javax.security.jacc.WebUserDataPermission.(WebUserDataPermission.java:84) > at > org.apache.geronimo.tomcat.realm.TomcatGeronimoRealm.hasUserDataPermission(TomcatGeronimoRealm.java:123) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:428) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:262) > at > org.apache.geronimo.tomcat.valve.PolicyContextValve.invoke(PolicyContextValve.java:50) > 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.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:534) > When I looked through Geronimo source code I found that "GET", "POST", "PUT", > "DELETE", "HEAD", "OPTIONS" and "TRACE" http-methods hardcoded into > HTTPMethodSpec class and if you tring to use another method it throws this > exception. Problem is that WebDAV specification extends standard > HTTP-methods, for example it uses MKCOL and LOCK methods so jakarta-slide > just not working. > Is there any workaround for this bug or geronimo is just not able to handle > any HTTP protocol extensions??? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-527) Should do better parameter checking in login modules
[ https://issues.apache.org/jira/browse/GERONIMO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-527. - Resolution: Fixed Fix Version/s: (was: 1.x) 2.1 Assignee: Vamsavardhana Reddy (was: Alan Cabrera) IMO vamsi's extensive login module review has this one more than covered. > Should do better parameter checking in login modules > > > Key: GERONIMO-527 > URL: https://issues.apache.org/jira/browse/GERONIMO-527 > Project: Geronimo > Issue Type: Improvement > Components: security >Reporter: Alan Cabrera >Assignee: Vamsavardhana Reddy > Fix For: 2.1 > > > Should do better parameter checking in login modules -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1384) Provide default security realm for web-apps with secured pages deployed without a plan
[ https://issues.apache.org/jira/browse/GERONIMO-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-1384. -- Resolution: Fixed Fix Version/s: (was: Wish List) 2.1 Assignee: David Jencks this was fixed a long time ago. Apps won't deploy if they have security configuration in the spec dds but no geronimo plan describing how to login and get to the app roles. I would need some argument that deploying a secured app with no geronimo security configuration and only allowing access to unsecured pages is a good idea. > Provide default security realm for web-apps with secured pages deployed > without a plan > -- > > Key: GERONIMO-1384 > URL: https://issues.apache.org/jira/browse/GERONIMO-1384 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: security, web >Affects Versions: 1.0-M5 >Reporter: Aaron Mulder >Assignee: David Jencks >Priority: Minor > Fix For: 2.1 > > Attachments: security-reject.patch > > > If you deploy a web application with certain pages/URLs protected by a login, > but you don't include a Geronimo deployment plan, all those pages/URLs are > unprotected. To replicate: > Deploy this with no plan: > http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-demo-1.0-SNAPSHOT.war > and then visit http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and > click the links to "secure" and "forbidden". Both links work, with no login > prompt. Instead, you should get a login prompt and (since no realm was > configured) all logins should fail. > The web.xml in this case contains: > > > Admin Role > /protect/* > > > content-administrator > > > > > > No Access > /forbidden/* > > > > > FORM > MYREALM > > /auth/logon.html?param=test > /auth/logonError.html?param=test > > > > content-administrator > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-481) HTTPS Connector should work with a keystore GBean
[ https://issues.apache.org/jira/browse/GERONIMO-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560279#action_12560279 ] David Jencks commented on GERONIMO-481: --- this was implemented for jetty a long time ago. > HTTPS Connector should work with a keystore GBean > - > > Key: GERONIMO-481 > URL: https://issues.apache.org/jira/browse/GERONIMO-481 > Project: Geronimo > Issue Type: Improvement > Components: security, web >Reporter: Jeremy Boynes > Fix For: 1.x > > > It currently looks directly at the keystore file. > We should have a GBean manage the certificates just using the file for > persistence if necessary. The HTTPS connector should then get its certs from > the GBean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3758) put our default jacc provider implementation into a different package than the required container stuff.
[ https://issues.apache.org/jira/browse/GERONIMO-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3758. -- Resolution: Fixed Implemented in rev 613094. > put our default jacc provider implementation into a different package than > the required container stuff. > > > Key: GERONIMO-3758 > URL: https://issues.apache.org/jira/browse/GERONIMO-3758 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.1 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.1 > > > It's too hard to tell which jacc classes are the container framework and > which are our default jacc provider implementation. Putting the latter into > a separate package should help people figure out how to integrate other jacc > providers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
