Nabble - Geronimo

[jira] Resolved: (GERONIMO-4450) EJB based Provider implementation should allow other interfaces in addtion to javax.xml.ws.Provider

2008-12-05T07:54:44Z

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

Jarek Gawor resolved GERONIMO-4450.
-----------------------------------

Resolution: Fixed
Fix Version/s: 2.2
2.1.4

Committed fixes (similar to the patch) to trunk (revision 723762) and branches/2.1 (revision 723773). Thanks Ivan for finding this!

> EJB based Provider implementation should allow other interfaces in addtion to javax.xml.ws.Provider
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4450
> URL: https://issues.apache.org/jira/browse/GERONIMO-4450
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.2
> Environment: Windows XP
> JDK 1.5.0
> Reporter: Ivan
> Assignee: Jarek Gawor
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4450.patch
>
>
> While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces in addition to the Provider.
> Current implmentation, an exception will be thrown
> javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
> at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
> at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:810)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Geronimo - Dev

feature? ContainerGroup

2008-12-05T07:46:03Z

Being that Geronimo only allows one statically configured Jetty instance,
configured as a GBean. And to get more instances, you have to install additional
Jetty gbeans under a new container name.

Plus, being that there is only one NCSARequestLog gbean, which has hard coded
the logfile name and location, and we are not able to change the name and
location without recompiling.

Should Geronimo be modified to allow these to be dynamic?

I think that being able to spawn multiple containers and reconfigure log files
should be something dynamic, and configurable in the var/config/config.xml file
without having to add additional gbeans/plugins.

Something like the following could result for configuration:
-
<module name="JettyWebContainer2"
gbean="org.apache.geronimo.jetty6.connector.JettyWebContainerFactory">
...
</module>

<module name="NCSARequestLog2"
gbeanInfo="org.apache.geronimo.jetty6.requestlog.NCSARequestLogFactory">
...
</module>

<module name="ContainerGroup" gbean="org.apache.geronimo.jetty6.ContainerGroup">
<reference name="JettyContainer">
<name>JettyWebContainer2</name>
</reference>
<reference name="RequestLog">
<name>NCSARequestLog2</name>
</reference>
<reference name="ThreadPool">
<name>DefaultThreadPool</name>
</reference>
<reference name="ServerInfo">
<name>ServerInfo</name>
</reference>
</module>
-

Where JettyWebContainerFactory and NCSARequestLogFactory produce separate
running instances of JettyWebContainer and NCSARequestLog respectively.

Or with the Factory option, perhaps all that is needed is:
-
<module name="NCSARequestLog2"
gbeanInfo="org.apache.geronimo.jetty6.requestlog.NCSARequestLogFactory">
...
</module>

<module name="JettyWebContainer2"
gbean="org.apache.geronimo.jetty6.connector.JettyWebContainerFactory">
...
<reference name="RequestLog">
<name>NCSARequestLog2</name>
</reference>
</module>
-

But I think it would be a good idea to be able to group configurations together.

<class1>
<listen socket/>
<virtual server 1>
<hostname alias/>
<log configuration/>
<web application 1/>
</virtual server 1>
<virtual server 2>
<hostname alias/>
<log configuration/>
<web application 1/>
</virtual server 2>
<log configuration/>
</class1>

<class2>
<listen socket/>
<virtual server 1>
<hostname alias/>
<log configuration/>
<web application 1/>
<web application 2/>
<web application 3/>
</virtual server 1>
<log configuration/>
</class2>

Where each class is a separated Web Container.

What is the general opinion about this?

-RG

From forum: Apache Geronimo - Users

Re: Geronimo, keystores and SSL

2008-12-05T07:43:16Z

Hello.

"Good" to hear - thought that I was going crazy.
I will file a bug report some time tomorrow.

Is there a work around? For example, how do you unlock your keystore in the 3:rd step?

Greetings,

On Fri, Dec 5, 2008 at 3:41 PM, Vamsavardhana Reddy <c1vamsi1c@...> wrote:

Hmm... the 3rd step is indeed unearthing a bug. At that step, a second "attribute" element is getting added (instead of replacing the existing element) to the keystore gbean for keystorePassword and keyPasswords attributes in config.xml . Can you create an issue in the JIRA [1]? The problem summary is, "locking and unlocking for availability of a keystore results in duplicate attributes in config.xml".

[1] https://issues.apache.org/jira/browse/GERONIMO

On Fri, Dec 5, 2008 at 7:29 PM, Christian Svensson <blue@...> wrote:

Hello.

It's a correct assumption that I am using Jetty, I'm using 2.1.3 Geronimo w/ Jetty package from the website (running with Sun Java 1.6).
I think it's the 3:rd step I'm lacking behind at.

This is how I created my setup:

1. Create a new keystore 'plasma-ssl'
2. Create a new private key 'wildcard'
3. Now the text on "Available" says "trust only" or something like that, I lock it and then unlock it in order for it to change to "1 key ready"
4. Then I configure my HTTPS connector to use the new keystore
5. Since the web server does not seem to do anything when I press "Shutdown" in the console, I use Ctrl+C to kill it.
6. Start the server again
7. Message appears.

