Re: [BUILD 2.1.4] [Error] Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
Can you try building with maven 2.0.9 or 2.0.10? I think we built the released 2.1.4 with maven 2.0.9. However, a svn tag shouldn't be using any snapshot versions of anything. Can you confirm which source you checked out? thanks david jencks On Jun 27, 2009, at 9:14 PM, 李伟超 wrote: Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0_19 Java home: /home/mark/install/jdk1.5.0_19/jre Default locale: zh_CN, platform encoding: UTF-8 OS name: linux version: 2.6.28-11-generic arch: i386 Family: unix 2009/6/28 李伟超 markoo...@gmail.com i build v2.1.4 from svn-tag because i think it will be more smoothly than from trunk, but not luck. [INFO] [INFO] Building Geronimo Plugins, ActiveMQ :: Portlets [INFO]task-segment: [install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1- SNAPSHOT [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1- SNAPSHOT at org .apache .maven .lifecycle .DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java: 1521) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .bindPluginToLifecycle(DefaultLifecycleExecutor.java:1479) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .constructLifecycleMappings(DefaultLifecycleExecutor.java:1245) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 518) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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: Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1- SNAPSHOT at org .apache .maven .plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:323) at org .apache .maven .plugin .DefaultPluginManager .verifyVersionedPlugin(DefaultPluginManager.java:217) at org .apache .maven .plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java: 177) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java: 1517) ... 17 more [INFO] [INFO] Total time: 16 minutes 6 seconds [INFO] Finished at: Sun Jun 28 09:14:54 CST 2009 [INFO] Final Memory: 159M/587M [INFO]
[BUILD] trunk: Failed for Revision: 789053
Geronimo Revision: 789053 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 50 seconds
[INFO] Finished at: Sun Jun 28 03:46:06 EDT 2009
[INFO] Final Memory: 434M/972M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-0300-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-0300-jetty/
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:50.916
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:14.651)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:36.003)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.453)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.803)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:27.703)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:22.184) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:12.331)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.598)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:58.550)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.904)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.369)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.472)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:37.620)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.241)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:02.643)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.796)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.591)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:50.264) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:51.490)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.483)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.524)
[INFO] web-testsuite/test-jetty RUNNING
[INFO] web-testsuite/test-jetty SUCCESS (0:00:25.651
[jira] Created: (GERONIMO-4717) There are some texts that aren't pulled out in the activemq portlet.
There are some texts that aren't pulled out in the activemq portlet. Key: GERONIMO-4717 URL: https://issues.apache.org/jira/browse/GERONIMO-4717 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 2.1.4, 2.1.3, 2.1.2, 2.1.1, 2.1, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.5, 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4717) There are some texts that aren't pulled out in the activemq portlet.
[ https://issues.apache.org/jira/browse/GERONIMO-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4717: Patch Info: [Patch Available] There are some texts that aren't pulled out in the activemq portlet. Key: GERONIMO-4717 URL: https://issues.apache.org/jira/browse/GERONIMO-4717 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.5, 2.2 Attachments: activemq-portlets_v21.patch, activemq-portlets_v22.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4717) There are some texts that aren't pulled out in the activemq portlet.
[ https://issues.apache.org/jira/browse/GERONIMO-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4717: Attachment: activemq-portlets_v22.patch activemq-portlets_v21.patch Attached the patches for both v2.1 and v2.2. Please review and commit them. There are some texts that aren't pulled out in the activemq portlet. Key: GERONIMO-4717 URL: https://issues.apache.org/jira/browse/GERONIMO-4717 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.5, 2.2 Attachments: activemq-portlets_v21.patch, activemq-portlets_v22.patch -- 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: 789091
Geronimo Revision: 789091 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 49 seconds
[INFO] Finished at: Sun Jun 28 09:44:57 EDT 2009
[INFO] Final Memory: 403M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-0900-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-0900-jetty/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:48.100
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:16.710)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.584)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:39.678)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.159)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:25.251)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:34.584)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:06.665)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:53.617)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:56.814)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.910)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.603)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.869)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.685)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:47.204)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.995)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.796)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.457)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.967) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:51.424)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.215)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.204)
[INFO] web-testsuite/test-jetty
Will the whole Geronimo framework be ported to OSGI?
Hi All: I am a newbie to Geronimo. Although I only digged into the internal implementation of Geronimo for only about a month. I was absorbed by the flexibility of Geronimo framework and its GBean implementation. Geronimo is a very great integration framework. Currently most other application server have been ported to OSGI framework in order to be standard compatible and utilize the strength of OSGI. Is there any schedule or plan for Geronimo to be ported to OSGI? Can the GBean framework be kept unchanged once Geronimo was changed to OSGI based? Any information about OSGI for Geronimo is welcomed. Thanks. Best Regards. luzhongda
Re: [BUILD 2.1.4] [Error] Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
yes, very thanks. maven 2.0.10 works.[?] 2009/6/28 David Jencks david_jen...@yahoo.com Can you try building with maven 2.0.9 or 2.0.10? I think we built the released 2.1.4 with maven 2.0.9. However, a svn tag shouldn't be using any snapshot versions of anything. Can you confirm which source you checked out? thanks david jencks On Jun 27, 2009, at 9:14 PM, 李伟超 wrote: Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0_19 Java home: /home/mark/install/jdk1.5.0_19/jre Default locale: zh_CN, platform encoding: UTF-8 OS name: linux version: 2.6.28-11-generic arch: i386 Family: unix 2009/6/28 李伟超 markoo...@gmail.com i build v2.1.4 from svn-tag because i think it will be more smoothly than from trunk, but not luck. [INFO] [INFO] Building Geronimo Plugins, ActiveMQ :: Portlets [INFO]task-segment: [install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1521) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1245) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:518) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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: Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:323) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:217) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1517) ... 17 more [INFO] [INFO] Total time: 16 minutes 6 seconds [INFO] Finished at: Sun Jun 28 09:14:54 CST 2009 [INFO] Final Memory: 159M/587M [INFO] B9F.gif
Need Help: WS-Security Support for CXF in Geronimo (UsernameToken property setting)
Hello Devs,
First of all, I apologize if the below questions are trivial.
I need some help in setting basic usernameToken Property for Geronimo (for
CXF). I did add the username token property elements in the schema and
generated the required classes by mvn install. And Geronimo is able to
accept this usertoken element which users define in the geronimo-web.xml.
(but I think I have not well configured this in Geronimo)
service-ref
service-ref-nameservices/HelloWorld/service-ref-name
port
port-nameHelloWorldImplPort/port-name
protocolhttp/protocol
hostlocalhost/host
port8080/port
uri/ServiceG/HelloWorld/uri
* usertoken
usernamews-client/username
passwordpassword/password
/usertoken*
/port
/service-ref
* I am testing it with a servlet client which is trying to access the
secured service (with username and password) running on tomcat server.
Here is the servlet client code:
public class HelloServlet extends HttpServlet {
public void doGet (HttpServletRequest req,
HttpServletResponse res)
throws ServletException, IOException
{
PrintWriter out = res.getWriter();
try {
InitialContext ic=new InitialContext();
Service service;
service = (Service)ic.lookup(java:comp/env/services/HelloWorld);
QName svcQname=new QName(http://service.web/
,HelloWorldImplPort);
HelloWorld hw=service.getPort(HelloWorld.class);
String greeting=hw.sayHi(Rahul);
out.println(greeting);
} catch (NamingException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
out.close();
}
}
Now, I am coding to configure this above ws-security userToken propery with
CXF apis in Apache Geronimo and I am not sure *How to use cxf apis* to
configure this. I am trying to write a CXF specific PortMethodInterceptor
class extended from (jaxws's PortMethodInterceptor) but not sure what CXF
apis I can use to configure the usertoken.
I start with the received error (pasted from geronimo.log) with some debug
statements:
...
2009-06-28 16:41:17,632 INFO [BusApplicationContext] Bean factory for
application context [org.apache.cxf.bus.spring.busapplicationcont...@1ccad1e]:
org.springframework.beans.factory.support.defaultlistablebeanfact...@d6ae95
2009-06-28 16:41:18,006 INFO [DefaultListableBeanFactory] Pre-instantiating
singletons in
org.springframework.beans.factory.support.defaultlistablebeanfact...@d6ae95:
defining beans
[cxf,org.apache.cxf.bus.spring.BusApplicationListener,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,org.apache.cxf.resource.ResourceManager,org.apache.cxf.configuration.Configurer,org.apache.cxf.binding.BindingFactoryManager,org.apache.cxf.transport.DestinationFactoryManager,org.apache.cxf.transport.ConduitInitiatorManager,org.apache.cxf.wsdl.WSDLManager,org.apache.cxf.phase.PhaseManager,org.apache.cxf.workqueue.WorkQueueManager,org.apache.cxf.buslifecycle.BusLifeCycleManager,org.apache.cxf.endpoint.ServerRegistry,org.apache.cxf.endpoint.ServerLifeCycleManager,org.apache.cxf.endpoint.ClientLifeCycleManager,org.apache.cxf.transports.http.QueryHandlerRegistry,org.apache.cxf.endpoint.EndpointResolverRegistry,org.apache.cxf.headers.HeaderManager,org.apache.cxf.catalog.OASISCatalogManager,org.apache.cxf.endpoint.ServiceContractResolverRegistry,org.apache.geronimo.cxf.GeronimoDestinationFactory#0,org.apache.cxf.jaxws.context.WebServiceContextResourceResolver,org.apache.cxf.jaxws.context.WebServiceContextImpl,org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder,org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder,org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider,org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory,org.apache.cxf.binding.soap.SoapBindingFactory,org.apache.cxf.binding.soap.SoapTransportFactory,org.apache.cxf.binding.soap.customEditorConfigurer,org.apache.cxf.binding.xml.XMLBindingFactory,org.apache.cxf.ws.addressing.policy.AddressingAssertionBuilder,org.apache.cxf.ws.addressing.policy.AddressingPolicyInterceptorProvider,org.apache.cxf.ws.addressing.policy.UsingAddressingAssertionBuilder];
root of factory hierarchy
*2009-06-28 16:41:18,661* DEBUG [CXFServiceReference] I am in
getPortMethodInterceptor, called from CXFServiceReference:
2009-06-28 16:41:18,662 DEBUG [CXFPortMethodInterceptor] View the
seiInfoMap.values() ![http://localhost:8080/ServiceG/HelloWorld null false
ws-client password, http://localhost:8080/ServiceG/HelloWorld null false
ws-client password]
2009-06-28 16:41:18,681 DEBUG [JAXWSServiceReference] Initializing service
with: file:/home/rahul/new_workspace1/Client/WEB-INF/wsdl/HelloWorld.wsdl {
http://service.web/}HelloWorldImplService
2009-06-28 16:41:18,844 DEBUG [CXFPortMethodInterceptor] I am in intercept
method of
Re: Will the whole Geronimo framework be ported to OSGI?
On Jun 28, 2009, at 8:40 AM, luzhongda wrote: Hi All: I am a newbie to Geronimo. Although I only digged into the internal implementation of Geronimo for only about a month. I was absorbed by the flexibility of Geronimo framework and its GBean implementation. Geronimo is a very great integration framework. Currently most other application server have been ported to OSGI framework in order to be standard compatible and utilize the strength of OSGI. Is there any schedule or plan for Geronimo to be ported to OSGI? We're working on it Can the GBean framework be kept unchanged once Geronimo was changed to OSGI based? My current plan is to - use osgi classloaders (bundles) - put the geronimo kernel in the osgi service registry - geronimo plugins will become bundles - there will be a bundle activator that starts up a Configuration (plugin). I think this will let gbeans more or less work in an osgi environment. We also have a osgi blueprint service implementation that is pretty far along and we may decide that converting all or most of our plugins to be blueprint based bundles is a good idea. There are also some problems I don't know how to solve in osgi, mostly how to decide, given several bundles that supply the same packages, which one to use. At the moment I'm leaning towards keeping our maven- like dependency system for this purpose. Another perspective on this problem is, given a bundle with some dependencies on packages and services, how do you figure out what other bundles are needed to assemble a working server. thanks david jencks Any information about OSGI for Geronimo is welcomed. Thanks. Best Regards. luzhongda
Re: Git mirrors for Geronimo
On Jun 27, 2009, at 2:09 AM, Ivan wrote: We will move from SVN to Git for Geronimo? No. SVN remains the version control system used to maintain our codebase. These are GIT mirrors of this SVN repository. You can continue to use SVN, unchanged. However, those interested can start to use Git. For more information, see: List of Git mirrors: http://git.apache.org/ Apache Git doc: http://www.apache.org/dev/git.html Apache Git wiki: http://wiki.apache.org/general/GitAtApache --kevan
[BUILD] trunk: Failed for Revision: 789132
Geronimo Revision: 789132 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 50 seconds
[INFO] Finished at: Sun Jun 28 15:46:09 EDT 2009
[INFO] Final Memory: 404M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-1500-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-1500-jetty/
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:46.674
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:14.634)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.530)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.194)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.467)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:23.816)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:30.526) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:07.824)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.819)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:13.948)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.351)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.638)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.303)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.393)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.672)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.734)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.176)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.621)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:48.935) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.207)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.485)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.347)
[INFO] web-testsuite/test-jetty RUNNING
[INFO] web-testsuite/test-jetty SUCCESS (0:00:25.589
Problem when deploy CXF WebService (Service resource injection failed)
Hi, I'm not able to deploy CXF WebService in Apache Geronimo. This is my environment: Java 1.6 Apache Geronimo (Jetty) 2.1.4 Apache CXF 2.0.8 Spring 2.5.6 When I deploy the application I get the following exception: Redeploy of module failed. See log for details. start of default/ViewControllerWS/1.0/car failed org.apache.geronimo.kernel.config.LifecycleException: start of default/ViewControllerWS/1.0/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:580) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:544) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:188) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:563) ... 39 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration default/ViewControllerWS/1.0/car failed to start due to the following reasons: The service J2EEApplication=null,WebModule=default/ViewControllerWS/1.0/car,j2eeType=Servlet,name=org.apache.cxf.js.rhino.DOMMessageProvider did not start because Service resource injection failed The service J2EEApplication=null,WebModule=default/ViewControllerWS/1.0/car,j2eeType=Servlet,name=org.apache.cxf.js.rhino.DOMPayloadProvider did not start because default/ViewControllerWS/1.0/car?J2EEApplication=null,WebModule=default/ViewControllerWS/1.0/car,j2eeType=Servlet,name=org.apache.cxf.js.rhino.DOMMessageProvider did not start. at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:485)
[jira] Updated: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1
[ https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4532: Attachment: mconsole-war_2nd.patch Donald, A mistake was found in the monitoring porlet, which is that it cannot successfully enable the registed server. I submit the 2nd patch to fix this, so please review and commit it. Port the GERONIMO-4484 patch for V2.1 - Key: GERONIMO-4532 URL: https://issues.apache.org/jira/browse/GERONIMO-4532 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4 Reporter: Kan Ogawa Assignee: Kan Ogawa Priority: Minor Fix For: 2.1.5 Attachments: activemq-portlets.patch, console-base-portlets.patch, console-core.patch, console-portal-driver.patch, debugviews-portlets.patch, mconsole-war.patch, mconsole-war_2nd.patch, plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch I think that this issue is very important. After the GERONIMO-4485 patches are committed, I will try to port GERONIMO-4484 patches for 2.1 version. -- 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: 789178
Geronimo Revision: 789178 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 43 seconds
[INFO] Finished at: Sun Jun 28 21:43:51 EDT 2009
[INFO] Final Memory: 468M/770M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-2100-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090628/logs-2100-jetty/
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:43.786
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:02.460)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:33.737)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:36.729)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.628)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:26.150)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:20.315) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:05.019)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:53.262)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:50.387)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.274)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:35.079)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.176)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:37.257)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:45.788)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:02.563)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.431)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.796)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.894) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:45.704) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.908)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:33.225)
[INFO] web-testsuite/test-jetty RUNNING
[INFO] web-testsuite/test-jetty SUCCESS (0:00:26.323)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces
[jira] Created: (GERONIMO-4718) Keystores portlet: Once unlocked for availability, keystore can not be locked
Keystores portlet: Once unlocked for availability, keystore can not be locked - Key: GERONIMO-4718 URL: https://issues.apache.org/jira/browse/GERONIMO-4718 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1.4 Reporter: Vamsavardhana Reddy Fix For: 2.1.5 Attempting to lock the keystore for availability is displaying the following message in the server console. 2009-06-29 08:23:07,265 ERROR [MultiPagePortlet] Unrecognized portlet action 'lockKeystore' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3389) console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector
[ https://issues.apache.org/jira/browse/GERONIMO-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12725039#action_12725039 ] Ivan commented on GERONIMO-3389: Commit the addon patches to 2.1.5-snapshot At revision: 789210, trunk At revision: 789211. console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector - Key: GERONIMO-3389 URL: https://issues.apache.org/jira/browse/GERONIMO-3389 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: documentation, Tomcat Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.x, 2.1, 2.1.1, 2.1.x, 2.2 Environment: Windows xp sp2, IE, Firefox Reporter: Song Assignee: Shawn Jiang Fix For: 2.1.5, 2.2 Attachments: G3389_addon_g21.patch, G3389_addon_trunk.patch, G3389_g21.patch, G3389_trunk.patch Click on Save button after entering all necessary parameters for creating a new Tomcat APR HTTP Connector test_APR_HTTP, it returned to the Network Listeners list page. However,the Protocol for test_APR_HTTP is empty, State is failed. And java.lang.UnsatisfiedLinkError is thrown from the server started console and server.log. Same error to creating Tomcat APR HTTPS Connetor. Detailed error as below: -- 13:33:46,515 WARN [ConnectorGBean] test_APR_HTTP connector failed 13:33:46,515 ERROR [Connector] Coyote connector has not been started 13:33:46,515 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car,j2eeType=GBean,name=test_APR_HTTP java.lang.UnsatisfiedLinkError: org/apache/tomcat/jni/Pool.create(J)J at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:579) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) at org.apache.catalina.connector.Connector.initialize(Connector.java:1059) at org.apache.catalina.core.StandardService.addConnector(StandardService.java:267) at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:327) at org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:383) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$fa3733e1.addConnector(generated) at org.apache.geronimo.tomcat.connector.ConnectorGBean.doStart(ConnectorGBean.java:95) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.connector.Http11APRProtocol$$EnhancerByCGLIB$$abc46ac2.startRecursive(generated) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:146) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at
[jira] Resolved: (GERONIMO-4688) hardcode port in plan.xml of plugin farming.
[
https://issues.apache.org/jira/browse/GERONIMO-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan resolved GERONIMO-4688.
Resolution: Fixed
Commit the changes to trunk At revision: 789212, 2.1.5-snapshot At revision:
789213. Thanks Shawn Jiang for the patch !
hardcode port in plan.xml of plugin farming.
-
Key: GERONIMO-4688
URL: https://issues.apache.org/jira/browse/GERONIMO-4688
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
Fix For: 2.1.5, 2.2
Attachments: G4688_G21.patch, G4688_trunk.patch
In Gtrunk\plugins\clustering\farming\src\main\plan\plan.xml, there are some
hardcodeed ser/pass/host/port string in it. I'm not sure if they should be
something like ${PlanClusterNodeName} so that they can be set in
server\config\config_substitution.properties.
gbean name=NodeInfo class=org.apache.geronimo.farm.config.BasicNodeInfo
attribute name=name${PlanClusterNodeName}/attribute
xml-attribute name=extendedJMXConnectorInfo
ns:javabean
xmlns:ns=http://geronimo.apache.org/xml/ns/deployment/javabean-1.0;
class=org.apache.geronimo.farm.deployment.DeploymentExtendedJMXConnectorInfo
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=protocolrmi/ns:property
ns:property name=hostlocalhost/ns:property
ns:property name=port1099/ns:property
ns:property name=urlPathJMXConnector/ns:property
ns:property name=localtrue/ns:property
/ns:javabean
/xml-attribute
/gbean
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (XBEAN-133) Jar file is not close after open resulting in files delete failure when finding resource
Jar file is not close after open resulting in files delete failure when finding resource Key: XBEAN-133 URL: https://issues.apache.org/jira/browse/XBEAN-133 Project: XBean Issue Type: Bug Components: finder Environment: os:win2003 Reporter: viola.lu Assignee: viola.lu Priority: Minor 1.Deploy a war including jar files under lib with a wrong deployment plan in Geronimo server 2.Fail to deploy but can't recursive delete files under lib coz jar files are open not close by xbean resource finder Refer to https://issues.apache.org/jira/browse/GERONIMO-4696 for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
