[jira] Updated: (SM-1081) A StaticRecipientListAggregator like SplitAggregator is needed
[ https://issues.apache.org/activemq/browse/SM-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1081: Fix Version/s: 3.2 > A StaticRecipientListAggregator like SplitAggregator is needed > --- > > Key: SM-1081 > URL: https://issues.apache.org/activemq/browse/SM-1081 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-eip >Affects Versions: 3.1.1 > Environment: ServiceMix 3.1.1 >Reporter: Andrea Zoppello > Fix For: 3.2 > > Attachments: RecipientListAggregator.java, > SplitAggregator.java.patch, StaticRecipientList.java.patch > > > We need a specific aggregator to use in couple with a Static recipient List. > To do this we need to: > 1) Modify the static recipient list to propagate some information needed to > be used by RecipientListAggregator > 2) Implement the RecipientListAggregator class > 3) With a small update to SplitAggregator class RecipientListAggregator could > simply extend SplitAggregator to reuse > the aggregation logic. The problem is that the Expression properties are > private, so we need to change SplitAgggregator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Scheduling 3.2 release - recipient list aggregator
Ok Done, I've just not closed the issue, so you could approve code modification. Andrea Guillaume Nodet ha scritto: Could you please create one and attach your patch ? It's way faster to review and apply, thx! On 9/27/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: Where's the JIRA issue ? ;-) On 9/27/07, Andrea Zoppello <[EMAIL PROTECTED]> wrote: Have you seen my post about the pattern: StaticRecipientList - RecipientListAggregator ? This will be included in next spagic release. I've only introduced the same idea of the xpath splitter - split aggregator to the static recipient list. I hope this will be included in smx 3.2 Andrea Guillaume Nodet ha scritto: I'm going through the remaining JIRA assigned for 3.2. If anybody has any important issues to schedule there (or patches to apply), please yell ! I'd like to put 3.2 in release mode asap. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Created: (SM-1081) A StaticRecipientListAggregator like SplitAggregator is needed
A StaticRecipientListAggregator like SplitAggregator is needed --- Key: SM-1081 URL: https://issues.apache.org/activemq/browse/SM-1081 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Affects Versions: 3.1.1 Environment: ServiceMix 3.1.1 Reporter: Andrea Zoppello Attachments: RecipientListAggregator.java, SplitAggregator.java.patch, StaticRecipientList.java.patch We need a specific aggregator to use in couple with a Static recipient List. To do this we need to: 1) Modify the static recipient list to propagate some information needed to be used by RecipientListAggregator 2) Implement the RecipientListAggregator class 3) With a small update to SplitAggregator class RecipientListAggregator could simply extend SplitAggregator to reuse the aggregation logic. The problem is that the Expression properties are private, so we need to change SplitAgggregator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Scheduling 3.2 release - recipient list aggregator
Could you please create one and attach your patch ? It's way faster to review and apply, thx! On 9/27/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Where's the JIRA issue ? ;-) > > On 9/27/07, Andrea Zoppello <[EMAIL PROTECTED]> wrote: > > Have you seen my post about the pattern: > > > > StaticRecipientList - RecipientListAggregator ? > > > > This will be included in next spagic release. > > I've only introduced the same idea of the xpath splitter - split aggregator > > to the static recipient list. > > > > I hope this will be included in smx 3.2 > > > > > > Andrea > > > > Guillaume Nodet ha scritto: > > > I'm going through the remaining JIRA assigned for 3.2. > > > If anybody has any important issues to schedule there (or patches to > > > apply), please yell ! > > > I'd like to put 3.2 in release mode asap. > > > > > > > > > > > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Updated: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1037: Component/s: geronimo > Geronimo Plugin enhancement and bug fix > --- > > Key: SM-1037 > URL: https://issues.apache.org/activemq/browse/SM-1037 > Project: ServiceMix > Issue Type: Bug > Components: geronimo >Reporter: Kristian Koehler >Assignee: Guillaume Nodet > Fix For: 3.2 > > Attachments: geronimo-plugin.patch, geronimo-plugin.patch, > geronimo-plugin.patch-03, geronimo-plugin.patch-04 > > > Hi > i encountered some problems with the Geronimo Plugin for ServiceMix. I > updated the version in trunk to use Geronimo 2.0.1 and "fixed a deployment > bug". > With the current version it's not possible to deploy service assemblies which > require a deployment to a service unit. > For example if you deploy JBI ODE BPEL engine package via the JBI deployment > mechanism to geronimo you are not able to deploy a service unit using this > BPEL engine. The deployment ends up in "jbi out of sync" exceptions because > the service assembly must also be deployt to the service assembly! > The attached patch fixes the Deployer and some ServiceMix Service problems. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Scheduling 3.2 release - recipient list aggregator
Where's the JIRA issue ? ;-) On 9/27/07, Andrea Zoppello <[EMAIL PROTECTED]> wrote: > Have you seen my post about the pattern: > > StaticRecipientList - RecipientListAggregator ? > > This will be included in next spagic release. > I've only introduced the same idea of the xpath splitter - split aggregator > to the static recipient list. > > I hope this will be included in smx 3.2 > > > Andrea > > Guillaume Nodet ha scritto: > > I'm going through the remaining JIRA assigned for 3.2. > > If anybody has any important issues to schedule there (or patches to > > apply), please yell ! > > I'd like to put 3.2 in release mode asap. > > > > > > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Resolved: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1037. - Resolution: Fixed Fix Version/s: 3.2 Assignee: Guillaume Nodet Hi Kristian, thx a lot for this patch. and keep up the good work :-) Sendinggeronimo/deployer/pom.xml Sendinggeronimo/deployer/src/plan/geronimo-service.xml Sendinggeronimo/deployer-service/pom.xml Sending geronimo/deployer-service/src/main/java/org/apache/servicemix/geronimo/ServiceMixConfigBuilder.java Sendinggeronimo/geronimo-plugins.xml Sendinggeronimo/pom.xml Sendinggeronimo/servicemix/pom.xml Sendinggeronimo/servicemix/src/plan/geronimo-service.xml Sendinggeronimo/servicemix-service/pom.xml Sending geronimo/servicemix-service/src/main/java/org/apache/servicemix/geronimo/ServiceMixGBean.java Transmitting file data .. Committed revision 580072. > Geronimo Plugin enhancement and bug fix > --- > > Key: SM-1037 > URL: https://issues.apache.org/activemq/browse/SM-1037 > Project: ServiceMix > Issue Type: Bug >Reporter: Kristian Koehler >Assignee: Guillaume Nodet > Fix For: 3.2 > > Attachments: geronimo-plugin.patch, geronimo-plugin.patch, > geronimo-plugin.patch-03, geronimo-plugin.patch-04 > > > Hi > i encountered some problems with the Geronimo Plugin for ServiceMix. I > updated the version in trunk to use Geronimo 2.0.1 and "fixed a deployment > bug". > With the current version it's not possible to deploy service assemblies which > require a deployment to a service unit. > For example if you deploy JBI ODE BPEL engine package via the JBI deployment > mechanism to geronimo you are not able to deploy a service unit using this > BPEL engine. The deployment ends up in "jbi out of sync" exceptions because > the service assembly must also be deployt to the service assembly! > The attached patch fixes the Deployer and some ServiceMix Service problems. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-157) Create a Transformation Service Engine
[ https://issues.apache.org/activemq/browse/SM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-157. -- Resolution: Fixed Done with saxon > Create a Transformation Service Engine > -- > > Key: SM-157 > URL: https://issues.apache.org/activemq/browse/SM-157 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > > Standard JBI Service Engine. > Handle XSLT, XQuery with saxon. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-50) make a standard JBI component example
[ https://issues.apache.org/activemq/browse/SM-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-50. - Resolution: Fixed Done a long time ago > make a standard JBI component example > - > > Key: SM-50 > URL: https://issues.apache.org/activemq/browse/SM-50 > Project: ServiceMix > Issue Type: New Feature >Reporter: James Strachan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-197) Eclipse Plugin to configure ServiceMix Integrations
[ https://issues.apache.org/activemq/browse/SM-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-197. -- Resolution: Won't Fix Cimero will be donated to Eclipse STP > Eclipse Plugin to configure ServiceMix Integrations > --- > > Key: SM-197 > URL: https://issues.apache.org/activemq/browse/SM-197 > Project: ServiceMix > Issue Type: Wish >Reporter: George Gastaldi > > Develop an eclipse plugin that could allow editing of the servicemix > configuration file and visual representation of the flow. > Please add comments regarding to the scope of this plug-in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-2) component for ActiveSOAP
[ https://issues.apache.org/activemq/browse/SM-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-2. Resolution: Won't Fix > component for ActiveSOAP > > > Key: SM-2 > URL: https://issues.apache.org/activemq/browse/SM-2 > Project: ServiceMix > Issue Type: New Feature >Reporter: James Strachan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-575) servicemix-common base classes are not designed to support persistent deployments
[ https://issues.apache.org/activemq/browse/SM-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-575: --- Fix Version/s: (was: 3.2) > servicemix-common base classes are not designed to support persistent > deployments > - > > Key: SM-575 > URL: https://issues.apache.org/activemq/browse/SM-575 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-common >Affects Versions: 3.0 >Reporter: Guillaume Nodet > > The Deployer and BaseServiceUnitManager should be enhanced for that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-944) IllegalStateException between servicemix-jms and servicemix-bean
[
https://issues.apache.org/activemq/browse/SM-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated SM-944:
---
Fix Version/s: (was: 3.2)
> IllegalStateException between servicemix-jms and servicemix-bean
>
>
> Key: SM-944
> URL: https://issues.apache.org/activemq/browse/SM-944
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-bean
>Affects Versions: 3.1.1
> Environment: Linux Redhat 4
>Reporter: Noseda Anne
>
> 08:11:11,840 | ERROR | pool-flow.seda.servicemix-jms-thread-2 | BeanComponent
>| ervicemix.common.BaseLifeCycle 48 | Error processing exchange
> InOnly[
> id: ID:127.0.0.1-111e98f3e46-5:3
> status: Done
> role: consumer
> service: {http://www.etnic.be/janus}JmsIn
> endpoint: endpoint
> in: xmlns="http://www.etnic.be/janus";>c5b55899-e985-11db-abd1-9dbf85725783http://www.etnic.be/janus/OrchestrationAsync/AsyncOrchestrationhttp://www.etnic.be/simulate/clientasync0WSJanusTEST_LDU1
> xmlns:ns2="http://www.etnic.be/janus";>cfwb.enseignement.fase.poxx.vwfromns_po_id24cfwb.enseignement.fase.etabxx.vwfromns_etab_id196cfwb.enseignement.janus.test.wss xmlns="http://www.etnic.be/janus/fase";>
>
> PO
> 100
>
> FICHE
>
> ]
> java.lang.IllegalStateException: Receiving unknown consumer exchange: InOnly[
> id: ID:127.0.0.1-111e98f3e46-5:3
> status: Done
> role: consumer
> service: {http://www.etnic.be/janus}JmsIn
> endpoint: endpoint
> in: xmlns="http://www.etnic.be/janus";>c5b55899-e985-11db-abd1-9dbf85725783http://www.etnic.be/janus/OrchestrationAsync/AsyncOrchestrationhttp://www.etnic.be/simulate/clientasync0WSJanusTEST_LDU1
> xmlns:ns2="http://www.etnic.be/janus";>cfwb.enseignement.fase.poxx.vwfromns_po_id24cfwb.enseignement.fase.etabxx.vwfromns_etab_id196cfwb.enseignement.janus.test.wss xmlns="http://www.etnic.be/janus/fase";>
>
> PO
> 100
>
> FICHE
>
> ]
> at
> org.apache.servicemix.bean.BeanEndpoint.onConsumerExchange(BeanEndpoint.java:268)
> at
> org.apache.servicemix.bean.BeanEndpoint.process(BeanEndpoint.java:198)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:463)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> 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)
> 08:11:11,845 | ERROR | pool-flow.seda.servicemix-jms-thread-2 | BeanComponent
>| ervicemix.common.BaseLifeCycle 60 | Error setting exchange
> status to ERROR
> javax.jbi.messaging.MessagingException: illegal call to send / sendSync
> at
> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(MessageExchangeImpl.java:571)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:372)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:419)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:58)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
> 08:13:20,539 | WARN | pool-flow.seda.servicemix-bean-thread-5 |
> HeaderServiceImpl| r
[jira] Resolved: (SM-930) ComponentListener does not get notified on Component uninstall
[ https://issues.apache.org/activemq/browse/SM-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-930. Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this patch! Sending servicemix-core/src/main/java/org/apache/servicemix/jbi/framework/ComponentMBeanImpl.java Transmitting file data . Committed revision 580070. > ComponentListener does not get notified on Component uninstall > -- > > Key: SM-930 > URL: https://issues.apache.org/activemq/browse/SM-930 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core >Affects Versions: 3.1 > Environment: Ubuntu-64, Java 1.5_06, ServiceMix-3.1-incubating >Reporter: Corey Baswell >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 3.2 > > Attachments: patch.txt > > > The org.apache.servicemix.jbi.event.ComponentListener does not get notified > when a component in the JBI container is uninstalled: > public void componentUninstalled(ComponentEvent event); > I attached a patch for how i got it working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1054) Port JmsMarshaler from lightweight jms component to servicemix-jms component
[ https://issues.apache.org/activemq/browse/SM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1054. - Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this patch! Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/AbstractJmsProcessor.java Adding servicemix-jms/src/main/java/org/apache/servicemix/jms/DefaultJmsMarshaler.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsEndpoint.java Adding servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsMarshaler.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/multiplexing/MultiplexingProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java Adding servicemix-jms/src/test/java/org/apache/servicemix/jms/JmsMarshalerTest.java Transmitting file data Committed revision 580069. > Port JmsMarshaler from lightweight jms component to servicemix-jms component > - > > Key: SM-1054 > URL: https://issues.apache.org/activemq/browse/SM-1054 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-jms >Affects Versions: 3.1.1 >Reporter: Jeff Peterson >Assignee: Guillaume Nodet > Fix For: 3.2 > > Attachments: SM-1054.patch > > > Many legacy JMS systems have non-xml messages (e.g. ObjectMessage) floating > around on their queues and topics. The servicemix-jms component needs a way > to marshall those jms messages to normalized messages. > The lightweight jms component currently has a marshaller layer to perform > these actions. Please port it to the servicemix-jms component. > See: > http://www.nabble.com/MapMessage-and-or-ObjectMessage-tf2226788s12049.html#a6188688 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Scheduling 3.2 release - recipient list aggregator
Have you seen my post about the pattern: StaticRecipientList - RecipientListAggregator ? This will be included in next spagic release. I've only introduced the same idea of the xpath splitter - split aggregator to the static recipient list. I hope this will be included in smx 3.2 Andrea Guillaume Nodet ha scritto: I'm going through the remaining JIRA assigned for 3.2. If anybody has any important issues to schedule there (or patches to apply), please yell ! I'd like to put 3.2 in release mode asap.
[jira] Updated: (SM-1054) Port JmsMarshaler from lightweight jms component to servicemix-jms component
[ https://issues.apache.org/activemq/browse/SM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1054: Patch Info: [Patch Available] > Port JmsMarshaler from lightweight jms component to servicemix-jms component > - > > Key: SM-1054 > URL: https://issues.apache.org/activemq/browse/SM-1054 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-jms >Affects Versions: 3.1.1 >Reporter: Jeff Peterson > Fix For: 3.2 > > Attachments: SM-1054.patch > > > Many legacy JMS systems have non-xml messages (e.g. ObjectMessage) floating > around on their queues and topics. The servicemix-jms component needs a way > to marshall those jms messages to normalized messages. > The lightweight jms component currently has a marshaller layer to perform > these actions. Please port it to the servicemix-jms component. > See: > http://www.nabble.com/MapMessage-and-or-ObjectMessage-tf2226788s12049.html#a6188688 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown
[ https://issues.apache.org/activemq/browse/SM-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-998. Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this great patch! Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/AbstractJmsProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsEndpoint.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/multiplexing/MultiplexingProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java Transmitting file data Committed revision 580043. > In-Out Exchanges in a JMS queue cannot be successfully processed after a > crash/shutdown > --- > > Key: SM-998 > URL: https://issues.apache.org/activemq/browse/SM-998 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-jms >Affects Versions: 3.2 > Environment: any >Reporter: Sam Gerstein >Assignee: Guillaume Nodet > Fix For: 3.2 > > Attachments: servicemix-jms_patch.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Because a temporary queue is used for the reply-to destination and the > Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS > queue cannot be returned to their sender after a crash or shutdown of > ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-981) Transaction Exception due to ServiceMix JMS Provider
[
https://issues.apache.org/activemq/browse/SM-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-981.
Resolution: Fixed
Fix Version/s: 3.1.3
Assignee: Guillaume Nodet
Thanks a lot for this patch!
Sending
servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java
Transmitting file data .
Committed revision 580020.
Sending
servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java
Transmitting file data .
Committed revision 580023.
> Transaction Exception due to ServiceMix JMS Provider
>
>
> Key: SM-981
> URL: https://issues.apache.org/activemq/browse/SM-981
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.1
> Environment: All platforms. The bug was encountered on ServiceMix 3.1
> running in JBoss against JBossMQ.
>Reporter: Martin Landua
>Assignee: Guillaume Nodet
> Fix For: 3.1.3, 3.2
>
> Attachments: servicemix-jms.patch
>
>
> Hi all,
> under heavy load, we have encountered a problem when writing messages using
> the JMS provider in a synchronous, transactional flow.
> The problem is that in the code (lines 100 and up)
> producer.send(msg);
> exchange.setStatus(ExchangeStatus.DONE);
> channel.send(exchange);
> } finally {
> if (session != null) {
> session.close();
> }
> if (connection != null) {
> connection.close();
> }
> }
> it is possible that the DONE state would return to the originator faster than
> the session and the connection is closed in the finally section. If this
> happens, the originator (and therefore owner of the transaction) will first
> commit and after this the provider would close the connection.
> This results in a transaction exception.
> From what we can tell, it should read like this:
> producer.send(msg);
> } finally {
> if (session != null) {
> session.close();
> }
> if (connection != null) {
> connection.close();
> }
> }
> exchange.setStatus(ExchangeStatus.DONE);
> channel.send(exchange);
> due to which we guarantee that the connection is safely closed before we send
> the confirmation back to the consumer.
> All of our load tests succeeded after this change.
> Best regards
> Martin Landua
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Scheduling 3.2 release
I'm going through the remaining JIRA assigned for 3.2. If anybody has any important issues to schedule there (or patches to apply), please yell ! I'd like to put 3.2 in release mode asap. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Updated: (SM-855) Non concurrent processing of files in LW FilePoller
[ https://issues.apache.org/activemq/browse/SM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-855: --- Fix Version/s: (was: 3.2) Unscheduling this issue until a correct patch is provided > Non concurrent processing of files in LW FilePoller > --- > > Key: SM-855 > URL: https://issues.apache.org/activemq/browse/SM-855 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-components >Affects Versions: 3.1 >Reporter: Juergen Mayrbaeurl > Attachments: FilePoller.diff, FilePoller.diff > > > LW FilePoller component always processes files concurrently. Sometimes it's > very important that files get processed in a defined sequence, because the > contents is depending on previously processed contents. > I've extended the LW FilePoller class. It has a 'concurrent' property now > (default is true) and properties for sorting the incoming files (Sort by name > and last modification date, asc and desc) > Maybe this functionality should be included in the LW FTP FilePoller and > servicemix-file BC, too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1011) WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions properly
[ https://issues.apache.org/activemq/browse/SM-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1011. - Resolution: Fixed Fix Version/s: 3.1.3 Assignee: Guillaume Nodet Thx a lot for this patch ! Sending servicemix-common/src/main/java/org/apache/servicemix/common/tools/wsdl/SchemaCollection.java Sending servicemix-common/src/test/java/org/apache/servicemix/common/tools/wsdl/WSDLFlattenerTest.java Adding servicemix-common/src/test/resources/includes Adding servicemix-common/src/test/resources/includes/nested-a1.xsd Adding servicemix-common/src/test/resources/includes/nested-b1.xsd Adding servicemix-common/src/test/resources/includes/nested-b2.xsd Adding servicemix-common/src/test/resources/includes/nested-b3.xsd Adding servicemix-common/src/test/resources/includes/nested-c1.xsd Adding servicemix-common/src/test/resources/includes/service.wsdl Transmitting file data Committed revision 580017. Sending servicemix-common/src/main/java/org/apache/servicemix/common/tools/wsdl/SchemaCollection.java Sending servicemix-common/src/test/java/org/apache/servicemix/common/tools/wsdl/WSDLFlattenerTest.java Adding servicemix-common/src/test/resources/includes Adding servicemix-common/src/test/resources/includes/nested-a1.xsd Adding servicemix-common/src/test/resources/includes/nested-b1.xsd Adding servicemix-common/src/test/resources/includes/nested-b2.xsd Adding servicemix-common/src/test/resources/includes/nested-b3.xsd Adding servicemix-common/src/test/resources/includes/nested-c1.xsd Adding servicemix-common/src/test/resources/includes/service.wsdl Transmitting file data .. Committed revision 580018. > WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions > properly > -- > > Key: SM-1011 > URL: https://issues.apache.org/activemq/browse/SM-1011 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-common >Affects Versions: 3.1.1 > Environment: Windows XP >Reporter: Konrad Argasinski >Assignee: Guillaume Nodet > Fix For: 3.1.3, 3.2 > > Attachments: nested schemas.txt, nested-schemas-reproduced-sm.zip > > > WSDLFlattener fails to analyse JSR-181 SU WSDL which imports multi-level > (nested) schemas structure. > My JSR-181 SU WSDL imports A1.xsd schema. A1.xsd includes B1.xsd, B2.xsd and > B3.xsd. B1.xsd includes C1.xsd. > The schema is used by JAXB during the project build and it works ok, however > when the SU gets deployed on ServiceMix I receive following error: > NOT_FOUND_ERR: An attempt is made to reference a node in a > context where it does not exist. >
Re: integration testing in spring
Is it possible to remove the dependency on activemq 5.0 snapshot ? Unless activemq release is planned soon, it will cause problem when releasing 3.2 :-( On 9/27/07, James Strachan <[EMAIL PROTECTED]> wrote: > BTW I've added an integration test for the bridge sample... > > http://svn.apache.org/repos/asf/incubator/servicemix/trunk/samples/bridge/bridge-sa-itest/ > > which from a single spring XML boots up an ActiveMQ broker, ServiceMix > with some components and the SA and then Camel to do some integration > testing (though I've not yet completed the Camel stuff to fire > messages into the bridge then do some Mock endpoint testing to ensure > things work as expected). > > > On 25/09/2007, James Strachan <[EMAIL PROTECTED]> wrote: > > I've taken a first stab at adding an easy way of integration testing > > JBI artifacts (shared libraries, components and service assemblies) > > using a simple Spring XML notation that can be included into any JUnit > > test case... > > > > http://cwiki.apache.org/SM/integration-testing-in-spring.html > > > > This allows you to depend on artifacts using their maven groupId and > > artifactId and then the version is inferred (using the generated > > META-INF/maven/dependencies.properties via the jbi-maven-plugin). > > > > My idea was to show how we can boot up servicemix with some artifacts > > from the local repo, then use Camel to fire in messages and make > > assertions and so forth to test that the JBI artifacts actually deploy > > correctly and do what is expected etc. > > > > Feedback most appreciated if this can be improved... > > > > > > -- > > James > > --- > > http://macstrac.blogspot.com/ > > > > Open Source SOA > > http://open.iona.com > > > > > -- > James > --- > http://macstrac.blogspot.com/ > > Open Source SOA > http://open.iona.com > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Resolved: (SM-750) ClientFactory should implement java.io.Serializable
[ https://issues.apache.org/activemq/browse/SM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-750. Resolution: Fixed Assignee: Guillaume Nodet Closing this issue. Please open another one if there are still problems. > ClientFactory should implement java.io.Serializable > --- > > Key: SM-750 > URL: https://issues.apache.org/activemq/browse/SM-750 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core > Environment: All, especially when running under the JBoss Deployer >Reporter: Martin Landua >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 3.2 > > > The object ClientFactory should implement the interface java.io.Serializable. > Otherwise, the JBoss Deployer throws an error when trying to register the > object in the JBoss JNDI directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: integration testing in spring
BTW I've added an integration test for the bridge sample... http://svn.apache.org/repos/asf/incubator/servicemix/trunk/samples/bridge/bridge-sa-itest/ which from a single spring XML boots up an ActiveMQ broker, ServiceMix with some components and the SA and then Camel to do some integration testing (though I've not yet completed the Camel stuff to fire messages into the bridge then do some Mock endpoint testing to ensure things work as expected). On 25/09/2007, James Strachan <[EMAIL PROTECTED]> wrote: > I've taken a first stab at adding an easy way of integration testing > JBI artifacts (shared libraries, components and service assemblies) > using a simple Spring XML notation that can be included into any JUnit > test case... > > http://cwiki.apache.org/SM/integration-testing-in-spring.html > > This allows you to depend on artifacts using their maven groupId and > artifactId and then the version is inferred (using the generated > META-INF/maven/dependencies.properties via the jbi-maven-plugin). > > My idea was to show how we can boot up servicemix with some artifacts > from the local repo, then use Camel to fire in messages and make > assertions and so forth to test that the JBI artifacts actually deploy > correctly and do what is expected etc. > > Feedback most appreciated if this can be improved... > > > -- > James > --- > http://macstrac.blogspot.com/ > > Open Source SOA > http://open.iona.com > -- James --- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com
XMLStreamException processing request
Hi, We are getting the error below for every request. Response is coming back after having couple of errors like this. Any idea where this is coming from? We are using Jetty6.1.3 in the HTTP BC. Even with Jetty6.0.1 also we have same problem. It looks like it's a problem with Continuation. Is there any way we can disable continuation? javax.xml.stream.XMLStreamException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:469) at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.java:22 9) at org.apache.servicemix.jbi.jaxp.XMLStreamHelper.writeStartElement(XMLStreamHe lper.java:169) at org.apache.servicemix.jbi.jaxp.XMLStreamHelper.copy(XMLStreamHelper.java:59) at org.apache.servicemix.soap.marshalers.SoapWriter.writeContents(SoapWriter.ja va:198) at org.apache.servicemix.soap.marshalers.SoapWriter.writeSoapEnvelope(SoapWrite r.java:190) at org.apache.servicemix.soap.marshalers.SoapWriter.writeSimpleMessage(SoapWrit er.java:99) at org.apache.servicemix.soap.marshalers.SoapWriter.write(SoapWriter.java:82) at org.apache.servicemix.http.processors.ConsumerProcessor.processResponse(Cons umerProcessor.java:223) at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProc essor.java:204) at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:7 1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl ection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11 4) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:372) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368) at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectCha nnelConnector.java:489) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:4 42)
[jira] Commented: (SM-750) ClientFactory should implement java.io.Serializable
[ https://issues.apache.org/activemq/browse/SM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40194 ] Guillaume Nodet commented on SM-750: Did you find a solution for that ? > ClientFactory should implement java.io.Serializable > --- > > Key: SM-750 > URL: https://issues.apache.org/activemq/browse/SM-750 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core > Environment: All, especially when running under the JBoss Deployer >Reporter: Martin Landua >Priority: Minor > Fix For: 3.2 > > > The object ClientFactory should implement the interface java.io.Serializable. > Otherwise, the JBoss Deployer throws an error when trying to register the > object in the JBoss JNDI 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-848) ServiceMix 3.x with Java 1.4.x
[ https://issues.apache.org/activemq/browse/SM-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-848: --- Fix Version/s: (was: 3.2) 3.1.3 > ServiceMix 3.x with Java 1.4.x > -- > > Key: SM-848 > URL: https://issues.apache.org/activemq/browse/SM-848 > Project: ServiceMix > Issue Type: Improvement >Affects Versions: 3.1 > Environment: Java Runtime Environment 1.4.x >Reporter: Juergen Mayrbaeurl > Fix For: 3.1.3 > > > Since ServiceMix 3.1 can only be used with Java 5 or higher, rework it to > make it Java 1.4.x compatible -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-679: --- Fix Version/s: (was: 3.2) > Create a servicemix-ehcache standard JBI component > -- > > Key: SM-679 > URL: https://issues.apache.org/activemq/browse/SM-679 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-components >Affects Versions: 3.0 >Reporter: Jeff Puro >Assignee: Jeff Puro >Priority: Minor > Attachments: servicemix-ehcache.patch > > > Add a servicemix-ehcache standard JBI component. Please see the following > forum thread for more information on how this component should work. > http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-926) Add a standard JBI component for Velocity templates
[ https://issues.apache.org/activemq/browse/SM-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-926: --- Fix Version/s: (was: 3.2) > Add a standard JBI component for Velocity templates > --- > > Key: SM-926 > URL: https://issues.apache.org/activemq/browse/SM-926 > Project: ServiceMix > Issue Type: New Feature >Reporter: Jeff Puro >Assignee: Jeff Puro >Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > I think it would be useful for ServiceMix to provide a velocity template > service engine. This would serve as an alternative to using XSLT to tranform > messages and could be particularly useful when creating the content of an > email message etc. The way it would work, in conjunction with JDOM, is that > a normalized message would be sent to the component that would inject the > properties and the content of the message into the Velocity context. You can > then use Velocity's syntax for generating XML documents or any content that > has CDATA tags around it. The properties of the normalized message would be > accessed via the $properties variable, whereas the content of the message > would be accessed via either a $content or $root variable using JDOM methods. > Since it is often nice to have Velocity templates pulled from sources other > than a .vm file (for example a database), it would be useful for the > to have a pluggable resource property where the resource > could be pulled from either the filesystem, a database, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-952) ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml
[ https://issues.apache.org/activemq/browse/SM-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-952. Resolution: Fixed Assignee: Guillaume Nodet Sending common/servicemix-common/src/main/java/org/apache/servicemix/common/xbean/ClassLoaderXmlPreprocessor.java Transmitting file data . Committed revision 579963. > ClassLoaderXmlPreprocessor not able to load shared libraries from xbean.xml > --- > > Key: SM-952 > URL: https://issues.apache.org/activemq/browse/SM-952 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-common >Affects Versions: 3.2 >Reporter: Honi Jain >Assignee: Guillaume Nodet >Priority: Critical > Fix For: 3.2 > > Attachments: ClassLoaderXmlPreprocessor.java, > ClassLoaderXmlPreprocessor.java.patch > > > If we dont specify location child node but specify library child node of > parent node classpath in xbean.xml we are getting Null Pointer Exception when > we deploy our service assembly in servicemix. > getClassLoader method of ClassLoaderXmlPreprocessor parses the xbean.xml for > the tag 'classpath'. For loading shared-libraries it searches for the child > nodes with tag name 'library'. After it found all the child library nodes it > adds to the arraylist for the shared library using the child node list of > 'location'. This will give null pointer exception if no location node is > there. Even if location node is present when the code will try to look for > shared library it will give an error. > I am attaching the patch file ClassLoaderXmlPreprocessor .java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1069) JAX-WS support
[ https://issues.apache.org/activemq/browse/SM-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1069: Assignee: Freeman Fang > JAX-WS support > -- > > Key: SM-1069 > URL: https://issues.apache.org/activemq/browse/SM-1069 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Freeman Fang > Fix For: 4.0 > > > It should be easy to expose a JAX-WS annotated bean on the bus, or even > outside using http/soap ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