1 to 4 are applied using the web console.

Have I done the step "Unlock keystore 'mykeystore' and private-key 'mykey' for availability." correctly?

Greetings,

On Fri, Dec 5, 2008 at 9:28 AM, Vamsavardhana Reddy <c1vamsi1c@...> wrote:
Hi Christian,

Once you create a new keystore, the keystore is not unlocked for availability automatically. After creating the keystore and private key, you need unlock the keystore for availability. The unlocked state for "availability" of the keystore is persistent. I assume that you are using Geronimo Jetty Server. Here are the steps I tried with Geronimo Jetty 2.1.3 and had no problem restarting the server.
1. Created a new keystore 'mykeystore'.
2. Created a private-key 'mykey'.
3. Unlock keystore 'mykeystore' and private-key 'mykey' for availability.
4. Edit HTTS web connector to use 'mykeystore'
5. Restart the server.

6. Unlock 'mykeystore' for editing.
7. Change password for 'mykey'.
8. Restart the server.

The Geronimo Tomcat server does not use the keystoregbean for HTTPS and directly access the keystore files. Also, "the keystore password and keypassword must be same" is applicable to G Tomcat server.

Can you tell me the exact version of Geronimo server and the steps you are following that are resulting in the problem?

On Tue, Dec 2, 2008 at 5:48 AM, Christian Svensson <blue@...> wrote:

Hello!

I've been trying for the better part of today getting keystores to automatically unlock on startup - with very limited success.
Is there something that I should know about keystore password / key password? Digging around some old mailing list threads said something about key password must be equal to keystore password - any more of those gotchas?

The problem is that I create (or change password on geronimo-default for that matter) a new keystore, assign SSL to use the certificate and restart the server:
org.apache.geronimo.management.geronimo.KeystoreIsLocked: Keystore 'plasma-ssl' is locked; please use the keystore page in the admin console to unlock it
at org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLContext(FileKeystoreManager.java:343)
at org.apache.geronimo.jetty6.connector.GeronimoSelectChannelSSLListener.createSSLContext(GeronimoSelectChannelSSLListener.java:54)

Resetting the SSL connector to using geronimo-default / geronimo with secret / secret as passwords makes it work again - but why on earth doesn't Geronimo unlock my keystores on startup? I mean, it saves the password (or something like it) in config.xml.

Greetings,
--
Christian Svensson
Command Systems

--
Vamsi

--
Christian Svensson
Command Systems

--
Vamsi

--
Christian Svensson
Command Systems

From forum: Apache Geronimo - Users

Re: How to deploy web application to one port

2008-12-05T07:29:47Z

Okay, so I have to deploy a second Jetty container inside Geronimo, so Geronimo
would have two different Jetty containers, one serving web applications on each
of the two ports.
So I would basically copy the Jetty plugin to a new plugin, compile it, and
place it in the repository.

So now we have JettyContainer/JettyWebContainer in Geronimo.
After doing what is suggested, I would have something like
JettyContainer2/JettyWebContainer2 - it would be a whole new module with the
same code - is this correct?

I have an additional question.
In a previous thread on 2008-12-03, I ask on the subject "How to set up logging
for a connector". Can I also perform this same suggestion for
org.apache.geronimo.jetty6.requestlog.NCSARequestLog ?

I would assume if they use the same NCSARequestLog gbean that both containers
would put their logs in the same log file.
So... since I cannot change the log file name and location (as I asked in this
other thread), I assume I also need to deploy a new NCSARequestLog gbean - is
this correct?

-RG

David Jencks wrote:

