May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1733) Remove the use of maxThreads="1" in the gateway declarations of jboss-esb.xml in all quickstarts

by Burr Sutter (JIRA)

Remove the use of maxThreads="1" in the gateway declarations of jboss-esb.xml in all quickstarts ------------------------------------------------------------------------------------------------ Key: JBESB-1733 URL: http://jira.jboss.com/jira/browse/JBESB-1733 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Burr Sutter Assigned To: Burr Sutter Fix For: 4.4 maxThreads="99" is presently ignored by the listener which has is-gateway="true" <jms-listener name="JMS-Gateway" busidref="quickstartGwChannel" maxThreads="1" is-gateway="true" /> The fact that this item is in the examples, suggests to people that it can be tuned it up and down but it is in fact, ignored by system. These examples confuse users. It will now look like the following: <jms-listener name="JMS-Gateway" busidref="quickstartGwChannel" is-gateway="true" /> while a native listener will still have max-threads like so: <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1763) Change src build so that we pull in 3rd party binaries from the repo, c.f., JBossAS.

by Mark Little (JIRA)

Change src build so that we pull in 3rd party binaries from the repo, c.f., JBossAS. ------------------------------------------------------------------------------------ Key: JBESB-1763 URL: http://jira.jboss.com/jira/browse/JBESB-1763 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release, Configuration Affects Versions: 4.3 Reporter: Mark Little Fix For: 4.4 Already spoken with Kev: does not have to be mavenized. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1428) JbossRemotingGatewayListener sending hardcoded string as response

by Vinicius Carvalho (JIRA)

JbossRemotingGatewayListener sending hardcoded string as response ----------------------------------------------------------------- Key: JBESB-1428 URL: http://jira.jboss.com/jira/browse/JBESB-1428 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Vinicius Carvalho The class sends an "<ack/>" as a response when it's used in asynchronous way. One should be able to set the response contents (for instance, for oneway operations on WS called by the SOAPProcessor) -- 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, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-1770) insert-timestamp-column parameter ignored in sql-message-filter

by Stefano Maestri (JIRA)

insert-timestamp-column parameter ignored in sql-message-filter --------------------------------------------------------------- Key: JBESB-1770 URL: http://jira.jboss.com/jira/browse/JBESB-1770 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3 Reporter: Stefano Maestri Assigned To: Stefano Maestri The parameter is ignored for a little bug in SqlTableGatewayListener class -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1622) Need to make sure that Message ID is not overwritten by JMS message ID

by Tom Cunningham (JIRA)

Need to make sure that Message ID is not overwritten by JMS message ID ---------------------------------------------------------------------- Key: JBESB-1622 URL: http://jira.jboss.com/jira/browse/JBESB-1622 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Need to make sure that the message ID is not overwritten by the JMS message ID. The message ID is going to be used to correlate reply-to messages and link message metadata - we're going to need them to be consistent so for monitoring. -- 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, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-1703) https_2way_ssl quickstart not runnable

by Julian Coleman (JIRA)

https_2way_ssl quickstart not runnable -------------------------------------- Key: JBESB-1703 URL: http://jira.jboss.com/jira/browse/JBESB-1703 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Environment: RHEL 5 Reporter: Julian Coleman The https_2way_ssl quickstart doesn't run out of the box. First, it doesn't deploy correctly, as the ESB dependency is wrong. Second, an extra "/" is needed to find the keystore. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-467) Reducing registry lookup overhead

by Mark Little (JIRA)

Reducing registry lookup overhead --------------------------------- Key: JBESB-467 URL: http://jira.jboss.com/jira/browse/JBESB-467 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2, 5.0 >From our previous discussion on reducing registry lookup overhead (currently lookup per message send): There are a number of solutions to this and we should try to support them all eventually: (i) EPR lifetime: service deployers can register a lifetime associated with the EPR in the registry and when something reads the EPR it also receives information on how long the EPR will remain valid for. After that time elapses, clients must go back to the registry to get a new copy. (ii) building on (i), EPRs can be marked as persistent - they never change so one lookup will always be enough. (iii) interactions with services are scoped by sessions and the EPR is assumed to remain valid for the duration of the session. The service can be marked as useable within such a session. (iv) EPRs are looked up once per client lifecycle and only rebound if the service fails. If you recall from the original ESB architecture document, service migration is something that is on the roadmap (5.0) and if a service moves it can leave a forwarding address (EPR) and the architecture allows messages to be redirected and eventually short-cut, i.e., the client EPR is updated with the new EPR transparently as a result of receiving a response from a different endpoint. (iii) and (iv) are really for the 5.0 architecture. However, it should be possible to add something along (i) and (ii) for 4.0. What do you think? -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1729) EJBProcessor doing JNDI lookup on every call - could cache

by Tom Fennelly (JIRA)

EJBProcessor doing JNDI lookup on every call - could cache ---------------------------------------------------------- Key: JBESB-1729 URL: http://jira.jboss.com/jira/browse/JBESB-1729 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Tom Fennelly -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1652) Need to update install/readme.txt

by Tom Cunningham (JIRA)

Need to update install/readme.txt --------------------------------- Key: JBESB-1652 URL: http://jira.jboss.com/jira/browse/JBESB-1652 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Fix For: 4.2.1 TP-FP1 Need to update install/readme.txt - it suggests using jbossws-native-2.0.1.SP2 from the jbossws downloads page, this release is no longer there. "If you are running JBossESB on JBoss AS 4.2.1.GA, you will need to update the Application Server with JBossWS 2.0.1.SP2 (Native). To do this, download the "jbossws-native-2.0.1.SP2" distribution from http://labs.jboss.org/jbossws/downloads/." -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1758) New parameter for ObjectToXStream to change mode for dealing with duplicate references

by Tuomo Jylkkￃﾃￂﾤ (JIRA)

New parameter for ObjectToXStream to change mode for dealing with duplicate references -------------------------------------------------------------------------------------- Key: JBESB-1758 URL: http://jira.jboss.com/jira/browse/JBESB-1758 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: All Reporter: Tuomo Jylkkￃﾃￂﾤ ObjectToXStream doesn't has parameter to configure XStream mode. Now we cannot change mode for dealing with duplicate references from default (XStream.XPATH_RELATIVE_REFERENCES) to other modes. -- 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, 9 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2008