[jira] Resolved: (GERONIMO-3525) Add a linkRef to map old MEJBGBean/MEJB JNDI name to new ejb/mgmt/MEJB
[ https://issues.apache.org/jira/browse/GERONIMO-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3525. Resolution: Fixed Fix Version/s: 2.0.2 2.0.x Add a linkRef to map old MEJBGBean/MEJB JNDI name to new ejb/mgmt/MEJB -- Key: GERONIMO-3525 URL: https://issues.apache.org/jira/browse/GERONIMO-3525 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.0.2, 2.0.x Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.0.x, 2.0.2 Openejb maps ejb refs of ejb/MEJB to jndi name of MEJBGBean/MEJB if a JNDI mapping is not specified. This should be changed in openejb however if we want to ship with openejb 3.0-beta-1 we must do an additional mapping from the old name to the new name with a jndi link. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3529) Cleanup old mejb bits laying around
[ https://issues.apache.org/jira/browse/GERONIMO-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-3529. -- Cleanup old mejb bits laying around --- Key: GERONIMO-3529 URL: https://issues.apache.org/jira/browse/GERONIMO-3529 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.0.x, 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.0.2, 2.0.x, 2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: OSGifying org.apache.geronimo.specs
Why not just have this in the root pom geronimo.osgi.import.pkg*/geronimo.osgi.import.pkg geronimo.osgi.export.pkgjavax.*/ geronimo.osgi.export.pkg geronimo.osgi.private.pkg*/geronimo.osgi.private.pkg Then the modules' pom would be more simple because we could remove both geronimo.osgi.export.pkg/ and geronimo.osgi.private.pkg/. Also, IIRC, you don't need to explicitly set the bundle's name and symbolic name since the default works quite nicely. Regards, Alan On Oct 19, 2007, at 8:19 AM, Guillaume Nodet wrote: So the question is wether these classes are meant to be seen by other jars or if they are only used by the javax.mail package. If they are to be exported, then it should be geronimo.osgi.export.pkgjavax.mail*,org.apache.geronimo.mail*/ geronimo.osgi.export.pkg but if they should be of private use, we need to add the following property geronimo.osgi.private.pkgorg.apache.geronimo.mail*/ geronimo.osgi.private.pkg I'm leaning toward the second option On 10/19/07, Rick McGuire [EMAIL PROTECTED] wrote: Guillaume, I'm working on a project that requires the latest javamail specs, and I've discovered that the OSGI changes have caused the org.apache.* classes to be ommitted from the jar file, which essentially renders this package inoperable. I was able to get those classes included by changing the geronimo.osgi.export.pkg definition to *. Is that the correct fix, or is something else more appropriate? Rick -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Commented: (GERONIMO-3451) Restricted listeners property file not found error logged during Tomcat server startup
[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536355
]
Paul McMahan commented on GERONIMO-3451:
It's not clear to me that this error message is actually harmless. Tomcat uses
RestrictedServlet.properties and RestrictedFilters.properties files as a sort
of internalized/proprietary security mechanism to limit access to certain types
of servlets and filters. The instance manager patch that is applied to
Geronimo's build of tomcat (see GERONIMO-3010 and GERONIMO-3206) introduced a
new type of security check in DefaultInstanceManager for restricted Listeners :
{{
private void checkAccess(Class clazz)
{
if(privileged)
return;
if(clazz.isAssignableFrom(javax/servlet/Filter))
checkAccess(clazz, restrictedFilters);
else
if(clazz.isAssignableFrom(javax/servlet/Servlet))
checkAccess(clazz, restrictedServlets);
else
checkAccess(clazz, restrictedListeners);
}
}}
However, that class also has a bug in the place where the
RestrictedListeners.properties is read in, adding its contents to the
restrictedFilters list instead of the restrictedListeners list.
{{
java.io.InputStream is =
getClass().getClassLoader().getResourceAsStream(org/apache/catalina/core/RestrictedListeners.properties);
if(is != null)
*restrictedFilters.load(is);*
else
catalinaContext.getLogger().error(sm.getString(defaultInstanceManager.restrictedListenersResources));
}}
So addressing this issue will involve :
# determine if the DefaultInstanceManager really needs to check for restricted
listeners
# if so, determine which listeners should be restricted (what to put in the
RestrictedListeners.properties)
# add RestrictedListeners.properties to Geronimo's catalina.jar
# fix the bug in DefaultInstanceManager mentioned above
Restricted listeners property file not found error logged during Tomcat
server startup
Key: GERONIMO-3451
URL: https://issues.apache.org/jira/browse/GERONIMO-3451
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Affects Versions: 2.0, 2.0.x
Reporter: Kevan Miller
Fix For: 2.0.x
During Tomcat server startup, the following log error is displayed on the
console:
12:57:32,559 ERROR [[/]] Restricted listeners property file not found
Althgough the log message can be ignored, users assume that something is
broken...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: OSGifying org.apache.geronimo.specs
I'm not sure that would work for javamail. Javamail has a strange discovery system where implementation of protocols, such as smtp, are loaded directly from the application class loader. I believe that if you hide the geronimo protocol implementations, javamail won't work. -dain On Oct 19, 2007, at 8:19 AM, Guillaume Nodet wrote: So the question is wether these classes are meant to be seen by other jars or if they are only used by the javax.mail package. If they are to be exported, then it should be geronimo.osgi.export.pkgjavax.mail*,org.apache.geronimo.mail*/ geronimo.osgi.export.pkg but if they should be of private use, we need to add the following property geronimo.osgi.private.pkgorg.apache.geronimo.mail*/ geronimo.osgi.private.pkg I'm leaning toward the second option On 10/19/07, Rick McGuire [EMAIL PROTECTED] wrote: Guillaume, I'm working on a project that requires the latest javamail specs, and I've discovered that the OSGI changes have caused the org.apache.* classes to be ommitted from the jar file, which essentially renders this package inoperable. I was able to get those classes included by changing the geronimo.osgi.export.pkg definition to *. Is that the correct fix, or is something else more appropriate? Rick -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Commented: (XBEAN-94) Need newest qdox version.... existing one freaks out on .
[ https://issues.apache.org/jira/browse/XBEAN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536377 ] David Jencks commented on XBEAN-94: --- I suspect it would be a better use of our time to actually use annotations and drop the fake javadoc stuff entirely. Need newest qdox version existing one freaks out on . -- Key: XBEAN-94 URL: https://issues.apache.org/jira/browse/XBEAN-94 Project: XBean Issue Type: Bug Components: maven-plugin Affects Versions: 3.1 Reporter: David Jencks Assignee: David Jencks Fix For: 3.2 Qdox 1.6.1 can't handle x y in field initializations. 1.6.3 can. Apache ds needs this :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3472) web server portlet does not save modifications to connectors correctly.
[ https://issues.apache.org/jira/browse/GERONIMO-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3472. --- Resolution: Fixed Fix Version/s: 2.1 2.0.x Applied patch to trunk (revision 586658) and branches/2.0 (revision 586657). Thanks! The bufferSizeBytes does not work for AJP connector because the Jetty setBufferSizeBytes() method for that connector does nothing and the SSL connector always overwrites the bufferSizeBytes its own value. web server portlet does not save modifications to connectors correctly. --- Key: GERONIMO-3472 URL: https://issues.apache.org/jira/browse/GERONIMO-3472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0.1, 2.1, Verification Required Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Fix For: 2.0.x, 2.1 Attachments: geronimo-3472.patch When the admin tries to edit a connector, any modifications to bufferSizeBytes, acceptQueueSize, and lingerMillis are not saved once the server is restarted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3539) Can not override providers using META-INF/javamail.providers file
Can not override providers using META-INF/javamail.providers file
-
Key: GERONIMO-3539
URL: https://issues.apache.org/jira/browse/GERONIMO-3539
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Affects Versions: 2.0.2, 2.0.1, 2.0
Reporter: Dain Sundstrom
Assignee: Rick McGuire
The Session.loadProviders(ClassLoader cl) loads provider files from:
META-INF/javamail.default.providers
${java.home}/lib/javamail.providers
META-INF/javamail.providers
but should be
${java.home}/lib/javamail.providers
META-INF/javamail.providers
META-INF/javamail.default.providers
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (XBEAN-94) Need newest qdox version.... existing one freaks out on .
[ https://issues.apache.org/jira/browse/XBEAN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed XBEAN-94. - Resolution: Fixed this got fixed a while back Need newest qdox version existing one freaks out on . -- Key: XBEAN-94 URL: https://issues.apache.org/jira/browse/XBEAN-94 Project: XBean Issue Type: Bug Components: maven-plugin Affects Versions: 3.1 Reporter: David Jencks Assignee: David Jencks Fix For: 3.2 Qdox 1.6.1 can't handle x y in field initializations. 1.6.3 can. Apache ds needs this :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3540) Session.loadProviders(ProviderInfo info, InputStream is) doesn't seem to handle comments correctly
Session.loadProviders(ProviderInfo info, InputStream is) doesn't seem to handle comments correctly -- Key: GERONIMO-3540 URL: https://issues.apache.org/jira/browse/GERONIMO-3540 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Affects Versions: 2.0.2, 2.0.1, 2.0 Reporter: Dain Sundstrom Assignee: Rick McGuire After reviewing the Session code, it doesn't appear that loadProviders is checking for comments. I believe that if you have an entry like this: # foo=bar; protocol=imap; type=store; class=com.sun.mail.imap.IMAPStore; vendor=Sun Microsystems, Inc.; it would process the entry. I have not tested this, so I could be wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ANNOUNCE] Availability of Geronimo 2.0.2
Congrats bubba ... we've come a long way baby. On Oct 19, 2007, at 11:30 AM, Kevan Miller wrote: All, Wanted to let everyone know that the Geronimo 2.0.2 binaries are available for download -- http://geronimo.apache.org/downloads.html 2.0.2 addresses a number of issues that were found in our 2.0.1 release, including the MEJB security vulnerability. Great work everyone! --kevan
[jira] Closed: (GERONIMO-3393) scrub the attribute lists for tomcat connector gbeans
[ https://issues.apache.org/jira/browse/GERONIMO-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-3393. -- Resolution: Fixed scrub the attribute lists for tomcat connector gbeans - Key: GERONIMO-3393 URL: https://issues.apache.org/jira/browse/GERONIMO-3393 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0.x Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 2.1 The list of attributes for tomcat connectors defined in TomcatManagerImpl should match Tomcat's online documentation as much as possible. The default values and descriptions are a little out of synch. HTTP : http://tomcat.apache.org/tomcat-6.0-doc/config/http.html AJP : http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html APR: http://tomcat.apache.org/tomcat-6.0-doc/apr.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3472) web server portlet does not save modifications to connectors correctly.
[ https://issues.apache.org/jira/browse/GERONIMO-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3472: - Assignee: Jarek Gawor web server portlet does not save modifications to connectors correctly. --- Key: GERONIMO-3472 URL: https://issues.apache.org/jira/browse/GERONIMO-3472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.0.1, 2.1, Verification Required Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Jarek Gawor Attachments: geronimo-3472.patch When the admin tries to edit a connector, any modifications to bufferSizeBytes, acceptQueueSize, and lingerMillis are not saved once the server is restarted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
servicemix-http/jsr181-component doesn't fully work with SoapBinding parameterStyle.WRAPPED, only work for BARE
Hi All, Has anybody used servicemix-http/jsr181-component pair (wsdl-first example) with SoapBinding.parameterStyle=WRAPPED for multiple input parameters or return value? I was trying to use this pair(just like the, GetPerson example in wsdl-first) for multiple parameters input (such as string arg0, string arg1) for a very simple service (basically a hello service, return = arg0 + arg1). I got two errors: arg1 is missing in input(the first input is passed in) and return is null. The client side is .Net client. instead of html. Does anybody see why? thanks, Ying -- View this message in context: http://www.nabble.com/servicemix-http-jsr181-component-doesn%27t-fully-work-with-SoapBinding-parameterStyle.WRAPPED%2C-only-work-for-BARE-tf4656378s12049.html#a13305204 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (XBEAN-94) Need newest qdox version.... existing one freaks out on .
[ https://issues.apache.org/jira/browse/XBEAN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536366 ] alex322 commented on XBEAN-94: -- QDox often fails on perfectly legitimate source files. Whould it be feasible to have the MappingGeneratorTask implemented as a standard doclet? It would then be invoked by javadoc doclet=..MappingGeneratorTask ... Need newest qdox version existing one freaks out on . -- Key: XBEAN-94 URL: https://issues.apache.org/jira/browse/XBEAN-94 Project: XBean Issue Type: Bug Components: maven-plugin Affects Versions: 3.1 Reporter: David Jencks Assignee: David Jencks Fix For: 3.2 Qdox 1.6.1 can't handle x y in field initializations. 1.6.3 can. Apache ds needs this :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3529) Cleanup old mejb bits laying around
[ https://issues.apache.org/jira/browse/GERONIMO-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3529. Resolution: Fixed Fix Version/s: 2.0.2 2.1 2.0.x Cleanup old mejb bits laying around --- Key: GERONIMO-3529 URL: https://issues.apache.org/jira/browse/GERONIMO-3529 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0.2, 2.0.x, 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 2.0.x, 2.1, 2.0.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3538) OSGI packaging of javamail spec removes org.apache.* classes from jav file.
[ https://issues.apache.org/jira/browse/GERONIMO-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-3538. -- Resolution: Fixed Fixed by another fix. OSGI packaging of javamail spec removes org.apache.* classes from jav file. --- Key: GERONIMO-3538 URL: https://issues.apache.org/jira/browse/GERONIMO-3538 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Reporter: Rick McGuire Assignee: Rick McGuire The OSGI packaging changes only included the javax.mail.* classes in the packaging. This resulted in the org.apache.* backing classes getting omitted from the jar file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ANNOUNCE] Availability of Geronimo 2.0.2
Sweet!!! I updated the website, some changes will get reflected within the next hour. Cheers! Hernan Kevan Miller wrote: All, Wanted to let everyone know that the Geronimo 2.0.2 binaries are available for download -- http://geronimo.apache.org/downloads.html 2.0.2 addresses a number of issues that were found in our 2.0.1 release, including the MEJB security vulnerability. Great work everyone! --kevan
[jira] Updated: (GERONIMO-3393) scrub the attribute lists for tomcat connector gbeans
[ https://issues.apache.org/jira/browse/GERONIMO-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan updated GERONIMO-3393: --- Description: The list of attributes for tomcat connectors defined in TomcatManagerImpl should match Tomcat's online documentation as much as possible. The default values and descriptions are a little out of synch. HTTP : http://tomcat.apache.org/tomcat-6.0-doc/config/http.html AJP : http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html APR: http://tomcat.apache.org/tomcat-6.0-doc/apr.html was: The list of attributes for tomcat connectors defined in TomcatManagerImpl should match Tomcat's online documentation as much as possible. The default values and descriptions are a little out of synch. HTTP : http://tomcat.apache.org/tomcat-6.0-doc/config/http.html AJP : http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html Fix Version/s: 2.1 scrub the attribute lists for tomcat connector gbeans - Key: GERONIMO-3393 URL: https://issues.apache.org/jira/browse/GERONIMO-3393 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0.x Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 2.1 The list of attributes for tomcat connectors defined in TomcatManagerImpl should match Tomcat's online documentation as much as possible. The default values and descriptions are a little out of synch. HTTP : http://tomcat.apache.org/tomcat-6.0-doc/config/http.html AJP : http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html APR: http://tomcat.apache.org/tomcat-6.0-doc/apr.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3393) scrub the attribute lists for tomcat connector gbeans
[ https://issues.apache.org/jira/browse/GERONIMO-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan reassigned GERONIMO-3393: -- Assignee: Paul McMahan scrub the attribute lists for tomcat connector gbeans - Key: GERONIMO-3393 URL: https://issues.apache.org/jira/browse/GERONIMO-3393 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0.x Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 2.1 The list of attributes for tomcat connectors defined in TomcatManagerImpl should match Tomcat's online documentation as much as possible. The default values and descriptions are a little out of synch. HTTP : http://tomcat.apache.org/tomcat-6.0-doc/config/http.html AJP : http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: OSGifying org.apache.geronimo.specs
The second option would still include the classes inside the jar. The only difference is that these classes would be hidden when inside an OSGi environment, while the javax.* classes would be visible. In a non-OSGi env, everything would be visible. I've just committed a fix and the classes are now back in the jar. I'd have to test it in an OSGi env... On 10/19/07, Rick McGuire [EMAIL PROTECTED] wrote: They are used by the provider jar also, so it would need to be the first option, I believe. This is how I ran into the problem originally. Rick Guillaume Nodet wrote: So the question is wether these classes are meant to be seen by other jars or if they are only used by the javax.mail package. If they are to be exported, then it should be geronimo.osgi.export.pkgjavax.mail*,org.apache.geronimo.mail*/geronimo.osgi.export.pkg but if they should be of private use, we need to add the following property geronimo.osgi.private.pkgorg.apache.geronimo.mail*/geronimo.osgi.private.pkg I'm leaning toward the second option On 10/19/07, Rick McGuire [EMAIL PROTECTED] wrote: Guillaume, I'm working on a project that requires the latest javamail specs, and I've discovered that the OSGI changes have caused the org.apache.* classes to be ommitted from the jar file, which essentially renders this package inoperable. I was able to get those classes included by changing the geronimo.osgi.export.pkg definition to *. Is that the correct fix, or is something else more appropriate? Rick -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: ServiceMix Bean issues with send()
So, basically, there is no concept of consumer endpoint: an exchange is sent from a component to an endpoint. Inside servicemix components, we usually have this concept of consumer endpoint, but in such case, this means that the component has to dispatch the incoming exchange back to the endpoint that sent it. On 10/19/07, Andreas Schaefer [EMAIL PROTECTED] wrote: HI Guillaume I hope you are right even though I am not quite sure how you want to figure out the service name of the consumer. I still think it is a problem of the core. Even if we can fix the problem inside the Bean BC the problem may arise on other BCs as well. I think that we should not only have a source component but also a source service name or any form of internal identification of the source SU. BTW today I am at home and so we may can discuss this through IRC if you want. -Andy Guillaume Nodet wrote: I had some time to look at your test case on the plane and i think i found a fix. In all cases i'm quite sure that the problem comes from the component and not from the container. The fix is mainly to inject on the pojo a delivery channel that will track consumer exchanges sent by the bean. That way, the component will know about the exchange and will not throw an exception. 2007/10/19, Andreas Schaefer (2) [EMAIL PROTECTED]: Tomorrow I plan to try to fix this issue but if anyone sees a flaw in my design please stop beforehand. Today I finally resolved the problem of how does ServiceMix know to which component it should send the Message Exchange (ME) back even though it uses the wrong Service Name. Inside the AbstractFlow.doRouting() it uses the SourceId from the ME to find the correct Binding Component (BC). That is why in my test project the call goes back tot he Bean BC even though it tries to call a service that is actually based on a Script BC. This makes me hopeful that applying the same logic to the service name could fix the issue. That is what I want to do to fix it: - service name is removed from the packet and placed inside the ME (maybe also the endpoint) - the ME.setServiceName() is actually set on the MIRROR.serviceName member (so that I don't have to change the logic of switching the ME with its MIRROR) - the consumer's service name is set on the ME before the ME is sent onto the flow. This is either done on the Message Exchange Factory or on the Delivery Channel which is probably the better choice because then on the way back the service name of the provider can also be set if not already done). I just have to figure out how to obtain the service name of the sending SU from within the Delivery Channel. I think that should do the trick even though I don't know what the implications on the SYNCHRONOUS ME are and hope that I am not going to open Pandora's Box. Thanks - Andy -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Resolved: (GERONIMO-3536) Out-of-date security descriptors in 2.0 documentation
[ https://issues.apache.org/jira/browse/GERONIMO-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3536. --- Resolution: Fixed Fixed 1). Updated the DD and uploaded a new screen shot. Out-of-date security descriptors in 2.0 documentation - Key: GERONIMO-3536 URL: https://issues.apache.org/jira/browse/GERONIMO-3536 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Reporter: Jarek Gawor Assignee: Jarek Gawor 1) http://cwiki.apache.org/GMOxDOC20/adminstering-security-realms.html - contains old DD and screen shot 2) http://cwiki.apache.org/GMOxDOC20/ldap-sample-application.html - bad ldap-realm.xml 3) http://cwiki.apache.org/GMOxDOC20/web-application-security-sample.html bad TimeReportPool.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: OSGifying org.apache.geronimo.specs
So the question is wether these classes are meant to be seen by other jars or if they are only used by the javax.mail package. If they are to be exported, then it should be geronimo.osgi.export.pkgjavax.mail*,org.apache.geronimo.mail*/geronimo.osgi.export.pkg but if they should be of private use, we need to add the following property geronimo.osgi.private.pkgorg.apache.geronimo.mail*/geronimo.osgi.private.pkg I'm leaning toward the second option On 10/19/07, Rick McGuire [EMAIL PROTECTED] wrote: Guillaume, I'm working on a project that requires the latest javamail specs, and I've discovered that the OSGI changes have caused the org.apache.* classes to be ommitted from the jar file, which essentially renders this package inoperable. I was able to get those classes included by changing the geronimo.osgi.export.pkg definition to *. Is that the correct fix, or is something else more appropriate? Rick -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: ServiceMix Bean issues with send()
HI Guillaume I hope you are right even though I am not quite sure how you want to figure out the service name of the consumer. I still think it is a problem of the core. Even if we can fix the problem inside the Bean BC the problem may arise on other BCs as well. I think that we should not only have a source component but also a source service name or any form of internal identification of the source SU. BTW today I am at home and so we may can discuss this through IRC if you want. -Andy Guillaume Nodet wrote: I had some time to look at your test case on the plane and i think i found a fix. In all cases i'm quite sure that the problem comes from the component and not from the container. The fix is mainly to inject on the pojo a delivery channel that will track consumer exchanges sent by the bean. That way, the component will know about the exchange and will not throw an exception. 2007/10/19, Andreas Schaefer (2) [EMAIL PROTECTED]: Tomorrow I plan to try to fix this issue but if anyone sees a flaw in my design please stop beforehand. Today I finally resolved the problem of how does ServiceMix know to which component it should send the Message Exchange (ME) back even though it uses the wrong Service Name. Inside the AbstractFlow.doRouting() it uses the SourceId from the ME to find the correct Binding Component (BC). That is why in my test project the call goes back tot he Bean BC even though it tries to call a service that is actually based on a Script BC. This makes me hopeful that applying the same logic to the service name could fix the issue. That is what I want to do to fix it: - service name is removed from the packet and placed inside the ME (maybe also the endpoint) - the ME.setServiceName() is actually set on the MIRROR.serviceName member (so that I don't have to change the logic of switching the ME with its MIRROR) - the consumer's service name is set on the ME before the ME is sent onto the flow. This is either done on the Message Exchange Factory or on the Delivery Channel which is probably the better choice because then on the way back the service name of the provider can also be set if not already done). I just have to figure out how to obtain the service name of the sending SU from within the Delivery Channel. I think that should do the trick even though I don't know what the implications on the SYNCHRONOUS ME are and hope that I am not going to open Pandora's Box. Thanks - Andy
Re: http://geronimo.apache.org/downloads.html
I'll look for a way to have two tabs, one for latest release and one for previous releases. For the latest tab, would it be too complicated to have a weekly stable build right out of trunk? I think we discussed about this some time ago but can't remember what was the outcome. Cheers! Hernan Jarek Gawor wrote: Just a small thought, since I think we are trying to move G 1.2 and 1.1 users onto G 2.0 maybe we should separate 2.0 downloads from the older downloads. Right now all the downloads are under the same Available releases tab. I would propose creating Current releases tab with the latest 2.0.x download and Previous releases tab with all the other older releases. Also increasing the font size of the 2.0.x download would help to distinguish itself from other downloads. Jarek
[jira] Updated: (XBEAN-97) default-lazy-init is ignored
[
https://issues.apache.org/jira/browse/XBEAN-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
alex322 updated XBEAN-97:
-
Component/s: spring
default-lazy-init is ignored
Key: XBEAN-97
URL: https://issues.apache.org/jira/browse/XBEAN-97
Project: XBean
Issue Type: Bug
Components: spring
Reporter: alex322
lazyInit is always false.
Adding this snippet to
org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement
should solve the problem :
BeanDefinition def = result.getBeanDefinition();
if (def instanceof AbstractBeanDefinition) {
AbstractBeanDefinition adef =
(AbstractBeanDefinition) def;
if
(!element.hasAttribute(BeanDefinitionParserDelegate.LAZY_INIT_ATTRIBUTE)) {
adef.setLazyInit(parserContext.isDefaultLazyInit());
}
}
Also checking for top-level bean definition can be simplified:
if (!parserContext.isNested())
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3538) OSGI packaging of javamail spec removes org.apache.* classes from jav file.
OSGI packaging of javamail spec removes org.apache.* classes from jav file. --- Key: GERONIMO-3538 URL: https://issues.apache.org/jira/browse/GERONIMO-3538 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Reporter: Rick McGuire Assignee: Rick McGuire The OSGI packaging changes only included the javax.mail.* classes in the packaging. This resulted in the org.apache.* backing classes getting omitted from the jar file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
AW: Possible Solution to a camel serviceengine problem or only a bad workaround??
please also see: https://issues.apache.org/activemq/browse/SM- this is the summary ;-) -Ursprüngliche Nachricht- Von: Guillaume Nodet [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 18. Oktober 2007 13:19 An: [EMAIL PROTECTED] Betreff: Re: Possible Solution to a camel serviceengine problem or only a bad workaround?? On 10/18/07, Kristian Köhler [EMAIL PROTECTED] wrote: Hi Anyway, I think you're on the right track. There's no reason why the camel SE would set the jbi.operation property when going from jbi to camel, but not use it when going from camel to jbi. In addition, we could make the operation also configurable on the endpoint (to be consistent with the mep), so I think we need to add: jbi:endpoint:?operation= Good to hear that I'm not totaly wrong ;-) I will also add the second option to the patch and raise a jira issue. Also, I can't recall if camel provides a way to change the mep easily: I know it is a loosely defined notion in camel, but still, there should be an accessor in the DSL I suppose. I also meant that if there is not, it should be added :-) I'm searching... Kristian -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Resolved: (GERONIMO-3532) Getting java.lang.IllegalStateException while stopping geronimo service
[ https://issues.apache.org/jira/browse/GERONIMO-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3532. --- Resolution: Fixed I updated the wiki page with newer wrapper.conf that changes how the server is stopped. Before the server was stopped using the shutdown client. However, the shutdown client needs to run in its own JVM. And since the shutdown client was running in the same JVM as the server that exception was generated. Now, the server will be shutdown when System.exit() is called. That actually simplifies the integration between Geronimo and Java Service Wrapper and is cleaner. Getting java.lang.IllegalStateException while stopping geronimo service --- Key: GERONIMO-3532 URL: https://issues.apache.org/jira/browse/GERONIMO-3532 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 2.0.1 Environment: Windows XP, geronimo-tomcat6-jee5-2.0.1, wrapper-windows-x86-32-3.2.3,Sun java 1.5.0_13, IBM java 1.5.0 sr5 Reporter: Ashish Jain Assignee: Jarek Gawor I am getting the following error while stopping geronimo service. I am referring the following link. http://cwiki.apache.org/GMOxDOC20/configuring-geronimo-as-a-windows-service.html Startup is fine but while stopping I am getting java.lang.IllegalStateException. I have tested this in Sun java as well as IBM Java.This is the complete trace for start and stop of the service STATUS | wrapper | 2007/10/11 23:07:42 | Starting the Apache Geronimo v2.0 Server service... STATUS | wrapper | 2007/10/11 23:07:42 | -- Wrapper Started as Service STATUS | wrapper | 2007/10/11 23:07:42 | Launching a JVM... INFO | jvm 1| 2007/10/11 23:07:42 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1| 2007/10/11 23:07:42 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1| 2007/10/11 23:07:42 | INFO | jvm 1| 2007/10/11 23:07:44 | Booting Geronimo Kernel (in Java 1.5.0)... INFO | jvm 1| 2007/10/11 23:07:44 | Starting Geronimo Application Server v2.0.1 INFO | jvm 1| 2007/10/11 23:07:44 | INFO | jvm 1| 2007/10/11 23:07:44 | [*] 0% 0s Loading INFO | jvm 1| 2007/10/11 23:07:44 | [*- ] 0% 0s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [*- ] 0% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [* ] 6% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [** ] 8% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [**- ] 8% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [** ] 9% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [** ] 9% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 11% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [***- ] 11% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 12% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 12% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [ ] 14% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [-] 14% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [] 15% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*] 17% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*- ] 17% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*- ] 17% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:47 | [* ] 18% 2s Loading org.apache.ge... STATUS | wrapper | 2007/10/11 23:07:47 | Apache Geronimo v2.0 Server started. INFO | jvm 1| 2007/10/11 23:07:47 | [* ] 18% 3s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:48 | [* ] 18% 3s Starting org.apache.ge.. . INFO | jvm 1| 2007/10/11 23:07:48 | [* ]
[jira] Commented: (SM-1110) ServiceMix is not sending a response back to the calling Service in an In-Out Message Exchange
[
https://issues.apache.org/activemq/browse/SM-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40436
]
Guillaume Nodet commented on SM-1110:
-
Sending
servicemix-bean/src/main/java/org/apache/servicemix/bean/BeanEndpoint.java
Adding
servicemix-bean/src/test/java/org/apache/servicemix/bean/ConsumerListenerTest.java
Sending
servicemix-bean/src/test/java/org/apache/servicemix/bean/beans/ConsumerListener.java
Transmitting file data ...
Committed revision 586570.
I will that in trunk asap.
ServiceMix is not sending a response back to the calling Service in an In-Out
Message Exchange
--
Key: SM-1110
URL: https://issues.apache.org/activemq/browse/SM-1110
Project: ServiceMix
Issue Type: Bug
Components: servicemix-bean, servicemix-core
Affects Versions: 3.1.2
Environment: MacBook Pro
Mac OS X 10.4
Java JDK 1.5.0.7
Maven 2.0.7
Reporter: Andreas Schaefer
Attachments: smx.send.problem.test.zip
When sending an In-Out message from a Bean SU to another component (here a
Script SU) asynchronously then the response is not routed back to the calling
SU even though it returns back to the correct BC. What is happening is that
the Consumer Endpoint of the called SU is used. In the attached test the
called SU is based on a Script BC and so it cannot even find a service.
Note: the problem is not somewhat shortcut by the issues SM-994
(https://issues.apache.org/activemq/browse/SM-944). I hacked the issue and I
see that the called SU is called.
The attached file is a ZIP file of a complete project. To run the test build
the project with mvn install.
The important lines are:
2007-10-18 10:32:07,851 [ed-0:1-thread-1] INFO InOutReceiver
- process(), send back response, ME: InOut[
id: ID:10.250.1.197-115b42ceaed-2:0
status: Active
role: provider
service: {urn:xTest}script-receiver-service
endpoint: in-out-receiver
operation: IdontCare: 0
in: ?xml version=1.0
encoding=UTF-8?receivertitleDontCareEvenMore/titleindex0/index/receiver
out: ?xml version=1.0 encoding=UTF-8?worldhello/world
]
2007-10-18 10:32:07,857 [ed-0:1-thread-1] DEBUG DeliveryChannelImpl
- Send ID:10.250.1.197-115b42ceaed-2:0 in
DeliveryChannel{ID:10.250.1.197-115b42ceaed-0:1}
2007-10-18 10:32:07,858 [ed-0:1-thread-1] DEBUG SedaFlow
- Called Flow send
2007-10-18 10:32:07,859 [ed-0:1-thread-2] DEBUG SedaQueue
- [EMAIL PROTECTED] dequeued exchange: InOut[
id: ID:10.250.1.197-115b42ceaed-2:0
status: Active
role: consumer
service: {urn:xTest}script-receiver-service
endpoint: in-out-receiver
operation: IdontCare: 0
in: ?xml version=1.0
encoding=UTF-8?receivertitleDontCareEvenMore/titleindex0/index/receiver
out: ?xml version=1.0 encoding=UTF-8?worldhello/world
]
2007-10-18 10:32:07,859 [ed-0:1-thread-2] DEBUG BeanComponent
- Received exchange: status: Active, role: consumer
2007-10-18 10:32:07,859 [ed-0:1-thread-2] DEBUG BeanComponent
- Retrieved correlation id: ID:10.250.1.197-115b42ceaed-2:0
2007-10-18 10:32:07,862 [ed-0:1-thread-2] ERROR BeanComponent
- Error processing exchange InOut[
id: ID:10.250.1.197-115b42ceaed-2:0
status: Active
role: consumer
service: {urn:xTest}script-receiver-service
endpoint: in-out-receiver
operation: IdontCare: 0
in: ?xml version=1.0
encoding=UTF-8?receivertitleDontCareEvenMore/titleindex0/index/receiver
out: ?xml version=1.0 encoding=UTF-8?worldhello/world
]
java.lang.IllegalStateException: Receiving unknown consumer exchange: InOut[
id: ID:10.250.1.197-115b42ceaed-2:0
status: Active
role: consumer
service: {urn:xTest}script-receiver-service
endpoint: in-out-receiver
operation: IdontCare: 0
in: ?xml version=1.0
encoding=UTF-8?receivertitleDontCareEvenMore/titleindex0/index/receiver
out: ?xml version=1.0 encoding=UTF-8?worldhello/world
]
at
org.apache.servicemix.bean.BeanEndpoint.onConsumerExchange(BeanEndpoint.java:266)
at
org.apache.servicemix.bean.BeanEndpoint.process(BeanEndpoint.java:196)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:463)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
Re: Possible Solution to a camel serviceengine problem or only a bad workaround??
On 18/10/2007, Guillaume Nodet [EMAIL PROTECTED] wrote: The attachment was removed from your mail i suppose. Maybe just raise a jira and attach it there. Anyway, I think you're on the right track. There's no reason why the camel SE would set the jbi.operation property when going from jbi to camel, but not use it when going from camel to jbi. In addition, we could make the operation also configurable on the endpoint (to be consistent with the mep), so I think we need to add: jbi:endpoint:?operation= Also, I can't recall if camel provides a way to change the mep easily: I know it is a loosely defined notion in camel, but still, there should be an accessor in the DSL I suppose. Yeah - the setPattern() is available on the camel Exchange; so it should be easy to change the MEP inside a component or in a processor or even adding it into the DSL -- James --- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com
[jira] Assigned: (GERONIMO-3536) Out-of-date security descriptors in 2.0 documentation
[ https://issues.apache.org/jira/browse/GERONIMO-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3536: - Assignee: Jarek Gawor Out-of-date security descriptors in 2.0 documentation - Key: GERONIMO-3536 URL: https://issues.apache.org/jira/browse/GERONIMO-3536 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Reporter: Jarek Gawor Assignee: Jarek Gawor 1) http://cwiki.apache.org/GMOxDOC20/adminstering-security-realms.html - contains old DD and screen shot 2) http://cwiki.apache.org/GMOxDOC20/ldap-sample-application.html - bad ldap-realm.xml 3) http://cwiki.apache.org/GMOxDOC20/web-application-security-sample.html bad TimeReportPool.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ServiceMix Bean issues with send()
I had some time to look at your test case on the plane and i think i found a fix. In all cases i'm quite sure that the problem comes from the component and not from the container. The fix is mainly to inject on the pojo a delivery channel that will track consumer exchanges sent by the bean. That way, the component will know about the exchange and will not throw an exception. 2007/10/19, Andreas Schaefer (2) [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tomorrow I plan to try to fix this issue but if anyone sees a flaw in my design please stop beforehand. Today I finally resolved the problem of how does ServiceMix know to which component it should send the Message Exchange (ME) back even though it uses the wrong Service Name. Inside the AbstractFlow.doRouting() it uses the SourceId from the ME to find the correct Binding Component (BC). That is why in my test project the call goes back tot he Bean BC even though it tries to call a service that is actually based on a Script BC. This makes me hopeful that applying the same logic to the service name could fix the issue. That is what I want to do to fix it: - - service name is removed from the packet and placed inside the ME (maybe also the endpoint) - - the ME.setServiceName() is actually set on the MIRROR.serviceName member (so that I don't have to change the logic of switching the ME with its MIRROR) - - the consumer's service name is set on the ME before the ME is sent onto the flow. This is either done on the Message Exchange Factory or on the Delivery Channel which is probably the better choice because then on the way back the service name of the provider can also be set if not already done). I just have to figure out how to obtain the service name of the sending SU from within the Delivery Channel. I think that should do the trick even though I don't know what the implications on the SYNCHRONOUS ME are and hope that I am not going to open Pandora's Box. Thanks - Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHGADWs4gPTNnP0gkRAsNpAJ9knS8kX0NfIbAMW+uGgBjIN0i3zQCfceDi rdw1L46NBoZnzqQzLYILOEw= =VDq2 -END PGP SIGNATURE- -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Created: (SM-1111) Endpoint operation information lost when routing through camel
Endpoint operation information lost when routing through camel
--
Key: SM-
URL: https://issues.apache.org/activemq/browse/SM-
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Reporter: Kristian Koehler
Attachments: patches.zip
Hi
I encountered problems regarding message routing to the camel service engine and
back to the jbi NMR again. The information about the (initial) called
operation on a endpoint is lost while communicating with camel.
see also
http://www.nabble.com/Possible-Solution-to-a-camel-serviceengine-problem-or-only-a-bad-workaround---tf4645158s12049.html
IMHO there are three different strategies to solve this problem:
(thanks Guillaume pointing me to them ;-) )
* (1) DSL - API call within the RouteBuilder
It's currently not possible to do this because the JbiEndpoint doesn't have
methods to set the operation.
Sample:
--- 8 ---
String toUri = jbi:endpoint:xxx;
Endpoint endpoint = getContext().getEndpoint(toUri);
if (endpoint instanceof JbiEndpoint) {
JbiEndpoint jbiEndpoint = (JbiEndpoint) endpoint;
//not possible
jbiEndpoint.setOperation(operation);
}
from(fromUri).to(toUri);
--- 8 ---
* (2) URI - Setting the operation within the endpoint URI.
This option specifies the operation within the given endpoint URI. It's clear
which operation should be called but you always have to define the operation
for a routing.
--- 8 ---
String toUri = jbi:endpoint:xxx?operation=process;
from(fromUri).to(toUri);
--- 8 ---
* (3) Copying the information
This option copies the operation information from the from-Endpoint to the
to-Endpoint. This is a simple solution if you want to call the same
operation on all endpoints involved.
I think option 2 and 3 should be applied. Option 2 overrides option 3. If you
specify a direct operation information within your URI this one is used.
Kristian
ps: option 2 and 3 are available as patches within the attached file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3478) Mulitple URISyntaxException getting plugins from another server
[ https://issues.apache.org/jira/browse/GERONIMO-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3478: - Assignee: Jarek Gawor Mulitple URISyntaxException getting plugins from another server --- Key: GERONIMO-3478 URL: https://issues.apache.org/jira/browse/GERONIMO-3478 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.0.1 Reporter: Ted Kirby Assignee: Jarek Gawor From the admin console, I added Repository http://tkirby3.example.acme.com:8080/console-standard/maven-repo/. This did not work, ie, it did not show up in my list of repositories. Then, I added http://tkirby3.example.acme.com:8080/console-standard/maven-repo (no trailing slash), and this worked, ie, http://tkirby3.example.acme.com:8080/console-standard/maven-repo/ (note the trailing slash) showed up in my repo list. I then searched for plugins, forgetting to put in the userid and password. This sequence of steps resulted in four of these errors and tracebacks in my server log, of which this is only the first: 18:56:21,906 WARN [AddRepositoryHandler] Unexpected response code while validating repository (505 HTTP Version Not Supported). Assuming you know what you're doing. 18:56:21,937 ERROR [PluginRepositoryDownloader] Unable to format plugin repository URL http://tkirby3.example.acme.com:8080/console-standard/maven-repo/ / java.net.URISyntaxException: Illegal character in path at index 64: http://tkirby3.exampl.acme.com:8080/console-standard/maven-repo/ / at java.net.URI$Parser.fail(URI.java:2821) at java.net.URI$Parser.checkChars(URI.java:2994) at java.net.URI$Parser.parseHierarchical(URI.java:3078) at java.net.URI$Parser.parse(URI.java:3026) at java.net.URI.init(URI.java:590) at org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getRepositories(PluginRepositoryDownloader.java:90) at org.apache.geronimo.system.plugin.PluginRepositoryDownloader$$FastClassByCGLIB$$7de10f4e.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.GBeanAttribute.getValue(GBeanAttribute.java:390) at org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(GBeanInstance.java:652) at org.apache.geronimo.gbean.runtime.RawInvoker.getAttribute(RawInvoker.java:49) at org.apache.geronimo.kernel.basic.RawGetAttributeInvoker.invoke(RawGetAttributeInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.system.plugin.PluginRepositoryList$$EnhancerByCGLIB$$9e116e33.getRepositories(generated) at org.apache.geronimo.console.car.IndexHandler.renderView(IndexHandler.java:54) at org.apache.geronimo.console.MultiPagePortlet.doView(MultiPagePortlet.java:146) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) 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 org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at
[jira] Assigned: (GERONIMO-3532) Getting java.lang.IllegalStateException while stopping geronimo service
[ https://issues.apache.org/jira/browse/GERONIMO-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3532: - Assignee: Jarek Gawor Getting java.lang.IllegalStateException while stopping geronimo service --- Key: GERONIMO-3532 URL: https://issues.apache.org/jira/browse/GERONIMO-3532 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 2.0.1 Environment: Windows XP, geronimo-tomcat6-jee5-2.0.1, wrapper-windows-x86-32-3.2.3,Sun java 1.5.0_13, IBM java 1.5.0 sr5 Reporter: Ashish Jain Assignee: Jarek Gawor I am getting the following error while stopping geronimo service. I am referring the following link. http://cwiki.apache.org/GMOxDOC20/configuring-geronimo-as-a-windows-service.html Startup is fine but while stopping I am getting java.lang.IllegalStateException. I have tested this in Sun java as well as IBM Java.This is the complete trace for start and stop of the service STATUS | wrapper | 2007/10/11 23:07:42 | Starting the Apache Geronimo v2.0 Server service... STATUS | wrapper | 2007/10/11 23:07:42 | -- Wrapper Started as Service STATUS | wrapper | 2007/10/11 23:07:42 | Launching a JVM... INFO | jvm 1| 2007/10/11 23:07:42 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1| 2007/10/11 23:07:42 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1| 2007/10/11 23:07:42 | INFO | jvm 1| 2007/10/11 23:07:44 | Booting Geronimo Kernel (in Java 1.5.0)... INFO | jvm 1| 2007/10/11 23:07:44 | Starting Geronimo Application Server v2.0.1 INFO | jvm 1| 2007/10/11 23:07:44 | INFO | jvm 1| 2007/10/11 23:07:44 | [*] 0% 0s Loading INFO | jvm 1| 2007/10/11 23:07:44 | [*- ] 0% 0s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [*- ] 0% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [* ] 6% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [** ] 8% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [**- ] 8% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:45 | [** ] 9% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [** ] 9% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 11% 1s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [***- ] 11% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 12% 1s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*** ] 12% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [ ] 14% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [-] 14% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [] 15% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*] 17% 2s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*- ] 17% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:46 | [*- ] 17% 2s Loading org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:47 | [* ] 18% 2s Loading org.apache.ge... STATUS | wrapper | 2007/10/11 23:07:47 | Apache Geronimo v2.0 Server started. INFO | jvm 1| 2007/10/11 23:07:47 | [* ] 18% 3s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:48 | [* ] 18% 3s Starting org.apache.ge.. . INFO | jvm 1| 2007/10/11 23:07:48 | [* ] 18% 4s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:49 | [* ] 18% 4s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:49 | [* ] 18% 5s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:49 | [* ] 18% 5s Starting org.apache.ge... INFO | jvm 1| 2007/10/11 23:07:50 | [* ] 18%
[ANNOUNCE] Availability of Geronimo 2.0.2
All, Wanted to let everyone know that the Geronimo 2.0.2 binaries are available for download -- http://geronimo.apache.org/downloads.html 2.0.2 addresses a number of issues that were found in our 2.0.1 release, including the MEJB security vulnerability. Great work everyone! --kevan