>
> On Dec 4, 2008, at 10:59 PM, viola.lu wrote:
>
>>
>> You can create two geronim instances in one server:instance A in http
>> port
>> 2150, instance B in port 2051, then deploy hello_1 to instance A,
>> hello_2 to
>> instance B.
>
> I think creating two entire server instances is a bit extreme and e.g.
> if both web apps are connecting to the same ejb app might not work as
> efficiently as possible.
>
> However, AFAIK you have to set up a second jetty server in your geronimo
> instance. Basically, copy the plugins/jetty plan (from source), call it
> something else, edit it (e.g. the ports), and deploy it. I'd copy the
> maven project and build a plugin, but you can deploy the plan separately
> if you want. You can also include all the gbeans in your geronimo plan
> for your web app. You need to indicate in the geronimo plan which web
> server you want the app to be deployed on.
>
> There are micro instructions for geronimo-tomcat here related to a
> sample app:
>
> http://cwiki.apache.org/GMOxDOC22/app-per-port-running-multiple-web-apps-on-different-ports.html
>
>
> If you come up with something relevant for jetty and want to help us
> with our docs and samples that would be great!
>
> I think I recall talking with Greg about filtering web apps per port in
> jetty but I don't think you can actually do it right now. I think he
> said it would be very easy to add though.... maybe we can get it into
> jetty 7.
>
> thanks
> david jencks
>
>>
>>
>> Russell E Glaue wrote:
>>>
>>> Using geronimo-jetty 2.1.3
>>>
>>> How do I deploy a web application to one and only one single port?
>>>
>>> Let's say I have configured two Listen Sockets:
>>> 1) 0.0.0.0:2150
>>> 2) 0.0.0.0:2151
>>>
>>> If I simply deploy a web application to Geronimo as in:
>>> % deploy.sh deploy HelloWorld.war
>>>
>>> The sample application HellowWorld is accessible on both ports as in:
>>> 1) http://0.0.0.0:2150/hello - SUCCESS!!!
>>> 2) http://0.0.0.0:2151/hello - SUCCESS!!!
>>>
>>>
>>>
>>> Now, I can modify WelloWorld/WEB-INF/geronimo-web.xml with the
>>> <virtual-host>virt1.com</virtual-host> attribute, but this restrict the
>>> web
>>> application to be served when the web client makes a HTTP 1.1 call to
>>> Geronimo
>>> for "virt1.com" GET /hello
>>>
>>> So with using this <virtual-host>, the HellowWorld is not available on
>>> either
>>> port when accessed as <server-ip>:<port-number>
>>>
>>>
>>>
>>> So, how do I deploy a web application so that it is available on one
>>> port,
>>> but
>>> not another port, yet both ports running under one geronimo instance?
>>>
>>> I want to deploy two web applications, each one accessible on a
>>> different
>>> port.
>>> If I do something like:
>>> % deploy.sh deploy HelloWorld_1.war
>>> % deploy.sh deploy HelloWorld_2.war
>>>
>>> I want the results to be like:
>>> 1) http://0.0.0.0:2150/hello_1 - SUCCESS!!!
>>> 2) http://0.0.0.0:2150/hello_2 - Fail
>>> 3) http://0.0.0.0:2151/hello_1 - Fail
>>> 4) http://0.0.0.0:2151/hello_2 - SUCCESS!!!
>>>
>>>
>>> How do I do this?
>>>
>>> -RG
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-deploy-web-application-to-one-port-tp20843348s134p20848710.html
>>
>> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>>
>

From forum: Apache Geronimo - Users

[jira] Updated: (GERONIMO-4450) EJB based Provider implementation should allow other interfaces in addtion to javax.xml.ws.Provider

2008-12-05T07:19:44Z

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

Ivan updated GERONIMO-4450:
---------------------------

Component/s: webservices
Description:
While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces in addition to the Provider.
Current implmentation, an exception will be thrown
javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:810)

was:
While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces except for the Provider.
Current implmentation, an exception will be thrown
javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:810)

Summary: EJB based Provider implementation should allow other interfaces in addtion to javax.xml.ws.Provider (was: EJB based Provider implementation should allow other interfaces except for javax.xml.ws.Provider)

I mean the implementation could implement other business interface, should not use the word 'except for'

> EJB based Provider implementation should allow other interfaces in addtion to javax.xml.ws.Provider
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4450
> URL: https://issues.apache.org/jira/browse/GERONIMO-4450
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.2
> Environment: Windows XP
> JDK 1.5.0
> Reporter: Ivan
> Assignee: Jarek Gawor
> Attachments: Geronimo-4450.patch
>
>
> While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces in addition to the Provider.
> Current implmentation, an exception will be thrown
> javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
> at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
> at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:810)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Geronimo - Dev

Re: Geronimo, keystores and SSL

2008-12-05T06:41:29Z

Hmm... the 3rd step is indeed unearthing a bug. At that step, a second "attribute" element is getting added (instead of replacing the existing element) to the keystore gbean for keystorePassword and keyPasswords attributes in config.xml . Can you create an issue in the JIRA [1]? The problem summary is, "locking and unlocking for availability of a keystore results in duplicate attributes in config.xml".

[1] https://issues.apache.org/jira/browse/GERONIMO

On Fri, Dec 5, 2008 at 7:29 PM, Christian Svensson <blue@...> wrote:

Hello.

It's a correct assumption that I am using Jetty, I'm using 2.1.3 Geronimo w/ Jetty package from the website (running with Sun Java 1.6).
I think it's the 3:rd step I'm lacking behind at.

This is how I created my setup:

1. Create a new keystore 'plasma-ssl'
2. Create a new private key 'wildcard'
3. Now the text on "Available" says "trust only" or something like that, I lock it and then unlock it in order for it to change to "1 key ready"
4. Then I configure my HTTPS connector to use the new keystore
5. Since the web server does not seem to do anything when I press "Shutdown" in the console, I use Ctrl+C to kill it.
6. Start the server again
7. Message appears.

1 to 4 are applied using the web console.

Have I done the step "Unlock keystore 'mykeystore' and private-key 'mykey' for availability." correctly?

Greetings,

On Fri, Dec 5, 2008 at 9:28 AM, Vamsavardhana Reddy <c1vamsi1c@...> wrote:
Hi Christian,

Once you create a new keystore, the keystore is not unlocked for availability automatically. After creating the keystore and private key, you need unlock the keystore for availability. The unlocked state for "availability" of the keystore is persistent. I assume that you are using Geronimo Jetty Server. Here are the steps I tried with Geronimo Jetty 2.1.3 and had no problem restarting the server.
1. Created a new keystore 'mykeystore'.
2. Created a private-key 'mykey'.
3. Unlock keystore 'mykeystore' and private-key 'mykey' for availability.
4. Edit HTTS web connector to use 'mykeystore'
5. Restart the server.

