March 2008 - esb-issues - Jboss List Archives

[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-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-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

[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

17 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-1590) Review File lifecycle management in the FileGateway

by Tom Fennelly (JIRA)

Review File lifecycle management in the FileGateway --------------------------------------------------- Key: JBESB-1590 URL: http://jira.jboss.com/jira/browse/JBESB-1590 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Fix For: 4.2.1 CP2 Task JBESB-1568 identified an issue thrown up by the scheduler code, but in doing so also highlighted a secondary issue in the way that the gateway itself manages the lifecycles of the files it is processing. Specifically... when a file "disappears" while that instance of the gateway is processing it (or about to process it). This could happen through a single FileGateway config before JBESB-1568 was fixed, but can still happen when multiple gateways are configured to process the same fileset in the same directory. The gateway should handle such contention issue more cleanly. Should it support multiple gateway instances processing a single fileset in a single directory? This could be a head wrecker to get right *and prove right* on all platforms! We could just document this as something that's not supported. It should def be able to handle different filesets in the same dir using multiple gateway instances! -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-668) Integrate with JON for monitoring and management

by Tom Cunningham (JIRA)

Integrate with JON for monitoring and management ------------------------------------------------ Key: JBESB-668 URL: http://jira.jboss.com/jira/browse/JBESB-668 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2 I'm splitting the "JON-integration" part of JBESB-544 into its own bug, because this part will go out past MR3. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-866) jUDDI retains invalid EPRs

by Jiri Pechanec (JIRA)

jUDDI retains invalid EPRs -------------------------- Key: JBESB-866 URL: http://jira.jboss.com/jira/browse/JBESB-866 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little If the ESB is terminated (crashes) it will retain EPRs in the database. Unfortunately when the EPR is changed e.g. by renaming of underlaying queue, both old and new EPRs are stored in jUDDI registry on the next start. Then under heavier load both EPRs are selected with the result of lot error messages related to unavailable EPR. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-539) Config Generator should normalise all listener, bus, provider name values.

by Tom Fennelly (JIRA)

Config Generator should normalise all listener, bus, provider name values. -------------------------------------------------------------------------- Key: JBESB-539 URL: http://jira.jboss.com/jira/browse/JBESB-539 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Because these are used as element names in the generated config. If there are invalid chars in there (spaces etc) the generator throws a totaly useless error. Improve the error handling there too :-) -- 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, 5 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008