September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-849) Should smooks test be an integration test?

by Mark Little (JIRA)

Should smooks test be an integration test? ------------------------------------------ Key: JBESB-849 URL: http://jira.jboss.com/jira/browse/JBESB-849 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly Priority: Trivial [java] [junit] 10:22:35,254 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled! [java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed. [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:161) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:203) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:122) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:109) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:236) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:218) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69) indicates that the test needs JMS set up beforehand. So doesn't that tend to imply it's an integration test? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1711) ESB unit test suite hangs when run against SOA-P CP1

by Aleksandar Kostadinov (JIRA)

ESB unit test suite hangs when run against SOA-P CP1 ---------------------------------------------------- Key: JBESB-1711 URL: http://jira.jboss.com/jira/browse/JBESB-1711 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Aleksandar Kostadinov unzip SOA-P distribution in $WORKSPACE/jbosssoa chprop product.properties org.jboss.esb.server.home "$WORKSPACE/jbosssoa/jboss-as" chprop product.properties org.jboss.esb.server.config $SERVER_NAME chprop product.properties org.jboss.esb.test.ftp.hostname dev39.qa.atl.jboss.com chprop product.properties org.jboss.esb.test.ftp.user user chprop product.properties org.jboss.esb.test.ftp.pwd pass chprop product.properties org.jboss.esb.test.ftp.dir /esb-in-soa then: cd product ant org.jboss.esb.integration.test Test suite hangs after first few tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET

by Burr Sutter (JIRA)

EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET ------------------------------------------------------------------------------- Key: JBESB-2052 URL: https://jira.jboss.org/jira/browse/JBESB-2052 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter The WSDL and the quickstart that creates it are attached. Here is the exact error message from Visual Studio/Visual Basic: Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding 'FetchCustomerBinding' from namespace 'http://soa.jboss.org/ESBWebServiceSample'. The operation 'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace 'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The operation has no matching binding. Check if the operation, input and output names in the Binding section match with the corresponding names in the PortType section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My Project\Settings.settings 1 1 WindowsApplication1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-1958) JBoss Remoting Gateway not providing HTTP query string in composed message

by Tom Fennelly (JIRA)

JBoss Remoting Gateway not providing HTTP query string in composed message -------------------------------------------------------------------------- Key: JBESB-1958 URL: https://jira.jboss.org/jira/browse/JBESB-1958 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x This happens because the JBR CoyoteInvoker doesn't forward the query string in the request parameters object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-2049) Check for invalid synchronous invocations within a transactional context

by Kevin Conner (JIRA)

Check for invalid synchronous invocations within a transactional context ------------------------------------------------------------------------ Key: JBESB-2049 URL: https://jira.jboss.org/jira/browse/JBESB-2049 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner We support a number of transports which integrate with transactions in a manner such that the delivery of the message will not occur until the transaction has been committed. If these transports are used to delivery a synchronous message then the result is a timeout/failure. We should introduce a mechanism where we can identify these situations and throw a different exception, clarifying the failure for our users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2003) Allow configuration of async redelivery property on a per message basis

by Kevin Conner (JIRA)

Allow configuration of async redelivery property on a per message basis ----------------------------------------------------------------------- Key: JBESB-2003 URL: https://jira.jboss.org/jira/browse/JBESB-2003 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 The codebase allows for this property to be set through the global properties but does not (officially) allow it to be set per invocation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1438) JMS Courrier does not support transacted mode

by Jiri Pechanec (JIRA)

JMS Courrier does not support transacted mode --------------------------------------------- Key: JBESB-1438 URL: http://jira.jboss.com/jira/browse/JBESB-1438 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker Fix For: 4.2.1 CP1 JMS Courrier (deliver side) operates only with non-transacted queue sessions. This prevents jBPM integration to work correctly. The problem can be sketched this way 1) The message is received via JMS/JCA listener, transaction is started 2) jBPM process is invoked 3) jBPM process sends message (calls service) in non-transacted mode Three situations can happen 1) Exception is thrown later, it means that global transaction is rolled back but another service was already invoked - BUG 2) jBPM process goes to the wait state and waits for response from ESB, global transaction is committed, called service sends back signal to continue process - OK 3) jBPM process goes to the wait state and waits for response from ESB, called service sends back signal to continue process - but the global transaction was not committed yet - BUG This is key feature to have ESB/jBPM integration working safely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
31
0 / 0

[JBoss JIRA] Created: (JBESB-1164) Crash creates multiple EPRs for same service in JUDDI

by Tom Cunningham (JIRA)

Crash creates multiple EPRs for same service in JUDDI ----------------------------------------------------- Key: JBESB-1164 URL: http://jira.jboss.com/jira/browse/JBESB-1164 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 IR1 Reporter: Tom Cunningham Assigned To: Mark Little If the AS or ESB server crashes or does not cleanly shut down, JUDDI will duplicate EPR records in its database table. For the monitoring/management console, this is a real problem because it depends on the fact that there will be only one EPR for its services per ESB server. Post-crash, every time the console tries to collect data, it is getting back results from multiple EPRs on the same machine, which is causing ConstraintViolations when we try to store results. This is causing JBESB-1139. JUDDI should probably clean up EPR records post-crash. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-1658) Project layout for Quickstarts

by Mark Little (JIRA)

Project layout for Quickstarts ------------------------------ Key: JBESB-1658 URL: http://jira.jboss.com/jira/browse/JBESB-1658 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Examples Affects Versions: 4.2.1 CP2 Reporter: Mark Little Fix For: 4.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2013) Create Inbound and Outbound routers for JMS

by Tom Fennelly (JIRA)

Create Inbound and Outbound routers for JMS ------------------------------------------- Key: JBESB-2013 URL: https://jira.jboss.org/jira/browse/JBESB-2013 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 5.0 initial development Reporter: Tom Fennelly Assignee: Daniel Bevenius -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008