6. Unlock 'mykeystore' for editing.
7. Change password for 'mykey'.
8. Restart the server.

The Geronimo Tomcat server does not use the keystoregbean for HTTPS and directly access the keystore files. Also, "the keystore password and keypassword must be same" is applicable to G Tomcat server.

Can you tell me the exact version of Geronimo server and the steps you are following that are resulting in the problem?

On Tue, Dec 2, 2008 at 5:48 AM, Christian Svensson <blue@...> wrote:

Hello!

I've been trying for the better part of today getting keystores to automatically unlock on startup - with very limited success.
Is there something that I should know about keystore password / key password? Digging around some old mailing list threads said something about key password must be equal to keystore password - any more of those gotchas?

The problem is that I create (or change password on geronimo-default for that matter) a new keystore, assign SSL to use the certificate and restart the server:
org.apache.geronimo.management.geronimo.KeystoreIsLocked: Keystore 'plasma-ssl' is locked; please use the keystore page in the admin console to unlock it
at org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLContext(FileKeystoreManager.java:343)
at org.apache.geronimo.jetty6.connector.GeronimoSelectChannelSSLListener.createSSLContext(GeronimoSelectChannelSSLListener.java:54)

Resetting the SSL connector to using geronimo-default / geronimo with secret / secret as passwords makes it work again - but why on earth doesn't Geronimo unlock my keystores on startup? I mean, it saves the password (or something like it) in config.xml.

Greetings,
--
Christian Svensson
Command Systems

--
Vamsi

--
Christian Svensson
Command Systems

--
Vamsi

From forum: Apache Geronimo - Users

Re: WARN [startup] Unresolved ejb reference "OutboundMessageHandlerService" in bean "OutboundMessageListenerServiceImpl"?!?!

2008-12-05T06:36:24Z

Hi,

I found a solution for my problem. In my ejb-jar.xml I removed the following entry:

<local-home></local-home>

and in the ejb-jar.xml of the other jar, where OutboundMessageHandlerService is in, I added the following lines:

<session id="OutboundMessageHandlerService">
<ejb-name>OutboundMessageHandlerService</ejb-name>
<ejb-class>com.test.OutboundMessageHandlerServiceImpl</ejb-class>
</session>

After redeployment and starting, I didn't found the warning again in my logfile.

sebbay

From forum: Apache Geronimo - Users

[jira] Assigned: (GERONIMO-4450) EJB based Provider implementation should allow other interfaces except for javax.xml.ws.Provider

2008-12-05T06:33:44Z

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

Jarek Gawor reassigned GERONIMO-4450:
-------------------------------------

Assignee: Jarek Gawor

> EJB based Provider implementation should allow other interfaces except for javax.xml.ws.Provider
> ------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4450
> URL: https://issues.apache.org/jira/browse/GERONIMO-4450
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.2
> Environment: Windows XP
> JDK 1.5.0
> Reporter: Ivan
> Assignee: Jarek Gawor
> Attachments: Geronimo-4450.patch
>
>
> While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces except for the Provider.
> Current implmentation, an exception will be thrown
> javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
> at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
> at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:810)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Geronimo - Dev

Re: Geronimo, keystores and SSL

2008-12-05T05:59:48Z

Hello.

It's a correct assumption that I am using Jetty, I'm using 2.1.3 Geronimo w/ Jetty package from the website (running with Sun Java 1.6).
I think it's the 3:rd step I'm lacking behind at.

This is how I created my setup:

1. Create a new keystore 'plasma-ssl'
2. Create a new private key 'wildcard'
3. Now the text on "Available" says "trust only" or something like that, I lock it and then unlock it in order for it to change to "1 key ready"
4. Then I configure my HTTPS connector to use the new keystore
5. Since the web server does not seem to do anything when I press "Shutdown" in the console, I use Ctrl+C to kill it.
6. Start the server again
7. Message appears.

1 to 4 are applied using the web console.

Have I done the step "Unlock keystore 'mykeystore' and private-key 'mykey' for availability." correctly?

Greetings,

On Fri, Dec 5, 2008 at 9:28 AM, Vamsavardhana Reddy <c1vamsi1c@...> wrote:

Hi Christian,

Once you create a new keystore, the keystore is not unlocked for availability automatically. After creating the keystore and private key, you need unlock the keystore for availability. The unlocked state for "availability" of the keystore is persistent. I assume that you are using Geronimo Jetty Server. Here are the steps I tried with Geronimo Jetty 2.1.3 and had no problem restarting the server.
1. Created a new keystore 'mykeystore'.
2. Created a private-key 'mykey'.
3. Unlock keystore 'mykeystore' and private-key 'mykey' for availability.
4. Edit HTTS web connector to use 'mykeystore'
5. Restart the server.

6. Unlock 'mykeystore' for editing.
7. Change password for 'mykey'.
8. Restart the server.

