[jira] Updated: (GERONIMO-3960) Make the spec jars OSGi friendly
[
https://issues.apache.org/jira/browse/GERONIMO-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-3960:
--
Attachment: GERONIMO-3960.diff
Most of the work on this issue has already been done -- all the spec jars now
have the OSGi metadata.
There's only one remaining problem with the jars when using them in an OSGi
environment: they all import the packages they export. E.g. the EL 1.0 bundle
exports javax.el;version=1.0 but it also imports javax.el;version=1.0
While this is a fine configuration for some bundles, there's no good reason for
the specs bundles to import their own packages. On top of that, the import
doesn't have an upper limit set on the version imported, which means that if
you install EL 2.2 in the same OSGi framewok instance as the EL 1.0 spec
mentioned before, it's perfectly possible that the import on the latter will
resolve to the packages exported by the former version (because 2.2 = 1.0)
Attaching a patch that removes these imports by adding the
*{{-noimport:=true}}* flag to the Export-Packages configuration
Make the spec jars OSGi friendly
Key: GERONIMO-3960
URL: https://issues.apache.org/jira/browse/GERONIMO-3960
Project: Geronimo
Issue Type: New Feature
Security Level: public(Regular issues)
Components: specs
Reporter: Guillaume Nodet
Attachments: GERONIMO-3960.diff, stax-osgi.diff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Gert Vanthienen
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being injected
is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from org.apache.felix.karaf.gshell.log.LruList
to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
This patch will give the raw type 'the benefit of the doubt' during type
conversion before invoking the setter.
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Gert Vanthienen
Attachments: GERONIMO-4727.diff
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being
injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from
org.apache.felix.karaf.gshell.log.LruList to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Gert Vanthienen
Attachments: GERONIMO-4727.diff, GERONIMO-4727.diff
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being
injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from
org.apache.felix.karaf.gshell.log.LruList to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1119. - Resolution: Fixed Fix Version/s: 3.3 3.2.1 3.1.3 Thank you, Philip, for providing the necessary test SAs to verify this fix! Adding charset=utf-8 to the content type fixes the issue: http://svn.apache.org/viewvc?view=revrevision=594063 (3.1 branch) http://svn.apache.org/viewvc?view=revrevision=594078 (3.2 branch) http://svn.apache.org/viewvc?view=revrevision=594064 (3.3 -- trunk) Encoding problem in text returned by HTTP-SU Key: SM-1119 URL: https://issues.apache.org/activemq/browse/SM-1119 Project: ServiceMix Issue Type: Bug Components: servicemix-core, servicemix-http, servicemix-jsr181 Affects Versions: 3.1, 3.1.1, 3.1.2 Environment: This issue can be reproduced on Windows XP Pro and Red Hat Linux. Reporter: Philip Webster Fix For: 3.1.3, 3.2.1, 3.3 Attachments: multimatch-search.zip, multimatch-search2.zip, SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar It looks as though there is an encoding problem at the point after the results are returned from the JSR181 service unit. The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th snapshot of 3.2 As discussed on this thread: http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html The attached service usints and service assembly can be used to reproduce the issue. Use the following input against http://localhost:8492/MultiMatchSearch/ soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:sear=http://eir.multimatch.org/search; soapenv:Header/ soapenv:Body sear:doSearchRequest query searchTriples searchTermsCharles Perrault/searchTerms searchFieldsTitle/searchFields searchOperators~/searchOperators /searchTriples queryLanguageSPANISH/queryLanguage resultLanguagesENGLISH/resultLanguages metadataSchemanonCached/metadataSchema fieldsmetadata/fields contentTypesRequested contentTypeTEXT/contentType startResults0/startResults numberOfResults1/numberOfResults /contentTypesRequested /query returnFullObjectsfalse/returnFullObjects /sear:doSearchRequest /soapenv:Body /soapenv:Envelope The result is: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:doSearchResponse xmlns:ns2=http://eir.multimatch.org/search; results textResults identifierurn://org.multimatch/search/result/1193668323010/identifier TitleMeñiquÃn Charles Perrault ; traducción de Teodoro Baró/Title sourceUrlhttp://www.google.com//sourceUrl /textResults /results /ns2:doSearchResponse /soapenv:Body /soapenv:Envelope The result should be: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:doSearchResponse xmlns:ns2=http://eir.multimatch.org/search; results textResults identifierurn://org.multimatch/search/result/1193668323010/identifier TitleMeñiquín Charles Perrault ; traducción de Teodoro Baró/Title sourceUrlhttp://www.google.com//sourceUrl /textResults /results /ns2:doSearchResponse /soapenv:Body /soapenv:Envelope -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40588 ] Gert Vanthienen commented on SM-1119: - Right you are! Although every message will be re-encoded by the SourceTransformer, I wrongfully assumed that it would always encode the response in UTF-8, while in reality this can be configured through the 'org.apache.servicemix.default.charset' system property. Thanks for reviewing the code so carefully! http://svn.apache.org/viewvc?view=revrevision=594255 (3.1 branch) http://svn.apache.org/viewvc?view=revrevision=594267 (3.2 branch) http://svn.apache.org/viewvc?view=revrevision=594259 (3.3 -- trunk) Encoding problem in text returned by HTTP-SU Key: SM-1119 URL: https://issues.apache.org/activemq/browse/SM-1119 Project: ServiceMix Issue Type: Bug Components: servicemix-core, servicemix-http, servicemix-jsr181 Affects Versions: 3.1, 3.1.1, 3.1.2 Environment: This issue can be reproduced on Windows XP Pro and Red Hat Linux. Reporter: Philip Webster Fix For: 3.1.3, 3.2.1, 3.3 Attachments: multimatch-search.zip, multimatch-search2.zip, SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar It looks as though there is an encoding problem at the point after the results are returned from the JSR181 service unit. The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th snapshot of 3.2 As discussed on this thread: http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html The attached service usints and service assembly can be used to reproduce the issue. Use the following input against http://localhost:8492/MultiMatchSearch/ soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:sear=http://eir.multimatch.org/search; soapenv:Header/ soapenv:Body sear:doSearchRequest query searchTriples searchTermsCharles Perrault/searchTerms searchFieldsTitle/searchFields searchOperators~/searchOperators /searchTriples queryLanguageSPANISH/queryLanguage resultLanguagesENGLISH/resultLanguages metadataSchemanonCached/metadataSchema fieldsmetadata/fields contentTypesRequested contentTypeTEXT/contentType startResults0/startResults numberOfResults1/numberOfResults /contentTypesRequested /query returnFullObjectsfalse/returnFullObjects /sear:doSearchRequest /soapenv:Body /soapenv:Envelope The result is: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:doSearchResponse xmlns:ns2=http://eir.multimatch.org/search; results textResults identifierurn://org.multimatch/search/result/1193668323010/identifier TitleMeñiquÃn Charles Perrault ; traducción de Teodoro Baró/Title sourceUrlhttp://www.google.com//sourceUrl /textResults /results /ns2:doSearchResponse /soapenv:Body /soapenv:Envelope The result should be: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:doSearchResponse xmlns:ns2=http://eir.multimatch.org/search; results textResults identifierurn://org.multimatch/search/result/1193668323010/identifier TitleMeñiquín Charles Perrault ; traducción de Teodoro Baró/Title sourceUrlhttp://www.google.com//sourceUrl /textResults /results /ns2:doSearchResponse /soapenv:Body /soapenv:Envelope -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1124) Message content silently dropped when conversion fails
[ https://issues.apache.org/activemq/browse/SM-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1124. - Resolution: Fixed Fix Version/s: (was: 3.2) 3.2.1 Added warning when message content conversions fails + use Camel type converter for Stringrarr;Source http://svn.apache.org/viewvc?view=revrevision=591300 Message content silently dropped when conversion fails -- Key: SM-1124 URL: https://issues.apache.org/activemq/browse/SM-1124 Project: ServiceMix Issue Type: Bug Components: servicemix-camel Reporter: Gert Vanthienen Priority: Trivial Fix For: 3.2.1 When a Camel message is sent to a JBI endpoint, the contents is converted into a Source (for message normalization). When the message content can not be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1124) Message content silently dropped when conversion fails
Message content silently dropped when conversion fails -- Key: SM-1124 URL: https://issues.apache.org/activemq/browse/SM-1124 Project: ServiceMix Issue Type: Bug Components: servicemix-camel Reporter: Gert Vanthienen Priority: Trivial Fix For: 3.2 When a Camel message is sent to a JBI endpoint, the contents is converted into a Source (for message normalization). When the message content can not be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] 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=revrevision=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
file:poller/ 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-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
Class not found (org.apache.camel.Component) while starting servicemix-camel
component
--
Key: SM-1103
URL: https://issues.apache.org/activemq/browse/SM-1103
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Affects Versions: 3.2
Reporter: Gert Vanthienen
servicemix-camel fails with new build from trunk (revision 584233)
{code}
ERROR - InstallerMBeanImpl - Class not found:
org.apache.servicemix.common.DefaultBootstrap
java.lang.NoClassDefFoundError: org/apache/camel/Component
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at
org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
at
org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
at
org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
[
https://issues.apache.org/activemq/browse/SM-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed SM-1103.
---
Resolution: Cannot Reproduce
Never mind... I guess everyone is entitled to a moment of confusion once in a
while...
Class not found (org.apache.camel.Component) while starting servicemix-camel
component
--
Key: SM-1103
URL: https://issues.apache.org/activemq/browse/SM-1103
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Affects Versions: 3.2
Reporter: Gert Vanthienen
servicemix-camel fails with new build from trunk (revision 584233)
{code}
ERROR - InstallerMBeanImpl - Class not found:
org.apache.servicemix.common.DefaultBootstrap
java.lang.NoClassDefFoundError: org/apache/camel/Component
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at
org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
at
org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
at
org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1098) Loop in StAX ElementReader while executing web service
Loop in StAX ElementReader while executing web service -- Key: SM-1098 URL: https://issues.apache.org/activemq/browse/SM-1098 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-jsr181 Affects Versions: 3.1.2 Reporter: Gert Vanthienen Attachments: Webservice-test.zip Cfr. mailing list http://www.nabble.com/Webservice-call-failes-when-log4j-level-is-set-to-DEBUG.-tf4575623s12049.html#a13096235 The user already provided us with an example of a failing SA -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40159 ] Gert Vanthienen commented on SM-1071: - Another option could be to use JCR for storing/versioning/accessing the configuration... Provisioning system --- Key: SM-1071 URL: https://issues.apache.org/activemq/browse/SM-1071 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 Maybe using OBR (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). Basically, i'm thinking about two things: * leverage OBR to install features easily (activemq, ode, cxf, etc...) * dynamic / automatic provisioning of applications For the second one, a service could pull an HTTP url from time to time to check is a new configuration for itself is available. if yes, download it and uninstall stop / uninstall unneeded bundes, install new ones, etc... The configuration would be a simple xml defining which bundles / version should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] 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=revrevision=577452 http://svn.apache.org/viewvc?view=revrevision=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] Created: (SM-1056) Add NamespaceContextImpl to servicemix-core
Add NamespaceContextImpl to servicemix-core --- Key: SM-1056 URL: https://issues.apache.org/activemq/browse/SM-1056 Project: ServiceMix Issue Type: Improvement Components: servicemix-core, servicemix-drools, servicemix-eip Affects Versions: 3.1.1 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Currently, servicemix-eip and servicemix-drools each ship with an almost identical copy of NamespaceContextImpl. It would be better to move this to servicemix-core (where the XPathExpression classes are -- which might also require a NamespaceContextImpl). In order not to break any existing xbean.xml files, we should keep the current classes in servicemix-eip and servicemix-drools (can become empty, simply inherit from the core one) to make sure that eip:namespace-context and drools:namespace-context still exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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=revrevision=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.Classcapture#863 of ?)
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] 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] Created: (SM-1042) Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class?)
Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class?)
-
Key: SM-1042
URL: https://issues.apache.org/activemq/browse/SM-1042
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Seems to be a problem that is mentioned in the adoption guide:
http://java.sun.com/javase/6/webnotes/adoption/adoptionguide.html#2.2.1
{noformat}
[INFO] Compilation failure
C:\projects\servicemix\core\servicemix-core\src\main\java\org\apache\servicemix\jbi\management\BaseStandardMBean.java:[117,8]
cannot
find symbol
symbol : constructor
StandardMBean(java.lang.Object,java.lang.Classcapture#863 of ?)
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] Created: (SM-1025) Add an example of eip:resequencer/ to the archetype's xbean.xml
Add an example of eip:resequencer/ 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 eip:resequencer/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-989) Backup File before Delete
[ https://issues.apache.org/activemq/browse/SM-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed SM-989. -- Resolution: Duplicate Fix Version/s: 3.2 Duplicate of SM-990 Backup File before Delete - Key: SM-989 URL: https://issues.apache.org/activemq/browse/SM-989 Project: ServiceMix Issue Type: New Feature Components: servicemix-file Affects Versions: 3.2 Reporter: Gordon Dickens Priority: Minor Fix For: 3.2 Provide backup directory option to copy file to before deleting. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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
beans xmlns:saxon=http://servicemix.apache.org/saxon/1.0;
xmlns:example=http://example.com/exampleService;
!-- START SNIPPET: xquery --
saxon:xquery service=example:xquery endpoint=endpoint
resource=classpath:query.xq /
!-- END SNIPPET: xquery --
!-- START SNIPPET: xquery-inline --
saxon:xquery service=example:xquery-inline endpoint=endpoint
!-- CDATA are not supported currently --
saxon:query
for $x in /bookstore/book
where $x/price 30
return $x/title
/saxon:query
saxon:outputProperties
saxon:property
key={http://saxon.sf.net/}wrap-result-sequence;yes/saxon:property
/saxon:outputProperties
/saxon:xquery
!-- END SNIPPET: xquery-inline --
!-- START SNIPPET: xquery-dynamic --
saxon:xquery service=example:xquery-dynamic endpoint=endpoint
saxon:expression
bean class=org.apache.servicemix.expression.PropertyExpression
property name=property value=xquery.source /
/bean
/saxon:expression
/saxon:xquery
!-- END SNIPPET: xquery-dynamic --
/beans
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. -- titles {#:
Unexpected token beyond end of query
[Fatal Error] :14:47: The element type titles must be terminated by the
matching end-tag /titles.
WARN - ServiceAssemblyLifeCycle - Could not parse result exception
org.xml.sax.SAXParseException: The element type titles must be terminated
by the matching end-tag /titles.
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: ?xml version=1.0 encoding=UTF-8?
jbi-task xmlns=http://java.sun.com/xml/ns/jbi/management-message;
version=1.0
jbi-task-result
frmwk-task-result
frmwk-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
/task-result-details
/frmwk-task-result-details
/frmwk-task-result
component-task-result
component-nameservicemix-saxon/component-name
component-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
task-status-msg
msg-loc-info
loc-token/
loc-messageUnable to parse result string/loc-message
/msg-loc-info
/task-status-msg
exception-info
nesting-level1/nesting-level
loc-token/
loc-messagecomponent-task-result
xmlns=http://java.sun.com/xml/ns/jbi/management-message;
component-nameservicemix-saxon/component-name
component-task-result-details
[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
beans xmlns:saxon=http://servicemix.apache.org/saxon/1.0;
xmlns:example=http://example.com/exampleService;
!-- START SNIPPET: xquery --
saxon:xquery service=example:xquery endpoint=endpoint
resource=classpath:query.xq /
!-- END SNIPPET: xquery --
!-- START SNIPPET: xquery-inline --
saxon:xquery service=example:xquery-inline endpoint=endpoint
!-- CDATA are not supported currently --
saxon:query
for $x in /bookstore/book
where $x/price 30
return $x/title
/saxon:query
saxon:outputProperties
saxon:property
key={http://saxon.sf.net/}wrap-result-sequence;yes/saxon:property
/saxon:outputProperties
/saxon:xquery
!-- END SNIPPET: xquery-inline --
!-- START SNIPPET: xquery-dynamic --
saxon:xquery service=example:xquery-dynamic endpoint=endpoint
saxon:expression
bean class=org.apache.servicemix.expression.PropertyExpression
property name=property value=xquery.source /
/bean
/saxon:expression
/saxon:xquery
!-- END SNIPPET: xquery-dynamic --
/beans
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. -- titles {#:
Unexpected token beyond end of query
[Fatal Error] :14:47: The element type titles must be terminated by the
matching end-tag /titles.
WARN - ServiceAssemblyLifeCycle - Could not parse result exception
org.xml.sax.SAXParseException: The element type titles must be terminated
by the matching end-tag /titles.
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: ?xml version=1.0 encoding=UTF-8?
jbi-task xmlns=http://java.sun.com/xml/ns/jbi/management-message;
version=1.0
jbi-task-result
frmwk-task-result
frmwk-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
/task-result-details
/frmwk-task-result-details
/frmwk-task-result
component-task-result
component-nameservicemix-saxon/component-name
component-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
task-status-msg
msg-loc-info
loc-token/
loc-messageUnable to parse result string/loc-message
/msg-loc-info
/task-status-msg
exception-info
nesting-level1/nesting-level
loc-token/
loc-messagecomponent-task-result
xmlns=http://java.sun.com/xml/ns/jbi/management-message;
component-nameservicemix-saxon/component-name
component-task-result-details
[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=revrevision=563873
http://svn.apache.org/viewvc?view=revrevision=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
beans xmlns:saxon=http://servicemix.apache.org/saxon/1.0;
xmlns:example=http://example.com/exampleService;
!-- START SNIPPET: xquery --
saxon:xquery service=example:xquery endpoint=endpoint
resource=classpath:query.xq /
!-- END SNIPPET: xquery --
!-- START SNIPPET: xquery-inline --
saxon:xquery service=example:xquery-inline endpoint=endpoint
!-- CDATA are not supported currently --
saxon:query
for $x in /bookstore/book
where $x/price 30
return $x/title
/saxon:query
saxon:outputProperties
saxon:property
key={http://saxon.sf.net/}wrap-result-sequence;yes/saxon:property
/saxon:outputProperties
/saxon:xquery
!-- END SNIPPET: xquery-inline --
!-- START SNIPPET: xquery-dynamic --
saxon:xquery service=example:xquery-dynamic endpoint=endpoint
saxon:expression
bean class=org.apache.servicemix.expression.PropertyExpression
property name=property value=xquery.source /
/bean
/saxon:expression
/saxon:xquery
!-- END SNIPPET: xquery-dynamic --
/beans
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. -- titles {#:
Unexpected token beyond end of query
[Fatal Error] :14:47: The element type titles must be terminated by the
matching end-tag /titles.
WARN - ServiceAssemblyLifeCycle - Could not parse result exception
org.xml.sax.SAXParseException: The element type titles must be terminated
by the matching end-tag /titles.
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: ?xml version=1.0 encoding=UTF-8?
jbi-task xmlns=http://java.sun.com/xml/ns/jbi/management-message;
version=1.0
jbi-task-result
frmwk-task-result
frmwk-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
/task-result-details
/frmwk-task-result-details
/frmwk-task-result
component-task-result
component-nameservicemix-saxon/component-name
component-task-result-details
task-result-details
task-idstart/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
task-status-msg
msg-loc-info
loc-token/
loc-messageUnable to parse result string/loc-message
/msg-loc-info
/task-status-msg
exception-info
nesting-level1/nesting-level
loc-token/
loc-messagecomponent-task-result
xmlns=http://java.sun.com/xml/ns/jbi/management-message;
component-nameservicemix-saxon/component-name
[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=revrevision=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-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
[ https://issues.apache.org/activemq/browse/SM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1014. - Resolution: Fixed Assignee: Gert Vanthienen Added a default value for defaultMep to SoapEndpoint http://svn.apache.org/viewvc?view=revrevision=562344 http://svn.apache.org/viewvc?view=revrevision=562351 WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null Key: SM-1014 URL: https://issues.apache.org/activemq/browse/SM-1014 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.1.1 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Priority: Minor Fix For: 3.1.2, 3.2 The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null Key: SM-1014 URL: https://issues.apache.org/activemq/browse/SM-1014 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.1.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.2, 3.2 The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39794 ] Gert Vanthienen commented on SM-1005: - On my machine, the message exchanges sent by the file binding component already contain these properties. Perhaps you're still using the 3.1 version, SM-861 fixes this in 3.1.1 for exchanges that are sent using sendSync() (such as those sent by the FilePoller) File BC doesnt set correlation Id and sender property - Key: SM-1005 URL: https://issues.apache.org/activemq/browse/SM-1005 Project: ServiceMix Issue Type: Bug Components: servicemix-file Affects Versions: 3.1, 3.1.1 Reporter: Gianfranco Boccalon The File binding component doesn't set the properties correlation id and sender. We fixed the problem changing the method processFile in class org.apache.servicemix.file.FilePollerEndpoint, adding these rows before sending the message (sendSync): exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); exchange.setProperty(JbiConstants.CORRELATION_ID, exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39768 ] Gert Vanthienen commented on SM-1005: - Gianfranco, I haven't tested the 3.1 release, but at least the 3.1.1 release already does this correctly. Can you describe the problem you were having with this? Gert File BC doesnt set correlation Id and sender property - Key: SM-1005 URL: https://issues.apache.org/activemq/browse/SM-1005 Project: ServiceMix Issue Type: Bug Components: servicemix-file Affects Versions: 3.1, 3.1.1 Reporter: Gianfranco Boccalon The File binding component doesn't set the properties correlation id and sender. We fixed the problem changing the method processFile in class org.apache.servicemix.file.FilePollerEndpoint, adding these rows before sending the message (sendSync): exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); exchange.setProperty(JbiConstants.CORRELATION_ID, exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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=revrevision=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_39702 ] Gert Vanthienen commented on SM-932: Fixed for servicemix-file: http://svn.apache.org/viewvc?view=revrevision=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-664) org.apache.servicemix.http.HttpAddressingTest (Hangs)
[ https://issues.apache.org/activemq/browse/SM-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-664. Resolution: Cannot Reproduce Because I was unable to reproduce this while going through the binding components for issue SM-623, I removed the exclusion from the test suite. We can always reopen the issue if someone can reproduce it... http://svn.apache.org/viewvc?view=revrevision=557757 org.apache.servicemix.http.HttpAddressingTest (Hangs) - Key: SM-664 URL: https://issues.apache.org/activemq/browse/SM-664 Project: ServiceMix Issue Type: Sub-task Components: servicemix-http Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-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.InvalidProjectModelException: Parse error reading POM. Reason: end tag name /exclusion must match start tag
[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 file:sender/. -- 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-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] 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
jms:endpoint/. 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-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] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39657
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
Was this a checkout from trunk? I cannot reproduce the CheckStyle errors with
my latest checkout here. Could you try to do an 'svn up' and retry it?
Gert
ServiceMix :: Maven2 JBI Plugin checkstyle issues
--
Key: SM-1000
URL: https://issues.apache.org/activemq/browse/SM-1000
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.2
Environment: Windows
Reporter: Rabi
[INFO] Building ServiceMix :: Maven2 JBI Plugin
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] Ignoring available plugin update: 2.3 as it requires Maven version
2.0.5
[INFO] [checkstyle:checkstyle {execution: validate}]
[INFO] Starting audit...
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
7 p
arameters.
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
def
modifier at indentation level 2 not at correct indentation, 4
E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
th
an 7 parameters.
Audit done.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: There are 4 checkstyle errors.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
[INFO] Final Memory: 13M/24M
[INFO]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-623) Unit test that fails when building using maven2.
[ https://issues.apache.org/activemq/browse/SM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39662 ] Gert Vanthienen commented on SM-623: It appears the servicemix-eip tests were failing when no additional memory was reserved for the unit tests (currently: -Xmx512m). With Adrian's centralized surefire configuration in place, all these tests now work fine. I have removed the exclusion/s from the pom.xml (cfr. http://svn.apache.org/viewvc?view=revrevision=555652) Unit test that fails when building using maven2. Key: SM-623 URL: https://issues.apache.org/activemq/browse/SM-623 Project: ServiceMix Issue Type: Test Reporter: Fritz Oconer Check the sub tasks. These are unit tests that fails when building using maven 2 and jdk1.5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-652) org.apache.servicemix.eip.StaticRoutingSlipTxTest
[ https://issues.apache.org/activemq/browse/SM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-652. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.StaticRoutingSlipTxTest - Key: SM-652 URL: https://issues.apache.org/activemq/browse/SM-652 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-653. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.WireTapJmsFlowTest Key: SM-653 URL: https://issues.apache.org/activemq/browse/SM-653 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-654: --- Fix Version/s: 3.2 org.apache.servicemix.eip.PipelineTxTest Key: SM-654 URL: https://issues.apache.org/activemq/browse/SM-654 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-654. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.PipelineTxTest Key: SM-654 URL: https://issues.apache.org/activemq/browse/SM-654 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-655) org.apache.servicemix.eip.SplitAggregatorTxTest
[ https://issues.apache.org/activemq/browse/SM-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-655. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.SplitAggregatorTxTest --- Key: SM-655 URL: https://issues.apache.org/activemq/browse/SM-655 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-656) org.apache.servicemix.eip.StaticRecipientListTxTest
[ https://issues.apache.org/activemq/browse/SM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-656. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.StaticRecipientListTxTest --- Key: SM-656 URL: https://issues.apache.org/activemq/browse/SM-656 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-657) org.apache.servicemix.eip.MessageFilterTxTest
[ https://issues.apache.org/activemq/browse/SM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-657. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.MessageFilterTxTest - Key: SM-657 URL: https://issues.apache.org/activemq/browse/SM-657 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-658. Resolution: Fixed Cfr. explanation on SM-623 org.apache.servicemix.eip.WireTapTxTest --- Key: SM-658 URL: https://issues.apache.org/activemq/browse/SM-658 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-658: --- Fix Version/s: 3.2 org.apache.servicemix.eip.WireTapTxTest --- Key: SM-658 URL: https://issues.apache.org/activemq/browse/SM-658 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-659) org.apache.servicemix.eip.XPathSplitterTxTest
[ https://issues.apache.org/activemq/browse/SM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-659. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.XPathSplitterTxTest - Key: SM-659 URL: https://issues.apache.org/activemq/browse/SM-659 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-661) org.apache.servicemix.eip.support.NamespaceContextImplTest
[ https://issues.apache.org/activemq/browse/SM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-661. Resolution: Fixed Fix Version/s: 3.2 org.apache.servicemix.eip.support.NamespaceContextImplTest -- Key: SM-661 URL: https://issues.apache.org/activemq/browse/SM-661 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-660) org.apache.servicemix.eip.DeploymentTest
[ https://issues.apache.org/activemq/browse/SM-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-660. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.DeploymentTest Key: SM-660 URL: https://issues.apache.org/activemq/browse/SM-660 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-662) org.apache.servicemix.eip.SpringConfigurationTest
[ https://issues.apache.org/activemq/browse/SM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-662. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.SpringConfigurationTest - Key: SM-662 URL: https://issues.apache.org/activemq/browse/SM-662 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-663) org.apache.servicemix.eip.ContentBasedRouterTxTest
[ https://issues.apache.org/activemq/browse/SM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-663. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 org.apache.servicemix.eip.ContentBasedRouterTxTest -- Key: SM-663 URL: https://issues.apache.org/activemq/browse/SM-663 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-653: --- Fix Version/s: 3.2 org.apache.servicemix.eip.WireTapJmsFlowTest Key: SM-653 URL: https://issues.apache.org/activemq/browse/SM-653 Project: ServiceMix Issue Type: Sub-task Components: servicemix-eip Affects Versions: incubation Reporter: Fritz Oconer Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-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=revrevision=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.init(ClassPathXmlApplicationContext.java:161) at org.apache.xbean.spring.context.ClassPathXmlApplicationContext.init(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] Commented: (SM-997) Basic example fails to build: InvalidProjectModelException
[
https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39643
]
Gert Vanthienen commented on SM-997:
The file at
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
doesn't match the pom.xml that is in SVN for tag {{servicemix-3.1.1}}, so I
guess something went wrong with the publishing. Does anyone know how to
publish a correct file?
Basic example fails to build: InvalidProjectModelException
--
Key: SM-997
URL: https://issues.apache.org/activemq/browse/SM-997
Project: ServiceMix
Issue Type: Bug
Components: servicemix-assembly
Affects Versions: 3.1.1
Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12,
Maven 2.0.6
Reporter: Evan Deaubl
When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on
the project in examples/basic, I receive the following error. I have
completely removed my Maven repository and had it redownload everything from
scratch, and still received this error. I manually checked the file it had
downloaded, and the XML file was indeed invalid, and downloading the file
directly from the source
(http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom)
using Firefox yields an XML Parsing Error.
[INFO] Scanning for projects...
Downloading:
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom
2K downloaded
Downloading:
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
69K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'507906935d130cfa9b44696270f62e006367533d'; remote =
'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING
Downloading:
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
69K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'507906935d130cfa9b44696270f62e006367533d'; remote =
'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.servicemix:samples:pom:null
Reason: Cannot find parent: org.apache.servicemix:servicemix for project:
org.apache.servicemix:samples:pom:null
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.apache.servicemix:servicemix for project:
org.apache.servicemix:samples:pom:null
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
parent: org.apache.servicemix:servicemix for project:
org.apache.servicemix:samples:pom:null
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(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
[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=revrevision=552098
http://svn.apache.org/viewvc?view=revrevision=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] Created: (SM-988) WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit archetype)
WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit
archetype)
--
Key: SM-988
URL: https://issues.apache.org/activemq/browse/SM-988
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor
If you build a SU using the servicemix-jsr181-annotated-service-unit, it
generates a pom.xml file which calls upon XFire's wsdlgen to generate a WSDL
file. However, this WSDL generation fails with this exception:
{noformat}
Embedded error: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.codehaus.xfire.spring.ServiceBean' defined in file
[C:\opt\project\jsr181-sample\wsdl-generate-sample\wsdlgen-jsr181-su\src\main\resources\services.xml]:
Error setting property values; nested
exception is org.springframework.beans.PropertyAccessExceptionsException:
PropertyAccessExceptionsException (1 errors); nested propertyAccessExceptions
are: [org.springframework.beans.TypeMismatchException: Failed to convert
property value of type [java.lang.String] to required type [java.lang.Class
] for property 'serviceClass'; nested exception is
java.lang.IllegalArgumentException: Class not found: com.sample.ExampleService]
{noformat}
Seems like the generator can't find the class, but yet the configuration for
the Ant task looks correct...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39544 ] Gert Vanthienen commented on SM-939: Applied and tested the second patch: everything compiles and tests run without failures. Committed as http://svn.apache.org/viewvc?view=revrevision=551139 Thanks to Freeman Fang... CXF based Service Engine and Bnding Component - Key: SM-939 URL: https://issues.apache.org/activemq/browse/SM-939 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Priority: Critical Fix For: 3.2 Attachments: patch.txt, patch0627.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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
*{{profileorg.codehaus.xfire.jaxws.gen.JAXWSProfile/profile}}* 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] 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=revrevision=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=revrevision=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- ?xml version=1.0
encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlso
ap.org/soap/envelope/ xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:Bo
dyLocalTimeByZipCodeResponse
xmlns=http://ripedev.com/xsd/ZipCodeResults.xsd;LocalTimeByZipCodeResult5/30/2007
8:51:44 PM/L
ocalTimeByZipCodeResult/LocalTimeByZipCodeResponse/soap:Body/soap:Envelope
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
[jira] Commented: (SM-970) Add support for wildcards in the classpathlocation 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 classpathlocation 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: classpath location./location location./lib/lib1.jar/location location./lib/lib2.jar/location ... location./lib/libn.jar/location /classpath Desired status: classpath location./location location./lib/*.jar/location /classpath 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.init(ElementReader.java:58) at org.codehaus.xfire.aegis.stax.ElementReader.init(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-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.init(ElementReader.java:58) at org.codehaus.xfire.aegis.stax.ElementReader.init(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] 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] 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=revrevision=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] 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] 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] 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] 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] 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] Updated: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
[
https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-960:
---
Attachment: citytime-sa-1.0-SNAPSHOT.jar
This is a SA that shows the problem when deploying it. Could this be bug
within XFire, StAX, ...?
JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT,
END_ELEMENT or ENTITY_REFERENCE )
Key: SM-960
URL: https://issues.apache.org/activemq/browse/SM-960
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jsr181
Reporter: Sangwoo Han
Priority: Minor
Attachments: citytime-sa-1.0-SNAPSHOT.jar
The jsr181 orchestration sample doesn't work.
In the sample of jsr181 orchestration's CityTimeImpl.java class file
[...]
public GetCityTimeResponse getCityTime(GetCityTimeRequest
GetCityTimeRequest) {
GetInfoByCity GetInfoByCity = new GetInfoByCity();
GetInfoByCity.setUSCity(GetCityTimeRequest.getCity());
GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity);
Element e = (Element)
r.getGetInfoByCityResult().getContent().get(0);
e = (Element) e.getElementsByTagName(Table).item(0);
e = (Element) e.getElementsByTagName(ZIP).item(0);
String ZipCode = e.getTextContent();
//String lt = localTime.localTimeByZipCode(ZipCode); // at this
part it errored
GetCityTimeResponse rep = new GetCityTimeResponse();
rep.getString().add(23:23);
//rep.setTime(lt); // wsgen didn't generate setTime function
return rep;
}
[...]
and the error output is below:
[...]
DEBUG - header - Content-Length: 426[\r][\n]
DEBUG - content- ?xml version=1.0
encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlso
ap.org/soap/envelope/ xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:Bo
dyLocalTimeByZipCodeResponse
xmlns=http://ripedev.com/xsd/ZipCodeResults.xsd;LocalTimeByZipCodeResult5/30/2007
8:51:44 PM/L
ocalTimeByZipCodeResult/LocalTimeByZipCodeResponse/soap:Body/soap:Envelope
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
DEBUG - HandlerPipeline- Invoking phase user
DEBUG - HandlerPipeline- Invoking handler
[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] 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.
==
sm:component
bean class=org.apache.servicemix.components.file.FileWriter
property name=directory value=D:/outbox /
property name=marshaler
bean
class=org.apache.servicemix.components.util.DefaultFileMarshaler
!-- property name=fileName
bean
class=org.apache.servicemix.expression.JaxenStringXPathExpression
constructor-arg
value=concat('sample_', /sample/@id, '.xml') /
/bean
/property
--
/bean
/property
/bean
/sm:component
--
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] 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] 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-jms.patch SM-932-jms.patch fixes PDM/CheckStyle errors for servicemix-jms Enable PMD/CheckStyle for binding components Key: SM-932 URL: https://issues.apache.org/activemq/browse/SM-932 Project: ServiceMix Issue Type: Task Components: servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-truezip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-xmpp.patch SM-932-truezip.patch Patches for servicemix-truezip and servicemix-xmpp Enable PMD/CheckStyle for binding components Key: SM-932 URL: https://issues.apache.org/activemq/browse/SM-932 Project: ServiceMix Issue Type: Task Components: servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-truezip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch, SM-932-truezip.patch, SM-932-xmpp.patch PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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.
==
sm:component
bean class=org.apache.servicemix.components.file.FileWriter
property name=directory value=D:/outbox /
property name=marshaler
bean
class=org.apache.servicemix.components.util.DefaultFileMarshaler
!-- property name=fileName
bean
class=org.apache.servicemix.expression.JaxenStringXPathExpression
constructor-arg
value=concat('sample_', /sample/@id, '.xml') /
/bean
/property
--
/bean
/property
/bean
/sm:component
--
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] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-ftp.patch SM-932-ftp.patch fixes PDM/CheckStyle errors for servicemix-ftp Enable PMD/CheckStyle for binding components Key: SM-932 URL: https://issues.apache.org/activemq/browse/SM-932 Project: ServiceMix Issue Type: Task Components: servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-truezip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-932-file.patch, SM-932-ftp.patch PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38955
]
Gert Vanthienen commented on SM-915:
... but the original problem still isn't solved.
We get an additional stacktrace when ServiceMix is stopping and the problem
only appears to exist when the FTP server is IIS.
{code}
java.io.IOException: Fatal thread interruption during read.
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:344)
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:466)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:264)
at org.apache.commons.net.ftp.FTP.getReply(FTP.java:605)
at
org.apache.commons.net.ftp.FTPClient.completePendingCommand(FTPClient.java:1253)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2400)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:210)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:202)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:77)
at
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
{code}
I've asked the commons mailing list for help on this one...
FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
Key: SM-915
URL: https://issues.apache.org/activemq/browse/SM-915
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1
Reporter: Gert Vanthienen
Attachments: SM-915.patch
FTP poller threads stop working with the stack trace below, causing the FTP
client pool to run out of connections
{code}
Name: pool-component.servicemix-ftp-thread-2
State: RUNNABLE
Total blocked: 78,430 Total waited: 4,771
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
java.lang.Thread.run(Thread.java:595)
{code}
See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] 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] Created: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
Key: SM-915
URL: https://issues.apache.org/activemq/browse/SM-915
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1
Reporter: Gert Vanthienen
FTP poller threads stop working with the stack trace below, causing the FTP
client pool to run out of connections
{code}
Name: pool-component.servicemix-ftp-thread-2
State: RUNNABLE
Total blocked: 78,430 Total waited: 4,771
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
java.lang.Thread.run(Thread.java:595)
{code}
See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38944
]
Gert Vanthienen commented on SM-915:
Some additional observations - the problem only appears when:
* when a lot of files become available on the FTP server together
* some of them are being downloaded before they are complete, i.e. incomplete
XML messages are being read and processing fails for these messages
In the FTP poller code, we find
{code}
InputStream in = ftp.retrieveFileStream(file);
InOnly exchange = getExchangeFactory().createInOnlyExchange();
configureExchangeTarget(exchange);
NormalizedMessage message = exchange.createMessage();
exchange.setInMessage(message);
marshaler.readMessage(exchange, message, in, file);
sendSync(exchange);
in.close();
ftp.completePendingCommand();
{code}
My question: Is it possible that {{sendSync(exchange)}} throws an Exception
when an incomplete XML message is retrieved from the server? If it does, the
inputstream is never closed and {{completePendingCommand()}} is never called,
which might explain the problems
FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
Key: SM-915
URL: https://issues.apache.org/activemq/browse/SM-915
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1
Reporter: Gert Vanthienen
FTP poller threads stop working with the stack trace below, causing the FTP
client pool to run out of connections
{code}
Name: pool-component.servicemix-ftp-thread-2
State: RUNNABLE
Total blocked: 78,430 Total waited: 4,771
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
java.lang.Thread.run(Thread.java:595)
{code}
See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-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] Created: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
org.apache.servicemix.file.SpringComponentTest fails with
java.lang.IllegalStateException
-
Key: SM-899
URL: https://issues.apache.org/activemq/browse/SM-899
Project: ServiceMix
Issue Type: Sub-task
Components: servicemix-file
Affects Versions: 3.1
Reporter: Gert Vanthienen
This is the stack trace:
{noformat}
Caused by: javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
Caused by: java.lang.IllegalStateException: An endpoint is already registered
for key: {urn:test}service:endpoint
at org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
at
org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
at
org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
[
https://issues.apache.org/activemq/browse/SM-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38916
]
Gert Vanthienen commented on SM-899:
As far as I understand the code:
DefaultComponent's doInit() method first registers all endpoint, thereby lazily
creating the corresponding service unit. After all endpoint have been
registered, the serviceUnit is no longer *{{null}}* and the doInit() method
will call Registry's registerServiceUnit() which will attempt to register all
the endpoints again, resulting in the stacktrace shown above.
The simple solution would be to add a test to DefaultComponent's doInit()
method, only registering the service unit if it hasn't been registered before.
As a more general solution, the same test could also be added to Registry's
registerServiceUnit(). Does anyone see a problem with the latter approach?
org.apache.servicemix.file.SpringComponentTest fails with
java.lang.IllegalStateException
-
Key: SM-899
URL: https://issues.apache.org/activemq/browse/SM-899
Project: ServiceMix
Issue Type: Sub-task
Components: servicemix-file
Affects Versions: 3.1
Reporter: Gert Vanthienen
This is the stack trace:
{noformat}
Caused by: javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
Caused by: java.lang.IllegalStateException: An endpoint is already registered
for key: {urn:test}service:endpoint
at
org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
at
org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
at
org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-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-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] 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] Created: (SM-889) Add possibility to rename files after FTP upload
Add possibility to rename files after FTP upload Key: SM-889 URL: https://issues.apache.org/activemq/browse/SM-889 Project: ServiceMix Issue Type: Improvement Components: servicemix-ftp Affects Versions: 3.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.1, 3.2 Add the possibility to upload files to the FTP server using another suffix (e.g. .part) and rename the file after the upload is completed. This way, it is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-889) Add possibility to rename files after FTP upload
[ https://issues.apache.org/activemq/browse/SM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-889: --- Attachment: SM-889.patch This patch allows users to specify an attribute uploadSuffix=... on the ftp:sender / endpoint. This suffix will be appended to the file name during upload. Upon completion, the file will be renamed to the correct name. This attribute only works if a name has been specified for upload, otherwise it is ignored. The patch also tries to solve a problem I have encountered with IIS/FTP. If no data was actually transferred to the server (e.g. because of an already existing file name), the call to client.completePendingCommand() sometimes appeared to take a very long time (waiting for some kind of time-out). With this patch, this call will only be issued if an OutputStream has actually been acquired. Add possibility to rename files after FTP upload Key: SM-889 URL: https://issues.apache.org/activemq/browse/SM-889 Project: ServiceMix Issue Type: Improvement Components: servicemix-ftp Affects Versions: 3.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.1, 3.2 Attachments: SM-889.patch Add the possibility to upload files to the FTP server using another suffix (e.g. .part) and rename the file after the upload is completed. This way, it is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] 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] 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] Created: (GERONIMODEVTOOLS-109) Eclipse plug-in doesn't show errors on deployment
Eclipse plug-in doesn't show errors on deployment - Key: GERONIMODEVTOOLS-109 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-109 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.1.0 Reporter: Gert Vanthienen Priority: Minor As discussed in the thread of http://mail-archives.apache.org/mod_mbox/geronimo-user/200609.mbox/browser, errors that occur on deployment of an application are not available in the Eclipse UI. You can get to them in a log in workspace/.metadata, but a more user friendly way would be to show this information in the error dialog itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
