March 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-682) include switchyard console in release distribution

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-682: -------------------------------------- Summary: include switchyard console in release distribution Key: SWITCHYARD-682 URL: https://issues.jboss.org/browse/SWITCHYARD-682 Project: SwitchYard Issue Type: Enhancement Components: distribution Reporter: Rob Cernich Assignee: Rob Cernich Priority: Minor Fix For: 0.4 Move the console back into the distribution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-681) Back out synchronization fix for Weld deployments

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-681: --------------------------------------- Summary: Back out synchronization fix for Weld deployments Key: SWITCHYARD-681 URL: https://issues.jboss.org/browse/SWITCHYARD-681 Project: SwitchYard Issue Type: Task Components: distribution Affects Versions: 0.4 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.5 Real fix is WELD-1067. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-680) track artifact dependencies into .war deployments

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-680: ------------------------------------- Summary: track artifact dependencies into .war deployments Key: SWITCHYARD-680 URL: https://issues.jboss.org/browse/SWITCHYARD-680 Project: SwitchYard Issue Type: Enhancement Components: admin, deployment Reporter: Keith Babo If i deploy a war with a switchyard.xml containing an artifact definition, the app does not come up in a "uses-artifact" query. Figure out why this is and fix it. I noticed that the war is also not listed in the output of list-applications, so my guess is that is where things are falling down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-679) Operation xxx is not included in interface for service yyy

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-679: ------------------------------------- Summary: Operation xxx is not included in interface for service yyy Key: SWITCHYARD-679 URL: https://issues.jboss.org/browse/SWITCHYARD-679 Project: SwitchYard Issue Type: Bug Environment: as7-0.4 snapshot Reporter: Gary Brown Getting the following exception when a BPEL process is invoking an external web service. However when stepping into org.switchyard.internal.ServiceReferenceImpl.createExchange(opName,exchangeHandler), it passes the first check (i.e. operation exists in the interface), but throws exception inside the DomainImpl.createExchange as the service interface only has a single "process" method, which appears to be a default operation. ..... at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_18] at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_18] Caused by: org.switchyard.exception.SwitchYardException: Operation getCustomer is not included in interface for service: {urn:bpel:gb.bpel.gsm:1.0}CustomerServiceService at org.switchyard.internal.DomainImpl.createExchange(DomainImpl.java:221) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.ServiceReferenceImpl.createExchange(ServiceReferenceImpl.java:107) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.bpel.riftsaw.RiftsawServiceLocator$ServiceProxy.invoke(RiftsawServiceLocator.java:276) [switchyard-component-bpel-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.riftsaw.engine.internal.MessageExchangeContextImpl.invokePartnerUnreliable(MessageExchangeContextImpl.java:78) [engine-3.0.0-SNAPSHOT.jar:] ... 55 more It may be a configuration issue in the switchyard.xml descriptor? But can't see anything obvious. Will attach the user's example BPEL process and separate Web Service to reproduce the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-678) Updated BPEL component to 3.0.0-M2 release.

by Jeff Yu (JIRA)

Jeff Yu created SWITCHYARD-678: ---------------------------------- Summary: Updated BPEL component to 3.0.0-M2 release. Key: SWITCHYARD-678 URL: https://issues.jboss.org/browse/SWITCHYARD-678 Project: SwitchYard Issue Type: Task Components: component-bpel Affects Versions: 0.3 Reporter: Jeff Yu Fix For: 0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-677) Deploy BPEL component console into SwitchYard.

by Jeff Yu (JIRA)

Jeff Yu created SWITCHYARD-677: ---------------------------------- Summary: Deploy BPEL component console into SwitchYard. Key: SWITCHYARD-677 URL: https://issues.jboss.org/browse/SWITCHYARD-677 Project: SwitchYard Issue Type: Task Components: component-bpel Affects Versions: 0.3 Reporter: Jeff Yu Fix For: 0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-676) Upgrade OpenShift application to 0.4.0.OS1

by Magesh Bojan (JIRA)