The Geronimo Tomcat server does not use the keystoregbean for HTTPS and directly access the keystore files. Also, "the keystore password and keypassword must be same" is applicable to G Tomcat server.

Can you tell me the exact version of Geronimo server and the steps you are following that are resulting in the problem?

On Tue, Dec 2, 2008 at 5:48 AM, Christian Svensson <blue@...> wrote:

Hello!

I've been trying for the better part of today getting keystores to automatically unlock on startup - with very limited success.
Is there something that I should know about keystore password / key password? Digging around some old mailing list threads said something about key password must be equal to keystore password - any more of those gotchas?

The problem is that I create (or change password on geronimo-default for that matter) a new keystore, assign SSL to use the certificate and restart the server:
org.apache.geronimo.management.geronimo.KeystoreIsLocked: Keystore 'plasma-ssl' is locked; please use the keystore page in the admin console to unlock it
at org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLContext(FileKeystoreManager.java:343)
at org.apache.geronimo.jetty6.connector.GeronimoSelectChannelSSLListener.createSSLContext(GeronimoSelectChannelSSLListener.java:54)

Resetting the SSL connector to using geronimo-default / geronimo with secret / secret as passwords makes it work again - but why on earth doesn't Geronimo unlock my keystores on startup? I mean, it saves the password (or something like it) in config.xml.

Greetings,
--
Christian Svensson
Command Systems

--
Vamsi

--
Christian Svensson
Command Systems

From forum: Apache Geronimo - Users

[BUILD] trunk: Failed for Revision: 723643

2008-12-05T05:14:07Z

Geronimo Revision: 723643 built with tests included

See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20081205/build-0300.log

See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20081205/unit-test-reports

[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[INFO] snapshot org.openqa.selenium.core:selenium-core:1.0-SNAPSHOT: checking for updates from codehaus-snapshots
[INFO] snapshot org.openqa.selenium.core:selenium-core:1.0-SNAPSHOT: checking for updates from apache.snapshots
[INFO] snapshot org.openqa.selenium.core:selenium-core:1.0-SNAPSHOT: checking for updates from openqa-snapshots
[INFO] snapshot org.openqa.selenium.core:selenium-core:1.0-SNAPSHOT: checking for updates from codehaus.org
Downloading: http://archiva.openqa.org/repository/snapshots/org/openqa/selenium/core/selenium-core/1.0-SNAPSHOT/selenium-core-1.0-20081113.155621-69.pom
15K downloaded
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
Downloading: http://archiva.openqa.org/repository/releases/log4j/log4j/1.2.14/log4j-1.2.14.pom
Downloading: http://repo1.maven.org/maven2/log4j/log4j/1.2.14/log4j-1.2.14.pom
2K downloaded
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1f6a1f6a
[WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.JdkPrefixProfileActivator@1f6a1f6a
Downloading: http://archiva.openqa.org/repository/releases/org/codehaus/groovy/maven/gmaven-mojo-support/1.0-rc-3/gmaven-mojo-support-1.0-rc-3.jar
Downloading: http://repo1.maven.org/maven2/org/codehaus/groovy/maven/gmaven-mojo-support/1.0-rc-3/gmaven-mojo-support-1.0-rc-3.jar
25K downloaded
Downloading: http://archiva.openqa.org/repository/snapshots/org/openqa/selenium/server/selenium-server/1.0-SNAPSHOT/selenium-server-1.0-20081127.211843-112-standalone.jar
5253K downloaded
Downloading: http://archiva.openqa.org/repository/snapshots/org/openqa/selenium/client-drivers/selenium-java-client-driver/1.0-SNAPSHOT/selenium-java-client-driver-1.0-20081127.211843-93.jar
49K downloaded
Downloading: http://archiva.openqa.org/repository/snapshots/org/openqa/selenium/core/selenium-core/1.0-SNAPSHOT/selenium-core-1.0-20081113.155621-69.jar
1615K downloaded
Downloading: http://archiva.openqa.org/repository/releases/log4j/log4j/1.2.14/log4j-1.2.14.jar
Downloading: http://repo1.maven.org/maven2/log4j/log4j/1.2.14/log4j-1.2.14.jar
358K downloaded
[INFO] [selenium:start-server {execution: start}]
Created dir: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/selenium
Launching Selenium Server
Waiting for Selenium Server...
[WARNING] OS appears to be Unix and no DISPLAY environment variable has been detected. Browser maybe unable to function correctly. Consider using the selenium:xvfb goal to enable headless operation.
[INFO] Redirecting output to: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/selenium/server.log
[INFO] User extensions: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/selenium/user-extensions.js
Selenium Server started
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using non-artifact based assembly archive: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/mconsole-jetty-server-2.2-SNAPSHOT-bin.zip
[INFO] Using geronimoHome: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/mconsole-jetty-server-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/mconsole-jetty-server-2.2-SNAPSHOT-bin.zip into /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: /home/geronimo/geronimo/trunk/plugins/monitoring/mconsole-jetty-server/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to start Geronimo server

Java returned: 1
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to start Geronimo server
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
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: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.MojoExecutionException: Failed to start Geronimo server
at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:106)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to start Geronimo server
at org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.doExecute(StartServerMojo.java:354)
at org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:99)
... 18 more
Caused by: Java returned: 1
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)
at org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo$1.run(StartServerMojo.java:313)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 293 minutes 47 seconds
[INFO] Finished at: Fri Dec 05 07:58:32 EST 2008
[INFO] Final Memory: 403M/1024M
[INFO] ------------------------------------------------------------------------

