August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-848) Configure sample-bindings.xml as part of installation process

by Kevin Conner (JIRA)

Configure sample-bindings.xml as part of installation process ------------------------------------------------------------- Key: JBESB-848 URL: http://jira.jboss.com/jira/browse/JBESB-848 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 We need to support configuration of ESB through the service binding manager. To enable this the installation process should modify the sample-bindings.xml shipped as part of the AS distribution. This also needs to be executed against the jbossesb-server when the artifact is created. -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-822) Change the <simple-schedule> "repeatCount" to be an "execCount"

by Tom Fennelly (JIRA)

Change the <simple-schedule> "repeatCount" to be an "execCount" --------------------------------------------------------------- Key: JBESB-822 URL: http://jira.jboss.com/jira/browse/JBESB-822 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 People may find "repeatCount" unintuitive because it's the number of times it's repeated, not the total i.e. if you want a schedule to be triggered 5 times, you set repeatCount="4". It was done this way simply to mirror the behavior of Quartz. Under the hood, "execCount" will get mapped to "repeatCount" simply by subtracting 1. -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-571) Next release should be against AS 4.2.

by Mark Little (JIRA)

Next release should be against AS 4.2. -------------------------------------- Key: JBESB-571 URL: http://jira.jboss.com/jira/browse/JBESB-571 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2 -- 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

18 years, 8 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-677) Make sure we use the EAP branch of AS 4.2 and not the community version.

by Mark Little (JIRA)

Make sure we use the EAP branch of AS 4.2 and not the community version. ------------------------------------------------------------------------ Key: JBESB-677 URL: http://jira.jboss.com/jira/browse/JBESB-677 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Kurt Stam -- 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

18 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-846) Exception when deploying to JBoss AS

by Tom Cunningham (JIRA)

Exception when deploying to JBoss AS ------------------------------------- Key: JBESB-846 URL: http://jira.jboss.com/jira/browse/JBESB-846 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2 I get this error on startup in jboss-4.2.0.GA and on jboss-4.2.1.GA 12:24:55,422 INFO [JBoss4ESBDeployer] create esb service, jbossesb.esb 12:24:55,446 INFO [DeadMessageQueue] Bound to JNDI name: queue/DeadMessageQueue 12:24:56,322 INFO [J2eeConnectionManager] initializing... 12:24:56,426 ERROR [MessageRedeliverer] Could not obtain messages. org.jboss.soa.esb.services.persistence.MessageStoreException: java.sql.SQLException: Table not found in statement [select uuid, message from message] at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.getAllMessages(DBMessageStoreImpl.java:271) at org.jboss.soa.esb.actions.MessageRedeliverer.process(MessageRedeliverer.java:72) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:264) at org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:79) at org.jboss.soa.esb.schedule.ScheduleProvider$ESBScheduledJob.execute(ScheduleProvider.java:180) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: java.sql.SQLException: Table not found in statement [select uuid, message from message] at org.hsqldb.jdbc.Util.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source) at org.hsqldb.jdbc.jdbcStatement.executeQuery(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:171) at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.getAllMessages(DBMessageStoreImpl.java:258) ... 6 more -- 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

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-851) in .esb depency problem

by Kurt Stam (JIRA)

in .esb depency problem ----------------------- Key: JBESB-851 URL: http://jira.jboss.com/jira/browse/JBESB-851 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little The scheduled listeners have surfaced a sneaky dependency issue in the deployment of esb archives. For instance in the jbossesb.esb we have an mbean to create the MessageStore schema if it does not already exist. Now that we have the RedeliveryService, it goes and checks for messages every 5 min according to the schedule: [code]<simple-schedule scheduleid="5-min-trigger" frequency="300" repeatCount="-1"/>[/code] Now this schedule fires right away on deployment of the esb archive. Even before the mbean was was run. And so the hsqldb for the MessageStore was not created yet: [url]http://jira.jboss.com/jira/browse/JBESB-846[/url] I have no way of specifying this "in esb dependency", and I that is ok, as long as we do not start the listeners until the entire esb archive is deployed. I think Kev worked on something very similar a few months back and I think the problem just resurfaced in a slightly different way now that we have the scheduled listeners. -- 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

18 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-796) Make sure ServiceInvoker is documented

by Mark Little (JIRA)

Make sure ServiceInvoker is documented -------------------------------------- Key: JBESB-796 URL: http://jira.jboss.com/jira/browse/JBESB-796 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.2 -- 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

18 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-806) ServiceInvoker should ignore To field

by Mark Little (JIRA)

ServiceInvoker should ignore To field ------------------------------------- Key: JBESB-806 URL: http://jira.jboss.com/jira/browse/JBESB-806 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little -- 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

18 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-804) Remove base64 encoding from DBMessageStoreImpl

by Mark Little (JIRA)

Remove base64 encoding from DBMessageStoreImpl ---------------------------------------------- Key: JBESB-804 URL: http://jira.jboss.com/jira/browse/JBESB-804 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial Fix For: 4.2.1 -- 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

18 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-852) Retransmission for fail-over is a property of the transport requirement (or service contract)

by Mark Little (JIRA)

Retransmission for fail-over is a property of the transport requirement (or service contract) --------------------------------------------------------------------------------------------- Key: JBESB-852 URL: http://jira.jboss.com/jira/browse/JBESB-852 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 What we have now is great and fine with our current purposes. (Hence settin this to a 5.0). But we should not be reusing the general MessageStore for this either, since that is intended for audit trail purposes and may have specific security requirements places on it by the deployer. The need for a retransmission/redeliver store may not be needed at all by some transports, e.g., WS-RX, because it's built in to the implementation. But it may be for others (e.g., HTTP). -- 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

18 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007