July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-717) Test soapui-client service against soapui-1.7.5-beta2.jar

by Tom Fennelly (JIRA)

Test soapui-client service against soapui-1.7.5-beta2.jar --------------------------------------------------------- Key: JBESB-717 URL: http://jira.jboss.com/jira/browse/JBESB-717 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Ole has merged in the changes we needed for the soapui-client service. We're using a slightly modified version of 1.7.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

16 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-585) Look at XMPP support

by Mark Little (JIRA)

Look at XMPP support -------------------- Key: JBESB-585 URL: http://jira.jboss.com/jira/browse/JBESB-585 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 http://www.igniterealtime.org/projects/smack/index.jsp -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-666) Create a separate common module/jar

by Mark Little (JIRA)

Create a separate common module/jar ----------------------------------- Key: JBESB-666 URL: http://jira.jboss.com/jira/browse/JBESB-666 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: Mark Little Priority: Optional -- 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

16 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-667) Echo action

by Mark Little (JIRA)

Echo action ----------- Key: JBESB-667 URL: http://jira.jboss.com/jira/browse/JBESB-667 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Add an echo Action that simply send back the same message to the sender. Could be used for heart-beat, but also for distributed management. -- 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

16 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-697) Add loop-back transport.

by Mark Little (JIRA)

Add loop-back transport. ------------------------ Key: JBESB-697 URL: http://jira.jboss.com/jira/browse/JBESB-697 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 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

16 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-454) Allow no inputSuffix on the FileGateway

by Kurt Stam (JIRA)

Allow no inputSuffix on the FileGateway --------------------------------------- Key: JBESB-454 URL: http://jira.jboss.com/jira/browse/JBESB-454 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Make the suffix on input Files optional so that it simply picks up all the files in the directory. Check to see that in this case the output directory is not the same as the input directory. -- 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

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-746) Potential memory leak in Aggregator

by Jiri Pechanec (JIRA)

Potential memory leak in Aggregator ----------------------------------- Key: JBESB-746 URL: http://jira.jboss.com/jira/browse/JBESB-746 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor There is minor potential memory leak in Aggregator action. 1) The message is in timeout 2) The process method is started by receiveing one part of timeout message 3) Timeout checker checks the same message 4) Regular process creates aggregated message and removes the record in notification HashMap 5) Timout checker sends a notfificaion message and creates the record in notification HashMap 6) Regular process method receives notification message and ignores it as already timed out 7) The record remains in notification map Recommended solution Add _notified.remove(uuId) call to the branch that handles ignoring already timed out messages. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-719) The messages can be lost in case of ESB termination

by Jiri Pechanec (JIRA)

The messages can be lost in case of ESB termination --------------------------------------------------- Key: JBESB-719 URL: http://jira.jboss.com/jira/browse/JBESB-719 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Even if the ESB is using internally reliable JMS as a transport the messages can be lost during ESB termination. The reasons for this behaviour are two 1) ESB uses internally queue sessions with AUTO_ACK flag 2) Pick-up and deliver couriers works in different session Proposed solution 1) Change flag to CLIENT_ACK 2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If the allocated session is stored into ThreadLocal variable and returned by the subsequent calls by the same thread and get commited on call JMSConnectionPool.closeSession() then all internal message transfers via JMS will be done in transaction - one transfer/one transaction. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBESB-736) ReceiveJMSMessage class is confusing and partly buggy

by Jiri Pechanec (JIRA)

ReceiveJMSMessage class is confusing and partly buggy ----------------------------------------------------- Key: JBESB-736 URL: http://jira.jboss.com/jira/browse/JBESB-736 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Optional The class used in samples for reading JMS messages from the queue is confusing and partly buggy. The class repeatedly reads from the queue directly and repeatedly sets up own listener. Also it creates an infinite number of sessions that are not closed. Recommended solution In method main cut the call of method receive one from the infinite loop and put it before the loop. Place a sleep method inside the infinite loop. In that way both direct reading and listener pattern will be demonstrated. Initialization of all resources will be executed only once. -- 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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-735) Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed

by Burr Sutter (JIRA)

Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed --------------------------------------------------------------------- Key: JBESB-735 URL: http://jira.jboss.com/jira/browse/JBESB-735 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 My notes on how to make it run with AS 4.2 with Java 5 are here: http://jboss.org/index.html?module=bb&op=viewtopic&t=112908 And here: Steps (for AS 4.2 + Messaging 1.3 + ESB 4.2MR3) 1. Deploy attached hypersonic databases to the server\messaging\data\hypersonic director. jbpmDB.properties, jbpmDB.script 2. Deploy attached datasource - jbpm-ds.xml into the server\messaging\deploy directory 3. Deploy attached jbpm-console.war - created from CVS because the one in the jBPM3.2.1 suite do not work with Java 5 4. Modify the conf\login-config.xml be inserting the following: <application-policy name = "jbpm"> <authentication> <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required"> <module-option name="dsJndiName">java:/JbpmDS</module-option> <module-option name="principalsQuery"> SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=? </module-option> <module-option name="rolesQuery"> SELECT g.NAME_ ,'Roles' FROM JBPM_ID_USER u, JBPM_ID_MEMBERSHIP m, JBPM_ID_GROUP g WHERE g.TYPE_='security-role' AND m.GROUP_ = g.ID_ AND m.USER_ = u.ID_ AND u.NAME_=? </module-option> </login-module> </authentication> </application-policy> 5. Modify the server\messaging\deploy\jbpm.esb\hibernate.cfg.xml so that it uses the DS defined in step 2. The result should look something like the following: <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property>  <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>  <property name="hibernate.connection.datasource">java:/JbpmDS</property>  6. Start your server with run -c messaging N . http://localhost:8080/jbpm-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, 1 month

6
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007