From forum: Apache Geronimo - Dev

Re: WARN [startup] Unresolved ejb reference "OutboundMessageHandlerService" in bean "OutboundMessageListenerServiceImpl"?!?!

2008-12-05T04:35:12Z

I changed my openejb-jar.xml as followed:

<message-driven>
<ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
<resource-adapter>
<resource-link>ebox2.mq.resource.adapter</resource-link>
</resource-adapter>
<ejb-ref>
<ref-name>OutboundMessageListenerServiceImpl</ref-name>
<ejb-link>OutboundMessageListenerServiceImpl</ejb-link>
</ejb-ref>
</message-driven>

I still get the same error/warn:

Unresolved ejb reference "OutboundMessageHandlerService" in bean "OutboundMessageListenerServiceImpl". Will attempt resolution again at runtime.

The EJB OutboundMessageHandlerService is in another jar-File, what's the reason for the following entry in ejb-jar.xml:

<ejb-local-ref id="OutboundMessageListenerServiceImplRefID">
...

In my ejb-jar.xml of the other jar, this ejb is not separatly declared. Could this be the reason for my problem?

manucet wrote:

Hi,
The ejb-link in openejb-jar.xml points to
OutboundMessageHandlerServiceImpl.For this to be resolved there should
be an ejb with the same name defined in openejb-jar.xml or
ejb-jar.xml.

Regards
Manu

On Fri, Dec 5, 2008 at 2:05 PM, sebbay <sebastian.bayerlein@elaxy.de> wrote:
>
> Hello,
>
> I'm new to geronimo and I have the following problem:
>
> I have an ear-file with two ejb jar's. the application gets successfully
> deployed, but not successfully started. In my server.out logfile I find the
> following entry:
>
>
> WARN [startup] Unresolved ejb reference "OutboundMessageHandlerService" in
> bean "OutboundMessageListenerServiceImpl"
>
> In my ejb-jar.xml of the jar-file where the
> OutboundMessageListenerServiceImpl-class is in, I have the following entry:
>
> <enterprise-beans>
> <message-driven id="OutboundMessageListenerServiceImplID">
> <ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
> <ejb-class>com.test.OutboundMessageListenerServiceImpl</ejb-class>
> <messaging-type>javax.jms.MessageListener</messaging-type>
> <transaction-type>Bean</transaction-type>
> <ejb-local-ref id="OutboundMessageListenerServiceImplRefID">
> <ejb-ref-name>OutboundMessageHandlerService</ejb-ref-name>
> <ejb-ref-type>Session</ejb-ref-type>
> <local-home></local-home>
> <local>com.test.OutboundMessageHandlerService</local>
> </ejb-local-ref>
> </message-driven>
> </enterprise-beans>
>
> My openejb-jar.xml consists the following entry:
>
> <message-driven>
> <ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
> <resource-adapter>
> <resource-link>ebox2.mq.resource.adapter</resource-link>
> </resource-adapter>
> <ejb-ref>
> <ref-name>OutboundMessageHandlerService</ref-name>
> <ejb-link>OutboundMessageHandlerServiceImpl</ejb-link>
> </ejb-ref>
> </message-driven>
>
>
> Can somebody tell me, what is missing in the files?
>
> sebbay
>
> --
> View this message in context: http://www.nabble.com/WARN---startup--Unresolved-ejb-reference-%22OutboundMessageHandlerService%22-in-bean-%22OutboundMessageListenerServiceImpl%22-%21-%21-tp20849699s134p20849699.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

From forum: Apache Geronimo - Users

Re: svn commit: r723242 - /geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml

2008-12-05T04:11:09Z

I've been seeing the same thing trying to run tck tests.

Joe

Jarek Gawor wrote:

