[BUILD] branches/2.1: Failed for Revision: 991820
Geronimo Revision: 991820 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100902/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100902/unit-test-reports this realm = plexus.core urls[0] = file:/usr/local/maven/lib/maven-2.0.9-uber.jar Number of imports: 6 import: org.codehaus.classworlds.en...@4891bb28 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@c51bc9e7 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Lorg/codehaus/mojo/jspc/compiler/JspCompiler; [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.codehaus.mojo.jspc.CompileMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93
[BUILD] trunk: Failed for Revision: 991823
Geronimo Revision: 991823 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_1-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_1-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots
[jira] Created: (GERONIMO-5569) fail to login the encoding options of Properties File Login Modul
fail to login the encoding options of Properties File Login Modul - Key: GERONIMO-5569 URL: https://issues.apache.org/jira/browse/GERONIMO-5569 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment, security Affects Versions: 3.0 Environment: « Hide OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 setps to recur: 1.Start the server 2.Copy users-sha1-hex.properties users-md5-base64.properties to server_root/var/security directory 3.Deploy the plan. Note: This does not require an archive.For v2.1 or later, using this plan prop-md5-base64_v2.1.xml instead. 4.Deploy realm-md5-test-webapp.war using realm-md5-test-plan.xml. 5.Open a browser window and access http://localhost:8080/prop-md5-test/secure/secure.jsp using UID/PWD: system/manager 6.Deploy the plan prop-sha1-hex_v1.0.xml Note: This does not require an archive.For v2.1 or later, using this plan prop-sha1-hex_v2.1.xml instead. 7.Deploy realm-sha1-test-webapp.war using realm-sha1-test-plan.xml 8.Open a new browser window and access http://localhost:8080/prop-sha1-test/secure/secure.jsp using UID/PWD: system/manager when you execute step4 and step7, you will find this log info: 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:861610605766878 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'plugin.Deployment!-2135677113|0' 2010-09-02 15:58:36,843 WARN [Parameters] Parameters: Invalid chunk '' ignored. 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:37,515 INFO [config] Extracting jar: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp.war 2010-09-02 15:58:37,531 INFO [config] Extracted path: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp 2010-09-02 15:58:49,218 ERROR [DeploymentPortlet] Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] at org.apache.geronimo.deployment.DeploymentContext.getConfigurationData(DeploymentContext.java:534) at org.apache.geronimo.deployment.Deployer.install(Deployer.java:342) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:265) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
[jira] Updated: (GERONIMO-5568) fail to asembly custom server via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5568: - Attachment: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip all the file I mentioned above in this zip package fail to asembly custom server via admin console Key: GERONIMO-5568 URL: https://issues.apache.org/jira/browse/GERONIMO-5568 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: hello-2.1.1.2.war setps to recur: 1、start geronimo server 2、Install hello sample (click deploy new) (attachment) 3、Open Applications -- Plugins portlet(first clickcreate Geronimo plug-in,choose hello,then export the plug-in) 4、Click Assemble a Server button then you will find following infomation: ERROR [[car-export]] Servlet.service() for servlet car-export threw exception java.lang.NullPointerException at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.writeToZip(RepositoryConfigurationStore.java:280) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.exportConfiguration(RepositoryConfigurationStore.java:268) at org.apache.geronimo.console.car.CARExportServlet.doGet(CARExportServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:655) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:443) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) at org.apache.geronimo.console.servlet.GenericForwardServlet.doPost(GenericForwardServlet.java:154) at org.apache.geronimo.console.servlet.GenericForwardServlet.doGet(GenericForwardServlet.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:89) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:260) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:241) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:371) at
[jira] Updated: (GERONIMO-5568) fail to asembly custom server via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5568: - Attachment: (was: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip) fail to asembly custom server via admin console Key: GERONIMO-5568 URL: https://issues.apache.org/jira/browse/GERONIMO-5568 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: hello-2.1.1.2.war setps to recur: 1、start geronimo server 2、Install hello sample (click deploy new) (attachment) 3、Open Applications -- Plugins portlet(first clickcreate Geronimo plug-in,choose hello,then export the plug-in) 4、Click Assemble a Server button then you will find following infomation: ERROR [[car-export]] Servlet.service() for servlet car-export threw exception java.lang.NullPointerException at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.writeToZip(RepositoryConfigurationStore.java:280) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.exportConfiguration(RepositoryConfigurationStore.java:268) at org.apache.geronimo.console.car.CARExportServlet.doGet(CARExportServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:655) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:443) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) at org.apache.geronimo.console.servlet.GenericForwardServlet.doPost(GenericForwardServlet.java:154) at org.apache.geronimo.console.servlet.GenericForwardServlet.doGet(GenericForwardServlet.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:89) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:260) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:241) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:371) at
[jira] Updated: (GERONIMO-5569) fail to login the encoding options of Properties File Login Modul
[ https://issues.apache.org/jira/browse/GERONIMO-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5569: - Attachment: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip all the file I mentioned above are in this zip fail to login the encoding options of Properties File Login Modul - Key: GERONIMO-5569 URL: https://issues.apache.org/jira/browse/GERONIMO-5569 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, security Affects Versions: 3.0 Environment: « Hide OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip setps to recur: 1.Start the server 2.Copy users-sha1-hex.properties users-md5-base64.properties to server_root/var/security directory 3.Deploy the plan. Note: This does not require an archive.For v2.1 or later, using this plan prop-md5-base64_v2.1.xml instead. 4.Deploy realm-md5-test-webapp.war using realm-md5-test-plan.xml. 5.Open a browser window and access http://localhost:8080/prop-md5-test/secure/secure.jsp using UID/PWD: system/manager 6.Deploy the plan prop-sha1-hex_v1.0.xml Note: This does not require an archive.For v2.1 or later, using this plan prop-sha1-hex_v2.1.xml instead. 7.Deploy realm-sha1-test-webapp.war using realm-sha1-test-plan.xml 8.Open a new browser window and access http://localhost:8080/prop-sha1-test/secure/secure.jsp using UID/PWD: system/manager when you execute step4 and step7, you will find this log info: 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:861610605766878 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'plugin.Deployment!-2135677113|0' 2010-09-02 15:58:36,843 WARN [Parameters] Parameters: Invalid chunk '' ignored. 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:37,515 INFO [config] Extracting jar: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp.war 2010-09-02 15:58:37,531 INFO [config] Extracted path: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp 2010-09-02 15:58:49,218 ERROR [DeploymentPortlet] Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] at
[jira] Updated: (GERONIMO-5569) fail to login the encoding options of Properties File Login Modul
[ https://issues.apache.org/jira/browse/GERONIMO-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5569: - Attachment: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip all the file I mentioned above are in this zip fail to login the encoding options of Properties File Login Modul - Key: GERONIMO-5569 URL: https://issues.apache.org/jira/browse/GERONIMO-5569 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, security Affects Versions: 3.0 Environment: « Hide OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip setps to recur: 1.Start the server 2.Copy users-sha1-hex.properties users-md5-base64.properties to server_root/var/security directory 3.Deploy the plan. Note: This does not require an archive.For v2.1 or later, using this plan prop-md5-base64_v2.1.xml instead. 4.Deploy realm-md5-test-webapp.war using realm-md5-test-plan.xml. 5.Open a browser window and access http://localhost:8080/prop-md5-test/secure/secure.jsp using UID/PWD: system/manager 6.Deploy the plan prop-sha1-hex_v1.0.xml Note: This does not require an archive.For v2.1 or later, using this plan prop-sha1-hex_v2.1.xml instead. 7.Deploy realm-sha1-test-webapp.war using realm-sha1-test-plan.xml 8.Open a new browser window and access http://localhost:8080/prop-sha1-test/secure/secure.jsp using UID/PWD: system/manager when you execute step4 and step7, you will find this log info: 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:861610605766878 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'plugin.Deployment!-2135677113|0' 2010-09-02 15:58:36,843 WARN [Parameters] Parameters: Invalid chunk '' ignored. 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:37,515 INFO [config] Extracting jar: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp.war 2010-09-02 15:58:37,531 INFO [config] Extracted path: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp 2010-09-02 15:58:49,218 ERROR [DeploymentPortlet] Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] at
[jira] Updated: (GERONIMO-5569) fail to login the encoding options of Properties File Login Modul
[ https://issues.apache.org/jira/browse/GERONIMO-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5569: - Attachment: (was: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip) fail to login the encoding options of Properties File Login Modul - Key: GERONIMO-5569 URL: https://issues.apache.org/jira/browse/GERONIMO-5569 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, security Affects Versions: 3.0 Environment: « Hide OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip setps to recur: 1.Start the server 2.Copy users-sha1-hex.properties users-md5-base64.properties to server_root/var/security directory 3.Deploy the plan. Note: This does not require an archive.For v2.1 or later, using this plan prop-md5-base64_v2.1.xml instead. 4.Deploy realm-md5-test-webapp.war using realm-md5-test-plan.xml. 5.Open a browser window and access http://localhost:8080/prop-md5-test/secure/secure.jsp using UID/PWD: system/manager 6.Deploy the plan prop-sha1-hex_v1.0.xml Note: This does not require an archive.For v2.1 or later, using this plan prop-sha1-hex_v2.1.xml instead. 7.Deploy realm-sha1-test-webapp.war using realm-sha1-test-plan.xml 8.Open a new browser window and access http://localhost:8080/prop-sha1-test/secure/secure.jsp using UID/PWD: system/manager when you execute step4 and step7, you will find this log info: 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:861610605766878 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'plugin.Deployment!-2135677113|0' 2010-09-02 15:58:36,843 WARN [Parameters] Parameters: Invalid chunk '' ignored. 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:37,515 INFO [config] Extracting jar: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp.war 2010-09-02 15:58:37,531 INFO [config] Extracted path: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp 2010-09-02 15:58:49,218 ERROR [DeploymentPortlet] Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] at
Re: [BUILD] branches/2.1: Failed for Revision: 990497
This is also preventing 2.2 build from passing. I can't recreate it locally.I checked the jspc plugin in private nexus and they look good to me. Can anyone have the build server access take a look ? On Mon, Aug 30, 2010 at 1:59 AM, Kevan Miller kevan.mil...@gmail.comwrote: There seems to be a problem with the maven configuration on the build system or the nexus repository that the build system is using. The contents of jspc-compiler-api-2.0-alpha-2.jar in the local repo on the build system contain a 301: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href= https://nexus.codehaus.org/content/repositories/releases/org/codehaus/mojo/jspc/jspc-compiler-api/2.0-alpha-2/jspc-compiler-api-2.0-alpha-2.jar here/a./p hr addressApache/2.0.52 (Red Hat) Server at repository.codehaus.org Port 80/address /body/html I don't see the problem locally. Hopefully the private nexus repo will get synced up, soon. If anybody is familiar with its configuration, maybe you could give it a kick? --kevan On Aug 29, 2010, at 8:10 AM, ga...@apache.org wrote: Geronimo Revision: 990497 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100829/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100829/unit-test-reports this realm = plexus.core urls[0] = file:/usr/local/maven/lib/maven-2.0.9-uber.jar Number of imports: 6 import: org.codehaus.classworlds.en...@4891bb28 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@c51bc9e7 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Lorg/codehaus/mojo/jspc/compiler/JspCompiler; [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more Caused by:
[jira] Updated: (GERONIMO-5569) fail to log in with the encoding options of properties file in login modular
[ https://issues.apache.org/jira/browse/GERONIMO-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5569: - Summary: fail to log in with the encoding options of properties file in login modular (was: fail to login the encoding options of Properties File Login Modul) fail to log in with the encoding options of properties file in login modular Key: GERONIMO-5569 URL: https://issues.apache.org/jira/browse/GERONIMO-5569 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, security Affects Versions: 3.0 Environment: « Hide OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 Attachments: VerifyDigestAndEncodingOptionsOfPropertiesFileLoginModule.zip setps to recur: 1.Start the server 2.Copy users-sha1-hex.properties users-md5-base64.properties to server_root/var/security directory 3.Deploy the plan. Note: This does not require an archive.For v2.1 or later, using this plan prop-md5-base64_v2.1.xml instead. 4.Deploy realm-md5-test-webapp.war using realm-md5-test-plan.xml. 5.Open a browser window and access http://localhost:8080/prop-md5-test/secure/secure.jsp using UID/PWD: system/manager 6.Deploy the plan prop-sha1-hex_v1.0.xml Note: This does not require an archive.For v2.1 or later, using this plan prop-sha1-hex_v2.1.xml instead. 7.Deploy realm-sha1-test-webapp.war using realm-sha1-test-plan.xml 8.Open a new browser window and access http://localhost:8080/prop-sha1-test/secure/secure.jsp using UID/PWD: system/manager when you execute step4 and step7, you will find this log info: 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:25,109 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:861610605766878 2010-09-02 15:58:27,578 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:27,578 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'plugin.Deployment!-2135677113|0' 2010-09-02 15:58:36,843 WARN [Parameters] Parameters: Invalid chunk '' ignored. 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] Hash value for page:/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113|0/__pmplugin0x2Deployment!-2135677113|0_view/__wsplugin0x2Deployment!-2135677113|0_normal is:-2346983809162886094 2010-09-02 15:58:36,843 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/2-1/Applications/Deployer/__acplugin0x2Deployment!-2135677113%7C0/__pmplugin0x2Deployment!-2135677113%7C0_view/__wsplugin0x2Deployment!-2135677113%7C0_normal 2010-09-02 15:58:37,515 INFO [config] Extracting jar: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp.war 2010-09-02 15:58:37,531 INFO [config] Extracted path: D:\server\geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT\var\temp\geronimo-deployer949419437165653088.tmpdir\realm-md5-test-webapp 2010-09-02 15:58:49,218 ERROR [DeploymentPortlet] Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns: [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] org.apache.geronimo.common.DeploymentException: Unable to resolve reference ConfigurationFactory in gbean tests/prop-md5-test/1.0/war?J2EEApplication=null,j2eeType=WebModule,name=tests/prop-md5-test/1.0/war to a gbean matching the pattern [?name=prop-md5-base64#org.apache.geronimo.security.jaas.ConfigurationFactory] due to: No matches for referencePatterns:
How to handle the naming context for those servlets added while starting web application
Hi, Yesterday, I just releaized that we might have a problem for servlet 3.0, in the new spec, it allows to add new servlets while starting the web application. In that case, how do we handle the bean scope naming context, seems we have no chance to build the naming context for that servlet, e.g. an EJB annotation, So far, I have not find words for it the spec, might need to double check it later. Any comment ? Thanks ! -- Ivan
[BUILD] branches/2.2: Failed for Revision: 991894
Geronimo Revision: 991894 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/unit-test-reports Number of imports: 10 import: org.codehaus.classworlds.en...@a6c57a42 import: org.codehaus.classworlds.en...@12f43f3b import: org.codehaus.classworlds.en...@20025374 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@92758522 import: org.codehaus.classworlds.en...@ebf2705b import: org.codehaus.classworlds.en...@bb25e54 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Lorg/codehaus/mojo/jspc/compiler/JspCompiler; [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:620) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:611) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.codehaus.mojo.jspc.CompileMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464
[BUILD] trunk: Failed for Revision: 991924
Geronimo Revision: 991924 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots
[jira] Commented: (GERONIMO-5228) Add classes for parsing a validation.xml descriptor
[ https://issues.apache.org/jira/browse/GERONIMO-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905543#action_12905543 ] Vamsavardhana Reddy commented on GERONIMO-5228: --- The built-in parser ValidationParser class in Bean Validation API tries to load the specified validation.xml file and constraint mapping files through the classloader API. At least in case of web applications, WEB-INF/validation.xml etc will not be available through web-app's classloader. So, there is definitely some work to be done here though we may use the JAXB generated classes from BVAL. Add classes for parsing a validation.xml descriptor --- Key: GERONIMO-5228 URL: https://issues.apache.org/jira/browse/GERONIMO-5228 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, naming Affects Versions: 3.0 Reporter: Rick McGuire Assignee: David Jencks Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-649) Can't build GEP trunk on 32-bit Mac
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905551#action_12905551
]
Tim Almdal commented on GERONIMODEVTOOLS-649:
-
For what it's worth I'm getting this issue with a version of the source
downloaded from trunk yesterday(Sept. 01, 2010):
Where was I supposed to put the updated maven-eclipsepde-plugin.jar file. In
the maven repository/eclipse plugin directory?
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] An invalid artifact was detected.
This artifact might be in your project's POM, or it might have been included
transitively during the resolution process. Here is the information we do have
for
this artifact:
o GroupID: org.eclipse.plugins
o ArtifactID: org.apache.geronimo.st.core
o Version: MISSING
o Type:jar
[INFO]
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.eclipse.plugins:org.apache.geronimo.st.core:null:jar}: The version cannot
be empty.
at
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
at
org.apache.maven.artifact.DefaultArtifact.init(DefaultArtifact.java:122)
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:70)
at
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:439)
at
org.apache.maven.project.MavenProject.createArtifacts(MavenProject.java:1651)
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1489)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Can't build GEP trunk on 32-bit Mac
Key: GERONIMODEVTOOLS-649
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Reporter: Delos Dai
Assignee: Delos Dai
Fix For: 3.0_M1, 3.0
Attachments: maven-eclipsepde-plugin-2.0.jar
Need to update eclipse/build.xml to make GEP build successfully on 32-bit
Mac. Eclipse 3.6 has dropped support for Mac carbon. The script should change
to Mac cocoa.
From Donald,
Could not build on MacOSX, as the referenced file no longer exists -
file=/technology/epp/downloads/release/helios/R/eclipse-jee-helios-macosx-carbon.tar.gz
Looks like we need to use the following 32bit Mac download instead in
eclipse/build.xml -
property name=helios_jee_macos
value=eclipse-jee-helios-macosx-cocoa.tar/
property name=helios_jee_macos-x86_64
value=eclipse-jee-helios-macosx-cocoa-x86_64.tar/
Also, I had to specify specific mirrors to use (like AWS) as the local
mirror didn't have the Helios files on it yet
--
This
Re: svn commit: r991866 - /geronimo/server/trunk/plugins/openwebbeans/pom.xml
Shouldn't this have been to 3.7.ga_1 rather than to 3.7.ga_2-SNAPSHOT? Rick On 9/2/2010 5:06 AM, genspr...@apache.org wrote: Author: genspring Date: Thu Sep 2 09:06:50 2010 New Revision: 991866 URL: http://svn.apache.org/viewvc?rev=991866view=rev Log: org.apache.servicemix.bundles.javassist 3.7.ga_1 was released. Modified: geronimo/server/trunk/plugins/openwebbeans/pom.xml Modified: geronimo/server/trunk/plugins/openwebbeans/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/openwebbeans/pom.xml?rev=991866r1=991865r2=991866view=diff == --- geronimo/server/trunk/plugins/openwebbeans/pom.xml (original) +++ geronimo/server/trunk/plugins/openwebbeans/pom.xml Thu Sep 2 09:06:50 2010 @@ -53,7 +53,7 @@ dependency groupIdorg.apache.servicemix.bundles/groupId artifactIdorg.apache.servicemix.bundles.javassist/artifactId -version3.7.ga_1-SNAPSHOT/version +version3.7.ga_2-SNAPSHOT/version /dependency dependency groupIdorg.apache.geronimo.bundles/groupId
[jira] Commented: (GERONIMODEVTOOLS-608) Publish with GEP takes minutes, while deploy takes seconds
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905614#action_12905614 ] Kory Markevich commented on GERONIMODEVTOOLS-608: - Since upgrading from 2.1 or so to the 2.2.0 version of the Eclipse plugin, we've started to see these same issues. Our application complexity is a bit more than the examples given here though, so our times are a little more extreme: after the upgrade we started seeing 20minutes to do a re-deploy. I did some debugging and found that almost all the time was spent dealing with dependencies. After applying the changes as described in the attachments, our re-deploy time went down to under a minute again. As is, the 2.2.0 plugin is unusable. Publish with GEP takes minutes, while deploy takes seconds -- Key: GERONIMODEVTOOLS-608 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: GEP 2.2 installed in Eclipse (galileo-SR1). Reporter: Boes Assignee: Delos Dai Attachments: getEnvironment.txt, HiThere.ear, HiThereSlow.ear, reorderModules.txt Publishing an Enterprise Application (EAR) with GEP to Geronimo takes much more time then deploying the same EAR to Geronimo using the console. See http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-td684484.html After doing some research I found that EAR's that have dependencies in geronimo-application.xml take a lot of time to publish. This is caused by the very inefficient implementation of the reorderModules method in the org.apache.geronimo.st.core.internal.DependencyHelper class. I installed a GEP development environment and put on tracing. It tested an EAR with 3 WAR's in it. In the EAR's geronimo-application.xml I added dependency tags for 4 libraries. Tracing shows that this results in parsing the geronimo-application.xml 1092 (!) times. In code this means that a call to DependencyHelper.getEnvironment is made 1092 times. Another inefficient part in the reorderModules method is that the call to DeploymentUtils.isInstalledModule is repeatedly made for the same module. In the test I found it was called at least 3 times for each dependent library. These calls result in a request to Geronimo and take almost a second each. The best way to solve this bug is to redesign the reordering process and make it work in a way that both DependencyHelper.getEnvironment and DeploymentUtils.isInstalledModule are not called more often then needed. I wonder why DeploymentUtils.isInstalledModule is called at all. Dependencies are defined in the xml. I can't imagine why it would matter if a module is installed in Geronimo or not. What I did to fix this problem and make GEP workable again for me is: - made sure the DeploymentUtils.isInstalledModule is never called twice for the same module. Once the DeploymentUtils.isInstalledModule is called for a certain module, I add this module to a list. Before a next call to DeploymentUtils.isInstalledModule I verify if the call has been made before. If so, it doesn't need to be called again. - reduced the number of times the xml is parsed. I put the results of the DependencyHelper.getEnvironment for a certain module in a hashmap. Next time the DependencyHelper.getEnvironment is called for the same module, I returns the result stored in the hashmap. After these two modifications GEP is up to speed again. Removal of the call to DeploymentUtils.isInstalledModule makes GEP even faster. Just as fast as deployment using the Geronimo console. For me this works, but I don't know what the impact is for other users. In the attached code I left it the way it was. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 992031
Geronimo Revision: 992031 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/unit-test-reports Number of imports: 10 import: org.codehaus.classworlds.en...@a6c57a42 import: org.codehaus.classworlds.en...@12f43f3b import: org.codehaus.classworlds.en...@20025374 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@92758522 import: org.codehaus.classworlds.en...@ebf2705b import: org.codehaus.classworlds.en...@bb25e54 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Lorg/codehaus/mojo/jspc/compiler/JspCompiler; [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:620) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:611) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.codehaus.mojo.jspc.CompileMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905625#action_12905625 ] Donald Woods commented on GERONIMO-5553: Reply to the 8/30 questions about enhancer, which dup my 8/27 comments When a list of classes is handed to the javaagent, then it will only enhance those classes, but when no class list is given it will discover all classes to enhance. When the 1.6 JVM's Attach API is used (new in OpenJPA 2.0) to dynamically load the OpenJPA enhancer agent, then the class list is used AND any other classes to enhance are discovered unless exclude-unlisted-classes is specified in the PU. So, I'll opened OPENJPA-1780 to request that the javaagent behave the same as the dynamic loader Fail to enchance entities on Geronimo - Key: GERONIMO-5553 URL: https://issues.apache.org/jira/browse/GERONIMO-5553 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 3.0 Environment: OS:win xp Geronimo :3.0 20100824 build Reporter: Lu Jiang Assignee: Rick McGuire Fix For: 3.0 Attachments: booknew.war I tried to deploy a simple jpa sample on geronimo.But when persist data into database. Following exception will occur. openjpa-2.0.0-r422266:935683 nonfatal user error org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance org.apache.sample.entities.b...@97781f to PersistenceCapable failed. Ensure that it has been enhanced. FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 992059
Geronimo Revision: 992059 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.servicemix.bundles -DartifactId=org.apache.servicemix.bundles.javassist -Dversion=3.7.ga_2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT 2) org.apache.servicemix.bundles:org.apache.servicemix.bundles.javassist:jar:3.7.ga_2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-openwebbeans:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots
Where is ValidatorFactoryBuilder interface?
Section EE.5.16.2 of Java EE 6 specification says, For the benefit of implementors, we note that the Bean Validation API includes a ValidatorFactoryBuilder interface that can be used to create a ValidatorFactory configured according to the contents of a validation deployment descriptor in the form of a java.io.InputStream.. I don't see it in geronimo-validation_1.0_spec-1.1.jar. Where can I find this ValidatorFactoryBuilder? -- Vamsi
Re: How to handle the naming context for those servlets added while starting web application
Hi Ivan, I'm having a little trouble understanding the servlet 3 spec section 4.4.3.5 but I think that it says we don't need to look for the jndi related annotations. What do you think? thanks david jencks On Sep 2, 2010, at 2:31 AM, Ivan wrote: Hi, Yesterday, I just releaized that we might have a problem for servlet 3.0, in the new spec, it allows to add new servlets while starting the web application. In that case, how do we handle the bean scope naming context, seems we have no chance to build the naming context for that servlet, e.g. an EJB annotation, So far, I have not find words for it the spec, might need to double check it later. Any comment ? Thanks ! -- Ivan
[BUILD] branches/2.2: Failed for Revision: 992158
Geronimo Revision: 992158 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100902/unit-test-reports import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@92758522 import: org.codehaus.classworlds.en...@ebf2705b import: org.codehaus.classworlds.en...@bb25e54 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' org.codehaus.mojo.jspc.compiler.JspCompiler [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:563) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:620) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:431) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:611) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.codehaus.mojo.jspc.CompileMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent
Re: How to handle the naming context for those servlets added while starting web application
Hmm, I missed that section, seems we only need to support the managed bean injection for those added dynamic. By the way, what makes you feel confusion ? 2010/9/3 David Jencks david_jen...@yahoo.com Hi Ivan, I'm having a little trouble understanding the servlet 3 spec section 4.4.3.5 but I think that it says we don't need to look for the jndi related annotations. What do you think? thanks david jencks On Sep 2, 2010, at 2:31 AM, Ivan wrote: Hi, Yesterday, I just releaized that we might have a problem for servlet 3.0, in the new spec, it allows to add new servlets while starting the web application. In that case, how do we handle the bean scope naming context, seems we have no chance to build the naming context for that servlet, e.g. an EJB annotation, So far, I have not find words for it the spec, might need to double check it later. Any comment ? Thanks ! -- Ivan -- Ivan
Re: [BUILD] branches/2.1: Failed for Revision: 990497
I can replicate the problem with Maven 2.0.10/11 (the version used for 2.1 and 2.2 builds) but not with Maven 2.2.1. For now I updated the builds to use Maven 2.2. Let's see if that works. Jarek On Thu, Sep 2, 2010 at 5:02 AM, Shawn Jiang genspr...@gmail.com wrote: This is also preventing 2.2 build from passing. I can't recreate it locally. I checked the jspc plugin in private nexus and they look good to me. Can anyone have the build server access take a look ? On Mon, Aug 30, 2010 at 1:59 AM, Kevan Miller kevan.mil...@gmail.com wrote: There seems to be a problem with the maven configuration on the build system or the nexus repository that the build system is using. The contents of jspc-compiler-api-2.0-alpha-2.jar in the local repo on the build system contain a 301: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=https://nexus.codehaus.org/content/repositories/releases/org/codehaus/mojo/jspc/jspc-compiler-api/2.0-alpha-2/jspc-compiler-api-2.0-alpha-2.jar;here/a./p hr addressApache/2.0.52 (Red Hat) Server at repository.codehaus.org Port 80/address /body/html I don't see the problem locally. Hopefully the private nexus repo will get synced up, soon. If anybody is familiar with its configuration, maybe you could give it a kick? --kevan On Aug 29, 2010, at 8:10 AM, ga...@apache.org wrote: Geronimo Revision: 990497 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100829/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100829/unit-test-reports this realm = plexus.core urls[0] = file:/usr/local/maven/lib/maven-2.0.9-uber.jar Number of imports: 6 import: org.codehaus.classworlds.en...@4891bb28 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@c51bc9e7 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' Lorg/codehaus/mojo/jspc/compiler/JspCompiler; [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile': Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-2:compile' in the plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin' at
[jira] Created: (GERONIMO-5570) fail to edit NIOHTTPConnector through console
fail to edit NIOHTTPConnector through console - Key: GERONIMO-5570 URL: https://issues.apache.org/jira/browse/GERONIMO-5570 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 setps to recur: 1. Open the web server portlet , and then click on edit link against an existing NIO HTTP Connector in network listener list 2. Modify host and/or port properties (the host and port should not be used by others) 3. Click on Save , to save your change. 4. you will find the modification that don't take effect and then you will find this log info: 2010-09-03 10:15:29,359 INFO [RedirectByHashFilter] Hash value for page:/portal/1-2/Application Server/Web Server/__acconsole-base0x2ConnectorManager!-743665070|1/__pmconsole-base0x2ConnectorManager!-743665070|1_view/__wsconsole-base0x2ConnectorManager!-743665070|1_normal is:8152646084778275299 2010-09-03 10:15:29,359 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/1-2/Application%20Server/Web%20Server/__acconsole-base0x2ConnectorManager!-743665070%7C1/__pmconsole-base0x2ConnectorManager!-743665070%7C1_view/__wsconsole-base0x2ConnectorManager!-743665070%7C1_normal 2010-09-03 10:15:29,390 INFO [RedirectByHashFilter] Hash value for page:/portal/1-2/Application Server/Web Server/__pmconsole-base0x2ConnectorManager!-743665070|1_view/__wsconsole-base0x2ConnectorManager!-743665070|1_normal/__rpconsole-base0x2ConnectorManager!-743665070|1_connectorURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebConnector/__rpconsole-base0x2ConnectorManager!-743665070|1_mode/edit/__rpconsole-base0x2ConnectorManager!-743665070|1_server/tomcat/__rpconsole-base0x2ConnectorManager!-743665070|1_containerURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebContainer/__rpconsole-base0x2ConnectorManager!-743665070|1_managerURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebManager is:6567245037214302374 2010-09-03 10:15:29,390 INFO [RedirectByHashFilter] no redirect for:http://localhost:8080/console/portal/1-2/Application%20Server/Web%20Server/__pmconsole-base0x2ConnectorManager!-743665070%7C1_view/__wsconsole-base0x2ConnectorManager!-743665070%7C1_normal/__rpconsole-base0x2ConnectorManager!-743665070%7C1_connectorURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebConnector/__rpconsole-base0x2ConnectorManager!-743665070%7C1_mode/edit/__rpconsole-base0x2ConnectorManager!-743665070%7C1_server/tomcat/__rpconsole-base0x2ConnectorManager!-743665070%7C1_containerURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebContainer/__rpconsole-base0x2ConnectorManager!-743665070%7C1_managerURI/org0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc3FServiceModule0xc3Dorg0x2apache0x2geronimo0x2configs0xc2Ftomcat70xc2F30x20-SNAPSHOT0xc2Fcar0xc2Cj2eeType0xc3DGBean0xc2Cname0xc3DTomcatWebManager 2010-09-03 10:15:29,421 INFO [SupportedModesServiceImpl] Portlet mode 'edit' not found for portletId: 'console-base.WebServerManager!-743665070|0' 2010-09-03 10:15:29,546 ERROR [ConnectorPortlet] Unable to retrieve value of property emptySessionPath java.lang.IllegalArgumentException: No such method found (getEmptySessionPath on org.apache.geronimo.management.StatisticsProvider$$EnhancerByCGLIB$$2fd633a9) at org.apache.geronimo.console.BasePortlet.getProperty(BasePortlet.java:121) at org.apache.geronimo.console.webmanager.ConnectorPortlet.doView(ConnectorPortlet.java:346) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) at
[BUILD] trunk: Failed for Revision: 992161
Geronimo Revision: 992161 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/build-2100.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 40 minutes 26 seconds [INFO] Finished at: Thu Sep 02 21:41:48 EDT 2010 [INFO] Final Memory: 437M/1013M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100902/logs-2100-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.382 sec FAILURE! [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi
[jira] Commented: (GERONIMODEVTOOLS-608) Publish with GEP takes minutes, while deploy takes seconds
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905787#action_12905787 ] Delos Dai commented on GERONIMODEVTOOLS-608: Hi Kory, I didn't see your attachment, could you attach your patch? Thanks in advance! Publish with GEP takes minutes, while deploy takes seconds -- Key: GERONIMODEVTOOLS-608 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: GEP 2.2 installed in Eclipse (galileo-SR1). Reporter: Boes Assignee: Delos Dai Attachments: getEnvironment.txt, HiThere.ear, HiThereSlow.ear, reorderModules.txt Publishing an Enterprise Application (EAR) with GEP to Geronimo takes much more time then deploying the same EAR to Geronimo using the console. See http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-td684484.html After doing some research I found that EAR's that have dependencies in geronimo-application.xml take a lot of time to publish. This is caused by the very inefficient implementation of the reorderModules method in the org.apache.geronimo.st.core.internal.DependencyHelper class. I installed a GEP development environment and put on tracing. It tested an EAR with 3 WAR's in it. In the EAR's geronimo-application.xml I added dependency tags for 4 libraries. Tracing shows that this results in parsing the geronimo-application.xml 1092 (!) times. In code this means that a call to DependencyHelper.getEnvironment is made 1092 times. Another inefficient part in the reorderModules method is that the call to DeploymentUtils.isInstalledModule is repeatedly made for the same module. In the test I found it was called at least 3 times for each dependent library. These calls result in a request to Geronimo and take almost a second each. The best way to solve this bug is to redesign the reordering process and make it work in a way that both DependencyHelper.getEnvironment and DeploymentUtils.isInstalledModule are not called more often then needed. I wonder why DeploymentUtils.isInstalledModule is called at all. Dependencies are defined in the xml. I can't imagine why it would matter if a module is installed in Geronimo or not. What I did to fix this problem and make GEP workable again for me is: - made sure the DeploymentUtils.isInstalledModule is never called twice for the same module. Once the DeploymentUtils.isInstalledModule is called for a certain module, I add this module to a list. Before a next call to DeploymentUtils.isInstalledModule I verify if the call has been made before. If so, it doesn't need to be called again. - reduced the number of times the xml is parsed. I put the results of the DependencyHelper.getEnvironment for a certain module in a hashmap. Next time the DependencyHelper.getEnvironment is called for the same module, I returns the result stored in the hashmap. After these two modifications GEP is up to speed again. Removal of the call to DeploymentUtils.isInstalledModule makes GEP even faster. Just as fast as deployment using the Geronimo console. For me this works, but I don't know what the impact is for other users. In the attached code I left it the way it was. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5571) Console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules.
Console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules. -- Key: GERONIMO-5571 URL: https://issues.apache.org/jira/browse/GERONIMO-5571 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Environment: Server:geronimo 3.0 trunk Reporter: janel Zhang Fix For: 3.0 This patch is console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5571) Console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules.
[ https://issues.apache.org/jira/browse/GERONIMO-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5571: -- Attachment: console-eba.patch This patch is console support for EBA modules:list EBA modules,restart EBA modules,stop EBA modules and uninstall EBA modules. Console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules. -- Key: GERONIMO-5571 URL: https://issues.apache.org/jira/browse/GERONIMO-5571 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: Server:geronimo 3.0 trunk Reporter: janel Zhang Fix For: 3.0 Attachments: console-eba.patch This patch is console support for EBA modules:list EBA modules,start EBA modules,stop EBA modules and uninstall EBA moules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5548) Default user monitor can't login admin console in Geronimo_3.0_trunk
[ https://issues.apache.org/jira/browse/GERONIMO-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang updated GERONIMO-5548: - Description: setps to recur: 1. startup the Geronimo server 2. open http://localhost:8080/console; 3. login with User name monitor and default password password 4.you will find : HTTP Status 403 - type Status report message description Access to the specified resource () has been forbidden. was: setps to recur: 1. startup the Geronimo server 2. open http://localhost:8080/console; 3. login with User name system and default password password 4.you will find : HTTP Status 403 - type Status report message description Access to the specified resource () has been forbidden. Default user monitor can't login admin console in Geronimo_3.0_trunk Key: GERONIMO-5548 URL: https://issues.apache.org/jira/browse/GERONIMO-5548 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Minor Fix For: 3.0 setps to recur: 1. startup the Geronimo server 2. open http://localhost:8080/console; 3. login with User name monitor and default password password 4.you will find : HTTP Status 403 - type Status report message description Access to the specified resource () has been forbidden. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
