July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1881) DataFiler errors on trunk

by Tom Cunningham (JIRA)

DataFiler errors on trunk ------------------------- Key: JBESB-1881 URL: https://jira.jboss.org/jira/browse/JBESB-1881 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Burr sees the following on trunk: 17:00:03,296 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio n bytes failed 17:00:03,298 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio n bytes processed 17:00:03,304 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa ll bytes processed 17:00:03,307 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa ll bytes failed 17:00:03,373 ERROR [DataFiler] ERROR - found type of java.lang.Integer for testS tore bytes failed 17:00:03,375 ERROR [DataFiler] ERROR - found type of java.lang.Integer for setup Key bytes failed -- 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

17 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1732) Revisit the trailblazer

by Kevin Conner (JIRA)

Revisit the trailblazer ----------------------- Key: JBESB-1732 URL: http://jira.jboss.com/jira/browse/JBESB-1732 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.3 Reporter: Kevin Conner Fix For: 4.4 We need to revisit the trailblazer, providing a more comprehensive example of what is available using the ESB. As things stand, some of the quickstarts involve more functionality. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-520) convert quickstart readme.txt to readme.html to allow for links & images

by Burr Sutter (JIRA)

convert quickstart readme.txt to readme.html to allow for links & images ------------------------------------------------------------------------ Key: JBESB-520 URL: http://jira.jboss.com/jira/browse/JBESB-520 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Jason Lenhart Priority: Minor Fix For: 4.2 Milestone Release 2 The main readme.txt should be converted to HTML, provide a brief description of each individual quickstart and actually link to that quickstart's readme.html. readme.html's might also include an image describing the architecture as well. -- 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

17 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1546) ESBConfig GUI needs additional configuration options

by Antonio Souza (JIRA)

ESBConfig GUI needs additional configuration options ---------------------------------------------------- Key: JBESB-1546 URL: http://jira.jboss.com/jira/browse/JBESB-1546 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Environment: JDK 1.5.0_14 Windows XP MCE Reporter: Antonio Souza The "JBR Provider" must be added to the list of available providers in ESBConfig Flash GUI. Additionally, when adding 'Actions', it should have a field of MEP type (one-way, request-response). This 2 items must be addressed in the next releases of the ESBConfig GUI. -- 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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-591) SQL Listener should deal with rows

by Tom Cunningham (JIRA)

SQL Listener should deal with rows ---------------------------------- Key: JBESB-591 URL: http://jira.jboss.com/jira/browse/JBESB-591 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Mark Little Talked to Burr and Kurt today about the SQL poller quickstart and the SQL listener with regards to the hibernate listener. Burr thinks that the SQL listener should be dealing with the entire row as a message, rather than just a column. This would probably demand changes in both Listener and Quickstart. -- 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

17 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-629) Upgrade the Smooks console to use the newer config model

by Tom Fennelly (JIRA)

Upgrade the Smooks console to use the newer config model -------------------------------------------------------- Key: JBESB-629 URL: http://jira.jboss.com/jira/browse/JBESB-629 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling, Transformation Service Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly It's currently using the Smooks v0.8 DTD based model. Upgrade it to use the newer v0.9 XSD based model. v0.9 is backward compatible with the v0.8 config model, but it throws out warnings (not exceptions) to the console. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1721) Add MSSQL config files

by Martin Vecera (JIRA)

Add MSSQL config files ---------------------- Key: JBESB-1721 URL: http://jira.jboss.com/jira/browse/JBESB-1721 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Martin Vecera Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2.1 CP3 Add following configuration files to support MSSQL: deploy/jbossesb.esb/message-store-sql/mssql deploy/jbossesb.sar/juddi-sql/mssql deploy/jbossesb.sar/lib/juddi-2.0rc5.jar/juddi-sql/mssql For juddi we are experimenting with files copied from sybase config. The server is able to start with that. We will know more after running the 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

17 years, 3 months

3
15
0 / 0

[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

17 years, 3 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

17 years, 3 months

4
13
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

17 years, 4 months

5
31
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008