> David,
>
> I'm not sure if anybody else is seeing this but I'm unable to reliably
> start a server after this change. Here's the error I get (from time to
> time when I try to start the server):
>
> 2008-12-04 22:26:45,686 ERROR [GBeanInstanceState] Error while
> starting; GBean is now in the FAILED state:
> abstractName="org.apache.geronimo.plugins.monitoring/agent/2.2-SNAPSHOT/car?EJBModule
> =org.apache.geronimo.plugins.monitoring/agent/2.2-SNAPSHOT/car,J2EEApplication=null,j2eeType=JACCManager,name=JACCManager"
> javax.security.auth.login.LoginException: No LoginModules configured
> for monitoring-runas-realm
> at javax.security.auth.login.LoginContext.init(LoginContext.java:256)
> at javax.security.auth.login.LoginContext.<init>(LoginContext.java:499)
> at org.apache.geronimo.security.ContextManager.login(ContextManager.java:83)
> at org.apache.geronimo.security.credentialstore.SimpleCredentialStoreImpl.getSubject(SimpleCredentialStoreImpl.java:100)
> at org.apache.geronimo.security.jacc.ApplicationPolicyConfigurationManager.<init>(ApplicationPolicyConfigurationManager.java:111)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:882)
> at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:272)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
> at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>
> Jarek
>
> On Thu, Dec 4, 2008 at 3:35 AM, <djencks@...> wrote:
>> Author: djencks
>> Date: Thu Dec 4 00:35:20 2008
>> New Revision: 723242
>>
>> URL: http://svn.apache.org/viewvc?rev=723242&view=rev
>> Log:
>> GERONIMO-4415 Use new SimpleCredentialStore isolation features
>>
>> Modified:
>> geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml
>>
>> Modified: geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml
>> URL: http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml?rev=723242&r1=723241&r2=723242&view=diff
>> ==============================================================================
>> --- geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml (original)
>> +++ geronimo/server/trunk/plugins/monitoring/agent/src/main/plan/plan.xml Thu Dec 4 00:35:20 2008
>> @@ -22,6 +22,7 @@
>> xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"
>> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
>> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2"
>> + xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"
>> xmlns:cs="http://geronimo.apache.org/xml/ns/credentialstore-1.0">
>>
>>
>> @@ -37,7 +38,7 @@
>> <sys:name>monitoring-credential-store</sys:name>
>> </sec:credential-store-ref>
>> <sec:default-subject>
>> - <sec:realm>geronimo-admin</sec:realm>
>> + <sec:realm>monitoring-runas-realm</sec:realm>
>> <sec:id>monitoring-user</sec:id>
>> </sec:default-subject>
>> <sec:role-mappings>
>> @@ -58,20 +59,43 @@
>> <sys:gbean name="monitoring-credential-store" class="org.apache.geronimo.security.credentialstore.SimpleCredentialStoreImpl">
>> <sys:xml-attribute name="credentialStore">
>> <cs:credential-store>
>> - <cs:realm name="geronimo-admin">
>> + <cs:realm name="monitoring-runas-realm">
>> <cs:subject>
>> <cs:id>monitoring-user</cs:id>
>> <cs:credential>
>> <cs:type>org.apache.geronimo.security.credentialstore.NameCallbackHandler</cs:type>
>> - <cs:value>system</cs:value>
>> - </cs:credential>
>> - <cs:credential>
>> - <cs:type>org.apache.geronimo.security.credentialstore.PasswordCallbackHandler</cs:type>
>> - <cs:value>manager</cs:value>
>> + <cs:value>admin</cs:value>
>> </cs:credential>
>> </cs:subject>
>> </cs:realm>
>> </cs:credential-store>
>> </sys:xml-attribute>
>> + <sys:reference name="Realms">
>> + <sys:name>monitoring-runas-realm</sys:name>
>> + </sys:reference>
>> + <sys:dependency>
>> + <nam:name>monitoring-runas-realm</nam:name>
>> + </sys:dependency>
>> </sys:gbean>
>> +
>> + <gbean name="monitoring-runas-realm"
>> + class="org.apache.geronimo.security.realm.GenericSecurityRealm">
>> + <attribute name="realmName">monitoring-runas-realm</attribute>
>> + <attribute name="publish">false</attribute>
>> + <xml-reference name="LoginModuleConfiguration">
>> + <lc:login-config xmlns:lc="http://geronimo.apache.org/xml/ns/loginconfig-1.2">
>> + <lc:login-module control-flag="REQUIRED">
>> + <lc:login-domain-name>monitoring-runas-domain</lc:login-domain-name>
>> + <lc:login-module-class>org.apache.geronimo.security.credentialstore.RunAsLoginModule</lc:login-module-class>
>> + <lc:option name="principalClass">org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal</lc:option>
>> + <lc:option name="principalNames">admin</lc:option>
>> + </lc:login-module>
>> + </lc:login-config>
>> + </xml-reference>
>> + 
>> + 
>> + 
>> + </gbean>
>> +
>> +
>> </openejb-jar>
>>
>>
>>
>

From forum: Apache Geronimo - Dev

Re: java.lang.LinkageError: Class org/apache/xbean/finder/ClassFinder violates loader constraints

2008-12-05T03:27:40Z

Another thing I am noticing is that module.getClassFinder().getClass().getClassLoader() returns "configs/j2ee-deployer/2.1.3/car" classLoader, whereas ClassFinder.class.getClassLoader() return "configs/openejb/2.1.3/car" classLoader.

On Tue, Nov 18, 2008 at 4:53 PM, Vamsavardhana Reddy <c1vamsi1c@...> wrote:

I am trying to invoke ClassFinder code from TuscanyModuleBuilderExtension I am creating for the Tuscany plugin. I have the following code
        ClassFinder cf = module.getClassFinder();
        List<Class> annotatedClasses = cf.findAnnotatedClasses(org.osoa.sca.annotations.Reference.class);

The call in the second line above is throwing a LinkageError. Stack trace is given below.

