[jira] Commented: (SM-1132) No clean shutdown of ServiceMix
[ https://issues.apache.org/activemq/browse/SM-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40596 ] Gert Vanthienen commented on SM-1132: - Instead of only notifying the lock object in SpringJBIContainer's shutdownHook implemenation, we now moved the entire destroy() of the ApplicationContext into the shutdown hook to ensure correct shutdown behavior. http://svn.apache.org/viewvc?view=rev&revision=594535 http://svn.apache.org/viewvc?view=rev&revision=594553 There are still a few exceptions left, probably due to JMS connections/sessions not being closed properly. > No clean shutdown of ServiceMix > --- > > Key: SM-1132 > URL: https://issues.apache.org/activemq/browse/SM-1132 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core >Affects Versions: 3.2 > Environment: Tested on Gentoo Linux and also Ubuntu Linux 7.10 >Reporter: Lars Heinemann > Fix For: 3.1.2 > > > If I shutdown servicemix by hitting CTRL-C in the shell, the shutdown process > is finished almost in a second or so. Next thing is that components are not > shut down properly as they were in the 3.1.2 version. This was not a problem > with the old version of smix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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 updated SM-1119: Attachment: SM-1119.patch Philip, The WSDL first SA I created works correctly if I add "encoding=utf-8" to the content type in SoapWriter. Could you try if this patch also solves your original problem? Gert > 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 > Attachments: multimatch-search.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] Updated: (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 updated SM-1119: Attachment: wsdl-first-sa-3.2-SNAPSHOT.jar I was unable to build the example provided (due to missing libraries that are not publicly available), but I think I managed to reproduce the same error with this SA. > 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 > Attachments: multimatch-search.zip, 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-1104) Type converters not working in ServiceMix
[
https://issues.apache.org/activemq/browse/SM-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1104.
-
Resolution: Fixed
This commit (https://svn.apache.org/viewvc?view=rev&revision=587048) by James
Strachan fixed the issue
> Type converters not working in ServiceMix
> -
>
> Key: SM-1104
> URL: https://issues.apache.org/activemq/browse/SM-1104
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
>Reporter: Gert Vanthienen
> Fix For: 3.2
>
>
> Currently, the Camel type converters do not work inside ServiceMix. Consider
> this example (replacing the eip:wire-tap in our tutorial using Camel)
> {code}
> from("jbi:service:urn:servicemix:tutorial:wiretap")
> .convertBodyTo(DOMSource.class)
> .to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue",
> "jbi:endpoint:urn:servicemix:tutorial:file:sender");
> {code}
> The snippet intends to convert the StreamSource, coming from the
> to a DOMSource for sending it to both other endpoints, but
> conversion never happens. Haven't really looked into this, but it might be a
> classloading issue..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1104) Type converters not working in ServiceMix
Type converters not working in ServiceMix
-
Key: SM-1104
URL: https://issues.apache.org/activemq/browse/SM-1104
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Reporter: Gert Vanthienen
Fix For: 3.2
Currently, the Camel type converters do not work inside ServiceMix. Consider
this example (replacing the eip:wire-tap in our tutorial using Camel)
{code}
from("jbi:service:urn:servicemix:tutorial:wiretap")
.convertBodyTo(DOMSource.class)
.to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue",
"jbi:endpoint:urn:servicemix:tutorial:file:sender");
{code}
The snippet intends to convert the StreamSource, coming from the
to a DOMSource for sending it to both other endpoints, but conversion never
happens. Haven't really looked into this, but it might be a classloading
issue..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1096) File-based message auditor
[ https://issues.apache.org/activemq/browse/SM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40308 ] Gert Vanthienen commented on SM-1096: - Partial implementation available: http://svn.apache.org/viewvc?view=rev&revision=582783 Two major issues: - There is no way to specify a filename for archiving: perhaps we can add a FileAuditorNamingStrategy interface to allow people to plug in their own naming rules. - It only stores the 'in' normalized message content. We should add the message properties to the file as well. > File-based message auditor > -- > > Key: SM-1096 > URL: https://issues.apache.org/activemq/browse/SM-1096 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-audit >Reporter: Gert Vanthienen >Priority: Minor > Fix For: 3.2 > > > Adding a file-based auditor implementation. As discussed in SM-990, a > TeeInputStream should be used for optimizing performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1096) File-based message auditor
File-based message auditor -- Key: SM-1096 URL: https://issues.apache.org/activemq/browse/SM-1096 Project: ServiceMix Issue Type: New Feature Components: servicemix-audit Reporter: Gert Vanthienen Priority: Minor Fix For: 3.2 Adding a file-based auditor implementation. As discussed in SM-990, a TeeInputStream should be used for optimizing performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1093) NPE - FTP Sender Endpoint
[
https://issues.apache.org/activemq/browse/SM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1093.
-
Resolution: Fixed
Fix Version/s: 3.1.3
Right you are, missed that one...
It was already fixed in 3.2 while adding the rename-after-upload feature. Here
is the fix for the 3.1.3 branch:
http://svn.apache.org/viewvc?view=rev&revision=582204
> NPE - FTP Sender Endpoint
> -
>
> Key: SM-1093
> URL: https://issues.apache.org/activemq/browse/SM-1093
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1.1
> Environment: Windows XP / Servicemix 3.1.1
>Reporter: Noseda Anne
> Fix For: 3.1.3
>
>
> FTP Sender Endpoint config :
> endpoint="FtpEndpoint"
> overwrite="true"
> uri="ftp://root:[EMAIL PROTECTED]/usr/ftp/cosu" />
> Error Log :
> ERROR - FtpComponent - Error processing exchange InOnly[
> id: ID:192.168.80.76-1156f58bd83-2:1
> status: Active
> role: provider
> service: {http://www.etnic.be/janus/test/cosu}FtpService
> endpoint: FtpEndpoint
> in: 0123456789;1;MED
> 9876543210;1;ING
>
> ]
> java.lang.NullPointerException
> at
> org.apache.servicemix.ftp.FtpSenderEndpoint.processInOnly(FtpSenderEndpoint.java:176)
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1093) NPE - FTP Sender Endpoint
[
https://issues.apache.org/activemq/browse/SM-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40283
]
Gert Vanthienen commented on SM-1093:
-
That would be on the line that says:
{code}
client.completePendingCommand();
{code}
Unsure how the client object can be null on that line... Is there any
additional information in the logs before that? Can you try setting the
logging level to DEBUG for org.apache.servicemix.ftp, so we can figure out what
exactly has been done by the sender endpoint?
> NPE - FTP Sender Endpoint
> -
>
> Key: SM-1093
> URL: https://issues.apache.org/activemq/browse/SM-1093
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1.1
> Environment: Windows XP / Servicemix 3.1.1
>Reporter: Noseda Anne
>
> FTP Sender Endpoint config :
> endpoint="FtpEndpoint"
> overwrite="true"
> uri="ftp://root:[EMAIL PROTECTED]/usr/ftp/cosu" />
> Error Log :
> ERROR - FtpComponent - Error processing exchange InOnly[
> id: ID:192.168.80.76-1156f58bd83-2:1
> status: Active
> role: provider
> service: {http://www.etnic.be/janus/test/cosu}FtpService
> endpoint: FtpEndpoint
> in: 0123456789;1;MED
> 9876543210;1;ING
>
> ]
> java.lang.NullPointerException
> at
> org.apache.servicemix.ftp.FtpSenderEndpoint.processInOnly(FtpSenderEndpoint.java:176)
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1056) Add NamespaceContextImpl to servicemix-core
[ https://issues.apache.org/activemq/browse/SM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1056. - Resolution: Fixed Fix Version/s: 3.2 http://svn.apache.org/viewvc?view=rev&revision=577452 http://svn.apache.org/viewvc?view=rev&revision=577453 > 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 > Fix For: 3.2 > > > 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.
[jira] Resolved: (SM-1043) Poller sends invalid MessageExchange when file has been deleted
[ https://issues.apache.org/activemq/browse/SM-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1043. - Resolution: Fixed http://svn.apache.org/viewvc?view=rev&revision=572807 http://svn.apache.org/viewvc?view=rev&revision=572808 > Poller sends invalid MessageExchange when file has been deleted > --- > > Key: SM-1043 > URL: https://issues.apache.org/activemq/browse/SM-1043 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-ftp >Affects Versions: 3.1.1 >Reporter: Gert Vanthienen >Assignee: Gert Vanthienen > Fix For: 3.1.2, 3.2 > > > If a file is deleted from the FTP server while the Poller is processing a > directory, the poller stills sends a MessageExchange, resulting in a > FileNotFoundException... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1043) Poller sends invalid MessageExchange when file has been deleted
Poller sends invalid MessageExchange when file has been deleted --- Key: SM-1043 URL: https://issues.apache.org/activemq/browse/SM-1043 Project: ServiceMix Issue Type: Bug Components: servicemix-ftp Affects Versions: 3.1.1 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Fix For: 3.1.2, 3.2 If a file is deleted from the FTP server while the Poller is processing a directory, the poller stills sends a MessageExchange, resulting in a FileNotFoundException... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-1042) Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class)
[
https://issues.apache.org/activemq/browse/SM-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed SM-1042.
---
Resolution: Fixed
Fix Version/s: 3.2
Changing Class back into Class fixes this:
http://svn.apache.org/viewvc?view=rev&revision=570136
> 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
> Fix For: 3.2
>
>
> 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.
[jira] Resolved: (SM-1025) Add an example of to the archetype's xbean.xml
[
https://issues.apache.org/activemq/browse/SM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1025.
-
Resolution: Fixed
Fix Version/s: 3.2
Thanks again, Martin Krasser!
http://svn.apache.org/viewvc?view=rev&revision=564874
> Add an example of to the archetype's xbean.xml
> -
>
> Key: SM-1025
> URL: https://issues.apache.org/activemq/browse/SM-1025
> Project: ServiceMix
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 3.1.1
>Reporter: Gert Vanthienen
>Priority: Minor
> Fix For: 3.2
>
> Attachments: servicemix-eip-service-unit-patch.txt
>
>
> The xbean.xml file generated by the {{servicemix-eip-service-unit}} archetype
> doesn't contain an example for the new
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1025) Add an example of to the archetype's xbean.xml
Add an example of to the archetype's xbean.xml
-
Key: SM-1025
URL: https://issues.apache.org/activemq/browse/SM-1025
Project: ServiceMix
Issue Type: Improvement
Components: tooling
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Priority: Minor
The xbean.xml file generated by the {{servicemix-eip-service-unit}} archetype
doesn't contain an example for the new
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1024) Archetype generates invalid brokerURL
[
https://issues.apache.org/activemq/browse/SM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1024.
-
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
The servicemix-jms-consumer-service-unit archetype had the same problem. Fixed
in both trunk and the 3.1.2-SNAPSHOT branch
http://svn.apache.org/viewvc?view=rev&revision=564082
http://svn.apache.org/viewvc?view=rev&revision=564083
> Archetype generates invalid brokerURL
> -
>
> Key: SM-1024
> URL: https://issues.apache.org/activemq/browse/SM-1024
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.1.1
>Reporter: Gert Vanthienen
>Priority: Trivial
> Fix For: 3.1.2, 3.2
>
>
> The servicemix-jms-provider-service-unit generates an xbean.xml file that
> contains
> {code:xml}
> brokerURL="tcp://localhost:61616/" />
> {code}
> When you try to deploy this, you get an exception on the trailing /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1024) Archetype generates invalid brokerURL
Archetype generates invalid brokerURL
-
Key: SM-1024
URL: https://issues.apache.org/activemq/browse/SM-1024
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Priority: Trivial
The servicemix-jms-provider-service-unit generates an xbean.xml file that
contains
{code:xml}
{code}
When you try to deploy this, you get an exception on the trailing /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-990) FilePoller with Archiving
[
https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-990.
Resolution: Fixed
Fix Version/s: 3.2
Added {{archive}} attribute to specify the archive directory
http://svn.apache.org/viewvc?view=rev&revision=564081
> 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
> Fix For: 3.2
>
>
> 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-1020) Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
[
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1020.
-
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
Changed the comment syntax in the archetype
http://svn.apache.org/viewvc?view=rev&revision=563873
http://svn.apache.org/viewvc?view=rev&revision=563877
> Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
>
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
> Fix For: 3.1.2, 3.2
>
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>
>resource="classpath:query.xq" />
>
>
>
>
>
> for $x in /bookstore/book
> where $x/price > 30
> return $x/title
>
>
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
> XPST0003: XQuery syntax error in #...er the License. --> {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the
> matching end-tag "".
> WARN - ServiceAssemblyLifeCycle - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-jsr181-su
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-http-su
> INFO - DeploymentService - Error in start
> java.lang.Exception:
> http://java.sun.com/xml/ns/jbi/management-message";
> version="1.0">
>
>
>
>
> start
> FAILED
> ERROR
>
>
>
>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
>
>
> Unable to parse result string
>
>
>
> 1
>
> xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
> Unable to start
> service unit
>
> 1
>
>
> XQuery syntax error in
> #...er the License. --> {#:
> Unexpected token ">" beyond end of query
>
>
>
>
>
>
>
>
>
>
>
>
>
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi
[jira] Updated: (SM-1020) Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
[
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-1020:
Component/s: (was: servicemix-saxon)
tooling
Summary: Invalid query.xq generated by
servicemix-saxon-xquery-service-unit archetype (was: Problem with the
saxon-xquery component and the generic query.xq file)
> Invalid query.xq generated by servicemix-saxon-xquery-service-unit archetype
>
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>
>resource="classpath:query.xq" />
>
>
>
>
>
> for $x in /bookstore/book
> where $x/price > 30
> return $x/title
>
>
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
> XPST0003: XQuery syntax error in #...er the License. --> {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the
> matching end-tag "".
> WARN - ServiceAssemblyLifeCycle - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-jsr181-su
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-http-su
> INFO - DeploymentService - Error in start
> java.lang.Exception:
> http://java.sun.com/xml/ns/jbi/management-message";
> version="1.0">
>
>
>
>
> start
> FAILED
> ERROR
>
>
>
>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
>
>
> Unable to parse result string
>
>
>
> 1
>
> xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
> Unable to start
> service unit
>
> 1
>
>
> XQuery syntax error in
> #...er the License. --> {#:
> Unexpected token ">" beyond end of query
>
>
>
>
>
>
>
>
>
>
>
>
>
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi.framework.AutoDeploy
[jira] Reopened: (SM-1020) Problem with the saxon-xquery component and the generic query.xq file
[
https://issues.apache.org/activemq/browse/SM-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen reopened SM-1020:
-
Assignee: Gert Vanthienen
The query.xq Erik refers to is generated by our own
servicemix-saxon-xquery-service-unit archetype. It would be better to fix the
archetype to provide the users with a correct query.xq sample file.
> Problem with the saxon-xquery component and the generic query.xq file
> -
>
> Key: SM-1020
> URL: https://issues.apache.org/activemq/browse/SM-1020
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-saxon
>Affects Versions: 3.1.1
>Reporter: Erik Allais
>Assignee: Gert Vanthienen
>Priority: Trivial
>
> hi,
> i compile the saxon component and deploy on servicemix-3.1.1
> here the following xbean.xml
> http://servicemix.apache.org/saxon/1.0";
>xmlns:example="http://example.com/exampleService";>
>
>resource="classpath:query.xq" />
>
>
>
>
>
> for $x in /bookstore/book
> where $x/price > 30
> return $x/title
>
>
>key="{http://saxon.sf.net/}wrap-result-sequence";>yes
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> i dont touch the query.xq (the problem seems to come from this file)
> My error is :
> Error on line 18 column 8
> XPST0003: XQuery syntax error in #...er the License. --> {#:
> Unexpected token ">" beyond end of query
> [Fatal Error] :14:47: The element type "titles" must be terminated by the
> matching end-tag "".
> WARN - ServiceAssemblyLifeCycle - Could not parse result exception
> org.xml.sax.SAXParseException: The element type "titles" must be terminated
> by the matching end-tag "".
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-jsr181-su
> INFO - ServiceUnitLifeCycle - Starting service unit: mc-http-su
> INFO - DeploymentService - Error in start
> java.lang.Exception:
> http://java.sun.com/xml/ns/jbi/management-message";
> version="1.0">
>
>
>
>
> start
> FAILED
> ERROR
>
>
>
>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
>
>
> Unable to parse result string
>
>
>
> 1
>
> xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
> servicemix-saxon
>
>
> start
> FAILED
> ERROR
>
> Unable to start
> service unit
>
> 1
>
>
> XQuery syntax error in
> #...er the License. --> {#:
> Unexpected token ">" beyond end of query
>
>
>
>
>
>
>
>
>
>
>
>
>
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
> at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.mo
[jira] Commented: (SM-990) FilePoller with Archiving
[ 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-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 resolved SM-932. Resolution: Fixed Fix Version/s: 3.2 Updated the binding components' parent pom.xml http://svn.apache.org/viewvc?view=rev&revision=557983 > 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 > Fix For: 3.2 > > Attachments: SM-932-file.patch, SM-932-ftp.patch, > SM-932-http-part2.patch, SM-932-http.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.
[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39721 ] Gert Vanthienen commented on SM-932: Fixed for servicemix-ftp http://svn.apache.org/viewvc?view=rev&revision=557640 Fixed for servicemix-http http://svn.apache.org/viewvc?view=rev&revision=557757 Fixed for servicemix-jms http://svn.apache.org/viewvc?view=rev&revision=557769 Fixed for servicemix-truezip http://svn.apache.org/viewvc?view=rev&revision=557978 Fixed for servicemix-xmpp http://svn.apache.org/viewvc?view=rev&revision=557981 > 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-http-part2.patch, SM-932-http.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.
[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39702 ] Gert Vanthienen commented on SM-932: Fixed for servicemix-file: http://svn.apache.org/viewvc?view=rev&revision=557551 > 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-http-part2.patch, SM-932-http.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.
[jira] Resolved: (SM-1006) 0 byte files written when message contains invalid content
[ https://issues.apache.org/activemq/browse/SM-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1006. - Resolution: Fixed Fix Version/s: 3.2 3.1.2 http://svn.apache.org/viewvc?view=rev&revision=557173 http://svn.apache.org/viewvc?view=rev&revision=557174 > 0 byte files written when message contains invalid content > -- > > Key: SM-1006 > URL: https://issues.apache.org/activemq/browse/SM-1006 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1.1 >Reporter: Gert Vanthienen > Fix For: 3.1.2, 3.2 > > > When a message contains invalid content (e.g. incomplete XML message), a 0 > byte file is created by the . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1006) 0 byte files written when message contains invalid content
0 byte files written when message contains invalid content -- Key: SM-1006 URL: https://issues.apache.org/activemq/browse/SM-1006 Project: ServiceMix Issue Type: Bug Components: servicemix-file Affects Versions: 3.1.1 Reporter: Gert Vanthienen When a message contains invalid content (e.g. incomplete XML message), a 0 byte file is created by the . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-997) Basic example fails to build: InvalidProjectModelException
[ https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-997: --- Priority: Critical (was: Major) > 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 >Priority: Critical > > 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(DefaultMavenProjectBuilder.java:749) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) > ... 11 more > Caused by: org.apache.maven.project.InvalidProjectModelExceptio
[jira] Resolved: (SM-937) Poller polls subdirectory even though recursive is set to false
[ https://issues.apache.org/activemq/browse/SM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-937. Resolution: Fixed Fix Version/s: 3.2 3.1.2 Thanks to Rabi Mishra for providing this patch! http://svn.apache.org/viewvc?view=rev&revision=556821 http://svn.apache.org/viewvc?view=rev&revision=556822 > Poller polls subdirectory even though recursive is set to false > > > Key: SM-937 > URL: https://issues.apache.org/activemq/browse/SM-937 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-ftp >Affects Versions: 3.1 >Reporter: Markus Rado >Priority: Minor > Fix For: 3.1.2, 3.2 > > Attachments: patch-ftppoller.txt > > > Poller polls subdirectory even though recursive is set to false because in > the first call to pollFileOrDirectory processDir is set to true. Either the > first call should use the value of property recursive or the processDir flag > should be checked before starting to process the files in the 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-1004) File poller deletes files, even if errors occur while processing
[ https://issues.apache.org/activemq/browse/SM-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1004. - Resolution: Fixed Fix Version/s: 3.2 3.1.2 Thanks to Rabi Mishra for the initial patch and help in resolving this issue! http://svn.apache.org/viewvc?view=rev&revision=556580 http://svn.apache.org/viewvc?view=rev&revision=556595 > File poller deletes files, even if errors occur while processing > > > Key: SM-1004 > URL: https://issues.apache.org/activemq/browse/SM-1004 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1.1 >Reporter: Gert Vanthienen > Fix For: 3.1.2, 3.2 > > > Other poller components (e.g. FTP poller) leave the message where it is in > case of error/fault, so it can be retried afterwards (e.g. services > unavailable, XML message content not yet complete, ...). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1004) File poller deletes files, even if errors occur while processing
File poller deletes files, even if errors occur while processing Key: SM-1004 URL: https://issues.apache.org/activemq/browse/SM-1004 Project: ServiceMix Issue Type: Bug Components: servicemix-file Affects Versions: 3.1.1 Reporter: Gert Vanthienen Other poller components (e.g. FTP poller) leave the message where it is in case of error/fault, so it can be retried afterwards (e.g. services unavailable, XML message content not yet complete, ...). -- 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_39661
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
My checkout has a CheckStyle suppresion for this particular check in the
GraphArtifactCollector class registered in
{{build/src/main/resources/smx-checkstyle-suppressions.xml}}. Can you check if
you have that too? Perhaps your build/ directory needs another update...
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] Updated: (SM-935) Allow to specify additional JNDI properties
[
https://issues.apache.org/activemq/browse/SM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-935:
---
Attachment: SM-935.patch
Phiroze,
The attached patch should enable you to specify jndiProperties="..." on the
. Can you help me try it out before I commit it?
Gert
> Allow to specify additional JNDI properties
> ---
>
> Key: SM-935
> URL: https://issues.apache.org/activemq/browse/SM-935
> Project: ServiceMix
> Issue Type: New Feature
> Components: servicemix-jms
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-935.patch
>
>
> In addition to using initialContext and jndiProviderUrl to configure a JMS
> endpoint, it should be possible to specify additional JNDI properties (e.g
> {{java.naming.security.principal}}, {{java.naming.security.credentials}})
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-990) FilePoller with Archiving
[ https://issues.apache.org/activemq/browse/SM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39651 ] Gert Vanthienen commented on SM-990: Perhaps we can create a more generic solution for this: with SM-751 we have a correlation id that allows us to do flow tracing, so it should be possible to build an auditor that is triggered whenever a new message arrives (at any kind of endpoint: FTP, File, HTTP, ...) and sends a copy of the message to an archiving endpoint. > 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-996) ServiceMix doesn't start correctly due to javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String
[ https://issues.apache.org/activemq/browse/SM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-996. Resolution: Fixed Fix Version/s: 3.2 Piotr: Apparently, we were working on the same thing. I created setter methods for the two supported types (String and ObjectName) to trick Spring into skipping the conversion to QName. Anyway, the problem is resolved now: http://svn.apache.org/viewvc?view=rev&revision=555219 > ServiceMix doesn't start correctly due to > javax.management.MalformedObjectNameException: Invalid ObjectName value type > [javax.xml.namespace.QName]: only ObjectName and String supported > > > Key: SM-996 > URL: https://issues.apache.org/activemq/browse/SM-996 > Project: ServiceMix > Issue Type: Bug >Affects Versions: 3.2 > Environment: ServiceMix trunk rev. 553445 >Reporter: Piotr Bzdyl >Priority: Blocker > Fix For: 3.2 > > Attachments: SM-996.patch.diff > > > After I rebuild SMix from trunk with revision 553445 I got following error > upon startup: > Loading Apache ServiceMix from servicemix.xml on the CLASSPATH > Caught: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name > 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined in class > path resource [jmx.xml]: Invocation of init method failed; nested exception > is javax.management.MalformedObjectNameException: Invalid ObjectName value > type [javax.xml.namespace.QName]: only ObjectName and String supported. > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined > in class path resource [jmx.xml]: Invocation of init method failed; nested > exception is javax.management.MalformedObjectNameException: Invalid > ObjectName value type [ > javax.xml.namespace.QName]: only ObjectName and String supported. > Caused by: javax.management.MalformedObjectNameException: Invalid ObjectName > value type [javax.xml.namespace.QName]: only ObjectName and String supported. > at > org.springframework.jmx.support.ObjectNameManager.getInstance(ObjectNameManager.java:58) > at > org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName(ConnectorServerFactoryBean.java:104) > at > org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:186) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425) > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:284) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) > at > org.apache.xbean.spring.context.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:161) > at > org.apache.xbean.spring.context.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:51) > at org.apache.servicemix.Main.main(Main.java:51) > 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.launchStandard(Launcher.java:410) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:344) > at org.codehaus.classworlds.Launcher.main(Launcher.java:461) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-977) wsdl-first example fails: XFireFault (could not unmarshal type)
[
https://issues.apache.org/activemq/browse/SM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed SM-977.
--
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
http://svn.apache.org/viewvc?view=rev&revision=552098
http://svn.apache.org/viewvc?view=rev&revision=552099
> wsdl-first example fails: XFireFault (could not unmarshal type)
> ---
>
> Key: SM-977
> URL: https://issues.apache.org/activemq/browse/SM-977
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
>Affects Versions: 3.1.2
>Reporter: Gert Vanthienen
> Fix For: 3.1.2, 3.2
>
>
> After 'resolving' SM-960, the wsdl-first example no longer works. It throws
> this exception, caused by differences in namespace. The original wsdl file
> has it's GetPerson element in another namespace than the one that is being
> shown when browsing for the wsdl after deployment.
> {noformat}
> org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected
> element (uri:"http://servicemix.apache.org/samples/wsdl-first";,
> local:"GetPerson"). Expected elements are
> <{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
> at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
> at
> org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
> at
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
> at
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
> at
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
> at
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
> at
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-977) wsdl-first example fails: XFireFault (could not unmarshal type)
[
https://issues.apache.org/activemq/browse/SM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39494
]
Gert Vanthienen commented on SM-977:
Apparently, you can avoid this exception by omitting the
*{{org.codehaus.xfire.jaxws.gen.JAXWSProfile}}* from the
wsgen generator configuration in pom.xml
> wsdl-first example fails: XFireFault (could not unmarshal type)
> ---
>
> Key: SM-977
> URL: https://issues.apache.org/activemq/browse/SM-977
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
>Affects Versions: 3.1.2
>Reporter: Gert Vanthienen
>
> After 'resolving' SM-960, the wsdl-first example no longer works. It throws
> this exception, caused by differences in namespace. The original wsdl file
> has it's GetPerson element in another namespace than the one that is being
> shown when browsing for the wsdl after deployment.
> {noformat}
> org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected
> element (uri:"http://servicemix.apache.org/samples/wsdl-first";,
> local:"GetPerson"). Expected elements are
> <{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
> at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
> at
> org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
> at
> org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
> at
> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
> at
> org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
> at
> org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
> at
> org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> {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-977) wsdl-first example fails: XFireFault (could not unmarshal type)
wsdl-first example fails: XFireFault (could not unmarshal type)
---
Key: SM-977
URL: https://issues.apache.org/activemq/browse/SM-977
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jsr181
Affects Versions: 3.1.2
Reporter: Gert Vanthienen
After 'resolving' SM-960, the wsdl-first example no longer works. It throws
this exception, caused by differences in namespace. The original wsdl file has
it's GetPerson element in another namespace than the one that is being shown
when browsing for the wsdl after deployment.
{noformat}
org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected
element (uri:"http://servicemix.apache.org/samples/wsdl-first";,
local:"GetPerson"). Expected elements are
<{http://servicemix.apache.org/samples/wsdl-first/types}GetPerson>,<{http://servicemix.apache.org/samples/wsdl-first/types}GetPersonResponse>,<{http://servicemix.apache.org/samples/wsdl-first/types}UnknownPersonFault>
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:216)
at
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-973) servmicemix-sca: 2 PMD violations fix.
[ https://issues.apache.org/activemq/browse/SM-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-973. Resolution: Fixed Fixed together with SM-976 http://svn.apache.org/viewvc?view=rev&revision=550026 > servmicemix-sca: 2 PMD violations fix. > -- > > Key: SM-973 > URL: https://issues.apache.org/activemq/browse/SM-973 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-sca > Environment: all >Reporter: Brian O'Neill >Assignee: Bruce Snyder >Priority: Minor > Attachments: sca_pmd_patch.txt > > > Fix for PMD violations causing 2 compilation errors for servicemix-sca -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-976) servicemix-sca is out of touch with the CheckStyle and PMD guides.
[ https://issues.apache.org/activemq/browse/SM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-976. Resolution: Fixed Thank you for this patch, Kit! Building servicemix-sca now succeeds with PMD/CheckStyle enabled... > servicemix-sca is out of touch with the CheckStyle and PMD guides. > --- > > Key: SM-976 > URL: https://issues.apache.org/activemq/browse/SM-976 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-sca >Reporter: Kit Plummer > Attachments: checkstyle_fixes_servicemix-sca.diff > > > The current state of the servicemix-sca codebase requires turning off the > CheckStyle plugin in SMX/parent/pom.xml and installing it into the Maven repo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 resolved SM-960.
Resolution: Fixed
Fix Version/s: 3.1.2
Modified FragmentStreamReader to get it working:
http://svn.apache.org/viewvc?view=rev&revision=549818
Just a side question: Is there any need for a second FragmentStreamReader in
servicemix-soap2, otherwise I would delete it there and reuse the
servicemix-core one...
> 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
> Fix For: 3.1.2
>
> 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 - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase service
> DEBUG - HandlerPipeline- Invoking phase dispatch
> DEBUG - HandlerPipeline- Invoking phase policy
>
[jira] Commented: (SM-970) Add support for wildcards in the element in servicemix.xml
[ https://issues.apache.org/activemq/browse/SM-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39454 ] Gert Vanthienen commented on SM-970: Isn't this already covered in ServiceMix 3.1 (cfr. "New in ServiceMix 3.1" on http://incubator.apache.org/servicemix/classloaders.html) or am I misunderstanding your question? > Add support for wildcards in the element in > servicemix.xml > > > Key: SM-970 > URL: https://issues.apache.org/activemq/browse/SM-970 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-lwcontainer >Affects Versions: 3.1 >Reporter: Michal Palicka > > Hello, > we are using service units based on servicemix-lwcontainer. > In many cases the service units depend on many dependencies (direct or > transitive), that also change during the development. > It would be very helpful, if we could specify the classpath using a wildcard > instead of a list of individual dependencies. > Current status: > > . > ./lib/lib1.jar > ./lib/lib2.jar > ... > ./lib/libn.jar > > Desired status: > > . > ./lib/*.jar > > Thank you. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-787) IllegalStateException when reading XML message
[ https://issues.apache.org/activemq/browse/SM-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39442 ] Gert Vanthienen commented on SM-787: After checking with the XFire mailing list and trying out some things, it appears that the exception only occurs if the body of the content is a StAXSource. When a DomSource enters Jsr181ExchangeProcessor's process() method, everything works fine. That explains why the error doesn't occur when setting the logging to DEBUG (conversion of body content to a re-readable XML source type). Could there be something wrong with our implementations for StaxSource, FragmentStreamReader, ...? I've already tried replacing our StaxSource with JDK 1.6 StAXSource implementation (for testing), but that doesn't help either > IllegalStateException when reading XML message > -- > > Key: SM-787 > URL: https://issues.apache.org/activemq/browse/SM-787 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-jsr181 >Affects Versions: 3.1 >Reporter: Horst Studer > > When sending a message to a JSR-181 service unit, I get an > IllegalStateException > thown by the Woodstox XML Processor (see stack trace). > It is important to note that this exception does NOT occur if the log-level > for org.apache.servicemix > is set to DEBUG. But it occurs if the log-level is INFO. This means that > writing the message to > the log seams to prevent the IllegalStateException from happening. > Here is the stack trace: > 17:09:14,806 | ERROR | pool-flow.seda.servicemix-jsr181-thread-1 | > DefaultFaultHandler | re.handler.DefaultFaultHandler 35 | Fault > occurred! > java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT > or ENTITY_REFERENCE > at > com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:708) > at > org.codehaus.xfire.util.stax.DepthXMLStreamReader.getLocalName(DepthXMLStreamReader.java:100) > at > org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:58) > at > org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:69) > at > org.apache.servicemix.jsr181.xfire.ServiceFactoryHelper$FixedJAXWSOperationBinding.readMessage(ServiceFactoryHelper.java:403) > at > org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) > at > org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:110) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441) > at > org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) > at > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593) > at > org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-965) Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
[
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-965.
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
Added the necessary expression=${...}
http://svn.apache.org/viewvc?view=rev&revision=547183
> Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
> ---
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 3.1
>Reporter: Steve Carmichael
> Fix For: 3.1.2, 3.2
>
>
> when I run the following command:
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX
> (where XXX = real values)
> to deploy to a remote server running ServiceMix standalone, I get the
> following error:
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root e
> xception is java.rmi.ConnectException: Connection refused to host: localhost;
> nested exception is:
> java.net.ConnectException: Connection refused: connect]
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85)
> at
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252)
> ... 21 more
> Caused by: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refuse
> Notice that localhost is being invoked (not the hostname I indicated in the
> -D option)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-965) Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
[ https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-965: --- Issue Type: Improvement (was: Bug) Summary: Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy (was: jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost) > Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy > --- > > Key: SM-965 > URL: https://issues.apache.org/activemq/browse/SM-965 > Project: ServiceMix > Issue Type: Improvement > Components: tooling >Affects Versions: 3.1 >Reporter: Steve Carmichael > > when I run the following command: > >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX > (where XXX = real values) > to deploy to a remote server running ServiceMix standalone, I get the > following error: > Caused by: java.io.IOException: Failed to retrieve RMIServer stub: > javax.naming.ServiceUnavailableException [Root e > xception is java.rmi.ConnectException: Connection refused to host: localhost; > nested exception is: > java.net.ConnectException: Connection refused: connect] > at > javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317) > at > javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) > > at > org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77) > > at > org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85) > at > org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252) > ... 21 more > Caused by: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refuse > Notice that localhost is being invoked (not the hostname I indicated in the > -D option) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-787) IllegalStateException when reading XML message
[ https://issues.apache.org/activemq/browse/SM-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39387 ] Gert Vanthienen commented on SM-787: I would like to look into this one. This message (or a similar one) is mentioned in two other issues (SM-960, SM-964) but I have no idea where to look. The exception is being thrown by Woodstox/XFire, but I do not find a mention of a similar bug in any of their mailing lists, so I figured it should be something in ServiceMix itself. Where should I start looking? > IllegalStateException when reading XML message > -- > > Key: SM-787 > URL: https://issues.apache.org/activemq/browse/SM-787 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-jsr181 >Affects Versions: 3.1 >Reporter: Horst Studer > > When sending a message to a JSR-181 service unit, I get an > IllegalStateException > thown by the Woodstox XML Processor (see stack trace). > It is important to note that this exception does NOT occur if the log-level > for org.apache.servicemix > is set to DEBUG. But it occurs if the log-level is INFO. This means that > writing the message to > the log seams to prevent the IllegalStateException from happening. > Here is the stack trace: > 17:09:14,806 | ERROR | pool-flow.seda.servicemix-jsr181-thread-1 | > DefaultFaultHandler | re.handler.DefaultFaultHandler 35 | Fault > occurred! > java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT > or ENTITY_REFERENCE > at > com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:708) > at > org.codehaus.xfire.util.stax.DepthXMLStreamReader.getLocalName(DepthXMLStreamReader.java:100) > at > org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:58) > at > org.codehaus.xfire.aegis.stax.ElementReader.(ElementReader.java:69) > at > org.apache.servicemix.jsr181.xfire.ServiceFactoryHelper$FixedJAXWSOperationBinding.readMessage(ServiceFactoryHelper.java:403) > at > org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) > at > org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:110) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441) > at > org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) > at > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593) > at > org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-965) jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost
[
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39367
]
Gert Vanthienen commented on SM-965:
It's not a bug apparently, but a feature that hasn't been implemented yet.
There are no expression annotations on any of the properties in
AbstractDeployableMojo.
An example:
{code}
/**
* @parameter default-value="localhost" expression="${jbi.host}"
*/
private String host;
{code}
After the change, I'm able to use this command succesfully:
{{mvn jbi:projectDeploy -Djbi.host=kiwi}}
> jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and
> uses localhost
> -
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.1
>Reporter: Steve Carmichael
>
> when I run the following command:
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX
> (where XXX = real values)
> to deploy to a remote server running ServiceMix standalone, I get the
> following error:
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root e
> xception is java.rmi.ConnectException: Connection refused to host: localhost;
> nested exception is:
> java.net.ConnectException: Connection refused: connect]
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85)
> at
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252)
> ... 21 more
> Caused by: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refuse
> Notice that localhost is being invoked (not the hostname I indicated in the
> -D option)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-964) Upgrade to XFire 1.2.6
[
https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39238
]
Gert Vanthienen edited comment on SM-964 at 6/8/07 1:37 PM:
I attempted to do this upgrade by simply changing the xfire-version to 1.2.6.
However, after the build was done the wsdl-first example no longer works
correctly. Is there anything else that I need to change?
{noformat}
The stacktrace is
java.lang.IllegalStateException: The current event is not START_ELEMENT but 7
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203)
at
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
{noformat}
was:
I attempted to do this upgrade by simply changing the xfire-version to 1.2.6.
However, after the build was done the wsdl-first example no longer works
correctly. Is there anything else that I need to change?
The stacktrace is
java.lang.IllegalStateException: The current event is not START_ELEMENT
but 7
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309)
at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203)
at
org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159)
at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
> Upgrade to XFire 1.2.6
> --
>
> Key: SM-964
> URL: https://issues.apache.org/activemq/browse/SM-964
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jsr181
>Affects Versions: 3.1
>
[jira] Commented: (SM-964) Upgrade to XFire 1.2.6
[
https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39239
]
Gert Vanthienen commented on SM-964:
I noticed that this is the same exception as is mentioned in SM-960, so I tried
to rerun that as well. This is the resulting error stack trace:
{noformat}
org.codehaus.xfire.fault.XFireFault: Could not invoke service.. Nested
exception is org.codehaus.xfire.fault.XFireFault: Could not write to outgoing
stream.
at
org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:83)
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.sendMessage(ServiceInvocationHandler.java:320)
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:86)
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:134)
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:109)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at
org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64)
at
org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38)
at
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.codehaus.xfire.XFireRuntimeException: Could not invoke service..
Nested exception is org.codehaus.xfire.fault.XFireFault: Could not write to
outgoing stream.
at
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:92)
at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
at
org.apache.servicemix.jsr181.xfire.JbiProxyFactoryBean$1.invoke(JbiProxyFactoryBean.java:73)
at $Proxy0.getInfoByCity(Unknown Source)
at
org.apache.servicemix.samples.citytime.CityTimeImpl.getCityTime(CityTimeImpl.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:59)
... 18 more
Caused by: org.codehaus.xfire.fault.XFireFault: Could not write to outgoing
stream.
at
org.codehaus.xfire.service.binding.DocumentBinding.writeMessage(DocumentBinding.java:67)
at
org.apache.servicemix.jsr181.xfire.JbiChannel.getContent(JbiChannel.java:173)
at
org.apache.servicemix.jsr181.xfire.JbiChannel.send(JbiChannel.java:122)
at
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
at org.codehaus.xfire.client.Client.invoke(Client.java:336)
at
org.apache.servicemix.jsr181.xfire.JbiProxy$JAXWSJBIClient.invoke(JbiProxy.java:232)
at
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
... 27 more
Caused by: javax.xml.stream.XMLStreamException: Trying to write a namespace
declaration when there is no open start element.
at
com.ctc.wstx.sw.BaseStreamWriter.throwOutputError(BaseStreamWriter.java:1473)
at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:128)
at
org.codehaus.xfire.util.NamespaceHelper.getUniquePrefix(NamespaceHelper.java:139)
at
org.codehaus.xfire.service.binding.DocumentBinding.writeMessage(DocumentBinding.java:65)
... 36 more
{noformat}
> Upgrade to XFire 1.2.6
> --
>
> Key: SM-964
>
[jira] Commented: (SM-964) Upgrade to XFire 1.2.6
[ https://issues.apache.org/activemq/browse/SM-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39238 ] Gert Vanthienen commented on SM-964: I attempted to do this upgrade by simply changing the xfire-version to 1.2.6. However, after the build was done the wsdl-first example no longer works correctly. Is there anything else that I need to change? The stacktrace is java.lang.IllegalStateException: The current event is not START_ELEMENT but 7 at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:124) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:337) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:309) at org.codehaus.xfire.jaxb2.JaxbType.readObject(JaxbType.java:203) at org.codehaus.xfire.jaxws.JAXWSOperationBinding.readMessage(JAXWSOperationBinding.java:159) at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) at org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) at org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113) at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:171) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) > Upgrade to XFire 1.2.6 > -- > > Key: SM-964 > URL: https://issues.apache.org/activemq/browse/SM-964 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-jsr181 >Affects Versions: 3.1 >Reporter: Gert Vanthienen > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-964) Upgrade to XFire 1.2.6
Upgrade to XFire 1.2.6 -- Key: SM-964 URL: https://issues.apache.org/activemq/browse/SM-964 Project: ServiceMix Issue Type: Improvement Components: servicemix-jsr181 Affects Versions: 3.1 Reporter: Gert Vanthienen -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-958) Dynamically determine basic authentication credentials for provider endpoint
[ https://issues.apache.org/activemq/browse/SM-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-958: --- Summary: Dynamically determine basic authentication credentials for provider endpoint (was: Dynamically determine basis authentication credentials for provider endpoint) > Dynamically determine basic authentication credentials for provider endpoint > > > Key: SM-958 > URL: https://issues.apache.org/activemq/browse/SM-958 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-http >Affects Versions: 3.1 >Reporter: Gert Vanthienen >Assignee: Gert Vanthienen >Priority: Minor > Fix For: 3.1.2 > > > It should be possible to just change the type for the username/password > properties in the BasicAuthCredentials into Expression, with a > PropertyEditor to ensure correct translation from String to > ConstantExpression on existing configuration files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-958) Dynamically determine basis authentication credentials for provider endpoint
[ https://issues.apache.org/activemq/browse/SM-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-958. Resolution: Fixed http://svn.apache.org/viewvc?view=rev&revision=542291 http://svn.apache.org/viewvc?view=rev&revision=542294 > Dynamically determine basis authentication credentials for provider endpoint > > > Key: SM-958 > URL: https://issues.apache.org/activemq/browse/SM-958 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-http >Affects Versions: 3.1 >Reporter: Gert Vanthienen >Assignee: Gert Vanthienen >Priority: Minor > Fix For: 3.1.2 > > > It should be possible to just change the type for the username/password > properties in the BasicAuthCredentials into Expression, with a > PropertyEditor to ensure correct translation from String to > ConstantExpression on existing configuration files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-958) Dynamically determine basis authentication credentials for provider endpoint
Dynamically determine basis authentication credentials for provider endpoint Key: SM-958 URL: https://issues.apache.org/activemq/browse/SM-958 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Affects Versions: 3.1 Reporter: Gert Vanthienen Assigned To: Gert Vanthienen Priority: Minor Fix For: 3.1.2 It should be possible to just change the type for the username/password properties in the BasicAuthCredentials into Expression, with a PropertyEditor to ensure correct translation from String to ConstantExpression on existing configuration files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-902) File Binding example error with JaxenStringXPathExpression
[ https://issues.apache.org/activemq/browse/SM-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-902: --- Attachment: SM-902-with-flag.patch Is this the kind of patch you're looking for? The useMessageContent="false" attribute can be used to signal that an Expression doesn't access the message content, so no conversion will be done. > File Binding example error with JaxenStringXPathExpression > > > Key: SM-902 > URL: https://issues.apache.org/activemq/browse/SM-902 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-components >Affects Versions: 3.1 > Environment: window xp, java1.5, >Reporter: Sangwoo Han >Priority: Minor > Attachments: SM-902-with-flag.patch, SM-902.patch > > > I have tried example-file binding with servicemix3.1 (latest version) > and the file generated in outbox was empty !! size zero ! > So I commented out the rename part (filename property with > JaxenStringXPathExpression) > and it generated file with original file content. It worked !! > Guillaume Nodet(gnodet) suspects a problem with the input stream which is not > converted before evaluating > the expression. > == > > > > >class="org.apache.servicemix.components.util.DefaultFileMarshaler"> > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-902) File Binding example error with JaxenStringXPathExpression
[ https://issues.apache.org/activemq/browse/SM-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39050 ] Gert Vanthienen commented on SM-902: I have run into the same issue once again, now while building an Auditor which wants to save all messages being handled by ServiceMix to the disk. From the moment I read the message content, the stream becomes unusable, so it's impossible to read it for auditing purposes and again within the service that actually needs the contents. Wouldn't it be better to change our NormalizedMessageImpl to that it automatically transforms any (not-rereadable) StreamSource being set into e.g. a StringSource to solve all these types of problems in one move? Or would that be too much of a performance overhead? > File Binding example error with JaxenStringXPathExpression > > > Key: SM-902 > URL: https://issues.apache.org/activemq/browse/SM-902 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-components >Affects Versions: 3.1 > Environment: window xp, java1.5, >Reporter: Sangwoo Han >Priority: Minor > Attachments: SM-902.patch > > > I have tried example-file binding with servicemix3.1 (latest version) > and the file generated in outbox was empty !! size zero ! > So I commented out the rename part (filename property with > JaxenStringXPathExpression) > and it generated file with original file content. It worked !! > Guillaume Nodet(gnodet) suspects a problem with the input stream which is not > converted before evaluating > the expression. > == > > > > >class="org.apache.servicemix.components.util.DefaultFileMarshaler"> > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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-http-part2.patch Additional http patch file to provide the missing AbstractProcessor file > 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-http-part2.patch, SM-932-http.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.
[jira] Created: (SM-935) Allow to specify additional JNDI properties
Allow to specify additional JNDI properties
---
Key: SM-935
URL: https://issues.apache.org/activemq/browse/SM-935
Project: ServiceMix
Issue Type: New Feature
Components: servicemix-jms
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor
In addition to using initialContext and jndiProviderUrl to configure a JMS
endpoint, it should be possible to specify additional JNDI properties (e.g
{{java.naming.security.principal}}, {{java.naming.security.credentials}})
--
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_39005
]
Gert Vanthienen commented on SM-915:
On the commons mailing list, Rory Winston suggested to upgrade to
commons-net-2.0 RC, because it contains fixes for various threading issues. It
is available at
http://people.apache.org/~rwinston/commons-net-2.0/commons-net-ftp-2.0.0-SNAPSHOT.jar
However, it requires JDK5/6 and it is not a simple replacement for the current
commons-net-1.4.x.jar (API changes).
> 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] 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-http.patch
The last patch file (*-http) contains all necessary modifications for
servicemix-http. It also contains the updated pom.xml for the binding
components.
Just a few remarks:
* I have used some J2SE 5.0 constructs (varargs, generics, ...) during the
cleanup (e.g. to reduce the amount of code per method). If you still want to
be 1.4-compliant, these have to be modified
* SslParameters contains a call to hash(String... strings). If I don't enclose
the parameters to this call in a new String[] { }, PMD (incorrectly) complains
about an unused private method
> 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-http.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.
[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-file.patch SM-932-file.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 > > > 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] Created: (SM-932) Enable PMD/CheckStyle for binding components
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 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] Created: (SM-931) PMD/CheckStyle errors for servicemix-eip
PMD/CheckStyle errors for servicemix-eip Key: SM-931 URL: https://issues.apache.org/activemq/browse/SM-931 Project: ServiceMix Issue Type: Bug Components: servicemix-eip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-931.patch Build fails with PMD/CheckStyle enabled for servicemix-eip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-931) PMD/CheckStyle errors for servicemix-eip
[ https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-931: --- Attachment: SM-931.patch On my machine, this patch fixes the build > PMD/CheckStyle errors for servicemix-eip > > > Key: SM-931 > URL: https://issues.apache.org/activemq/browse/SM-931 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-eip >Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-931.patch > > > Build fails with PMD/CheckStyle enabled for servicemix-eip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-902) File Binding example error with JaxenStringXPathExpression
[ https://issues.apache.org/activemq/browse/SM-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-902: --- Attachment: SM-902.patch I think this patch might at least solve the issue, but I admit it is a very naive solution. Main problem: the NormalizedMessage is always copied, even when only e.g.message properties are used in the expression (resulting in some overhead in that case). Any suggestions on how to avoid that? > File Binding example error with JaxenStringXPathExpression > > > Key: SM-902 > URL: https://issues.apache.org/activemq/browse/SM-902 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-components >Affects Versions: 3.1 > Environment: window xp, java1.5, >Reporter: Sangwoo Han >Priority: Minor > Attachments: SM-902.patch > > > I have tried example-file binding with servicemix3.1 (latest version) > and the file generated in outbox was empty !! size zero ! > So I commented out the rename part (filename property with > JaxenStringXPathExpression) > and it generated file with original file content. It worked !! > Guillaume Nodet(gnodet) suspects a problem with the input stream which is not > converted before evaluating > the expression. > == > > > > >class="org.apache.servicemix.components.util.DefaultFileMarshaler"> > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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:all-tabpanel
]
Gert Vanthienen updated SM-915:
---
Attachment: SM-915.patch
The patch file makes sure that the inputstream is always closed -- followed by
the required call to {{completePendingCommand}}.
> 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] Updated: (SM-898) soap2 unit tests fail with NullPointerException
[
https://issues.apache.org/activemq/browse/SM-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-898:
---
Attachment: SM-898.patch
I do not see any mention of
${basedir}\common\servicemix-soap2\src\test\java\org\apache\servicemix\soap\Person.wsdl2
being deleted in the patch file. It is not required there...
> soap2 unit tests fail with NullPointerException
> ---
>
> Key: SM-898
> URL: https://issues.apache.org/activemq/browse/SM-898
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-soap
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>Priority: Minor
> Attachments: SM-898.patch
>
>
> The mvn build fails with unit tests enabled, because some resources are not
> available at test execution time:
> - log4j-tests.properties
> - Person.wsdl2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-898) soap2 unit tests fail with NullPointerException
soap2 unit tests fail with NullPointerException --- Key: SM-898 URL: https://issues.apache.org/activemq/browse/SM-898 Project: ServiceMix Issue Type: Bug Components: servicemix-soap Affects Versions: 3.1 Reporter: Gert Vanthienen Priority: Minor The mvn build fails with unit tests enabled, because some resources are not available at test execution time: - log4j-tests.properties - Person.wsdl2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-894) Auto-create directory when file name contains subdirectories
[ https://issues.apache.org/activemq/browse/SM-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-894: --- Attachment: SM-894.patch This should do the trick... > Auto-create directory when file name contains subdirectories > > > Key: SM-894 > URL: https://issues.apache.org/activemq/browse/SM-894 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-file >Affects Versions: 3.1 >Reporter: Gert Vanthienen > Attachments: SM-894.patch > > > I'm using a servicemix-file sender component to archive messages on the local > file system. I would like to create a subdirectory for each message type > (order, dispatch advice, ...). It is possible to use / in the marshaler's > file name XML element to specify the subdirectory, but it is not being > automatically created. The autoCreateDirectory attribute currently only > refers to the sender' output directory itself, not to any subdirectories that > are specified in the file name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-894) Auto-create directory when file name contains subdirectories
[ https://issues.apache.org/activemq/browse/SM-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38896 ] Gert Vanthienen commented on SM-894: Is it OK if I simply modify servicemix-file's FileSenderEndpoint to create any subdirectories depending on the same autoCreateDirectory attribute (thus slightly changing the semantics of the existing attribute) or should I 'invent' another attribute for this? > Auto-create directory when file name contains subdirectories > > > Key: SM-894 > URL: https://issues.apache.org/activemq/browse/SM-894 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-file >Affects Versions: 3.1 >Reporter: Gert Vanthienen > > I'm using a servicemix-file sender component to archive messages on the local > file system. I would like to create a subdirectory for each message type > (order, dispatch advice, ...). It is possible to use / in the marshaler's > file name XML element to specify the subdirectory, but it is not being > automatically created. The autoCreateDirectory attribute currently only > refers to the sender' output directory itself, not to any subdirectories that > are specified in the file name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-894) Auto-create directory when file name contains subdirectories
Auto-create directory when file name contains subdirectories Key: SM-894 URL: https://issues.apache.org/activemq/browse/SM-894 Project: ServiceMix Issue Type: Improvement Components: servicemix-file Affects Versions: 3.1 Reporter: Gert Vanthienen I'm using a servicemix-file sender component to archive messages on the local file system. I would like to create a subdirectory for each message type (order, dispatch advice, ...). It is possible to use / in the marshaler's file name XML element to specify the subdirectory, but it is not being automatically created. The autoCreateDirectory attribute currently only refers to the sender' output directory itself, not to any subdirectories that are specified in the file name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-850) Error starting ServiceMix on AIX
[ https://issues.apache.org/activemq/browse/SM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38543 ] Gert Vanthienen commented on SM-850: The current script doesn't work correctly on AIX because: - the JVM on AIX was not correctly identified as an IBM JVM - the option -Xverify:none was not set for AIX, while it is required This patch file contains a fix for the startup script to solve both problems. > Error starting ServiceMix on AIX > > > Key: SM-850 > URL: https://issues.apache.org/activemq/browse/SM-850 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core >Affects Versions: 3.1 >Reporter: Gert Vanthienen > Fix For: 3.1.1 > > Attachments: SM-850.patch > > > After adding support for OS/400 to ServiceMix's startup script, the script no > longer worked correctly for AIX. See also: > http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 > (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-850) Error starting ServiceMix on AIX
[ https://issues.apache.org/activemq/browse/SM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-850: --- Attachment: SM-850.patch > Error starting ServiceMix on AIX > > > Key: SM-850 > URL: https://issues.apache.org/activemq/browse/SM-850 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core >Affects Versions: 3.1 >Reporter: Gert Vanthienen > Fix For: 3.1.1 > > Attachments: SM-850.patch > > > After adding support for OS/400 to ServiceMix's startup script, the script no > longer worked correctly for AIX. See also: > http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 > (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-850) Error starting ServiceMix on AIX
Error starting ServiceMix on AIX Key: SM-850 URL: https://issues.apache.org/activemq/browse/SM-850 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Gert Vanthienen Fix For: 3.1.1 After adding support for OS/400 to ServiceMix's startup script, the script no longer worked correctly for AIX. See also: http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
