[jira] Updated: (GERONIMO-3960) Make the spec jars OSGi friendly
[
https://issues.apache.org/jira/browse/GERONIMO-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-3960:
--
Attachment: GERONIMO-3960.diff
Most of the work on this issue has already been done -- all the spec jars now
have the OSGi metadata.
There's only one remaining problem with the jars when using them in an OSGi
environment: they all import the packages they export. E.g. the EL 1.0 bundle
exports javax.el;version="1.0" but it also imports javax.el;version="1.0"
While this is a fine configuration for some bundles, there's no good reason for
the specs bundles to import their own packages. On top of that, the import
doesn't have an upper limit set on the version imported, which means that if
you install EL 2.2 in the same OSGi framewok instance as the EL 1.0 spec
mentioned before, it's perfectly possible that the import on the latter will
resolve to the packages exported by the former version (because 2.2 >= 1.0)
Attaching a patch that removes these imports by adding the
*{{-noimport:=true}}* flag to the Export-Packages configuration
> Make the spec jars OSGi friendly
>
>
> Key: GERONIMO-3960
> URL: https://issues.apache.org/jira/browse/GERONIMO-3960
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Guillaume Nodet
> Attachments: GERONIMO-3960.diff, stax-osgi.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
> Setting a parameterized pojo in blueprint throws exception
> --
>
> Key: GERONIMO-4727
> URL: https://issues.apache.org/jira/browse/GERONIMO-4727
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Gert Vanthienen
> Attachments: GERONIMO-4727.diff, GERONIMO-4727.diff
>
>
> When the setter of property uses a parameterized type (e.g.
> *{{setLruList(LruList events)}}*) and the bean being
> injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
> {noformat}
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to convert property value from
> org.apache.felix.karaf.gshell.log.LruList to
> org.apache.felix.karaf.gshell.log.LruList
> for injection
> public void
> org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> at
> org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> ...
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
This patch will give the raw type 'the benefit of the doubt' during type
conversion before invoking the setter.
> Setting a parameterized pojo in blueprint throws exception
> --
>
> Key: GERONIMO-4727
> URL: https://issues.apache.org/jira/browse/GERONIMO-4727
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Reporter: Gert Vanthienen
> Attachments: GERONIMO-4727.diff
>
>
> When the setter of property uses a parameterized type (e.g.
> *{{setLruList(LruList events)}}*) and the bean being
> injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
> {noformat}
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to convert property value from
> org.apache.felix.karaf.gshell.log.LruList to
> org.apache.felix.karaf.gshell.log.LruList
> for injection
> public void
> org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> at
> org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> ...
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Gert Vanthienen
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruList events)}}*) and the bean being injected
is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from org.apache.felix.karaf.gshell.log.LruList
to
org.apache.felix.karaf.gshell.log.LruList
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r727321 - in /geronimo/gshell/trunk: gshell-api/src/main/java/org/apache/geronimo/gshell/command/ gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/comma
L.S.,
Thanks for making new SNAPSHOTs available again! Could we have another new
SNAPSHOT for
http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/gshell/wisdom/gshell-wisdom-core/1.0-alpha-2-SNAPSHOT/
as well?
Regards,
Gert
Gert Vanthienen wrote:
>
> L.S.,
>
> Do you have any idea when we will have a -SNAPSHOT available on
> people.apache.org that contains this change? The last gshell-api SNAPSHOT
> available at
> http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/gshell/gshell-api/1.0-alpha-2-SNAPSHOT/
> seems to be over a week old.
>
> Regards,
>
> Gert
>
>
> Jason Dillon wrote:
>>
>> Thx :-)
>>
>> --jason
>>
>>
>> On Dec 17, 2008, at 4:31 PM, gno...@apache.org wrote:
>>
>>> Author: gnodet
>>> Date: Wed Dec 17 01:31:44 2008
>>> New Revision: 727321
>>>
>>> URL: http://svn.apache.org/viewvc?rev=727321&view=rev
>>> Log:
>>> GSHELL-154: Create interfaces to represent links and aliases
>>>
>>> Added:
>>>geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Alias.java
>>>geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Link.java
>>>geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>>> java/org/apache/geronimo/gshell/wisdom/command/AliasImpl.java
>>>geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>>> java/org/apache/geronimo/gshell/wisdom/command/LinkImpl.java
>>> Modified:
>>>geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>>> java/org/apache/geronimo/gshell/wisdom/config/PluginParser.java
>>>geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>>> java/org/apache/geronimo/gshell/wisdom/plugin/bundle/
>>> CommandBundle.java
>>>
>>> Added: geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Alias.java
>>> URL:
>>> http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/geronimo/gshell/command/Alias.java?rev=727321&view=auto
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> ==
>>> --- geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Alias.java (added)
>>> +++ geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Alias.java Wed Dec 17 01:31:44 2008
>>> @@ -0,0 +1,33 @@
>>> +/*
>>> + * Licensed to the Apache Software Foundation (ASF) under one
>>> + * or more contributor license agreements. See the NOTICE file
>>> + * distributed with this work for additional information
>>> + * regarding copyright ownership. The ASF licenses this file
>>> + * to you under the Apache License, Version 2.0 (the
>>> + * "License"); you may not use this file except in compliance
>>> + * with the License. You may obtain a copy of the License at
>>> + *
>>> + * http://www.apache.org/licenses/LICENSE-2.0
>>> + *
>>> + * Unless required by applicable law or agreed to in writing,
>>> + * software distributed under the License is distributed on an
>>> + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>>> + * KIND, either express or implied. See the License for the
>>> + * specific language governing permissions and limitations
>>> + * under the License.
>>> + */
>>> +
>>> +package org.apache.geronimo.gshell.command;
>>> +
>>> +/**
>>> + * Convenient way to register an alias.
>>> + *
>>> + * @version $Rev: 705507 $ $Date: 2008-10-17 10:22:12 +0200 (Fri,
>>> 17 Oct 2008) $
>>> + */
>>> +public interface Alias {
>>> +
>>> +String getName();
>>> +
>>> +String getAlias();
>>> +
>>> +}
>>>
>>> Added: geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/
>>> geronimo/gshell/command/Link.java
>>> URL:
>>> http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-api/src/main/java/org/apache/geronimo/gshell/command/Link.java?rev=727321&view=auto
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> ===
Re: svn commit: r727321 - in /geronimo/gshell/trunk: gshell-api/src/main/java/org/apache/geronimo/gshell/command/ gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/comma
);
>>
>> -List links = new
>> ArrayList();
>> +List links = new ArrayList();
>>
>> List children = getChildElements(element, LINK);
>>
>> for (Element child : children) {
>> -BeanDefinitionBuilder link =
>> BeanDefinitionBuilder.rootBeanDefinition(LinkCommand.class);
>> -link.addConstructorArgReference("commandRegistry");
>> -
>> link.addConstructorArgValue(child.getAttribute(TARGET));
>> -
>> String name = child.getAttribute(NAME);
>> -BeanDefinition def = new GenericBeanDefinition();
>> -
>> def.setBeanClassName(CommandLocationImpl.class.getName());
>> -
>> def.getConstructorArgumentValues().addGenericArgumentValue(name);
>> -link.addPropertyValue(LOCATION, def);
>> +String target = child.getAttribute(TARGET);
>>
>> -links.add(link.getBeanDefinition());
>> +links.add(new LinkImpl(name, target));
>> }
>>
>> return links;
>> @@ -573,12 +575,12 @@
>> //
>> //
>>
>> -private Map parseAliases(final Element
>> element) {
>> +private List parseAliases(final Element element) {
>> assert element != null;
>>
>> log.trace("Parse aliases; element; {}", element);
>>
>> -Map aliases = new
>> LinkedHashMap();
>> +List aliases = new ArrayList();
>>
>> List children = getChildElements(element, ALIAS);
>>
>> @@ -586,7 +588,7 @@
>> String name = child.getAttribute(NAME);
>> String alias = child.getAttribute(ALIAS);
>>
>> -aliases.put(name, alias);
>> +aliases.add(new AliasImpl(name, alias));
>> }
>>
>> return aliases;
>>
>> Modified: geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/
>> main/java/org/apache/geronimo/gshell/wisdom/plugin/bundle/
>> CommandBundle.java
>> URL:
>> http://svn.apache.org/viewvc/geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/plugin/bundle/CommandBundle.java?rev=727321&r1=727320&r2=727321&view=diff
>> =
>> =
>> =
>> =
>> =
>> =
>> =
>> =
>> ==
>> --- geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>> java/org/apache/geronimo/gshell/wisdom/plugin/bundle/
>> CommandBundle.java (original)
>> +++ geronimo/gshell/trunk/gshell-wisdom/gshell-wisdom-core/src/main/
>> java/org/apache/geronimo/gshell/wisdom/plugin/bundle/
>> CommandBundle.java Wed Dec 17 01:31:44 2008
>> @@ -20,11 +20,16 @@
>> package org.apache.geronimo.gshell.wisdom.plugin.bundle;
>>
>> import org.apache.geronimo.gshell.command.Command;
>> +import org.apache.geronimo.gshell.command.Alias;
>> +import org.apache.geronimo.gshell.command.Link;
>> import org.apache.geronimo.gshell.registry.AliasRegistry;
>> import org.apache.geronimo.gshell.registry.CommandRegistry;
>> +import org.apache.geronimo.gshell.wisdom.command.LinkCommand;
>> +import
>> org.apache.geronimo.gshell.wisdom.registry.CommandLocationImpl;
>>
>> import java.util.List;
>> import java.util.Map;
>> +import java.util.ArrayList;
>>
>> /**
>> * A bundle of {...@link Command} instances.
>> @@ -40,7 +45,11 @@
>>
>> private List commands;
>>
>> -private Map aliases;
>> +private List links;
>> +
>> +private List aliases;
>> +
>> +private List linkCommands;
>>
>> public CommandBundle(final CommandRegistry commandRegistry,
>> final AliasRegistry aliasRegistry, final String name) {
>> super(name);
>> @@ -60,23 +69,47 @@
>> this.commands = commands;
>> }
>>
>> -public Map getAliases() {
>> +public List getLinks() {
>> +return links;
>> +}
>> +
>> +public void setLinks(List links) {
>> +assert links != null;
>> +
>> +this.links = links;
>> +}
>> +
>> +public List getAliases() {
>> return aliases;
>> }
>>
>> -public void setAliases(final Map aliases) {
>
>> +public void setAliases(final List aliases) {
>> assert aliases != null;
>>
>> this.aliases = aliases;
>> }
>>
>> protected void doEnable() throws Exception {
>> +// Create links commands
>> +if (linkCommands == null) {
>> +linkCommands = new ArrayList();
>> +for (Link link : links) {
>> +LinkCommand cmd = new LinkCommand(commandRegistry,
>> link.getTarget());
>> +cmd.setLocation(new
>> CommandLocationImpl(link.getName()));
>> +linkCommands.add(cmd);
>> +}
>> +}
>> +
>> for (Command command : commands) {
>> commandRegistry.registerCommand(command);
>> }
>>
>> -for (String name : aliases.keySet()) {
>> -aliasRegistry.registerAlias(name, aliases.get(name));
>> +for (Command command : linkCommands) {
>> +commandRegistry.registerCommand(command);
>> +}
>> +
>> +for (Alias alias : aliases) {
>> +aliasRegistry.registerAlias(alias.getName(),
>> alias.getAlias());
>> }
>> }
>>
>> @@ -85,8 +118,12 @@
>> commandRegistry.removeCommand(command);
>> }
>>
>> -for (String name : aliases.keySet()) {
>> -aliasRegistry.removeAlias(name);
>> +for (Command command : linkCommands) {
>> +commandRegistry.removeCommand(command);
>> +}
>> +
>> +for (Alias alias : aliases) {
>> +aliasRegistry.removeAlias(alias.getName());
>> }
>> }
>> }
>> \ No newline at end of file
>>
>>
>
>
>
-
---
Gert Vanthienen
http://gertvanthienen.blogspot.com
--
View this message in context:
http://www.nabble.com/Re%3A-svn-commit%3A-r727321---in--geronimo-gshell-trunk%3A-gshell-api-src-main-java-org-apache-geronimo-gshell-command--gshell-wisdom-gshell-wisdom-core-src-main-java-org-apache-geronimo-gshell-wisdom-command--gshell-wisdom-gshell-wisdom-core-src-main-java-org-a...-tp21067909s134p21091483.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Commented: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40588 ] Gert Vanthienen commented on SM-1119: - Right you are! Although every message will be re-encoded by the SourceTransformer, I wrongfully assumed that it would always encode the response in UTF-8, while in reality this can be configured through the 'org.apache.servicemix.default.charset' system property. Thanks for reviewing the code so carefully! http://svn.apache.org/viewvc?view=rev&revision=594255 (3.1 branch) http://svn.apache.org/viewvc?view=rev&revision=594267 (3.2 branch) http://svn.apache.org/viewvc?view=rev&revision=594259 (3.3 -- trunk) > Encoding problem in text returned by HTTP-SU > > > Key: SM-1119 > URL: https://issues.apache.org/activemq/browse/SM-1119 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core, servicemix-http, servicemix-jsr181 >Affects Versions: 3.1, 3.1.1, 3.1.2 > Environment: This issue can be reproduced on Windows XP Pro and Red > Hat Linux. >Reporter: Philip Webster > Fix For: 3.1.3, 3.2.1, 3.3 > > Attachments: multimatch-search.zip, multimatch-search2.zip, > SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar > > > It looks as though there is an encoding problem at the point after the > results are returned from the JSR181 service unit. > The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th > snapshot of 3.2 > As discussed on this thread: > http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html > The attached service usints and service assembly can be used to reproduce the > issue. > Use the following input against http://localhost:8492/MultiMatchSearch/ > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:sear="http://eir.multimatch.org/search";> > > > > > >Charles Perrault >Title >~ > > SPANISH > ENGLISH > nonCached > metadata > >TEXT >0 >1 > > > false > > > > The result is: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >MeñiquÃn Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > > The result should be: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >Meñiquín Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1119. - Resolution: Fixed Fix Version/s: 3.3 3.2.1 3.1.3 Thank you, Philip, for providing the necessary test SAs to verify this fix! Adding "charset=utf-8" to the content type fixes the issue: http://svn.apache.org/viewvc?view=rev&revision=594063 (3.1 branch) http://svn.apache.org/viewvc?view=rev&revision=594078 (3.2 branch) http://svn.apache.org/viewvc?view=rev&revision=594064 (3.3 -- trunk) > Encoding problem in text returned by HTTP-SU > > > Key: SM-1119 > URL: https://issues.apache.org/activemq/browse/SM-1119 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core, servicemix-http, servicemix-jsr181 >Affects Versions: 3.1, 3.1.1, 3.1.2 > Environment: This issue can be reproduced on Windows XP Pro and Red > Hat Linux. >Reporter: Philip Webster > Fix For: 3.1.3, 3.2.1, 3.3 > > Attachments: multimatch-search.zip, multimatch-search2.zip, > SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar > > > It looks as though there is an encoding problem at the point after the > results are returned from the JSR181 service unit. > The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th > snapshot of 3.2 > As discussed on this thread: > http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html > The attached service usints and service assembly can be used to reproduce the > issue. > Use the following input against http://localhost:8492/MultiMatchSearch/ > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:sear="http://eir.multimatch.org/search";> > > > > > >Charles Perrault >Title >~ > > SPANISH > ENGLISH > nonCached > metadata > >TEXT >0 >1 > > > false > > > > The result is: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >MeñiquÃn Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > > The result should be: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >Meñiquín Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1124) Message content silently dropped when conversion fails
[ https://issues.apache.org/activemq/browse/SM-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1124. - Resolution: Fixed Fix Version/s: (was: 3.2) 3.2.1 Added warning when message content conversions fails + use Camel type converter for String→Source http://svn.apache.org/viewvc?view=rev&revision=591300 > Message content silently dropped when conversion fails > -- > > Key: SM-1124 > URL: https://issues.apache.org/activemq/browse/SM-1124 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-camel > Reporter: Gert Vanthienen >Priority: Trivial > Fix For: 3.2.1 > > > When a Camel message is sent to a JBI endpoint, the contents is converted > into a Source (for message normalization). When the message content can not > be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1124) Message content silently dropped when conversion fails
Message content silently dropped when conversion fails -- Key: SM-1124 URL: https://issues.apache.org/activemq/browse/SM-1124 Project: ServiceMix Issue Type: Bug Components: servicemix-camel Reporter: Gert Vanthienen Priority: Trivial Fix For: 3.2 When a Camel message is sent to a JBI endpoint, the contents is converted into a Source (for message normalization). When the message content can not be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
[
https://issues.apache.org/activemq/browse/SM-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed SM-1103.
---
Resolution: Cannot Reproduce
Never mind... I guess everyone is entitled to a moment of confusion once in a
while...
> Class not found (org.apache.camel.Component) while starting servicemix-camel
> component
> --
>
> Key: SM-1103
> URL: https://issues.apache.org/activemq/browse/SM-1103
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
>Affects Versions: 3.2
>Reporter: Gert Vanthienen
>
> servicemix-camel fails with new build from trunk (revision 584233)
> {code}
> ERROR - InstallerMBeanImpl - Class not found:
> org.apache.servicemix.common.DefaultBootstrap
> java.lang.NoClassDefFoundError: org/apache/camel/Component
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at
> org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
> at
> org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
> at
> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at
> org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
> at
> org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
> at
> org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
Class not found (org.apache.camel.Component) while starting servicemix-camel
component
--
Key: SM-1103
URL: https://issues.apache.org/activemq/browse/SM-1103
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Affects Versions: 3.2
Reporter: Gert Vanthienen
servicemix-camel fails with new build from trunk (revision 584233)
{code}
ERROR - InstallerMBeanImpl - Class not found:
org.apache.servicemix.common.DefaultBootstrap
java.lang.NoClassDefFoundError: org/apache/camel/Component
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at
org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
at
org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
at
org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: ServiceMix 4 as a distributed OSGi spring container....
L.S., I really like the way ServiceMix 4.0 will be built around a set of core technologies (OSGi, ActiveMQ, Camel, CXF). It's a very good idea to leverage these technologies also for our own 'internal' operations wherever possible and the Camel snippet that was shown has a very nice touch of simplicity/readability to it. I also like the suggestion of sending only a URL of the container in the heartbeat, thus limiting the size of the heartbeat message, while still allowing the other node to retrieve the data it needs. Perhaps I'm completely missing the point here, but ... Wouldn't it be possible to also include 'update notifications' in the heartbeat message this way? Whenever a new service (or a bundle of services) becomes available, an update notification is sent with a URL to allow the other nodes to only retrieve information about what has changed. This way, the node receiving the heartbeat can update it's own internal registry to reflect changes that have occurred in the other nodes. Gert James Strachan wrote: On 11/10/2007, Guillaume Nodet <[EMAIL PROTECTED]> wrote: I was thinking that ldap may be handy for the registry, but hopefully Chris will join the discussion at this point... Though camel does not support ldap (yet). So your snippet would actually solve the heartbeat problem. But I'm not sure we can send the whole data at each heartbeat. I guess it depends how bit this data is, but if we have lots of services in the OSGi registry, it may not be very scalable. So we would have to default to send only updates or find another mechanism to send the data (the heartbeat could just contain the url of our container, and the data would be retrieved by another mechanism). Yeah; it does depend on how much data we're talking about. We could slice and dice the data using URLs. e.g. the full list of services available could be posted to some, say, Atom document on some shared server; this list can be updated incrementally or in total as and when services are added or removed. Then the heartbeat could just send around a URL to the detailed information. Or the list of services available could just be dynamically generated on demand if the container exposed a web front end. (push v pull) >From a client perspective, it doesn't much care - the heartbeat message contains a URL to the detailed list of actual services provided if it wishes to get more information etc.
Re: October board report
Guillaume, Looks fine to me... Gert Guillaume Nodet wrote: The report has to be submitted asap. I've written it at http://cwiki.apache.org/confluence/display/SM/2007-10-17. Please review and add anything missing asap.
[jira] Created: (SM-1098) Loop in StAX ElementReader while executing web service
Loop in StAX ElementReader while executing web service -- Key: SM-1098 URL: https://issues.apache.org/activemq/browse/SM-1098 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-jsr181 Affects Versions: 3.1.2 Reporter: Gert Vanthienen Attachments: Webservice-test.zip Cfr. mailing list http://www.nabble.com/Webservice-call-failes-when-log4j-level-is-set-to-DEBUG.-tf4575623s12049.html#a13096235 The user already provided us with an example of a failing SA -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
+1 Freeman Fang wrote: Hi All, I have uploaded a version of ServiceMix 3.1.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.1.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.1.2 Cheers Freeman
Re: ActiveMQ Causing OutOfMemoryError After Service Deployment
Guillaume, It was using the default configuration of ServiceMix, so it was using the tcp:// broker connection. However... today, the problem is gone. I restored the original config, with all flows enabled and now the memory usage is back to normal. However, the ActiveMQ config also still had the multicast:// discoveryUri and network transports enabled (I disabled them now). Could that somehow have caused ActiveMQ to go berserk yesterday, even though it is the only instance on the network? Gert Guillaume Nodet wrote: Do you use a vm:// activemq broker or a tcp:// one ? Does it change anything ? On 9/21/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: L.S., Just yesterday, I have run into the same problem with a customer. A ServiceMix installation that was working fine just started using excessive amounts of memory after adding a SA with only two endpoints in it. I have disabled the JMS/JCA flows for now, which solves the problem by taking most of the load of ActiveMQ. Does anyone know which ActiveMQ issue this user was referring to, so I can check if it really solves this particular problem while I have the opportunity to do so? Regards, Gert ArmenH wrote: Any word on when 3.1.2 would be available? Also, how do we proceed with commercial quality support? Armen H. Gert Vanthienen wrote: L.S., As soon as there is an ActiveMQ release which contains the bugfix, we can start the process for a 3.1.2 release. I think Bruce and Thomas have already backported some important fixes to be released with 3.1.2 as well... Gert ArmenH wrote: FYI. We did try replacing the ServiceMix ActiveMQ JAR files with the latest ActiveMQ SNAPSHOT JAR files and the problem was resolved. We would be very anxious to get the ServiceMix 3.1.2 release with all the latest bug fixes as soon as it becomes available. This directly affects our trading application. Armen H. Gert Vanthienen wrote: Armen H., We usually don't pick up SNAPSHOT builds in our releases. However, we are planning to a 3.1.2 release sometime in the near future, so if ActiveMQ has released the patch by then, we can include it at that time. Can you already provide me with a reference to a thread on the mailing list or a an ActiveMQ JIRA issue to document this issue? In the meantime, could you try replacing the JAR files for ActiveMQ in your installation with a recent build of ActiveMQ to see if it really resolves the problems you're experiencing? Gert ArmenH wrote: Hi Gert, We're using HTTP BC and JSR 181 SEs. We have custom business logic (very simple) that uses POJOs generated from the JAXB version of the JDK 1.6.0_01. We are also dependent on JDK 1.6 JAX-WS to generate our service interface (WSDL). We will check the number of service endpoints and let you know. By the way, I have another thread on the ActiveMQ forums and other folks have experienced very similar issues with ActiveMQ as that causes the heap overflow. The fix for this issue was put on July 24 but it's unclear which version it will end up in and also more importantly when would ServiceMix pick up the latest 4.1.x SNAPSHOT from ActiveMQ. Armen H. Gert Vanthienen wrote: Armen H., What JBI Components (JMS, HTTP, JSR-181, ...) are you using? From your description, I assume you at least have a few custom built components as well... Can you try to use jconsole (http://incubator.apache.org/servicemix/15-tutorial-using-jmx-to-look-inside-the-esb.html) to look at the number of service endpoint that are actually registered? Also, can you take a look at the number of threads that are in use? What version of Java are you using? Gert ArmenH wrote: Gert, We use the Windows version for development phase of our services. We are deploying services by dropping the files in the deploy and install directories. We don't use JMX for the development phase. We're using ServiceMix version 3.1 in stand-alone mode. We deploy SAs as well. Regards, Armen H. Gert Vanthienen wrote: L.S., One of my customers is running ServiceMix on Windows as well, but even with a dozen SA deployed, the memory usage doesn't raise to the amounts you mention here, although there are using several types of services (HTTP, JMS, FTP, File, Saxon, EIP, bean, lwcontainer). What version of ServiceMix and/or Java are you using? Are you using ServiceMix in stand-alone or web application 'mode'? What is the type of service you are trying to deploy? Can you try to check the number of threads that are running with a JMX console? Regards, Gert ArmenH wrote: We have found out that after just one service deployed on Windows ServiceMix the memory usage jumps to 500 MB and it increases linearly after each service deployment until ServiceMix dies with an OutOfMemoryError. We tried increasing th
[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40159 ] Gert Vanthienen commented on SM-1071: - Another option could be to use JCR for storing/versioning/accessing the configuration... > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1056) Add NamespaceContextImpl to servicemix-core
Add NamespaceContextImpl to servicemix-core --- Key: SM-1056 URL: https://issues.apache.org/activemq/browse/SM-1056 Project: ServiceMix Issue Type: Improvement Components: servicemix-core, servicemix-drools, servicemix-eip Affects Versions: 3.1.1 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Currently, servicemix-eip and servicemix-drools each ship with an almost identical copy of NamespaceContextImpl. It would be better to move this to servicemix-core (where the XPathExpression classes are -- which might also require a NamespaceContextImpl). In order not to break any existing xbean.xml files, we should keep the current classes in servicemix-eip and servicemix-drools (can become empty, simply inherit from the core one) to make sure that eip:namespace-context and drools:namespace-context still exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Getting started: Using the Maven tooling
L.S., Done! Wouldn't it be a good idea to add the distinction between beginner - intermediate - advanced to this page (http://incubator.apache.org/servicemix/tutorials.html) as well, just to 'discourage' beginner users to start writing SE/BC on day 1? Secondly, how about adding a links to these tutorials in the sites navigation (e.g. between user's guide and documentation)? Gert Guillaume Nodet wrote: What about moving these tutorials out of the sandbox ... On 8/9/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: L.S., I added a second tutorial to the wiki Sandbox (http://cwiki.apache.org/confluence/x/Q94), explaining to a newbie user how to leverage the Maven archetypes and tooling for building their own service assemblies. Any comments, corrections, feedback, ... are welcome. Gert
Re: How to obtain URI address of http:endpoint ?
Guillaume, I think this this user has several http consumer endpoints, configured at different URIs (e.g. http://0.0.0.0/service1, http://0.0.0.0/service2, http://0.0.0.0/service3). On all of these endpoints, the same targetService is configured (ex:Service) and it is in this targetService that he would like to distinguish between the originating consumer endpoints. Gert Guillaume Nodet wrote: Maybe you could rewrite your question ? I don't really understand what you want to do. The URI of the http endoint is usually configured using the httpLocation attribute of the endpoint... On 9/14/07, Micky Santomax <[EMAIL PROTECTED]> wrote: No help for me ? -- View this message in context: http://www.nabble.com/How-to-obtain-URI-address-of-http%3Aendpoint---tf4437467s12049.html#a12672738 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Created: (SM-1042) Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class)
Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class)
-
Key: SM-1042
URL: https://issues.apache.org/activemq/browse/SM-1042
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Seems to be a problem that is mentioned in the adoption guide:
http://java.sun.com/javase/6/webnotes/adoption/adoptionguide.html#2.2.1
{noformat}
[INFO] Compilation failure
C:\projects\servicemix\core\servicemix-core\src\main\java\org\apache\servicemix\jbi\management\BaseStandardMBean.java:[117,8]
cannot
find symbol
symbol : constructor
StandardMBean(java.lang.Object,java.lang.Class)
location: class javax.management.StandardMBean
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SM-990) FilePoller with Archiving
Guillaume Nodet wrote: On 8/9/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: Guillaume Nodet wrote: You mean a file based implementation of servicemix-audit ? See http://incubator.apache.org/servicemix/dist/servicemix-3.1-incubating/site/core/servicemix-audit/apidocs/org/apache/servicemix/jbi/audit/AuditorMBean.html Yes, my first comment was exactly that: using an auditor for archiving the files. This isn't the best solution for this particular issue, but it still might be a worthwhile addition to ServiceMix. We still need to find a good way to avoid having to load entire messages into memory however. Anybody has any good suggestions for solving that? I think a TeeInputStream should work perfectly. I guess this would be the best option for very large files (it would avoid reading the whole file twice). I think we should only backport bug fixes, do you ? But I'm open to discuss that, especially given the long release cycle we have (we really need to do something about that, btw). That's exactly why I was asking. I think these branches are great for doing bug fixes on an existing release, but I agree we should try to avoid it for new features. What is holding us back to shorten the release cycle (or even time-boxing it)? I'm trying to build a tool to regenerate the legal files, so we can already avoid the pain of checking those 'manually' every time. Is there anything else? Nothing, really. I'd like the new endpoints for http and jms be finished, but nothing else. However it may be worth waiting for the board meeting (one or two weeks) so that we can remove the incubation disclaimers and have a release that we can put on maven public repositories. Wdyt? It probably is worth waiting for then. I think we should even consider releasing 3.2 (with the new HTTP/JMS endpoints, servicemix-camel, ...) instead of another 3.1.x bugfix release. There is another issue I would like to see resolved in our next release, which is the one mentioned in http://www.nabble.com/ActiveMQ-Causing-OutOfMemoryError-After-Service-Deployment-tf4133779s12049.html. Does anyone know what the corresponding ActiveMQ issue is and when it will become available in a release?
[jira] Closed: (SM-989) Backup File before Delete
[ https://issues.apache.org/activemq/browse/SM-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed SM-989. -- Resolution: Duplicate Fix Version/s: 3.2 Duplicate of SM-990 > Backup File before Delete > - > > Key: SM-989 > URL: https://issues.apache.org/activemq/browse/SM-989 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-file >Affects Versions: 3.2 >Reporter: Gordon Dickens >Priority: Minor > Fix For: 3.2 > > > Provide backup directory option to copy file to before deleting. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SM-990) FilePoller with Archiving
Guillaume, I was thinking about creating a generic archiving service, which would be able to keep an archive of every message that has been processed by ServiceMix for auditing purposes (and e.g. to be able to re-send it when necessary). In this use case, it would be very useful to have a single point of configuration instead of having to configure the archive flag over and over again on all the consumer endpoints in an application. But this is probably an entirely different requirement than the one expressed by this user. I'll add an 'archive' attribute to the poller endpoint to refer to the archiving directory for this issue. Is this something to backport to 3.1.2-SNAPSHOT as well? Gert Guillaume Nodet wrote: It should be quite easy to write a TeeInputStream that would write to an OutputStream each time a charachter is read from the input stream. However, the content of the NormalizedMessage is a Source and may not be a stream. However, I think it would be easier to put this feature inside the BC rather than in an intermediate (a ExchangeListener on the container?). Well, at least, it would be easier to configure as a simple flag on the endpoint could work. If we use a single listener, we will have to configure on the main servicemix.xml configuration file or register it dynamically (from were?) ... On 8/8/07, Gert Vanthienen (JIRA) <[EMAIL PROTECTED]> wrote: [ https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39880 ] Gert Vanthienen commented on SM-990: I was thinking about some kind of WireTap (implemented as an Auditor to easily apply it to all message), but I suppose you're worrying about the fact that we need to ensure re-readability of the stream for this. Would it be possible to 'decorate' the NormalizedMessage somehow, so it can intercept when bytes are read from the inputstream by the provider and do the archiving on-the-fly? FilePoller with Archiving - Key: SM-990 URL: https://issues.apache.org/activemq/browse/SM-990 Project: ServiceMix Issue Type: Improvement Components: servicemix-components, servicemix-file Affects Versions: 3.1 Reporter: Juergen Mayrbaeurl Priority: Minor The various FilePoller implementations should archive the files before deleting them (e.g. by copying them to another directory) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
[ https://issues.apache.org/activemq/browse/SM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1014. - Resolution: Fixed Assignee: Gert Vanthienen Added a default value for defaultMep to SoapEndpoint http://svn.apache.org/viewvc?view=rev&revision=562344 http://svn.apache.org/viewvc?view=rev&revision=562351 > WSDL-first example fails javax.jbi.messaging.MessagingException: Do not > understand pattern: null > > > Key: SM-1014 > URL: https://issues.apache.org/activemq/browse/SM-1014 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-http, servicemix-soap >Affects Versions: 3.1.1 >Reporter: Gert Vanthienen >Assignee: Gert Vanthienen >Priority: Minor > Fix For: 3.1.2, 3.2 > > > The exception can be solved by specifying defaultMep on the HTTP consumer > endpoint, but I suppose it would be better to have a good default value for > the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null Key: SM-1014 URL: https://issues.apache.org/activemq/browse/SM-1014 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.1.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.2, 3.2 The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39794 ] Gert Vanthienen commented on SM-1005: - On my machine, the message exchanges sent by the file binding component already contain these properties. Perhaps you're still using the 3.1 version, SM-861 fixes this in 3.1.1 for exchanges that are sent using sendSync() (such as those sent by the FilePoller) > File BC doesnt set correlation Id and sender property > - > > Key: SM-1005 > URL: https://issues.apache.org/activemq/browse/SM-1005 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1, 3.1.1 >Reporter: Gianfranco Boccalon > > The File binding component doesn't set the properties correlation id and > sender. > We fixed the problem changing the method processFile in class > org.apache.servicemix.file.FilePollerEndpoint, adding these rows before > sending the message (sendSync): >exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); >exchange.setProperty(JbiConstants.CORRELATION_ID, > exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39768 ] Gert Vanthienen commented on SM-1005: - Gianfranco, I haven't tested the 3.1 release, but at least the 3.1.1 release already does this correctly. Can you describe the problem you were having with this? Gert > File BC doesnt set correlation Id and sender property > - > > Key: SM-1005 > URL: https://issues.apache.org/activemq/browse/SM-1005 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1, 3.1.1 >Reporter: Gianfranco Boccalon > > The File binding component doesn't set the properties correlation id and > sender. > We fixed the problem changing the method processFile in class > org.apache.servicemix.file.FilePollerEndpoint, adding these rows before > sending the message (sendSync): >exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); >exchange.setProperty(JbiConstants.CORRELATION_ID, > exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ActiveMQ Causing OutOfMemoryError After Service Deployment
L.S., One of my customers is running ServiceMix on Windows as well, but even with a dozen SA deployed, the memory usage doesn't raise to the amounts you mention here, although there are using several types of services (HTTP, JMS, FTP, File, Saxon, EIP, bean, lwcontainer). What version of ServiceMix and/or Java are you using? Are you using ServiceMix in stand-alone or web application 'mode'? What is the type of service you are trying to deploy? Can you try to check the number of threads that are running with a JMX console? Regards, Gert ArmenH wrote: > > We have found out that after just one service deployed on Windows > ServiceMix the memory usage jumps to 500 MB and it increases linearly > after each service deployment until ServiceMix dies with an > OutOfMemoryError. > > We tried increasing the heap size and it helped up to a certain number of > services deployed in the container, after that the Error happened as > expected. > > We used jhatfor heap analysis and found out that the following instance > usage (after just one service deployment): > > 1673478 instances of class org.apache.activemq.filter.DestinationMapNode > 3001 instances of class > edu.emory.mathcs.backport.java.util.concurrent.locks.ReentrantLock$NonfairSync > > > This is a critical issue for us. Please advise. > > Regards. > Armen H. > -- View this message in context: http://www.nabble.com/ActiveMQ-Causing-OutOfMemoryError-After-Service-Deployment-tf4133779s12049.html#a11770993 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Resolved: (SM-664) org.apache.servicemix.http.HttpAddressingTest (Hangs)
[ https://issues.apache.org/activemq/browse/SM-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-664. Resolution: Cannot Reproduce Because I was unable to reproduce this while going through the binding components for issue SM-623, I removed the exclusion from the test suite. We can always reopen the issue if someone can reproduce it... http://svn.apache.org/viewvc?view=rev&revision=557757 > org.apache.servicemix.http.HttpAddressingTest (Hangs) > - > > Key: SM-664 > URL: https://issues.apache.org/activemq/browse/SM-664 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-http >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-653: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.WireTapJmsFlowTest > > > Key: SM-653 > URL: https://issues.apache.org/activemq/browse/SM-653 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-663) org.apache.servicemix.eip.ContentBasedRouterTxTest
[ https://issues.apache.org/activemq/browse/SM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-663. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.ContentBasedRouterTxTest > -- > > Key: SM-663 > URL: https://issues.apache.org/activemq/browse/SM-663 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-662) org.apache.servicemix.eip.SpringConfigurationTest
[ https://issues.apache.org/activemq/browse/SM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-662. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.SpringConfigurationTest > - > > Key: SM-662 > URL: https://issues.apache.org/activemq/browse/SM-662 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-660) org.apache.servicemix.eip.DeploymentTest
[ https://issues.apache.org/activemq/browse/SM-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-660. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.DeploymentTest > > > Key: SM-660 > URL: https://issues.apache.org/activemq/browse/SM-660 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-661) org.apache.servicemix.eip.support.NamespaceContextImplTest
[ https://issues.apache.org/activemq/browse/SM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-661. Resolution: Fixed Fix Version/s: 3.2 > org.apache.servicemix.eip.support.NamespaceContextImplTest > -- > > Key: SM-661 > URL: https://issues.apache.org/activemq/browse/SM-661 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-659) org.apache.servicemix.eip.XPathSplitterTxTest
[ https://issues.apache.org/activemq/browse/SM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-659. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.XPathSplitterTxTest > - > > Key: SM-659 > URL: https://issues.apache.org/activemq/browse/SM-659 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-658: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.WireTapTxTest > --- > > Key: SM-658 > URL: https://issues.apache.org/activemq/browse/SM-658 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-658. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.WireTapTxTest > --- > > Key: SM-658 > URL: https://issues.apache.org/activemq/browse/SM-658 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-657) org.apache.servicemix.eip.MessageFilterTxTest
[ https://issues.apache.org/activemq/browse/SM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-657. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.MessageFilterTxTest > - > > Key: SM-657 > URL: https://issues.apache.org/activemq/browse/SM-657 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-656) org.apache.servicemix.eip.StaticRecipientListTxTest
[ https://issues.apache.org/activemq/browse/SM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-656. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.StaticRecipientListTxTest > --- > > Key: SM-656 > URL: https://issues.apache.org/activemq/browse/SM-656 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-655) org.apache.servicemix.eip.SplitAggregatorTxTest
[ https://issues.apache.org/activemq/browse/SM-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-655. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.SplitAggregatorTxTest > --- > > Key: SM-655 > URL: https://issues.apache.org/activemq/browse/SM-655 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-654. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.PipelineTxTest > > > Key: SM-654 > URL: https://issues.apache.org/activemq/browse/SM-654 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-654: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.PipelineTxTest > > > Key: SM-654 > URL: https://issues.apache.org/activemq/browse/SM-654 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-653. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.WireTapJmsFlowTest > > > Key: SM-653 > URL: https://issues.apache.org/activemq/browse/SM-653 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-652) org.apache.servicemix.eip.StaticRoutingSlipTxTest
[ https://issues.apache.org/activemq/browse/SM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-652. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.StaticRoutingSlipTxTest > - > > Key: SM-652 > URL: https://issues.apache.org/activemq/browse/SM-652 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-623) Unit test that fails when building using maven2.
[ https://issues.apache.org/activemq/browse/SM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39662 ] Gert Vanthienen commented on SM-623: It appears the servicemix-eip tests were failing when no additional memory was reserved for the unit tests (currently: -Xmx512m). With Adrian's centralized surefire configuration in place, all these tests now work fine. I have removed the s from the pom.xml (cfr. http://svn.apache.org/viewvc?view=rev&revision=555652) > Unit test that fails when building using maven2. > > > Key: SM-623 > URL: https://issues.apache.org/activemq/browse/SM-623 > Project: ServiceMix > Issue Type: Test >Reporter: Fritz Oconer > > Check the sub tasks. These are unit tests that fails when building using > maven 2 and jdk1.5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39657
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
Was this a checkout from trunk? I cannot reproduce the CheckStyle errors with
my latest checkout here. Could you try to do an 'svn up' and retry it?
Gert
> ServiceMix :: Maven2 JBI Plugin checkstyle issues
> --
>
> Key: SM-1000
> URL: https://issues.apache.org/activemq/browse/SM-1000
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.2
> Environment: Windows
>Reporter: Rabi
>
> [INFO] Building ServiceMix :: Maven2 JBI Plugin
> [INFO]task-segment: [install]
> [INFO]
> -
> ---
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven version
> 2.0.5
> [INFO] [checkstyle:checkstyle {execution: validate}]
> [INFO] Starting audit...
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
> def
> modifier at indentation level 2 not at correct indentation, 4
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
> th
> an 7 parameters.
> Audit done.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: There are 4 checkstyle errors.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 28 seconds
> [INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
> [INFO] Final Memory: 13M/24M
> [INFO]
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-997) Basic example fails to build: InvalidProjectModelException
[
https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39643
]
Gert Vanthienen commented on SM-997:
The file at
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
doesn't match the pom.xml that is in SVN for tag {{servicemix-3.1.1}}, so I
guess something went wrong with the publishing. Does anyone know how to
publish a correct file?
> Basic example fails to build: InvalidProjectModelException
> --
>
> Key: SM-997
> URL: https://issues.apache.org/activemq/browse/SM-997
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-assembly
>Affects Versions: 3.1.1
> Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12,
> Maven 2.0.6
>Reporter: Evan Deaubl
>
> When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on
> the project in examples/basic, I receive the following error. I have
> completely removed my Maven repository and had it redownload everything from
> scratch, and still received this error. I manually checked the file it had
> downloaded, and the XML file was indeed invalid, and downloading the file
> directly from the source
> (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom)
> using Firefox yields an XML Parsing Error.
> [INFO] Scanning for projects...
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom
> 2K downloaded
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '507906935d130cfa9b44696270f62e006367533d'; remote =
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '507906935d130cfa9b44696270f62e006367533d'; remote =
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.servicemix:samples:pom:null
> Reason: Cannot find parent: org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
> parent: org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenPro
Error formatting macro: snippet
L.S., Some of our documentation pages use Confluence's snippet macro to include code sample (e.g. http://incubator.apache.org/servicemix/ftp.html). Currently, this macro doesn't seem to work any more: Error formatting macro: snippet: java.lang.IllegalArgumentException: Invalid url: must begin with a configured prefix. We're not alone, apparently the Struts team has the same problem (e.g. http://struts.apache.org/2.0.5/docs/conversion-validator.html). A quick search on the web seems to indicate that this is some kind of confguration problem with the snippet macro. Who can administer the Confluence instance that hosts our website to resolve this issue? Gert
[jira] Created: (SM-988) WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit archetype)
WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit
archetype)
--
Key: SM-988
URL: https://issues.apache.org/activemq/browse/SM-988
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor
If you build a SU using the servicemix-jsr181-annotated-service-unit, it
generates a pom.xml file which calls upon XFire's wsdlgen to generate a WSDL
file. However, this WSDL generation fails with this exception:
{noformat}
Embedded error: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.codehaus.xfire.spring.ServiceBean' defined in file
[C:\opt\project\jsr181-sample\wsdl-generate-sample\wsdlgen-jsr181-su\src\main\resources\services.xml]:
Error setting property values; nested
exception is org.springframework.beans.PropertyAccessExceptionsException:
PropertyAccessExceptionsException (1 errors); nested propertyAccessExceptions
are: [org.springframework.beans.TypeMismatchException: Failed to convert
property value of type [java.lang.String] to required type [java.lang.Class
] for property 'serviceClass'; nested exception is
java.lang.IllegalArgumentException: Class not found: com.sample.ExampleService]
{noformat}
Seems like the generator can't find the class, but yet the configuration for
the Ant task looks correct...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39544 ] Gert Vanthienen commented on SM-939: Applied and tested the second patch: everything compiles and tests run without failures. Committed as http://svn.apache.org/viewvc?view=rev&revision=551139 Thanks to Freeman Fang... > CXF based Service Engine and Bnding Component > - > > Key: SM-939 > URL: https://issues.apache.org/activemq/browse/SM-939 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Freeman Fang >Priority: Critical > Fix For: 3.2 > > Attachments: patch.txt, patch0627.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: servicemix-bean, ServiceUnitAnalyzer
Congratulations Guillaume!
Keep up the good work ;)
gnodet wrote:
>
> Sorry, the week has been quite busy (I have just had my fifth child) ...
>
> On 5/31/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
>>
>> any news?
>>
>>
>> On 5/24/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>> >
>> > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
>> > >
>> > > JIRA for the custom serviceUnitAnalyzer in jbi-maven-plugin:
>> > >
>> > > https://issues.apache.org/activemq/browse/SM-956
>> > >
>> > > JIRA for the BeanServiceUnitAnalyzer for the servicemix-bean
>> component:
>> > >
>> > > https://issues.apache.org/activemq/browse/SM-957
>> >
>> >
>> > Thanks ! I'll take a look at these asap.
>> >
>> > Regarding the BeanServiceUnitAnalyzer, I only implemented it for
>> endpoints
>> > > of type (I just thought this would be the most common
>> > > case).
>> > > I generated the consumes by looking at the fields with
>> @ExchangeTarget
>> > > using
>> > > reflection.
>> >
>> >
>> > Yeah, I guess this is the most common use cases.
>> >
>> > Please take a look.
>> > >
>> > >
>> > > Eduardo Burgos
>> > >
>> > >
>> > > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>> > > >
>> > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
>> > > > >
>> > > > > No, I'm not thinking about removing the other way, it's just to
>> have
>> > > > this
>> > > > > as
>> > > > > an option.
>> > > > > About the custom service analyzer, for example, lets say we have
>> a
>> > > > > component
>> > > > > that is not supported by this team and we have no possibility to
>> > > access
>> > > > > it's
>> > > > > source code and I still need to build a service unit for it,
>> > currently
>> > > > > there
>> > > > > is no possibility for the jbi-maven-plugin to guess an analyzer
>> for
>> > > it,
>> > > > so
>> > > > > I
>> > > > > thought that if we had the option to define the analyzer class at
>> > > > service
>> > > > > unit level it should do.
>> > > >
>> > > >
>> > > > Yeah, I was thinking about that too.
>> > > >
>> > > > Another example is what I need right now, I'm looking to develop a
>> > > > > servicemix-bean SU and I couldn't find a ServiceUnitAnalyzer for
>> > that
>> > > > > component. I couldn't have solved my problem in a standard way if
>> I
>> > > > don't
>> > > > > have access to this mailing list :)
>> > > >
>> > > >
>> > > > Agreed
>> > > >
>> > > > I have it set in my servicemix source and its ready for a diff and
>> > JIRA.
>> > > > > Working on the BeanSUAnalyzer as we speak :)
>> > > >
>> > > >
>> > > > Cool, thx !
>> > > >
>> > > > Eduardo Burgos
>> > > > >
>> > > > > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>> > > > > >
>> > > > > > Sure, sounds good !
>> > > > > > What kind of custom service analyser are thinking about ?
>> > > > > > Or is that for non servicemix components ?
>> > > > > >
>> > > > > > But I don't think we should remove the other way, which work
>> > > > > > well for servicemix components.
>> > > > > >
>> > > > > > Btw, such discussions about enhancing ServiceMix should really
>> > > > > > take place on the dev list, so please answer to the dev list
>> > > > > > if possible.
>> > > > > >
>> > > > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
>> > > > > > >
>> > > > > > > There is something else I would like to suggest.
>> > > > > > >
>> > > > > > > Let's say I have a service-unit artifact and my target
>> component
>> > > > does
>> > > > > > not
>> > > > > > > have a serviceUnitAnalyzer, I've seen the logic on the
>> > > > > jbi-maven-plugin
>> > > > > > > and
>> > > > > > > how it uses the serviceUnitAnalyzer and I noticed that it
>> either
>> > > > uses
>> > > > > > that
>> > > > > > > jbi-services.xml file or looks up the target component for a
>> > > > > > > serviceUnitAnalyzer class name.
>> > > > > > > What if we also have a
>> > > > > > >
>> > > > > > > declared in that service-unit artifact (not the component)
>> where
>> > I
>> > > > can
>> > > > > > > specify my desired serviceUnitAnalyzer for that SU. Example:
>> > > > > > >
>> > > > > > > > > > > > > > myproject
>> > > > > > > jbi-service-unit
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > org.apache.servicemix.tooling
>>
>> > > > > > > jbi-maven-plugin
>> > > > > > > ${servicemix-version}
>> > > > > > >
>> > > > > > >
>> > > org.test.jbi.bean.BeanServiceUnitAnalyzer
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Notice that the is in the SU's
>> > > > > configuration
>> > > > > > > and
>> > > > > > > not the component, this way the desired serviceUnitAnalyzer
>> is
>> > not
>> > > > > tied
>> > > > > > to
>> > > > > > > the component but to the plugin's configuration (And also
>> > keeping
>> > > > the
>> > > > > > > current approach).
>> > > > > > >
>> > > > > > >
>> > > > > > > Then in the
>> > > > > > >
>> > > > > > >
>
[jira] Updated: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
[
https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-960:
---
Attachment: citytime-sa-1.0-SNAPSHOT.jar
This is a SA that shows the problem when deploying it. Could this be bug
within XFire, StAX, ...?
> JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT,
> END_ELEMENT or ENTITY_REFERENCE )
>
>
> Key: SM-960
> URL: https://issues.apache.org/activemq/browse/SM-960
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
>Reporter: Sangwoo Han
>Priority: Minor
> Attachments: citytime-sa-1.0-SNAPSHOT.jar
>
>
> The jsr181 orchestration sample doesn't work.
> In the sample of jsr181 orchestration's CityTimeImpl.java class file
> [...]
> public GetCityTimeResponse getCityTime(GetCityTimeRequest
> GetCityTimeRequest) {
>
> GetInfoByCity GetInfoByCity = new GetInfoByCity();
> GetInfoByCity.setUSCity(GetCityTimeRequest.getCity());
>
> GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity);
> Element e = (Element)
> r.getGetInfoByCityResult().getContent().get(0);
> e = (Element) e.getElementsByTagName("Table").item(0);
> e = (Element) e.getElementsByTagName("ZIP").item(0);
> String ZipCode = e.getTextContent();
>
> //String lt = localTime.localTimeByZipCode(ZipCode); // at this
> part it errored
> GetCityTimeResponse rep = new GetCityTimeResponse();
> rep.getString().add("23:23");
> //rep.setTime(lt); // wsgen didn't generate "setTime" function
> return rep;
> }
> [...]
> and the error output is below:
>
> [...]
> DEBUG - header - << "Content-Length: 426[\r][\n]"
> DEBUG - content- << " encoding="utf-8"?>http://schemas.xmlso
> ap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> dy> xmlns="http://ripedev.com/xsd/ZipCodeResults.xsd";>5/30/2007
> 8:51:44 PM ocalTimeByZipCodeResult>"
>
> DEBUG - Client - Received message to
> urn:xfire:transport:jbi:11805763005154-996237611
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase pre-dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase dispatch
> DEBUG - HandlerPipeline- Invoking phase transport
> DEBUG - HandlerPipeline- Invoking phase parse
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch
> DEBUG - Client - Correlating context with ID
> 118057630051551778993400
> DEBUG - Client - Found correlated context with ID
> 118057630051551778993400
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase service
> DEBUG - HandlerPipeline- Invoking phase dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase user
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking phase transport
> DEBUG - HandlerPipeline- Invoking phase parse
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch
> DEBUG - Client - Correlating context with ID
> 118057630051551778993400
> DEBUG - Client - Found correlated context with ID
> 118057630051551778993400
> DEBUG - HandlerPip
Getting started guide
L.S., After having followed the user mailing list for a while, it seems that it's quite a steep learning curve to get started with ServiceMix. I would like to add a tutorial or getting started guide to the website, just guiding a new user through the existing documentation and trying to explain some key concepts on the way. Something like... # starting the container and connect to it using JMX # installing some components and deploying e.g. the wsdl-first example [to explain e.g. components, service assembly, service unit] # building a simple SA, e.g. re-using the 'File binding' page [to explain about the maven archetypes] # building e.g. the protocol bridge example to explain about message exchange patterns, routing, ... Would this be a worthwhile addition or are there other areas in the documentation that need work more urgently? Are there any other topics to include in this guided tour? Regards, Gert
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-xmpp.patch SM-932-truezip.patch Patches for servicemix-truezip and servicemix-xmpp > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip > Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch, > SM-932-truezip.patch, SM-932-xmpp.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Checkstyle / PMD and recent commits
Thomas,
Thank you for the quick response! This makes a serious difference in
the effort to make the binding components CheckStyle-compliant
Gert
Thomas TERMIN wrote:
Gert,
I checked in the change of the line length to 140.
Thomas
Gert Vanthienen wrote:
Guillaume,
Just a few questions/remarks about the CheckStyle rules:
- a lot of the code seems to be written with a line length of 132 in
mind, why change it to 120?
- the rules don't allow using this way of creating setters
public void setMBeanServer(MBeanServer mbeanServer) {
this.mbeanServer = mbeanServer;
}
Regards,
Gert Vanthienen
Guillaume Nodet wrote:
Hi everybody !
I have recently checked in lots of changes. These are mostly
code conventions fixes. Let me explain.
I've started to add checkstyle and pmd checks at build time.
For those who do not know these tools, checkstyle
(http://checkstyle.sourceforge.net/) enforces
code conventions (braces, spaces, etc ...), while PMD
(http://pmd.sourceforge.net/) checks for possible bugs.
These tools are configured in the new parent module
which all other modules should inherit directly or indirectly
when they pass these checks (the buid fails if these checks
do not pass).
Currently, only the serviceengines module inherit from parent
so any help to migrate the other modules is welcome :-)
The goal is to have all modules (core, common, deployables mainly)
inherit from parent.
Btw, thanks to the CXF team which did that a few months ago,
and where I borrowed the configuration and all ...
Re: Checkstyle / PMD and recent commits
Guillaume,
You're right what the setter syntax is concerned. The error message is
a bit confusing (local variable 'mbeanServer' hides a field or something
like that), but once the correct case is used to match the property to
the setter, CheckStyle does allow this syntax...
Gert
Guillaume Nodet wrote:
On 4/12/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
Guillaume,
Just a few questions/remarks about the CheckStyle rules:
- a lot of the code seems to be written with a line le
ngth of 132 in
mind, why change it to 120?
Well, I have only copied the CXF rules I must admit.
So it may be a good idea to increase it to 140 if needed.
- the rules don't allow using this way of creating setters
public void setMBeanServer(MBeanServer mbeanServer) {
this.mbeanServer = mbeanServer;
}
It should afaik. The only problem is that the name of the parameter
must match the name of the property.
For example
public void setXyz(String xyz) {
this.xyz = xyz;
}
I like this syntax so I really want this to work.
I guess if the property is spelled "mBeanServer" it will work.
Else, we can also disable this rule (not sure what the exact rule is).
Regards,
Gert Vanthienen
Guillaume Nodet wrote:
> Hi everybody !
>
> I have recently checked in lots of changes. These are mostly
> code conventions fixes. Let me explain.
>
> I've started to add checkstyle and pmd checks at build time.
> For those who do not know these tools, checkstyle
> (http://checkstyle.sourceforge.net/) enforces
> code conventions (braces, spaces, etc ...), while PMD
> (http://pmd.sourceforge.net/) checks for possible bugs.
>
> These tools are configured in the new parent module
> which all other modules should inherit directly or indirectly
> when they pass these checks (the buid fails if these checks
> do not pass).
>
> Currently, only the serviceengines module inherit from parent
> so any help to migrate the other modules is welcome :-)
> The goal is to have all modules (core, common, deployables mainly)
> inherit from parent.
>
> Btw, thanks to the CXF team which did that a few months ago,
> and where I borrowed the configuration and all ...
>
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-jms.patch SM-932-jms.patch fixes PDM/CheckStyle errors for servicemix-jms > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip > Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Checkstyle / PMD and recent commits
Guillaume,
Just a few questions/remarks about the CheckStyle rules:
- a lot of the code seems to be written with a line length of 132 in
mind, why change it to 120?
- the rules don't allow using this way of creating setters
public void setMBeanServer(MBeanServer mbeanServer) {
this.mbeanServer = mbeanServer;
}
Regards,
Gert Vanthienen
Guillaume Nodet wrote:
Hi everybody !
I have recently checked in lots of changes. These are mostly
code conventions fixes. Let me explain.
I've started to add checkstyle and pmd checks at build time.
For those who do not know these tools, checkstyle
(http://checkstyle.sourceforge.net/) enforces
code conventions (braces, spaces, etc ...), while PMD
(http://pmd.sourceforge.net/) checks for possible bugs.
These tools are configured in the new parent module
which all other modules should inherit directly or indirectly
when they pass these checks (the buid fails if these checks
do not pass).
Currently, only the serviceengines module inherit from parent
so any help to migrate the other modules is welcome :-)
The goal is to have all modules (core, common, deployables mainly)
inherit from parent.
Btw, thanks to the CXF team which did that a few months ago,
and where I borrowed the configuration and all ...
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-ftp.patch SM-932-ftp.patch fixes PDM/CheckStyle errors for servicemix-ftp > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip > Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38955
]
Gert Vanthienen commented on SM-915:
... but the original problem still isn't solved.
We get an additional stacktrace when ServiceMix is stopping and the problem
only appears to exist when the FTP server is IIS.
{code}
java.io.IOException: Fatal thread interruption during read.
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:344)
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:466)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:264)
at org.apache.commons.net.ftp.FTP.getReply(FTP.java:605)
at
org.apache.commons.net.ftp.FTPClient.completePendingCommand(FTPClient.java:1253)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2400)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:210)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:202)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:77)
at
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
{code}
I've asked the commons mailing list for help on this one...
> FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
>
>
> Key: SM-915
> URL: https://issues.apache.org/activemq/browse/SM-915
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
> Attachments: SM-915.patch
>
>
> FTP poller threads stop working with the stack trace below, causing the FTP
> client pool to run out of connections
> {code}
> Name: pool-component.servicemix-ftp-thread-2
> State: RUNNABLE
> Total blocked: 78,430 Total waited: 4,771
> Stack trace:
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
>
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
>
> org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> java.lang.Thread.run(Thread.java:595)
> {code}
> See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
> information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38944
]
Gert Vanthienen commented on SM-915:
Some additional observations - the problem only appears when:
* when a lot of files become available on the FTP server together
* some of them are being downloaded before they are complete, i.e. incomplete
XML messages are being read and processing fails for these messages
In the FTP poller code, we find
{code}
InputStream in = ftp.retrieveFileStream(file);
InOnly exchange = getExchangeFactory().createInOnlyExchange();
configureExchangeTarget(exchange);
NormalizedMessage message = exchange.createMessage();
exchange.setInMessage(message);
marshaler.readMessage(exchange, message, in, file);
sendSync(exchange);
in.close();
ftp.completePendingCommand();
{code}
My question: Is it possible that {{sendSync(exchange)}} throws an Exception
when an incomplete XML message is retrieved from the server? If it does, the
inputstream is never closed and {{completePendingCommand()}} is never called,
which might explain the problems
> FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
>
>
> Key: SM-915
> URL: https://issues.apache.org/activemq/browse/SM-915
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1
> Reporter: Gert Vanthienen
>
> FTP poller threads stop working with the stack trace below, causing the FTP
> client pool to run out of connections
> {code}
> Name: pool-component.servicemix-ftp-thread-2
> State: RUNNABLE
> Total blocked: 78,430 Total waited: 4,771
> Stack trace:
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
>
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
>
> org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> java.lang.Thread.run(Thread.java:595)
> {code}
> See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
> information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
Key: SM-915
URL: https://issues.apache.org/activemq/browse/SM-915
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1
Reporter: Gert Vanthienen
FTP poller threads stop working with the stack trace below, causing the FTP
client pool to run out of connections
{code}
Name: pool-component.servicemix-ftp-thread-2
State: RUNNABLE
Total blocked: 78,430 Total waited: 4,771
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
java.lang.Thread.run(Thread.java:595)
{code}
See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
[
https://issues.apache.org/activemq/browse/SM-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38916
]
Gert Vanthienen commented on SM-899:
As far as I understand the code:
DefaultComponent's doInit() method first registers all endpoint, thereby lazily
creating the corresponding service unit. After all endpoint have been
registered, the serviceUnit is no longer *{{null}}* and the doInit() method
will call Registry's registerServiceUnit() which will attempt to register all
the endpoints again, resulting in the stacktrace shown above.
The simple solution would be to add a test to DefaultComponent's doInit()
method, only registering the service unit if it hasn't been registered before.
As a more general solution, the same test could also be added to Registry's
registerServiceUnit(). Does anyone see a problem with the latter approach?
> org.apache.servicemix.file.SpringComponentTest fails with
> java.lang.IllegalStateException
> -
>
> Key: SM-899
> URL: https://issues.apache.org/activemq/browse/SM-899
> Project: ServiceMix
> Issue Type: Sub-task
> Components: servicemix-file
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>
> This is the stack trace:
> {noformat}
> Caused by: javax.jbi.JBIException: Error calling init
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
>
> Caused by: java.lang.IllegalStateException: An endpoint is already registered
> for key: {urn:test}service:endpoint
> at
> org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
> at
> org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
> at
> org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
org.apache.servicemix.file.SpringComponentTest fails with
java.lang.IllegalStateException
-
Key: SM-899
URL: https://issues.apache.org/activemq/browse/SM-899
Project: ServiceMix
Issue Type: Sub-task
Components: servicemix-file
Affects Versions: 3.1
Reporter: Gert Vanthienen
This is the stack trace:
{noformat}
Caused by: javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
Caused by: java.lang.IllegalStateException: An endpoint is already registered
for key: {urn:test}service:endpoint
at org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
at
org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
at
org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-889) Add possibility to rename files after FTP upload
[ https://issues.apache.org/activemq/browse/SM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-889: --- Attachment: SM-889.patch This patch allows users to specify an attribute uploadSuffix="..." on the endpoint. This suffix will be appended to the file name during upload. Upon completion, the file will be renamed to the correct name. This attribute only works if a name has been specified for upload, otherwise it is ignored. The patch also tries to solve a problem I have encountered with IIS/FTP. If no data was actually transferred to the server (e.g. because of an already existing file name), the call to client.completePendingCommand() sometimes appeared to take a very long time (waiting for some kind of time-out). With this patch, this call will only be issued if an OutputStream has actually been acquired. > Add possibility to rename files after FTP upload > > > Key: SM-889 > URL: https://issues.apache.org/activemq/browse/SM-889 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-ftp >Affects Versions: 3.1 >Reporter: Gert Vanthienen >Priority: Minor > Fix For: 3.1.1, 3.2 > > Attachments: SM-889.patch > > > Add the possibility to upload files to the FTP server using another suffix > (e.g. .part) and rename the file after the upload is completed. This way, it > is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-889) Add possibility to rename files after FTP upload
Add possibility to rename files after FTP upload Key: SM-889 URL: https://issues.apache.org/activemq/browse/SM-889 Project: ServiceMix Issue Type: Improvement Components: servicemix-ftp Affects Versions: 3.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.1, 3.2 Add the possibility to upload files to the FTP server using another suffix (e.g. .part) and rename the file after the upload is completed. This way, it is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New css for the web site
Guillaume, Great! This looks much better (to me)... Gert Guillaume Nodet wrote: CSS updated. thx ! Feedback welcome :-) On 2/20/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: Guillaume, I like the new look. Just a few thoughts from someone who usually does a lousy job as a web designer ... - if you make the left margin (padding?) in the menu a bit smaller, the separation between the menu and the body part will be more visible - I would prefer a smaller font size for the body text (and perhaps also a sans-serif style font) - Would it be possible to make the images in the top banner just a little bit smaller? Regards, Gert Guillaume Nodet wrote: > I have written a new css for the web site today. > You can preview it at > http://cwiki.apache.org/SM/orchestration-with-jsr181.html > > What do people think about switching to it ? > I think there are a few things to tweak for IE .. >
Re: [VOTE] Release ServiceMix 3.1 (2nd try)
I tried some of the examples and a small app of my own: it all worked fine. +1 (non-binding) Hiram Chirino wrote: Sorry for the delay. +1 On 2/5/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: The vote is extended for another period of 3 days. And here's my +1 On 2/1/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > I have fixed and uploaded the samples, the jbi plugin (which i had to > build manually) > and uploaded everything to the incubating repository > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/ > > Distributions are available at: > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.1-incubating/ > http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix-web/3.1-incubating/ > > Please download, review and vote ... > This vote will be closed on sunday, midnight GMT > > -- > Cheers, > Guillaume Nodet > > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
[jira] Created: (GERONIMODEVTOOLS-109) Eclipse plug-in doesn't show errors on deployment
Eclipse plug-in doesn't show errors on deployment - Key: GERONIMODEVTOOLS-109 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-109 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.1.0 Reporter: Gert Vanthienen Priority: Minor As discussed in the thread of http://mail-archives.apache.org/mod_mbox/geronimo-user/200609.mbox/browser, errors that occur on deployment of an application are not available in the Eclipse UI. You can get to them in a log in workspace/.metadata, but a more user friendly way would be to show this information in the error dialog itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