Magesh Bojan created SWITCHYARD-676: --------------------------------------- Summary: Upgrade OpenShift application to 0.4.0.OS1 Key: SWITCHYARD-676 URL: https://issues.jboss.org/browse/SWITCHYARD-676 Project: SwitchYard Issue Type: Task Components: openshift Affects Versions: 0.3 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-675) Service monitoring is missing reference stats

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-675: ------------------------------------- Summary: Service monitoring is missing reference stats Key: SWITCHYARD-675 URL: https://issues.jboss.org/browse/SWITCHYARD-675 Project: SwitchYard Issue Type: Bug Components: admin, core Affects Versions: 0.4 Reporter: Keith Babo Assignee: Keith Babo Fix For: 0.4 We need to include metrics on service references when displaying metrics on a service. Also, it looks like the timing is off in ExchangeImpl.java - InOut exchanges are using an incorrect start time to calculate duration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-674) Recursive handler activity when invoking a web service from a BPEL process using the wrong URL

by Gary Brown (JIRA)

Gary Brown created SWITCHYARD-674: ------------------------------------- Summary: Recursive handler activity when invoking a web service from a BPEL process using the wrong URL Key: SWITCHYARD-674 URL: https://issues.jboss.org/browse/SWITCHYARD-674 Project: SwitchYard Issue Type: Bug Reporter: Gary Brown Attachments: loan-request.xml, switchyard-quickstart-bpel-service-loan-approval-WRONG-URL.jar, switchyard-quickstart-bpel-service-risk-assessment.jar Using the latest 0.4-SNAPSHOT, I deployed two separate BPEL apps, one doing an external invoke of the other. When the URL to the external web service (i.e. BPEL process) is valid, there is no problem. However when the URL is deliberately set to an incorrect location (valid URL, just no web service at the endpoint), there is recursive behaviour establishing the handler chain. This eventually results in no more file descriptors: 13:36:37,577 ERROR [org.switchyard.internal.DefaultHandlerChain] (pool-10-thread-318) org.switchyard.HandlerException was thrown by handler(provider): Unexpected exception handling SOAP Message --- Caused by javax.xml.soap.SOAPException: Cannot process SOAP request --- Caused by javax.xml.ws.WebServiceException: Could not send Message. --- Caused by java.net.SocketException: SocketException invoking http://127.0.0.1:18001/riskAssessorXXX: Too many open files --- Caused by java.net.SocketException: Too many open files 13:36:37,579 DEBUG [org.switchyard.internal.DefaultHandlerChain] (pool-10-thread-318) : org.switchyard.HandlerException: Unexpected exception handling SOAP Message at org.switchyard.component.soap.OutboundHandler.handleMessage(OutboundHandler.java:153) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.DefaultHandlerChain.handleMessage(DefaultHandlerChain.java:148) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.DefaultHandlerChain.handle(DefaultHandlerChain.java:121) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.LocalDispatcher.dispatch(LocalExchangeBus.java:72) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.ExchangeImpl.sendInternal(ExchangeImpl.java:255) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.internal.ExchangeImpl.send(ExchangeImpl.java:178) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.InboundHandler.invoke(InboundHandler.java:218) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:69) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:34) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT] at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source) [:1.6.0_18] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-673) Consolidate HornetQ and ClientUtil classes used in quickstarts

by Keith Babo (JIRA)

Keith Babo created SWITCHYARD-673: ------------------------------------- Summary: Consolidate HornetQ and ClientUtil classes used in quickstarts Key: SWITCHYARD-673 URL: https://issues.jboss.org/browse/SWITCHYARD-673 Project: SwitchYard Issue Type: Task Components: quickstarts, test Affects Versions: 0.4 Reporter: Keith Babo Assignee: Tomohisa igarashi Fix For: 0.4 These classes are starting to pop up over and over again in JMS-related quickstarts. Instead of just copying them over and over again, we should create one version that can be shared amongst all quickstarts. There are two use cases here: 1) Test cases which need to use JMS and/or a JMS server. These tests should be using the HornetQMixIn alone. Any additional dependencies on the ClientUtil classes need to be rolled into HornetQMixIn. 2) Most of these quickstarts also offer the option to use "mvn exec:java [options]" to test the application independently with the quickstart deployed to AS7. This case also relies on the ClientUtil classes. We need to change this to use HornetQMixIn (e.g. static methods on the class) or something else packaged in the switchyard-test module. This module should be included in the test classpath and if the exec plugin is configured to include test dependencies in the classpath, all should be good. BTW, it would be great if we could build the configuration for the exec plugin into the pom.xml, like I have done in multiApp/demos/consumer-service. This makes it much easier for the user to simply type "mvn exec:java" without having to pass a bunch of -D options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues March 2012