java.lang.LinkageError: Class org/apache/xbean/finder/ClassFinder violates loader constraints

    at org.apache.geronimo.tuscany.TuscanyModuleBuilderExtension.addGBeans(TuscanyModuleBuilderExtension.java:154)

    at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:497)

    at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165)

    at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647)

    at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254)

    at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)

    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.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.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)

    at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)

    at java.lang.Thread.run(Thread.java:595)

My guess is that it is some class loader issue. Any ideas on how to fix this problem?

--
Vamsi

--
Vamsi

From forum: Apache Geronimo - Dev

Re: WARN [startup] Unresolved ejb reference "OutboundMessageHandlerService" in bean "OutboundMessageListenerServiceImpl"?!?!

2008-12-05T03:04:07Z

Hi,
The ejb-link in openejb-jar.xml points to
OutboundMessageHandlerServiceImpl.For this to be resolved there should
be an ejb with the same name defined in openejb-jar.xml or
ejb-jar.xml.

Regards
Manu

On Fri, Dec 5, 2008 at 2:05 PM, sebbay <sebastian.bayerlein@...> wrote:

>
> Hello,
>
> I'm new to geronimo and I have the following problem:
>
> I have an ear-file with two ejb jar's. the application gets successfully
> deployed, but not successfully started. In my server.out logfile I find the
> following entry:
>
>
> WARN [startup] Unresolved ejb reference "OutboundMessageHandlerService" in
> bean "OutboundMessageListenerServiceImpl"
>
> In my ejb-jar.xml of the jar-file where the
> OutboundMessageListenerServiceImpl-class is in, I have the following entry:
>
> <enterprise-beans>
> <message-driven id="OutboundMessageListenerServiceImplID">
> <ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
> <ejb-class>com.test.OutboundMessageListenerServiceImpl</ejb-class>
> <messaging-type>javax.jms.MessageListener</messaging-type>
> <transaction-type>Bean</transaction-type>
> <ejb-local-ref id="OutboundMessageListenerServiceImplRefID">
> <ejb-ref-name>OutboundMessageHandlerService</ejb-ref-name>
> <ejb-ref-type>Session</ejb-ref-type>
> <local-home></local-home>
> <local>com.test.OutboundMessageHandlerService</local>
> </ejb-local-ref>
> </message-driven>
> </enterprise-beans>
>
> My openejb-jar.xml consists the following entry:
>
> <message-driven>
> <ejb-name>OutboundMessageListenerServiceImpl</ejb-name>
> <resource-adapter>
> <resource-link>ebox2.mq.resource.adapter</resource-link>
> </resource-adapter>
> <ejb-ref>
> <ref-name>OutboundMessageHandlerService</ref-name>
> <ejb-link>OutboundMessageHandlerServiceImpl</ejb-link>
> </ejb-ref>
> </message-driven>
>
>
> Can somebody tell me, what is missing in the files?
>
> sebbay
>
> --
> View this message in context: http://www.nabble.com/WARN---startup--Unresolved-ejb-reference-%22OutboundMessageHandlerService%22-in-bean-%22OutboundMessageListenerServiceImpl%22-%21-%21-tp20849699s134p20849699.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

From forum: Apache Geronimo - Users

[jira] Updated: (GERONIMO-4450) EJB based Provider implementation should allow other interfaces except for javax.xml.ws.Provider

2008-12-05T01:40:44Z

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

Ivan updated GERONIMO-4450:
---------------------------

Attachment: Geronimo-4450.patch

1.Change the logic to allow other interfaces exist.
2. Update the exception text.
Please help to review the patch, thanks !

> EJB based Provider implementation should allow other interfaces except for javax.xml.ws.Provider
> ------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4450
> URL: https://issues.apache.org/jira/browse/GERONIMO-4450
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.2
> Environment: Windows XP
> JDK 1.5.0
> Reporter: Ivan
> Attachments: Geronimo-4450.patch
>
>
> While a javax.xml.ws.Provider implementation is also an EJB session bean, it should allow other business interfaces except for the Provider.
> Current implmentation, an exception will be thrown
> javax.xml.ws.WebServiceException: Provider based SEI Class has to implement javax.xml.ws.Provider as javax.xml.ws.Provider<String>, javax.xml.ws.Provider<SOAPMessage>, javax.xml.ws.Provider<Source> or javax.xml.ws.Provider<JAXBContext>
> at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
> at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderType(EJBMessageReceiver.java:186)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.getProviderMethod(EJBMessageReceiver.java:171)
> at org.apache.geronimo.axis2.ejb.EJBMessageReceiver.receive(EJBMessageReceiver.java:73)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:84)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processXMLRequest(Axis2WebServiceContainer.java:444)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.processPOSTRequest(Axis2WebServiceContainer.java:386)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService2(Axis2WebServiceContainer.java:308)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.doService(Axis2WebServiceContainer.java:243)
> at org.apache.geronimo.axis2.Axis2WebServiceContainer.invoke(Axis2WebServiceContainer.java:201)
> at org.apache.geronimo.tomcat.TomcatEJBWebServiceContext$EJBWebServiceValve.invoke(TomcatEJBWebServiceContext.java:180)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:810)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Geronimo - Dev