May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-567) BAM-like capabilities within the core ESB

by Mark Little (JIRA)

BAM-like capabilities within the core ESB ----------------------------------------- Key: JBESB-567 URL: http://jira.jboss.com/jira/browse/JBESB-567 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: BPM, Tooling Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2 As we discussed, using something like Rules would be a great approach because it gives us the flexibility of dynamic updates to the system without requiring recompilations or redeployments. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1675) Possible Juddi Performance problems

by Tom Cunningham (JIRA)

Possible Juddi Performance problems ----------------------------------- Key: JBESB-1675 URL: http://jira.jboss.com/jira/browse/JBESB-1675 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham >From forum post : We are not using juddi directly, I do not know if it is a core required component of ESB. After a few runs, we are having performance problems that seems to be related to juddi. It happens only on shutdow/startup operations. The time spent to create the auth tokens (sorry, what are they used for anyway??) are taking longer and longer. JBoss takes over 2 minutes (in a 8 processor machine??) just to delete the template bindings for juddi on the shutdown process. -- 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, 8 months

5
19
0 / 0

[JBoss JIRA] Created: (JBESB-1717) Support additional naming properties in JMS EPRs

by Kevin Conner (JIRA)

Support additional naming properties in JMS EPRs ------------------------------------------------ Key: JBESB-1717 URL: http://jira.jboss.com/jira/browse/JBESB-1717 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Kevin Conner Fix For: 4.3, 4.4 Some JNDI providers require the specification of other properties in addition to the normal JNDI properties but, at present, we are restricting their inclusion. One example of this is SonicMQ which also requires properties such as com.sonicsw.jndi.mfcontext.domain and com.sonicsw.jndi.mfcontext.idleTimeout. We need to extend the JMS EPR so that it can include the specification of additional properties but without including all extensions. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1459) Services should be unique by node:esb:category:service

by Tom Cunningham (JIRA)

Services should be unique by node:esb:category:service ------------------------------------------------------ Key: JBESB-1459 URL: http://jira.jboss.com/jira/browse/JBESB-1459 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Currently, services are unique by : node:esb:service They should be unique by : node:esb:category:service >From Kevin: The gateway generator enforces a unique service name within an esb but it does not take the category into account. It looks like you may have added this requirement into the code at some point, can you remember why the category was never used? -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-1479) webservice_wsaddressing fails with NullPointerException due to failure to inject WebServiceContext

by Kevin Conner (JIRA)

webservice_wsaddressing fails with NullPointerException due to failure to inject WebServiceContext -------------------------------------------------------------------------------------------------- Key: JBESB-1479 URL: http://jira.jboss.com/jira/browse/JBESB-1479 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.3 -- 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
8
0 / 0

[JBoss JIRA] Created: (JBESB-1528) WS attachments does not work for non-image binary data

by Jiri Pechanec (JIRA)

WS attachments does not work for non-image binary data ------------------------------------------------------ Key: JBESB-1528 URL: http://jira.jboss.com/jira/browse/JBESB-1528 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP1 Attachments: wsa.tgz In the JBossWS docs there is a list of supported MIME types together with appropriate java data types http://jbws.dyndns.org/mediawiki/index.php?title=User_Guide#Attachments java.awt.Image and javax.xml.transform.Source works but javax.activation.DataHandler that can be used to transfer any binary data does not. Attached is test app and TestNG test that can be convereted into standalone client in two minutes If call is done against WS itself then it works, if it send via ESB facade, the attachment is not added. Can it be related to JBESB-1479 ? -- 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
16
0 / 0

[JBoss JIRA] Created: (JBESB-1681) Add Property Substitution to NotifyJMS, NotifyTopics, and NotifyEmail

by Tom Cunningham (JIRA)

Add Property Substitution to NotifyJMS, NotifyTopics, and NotifyEmail --------------------------------------------------------------------- Key: JBESB-1681 URL: http://jira.jboss.com/jira/browse/JBESB-1681 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Priority: Minor Fix For: 4.3 Add Property Substitution to NotifyJMS, NotifyTopics, and NotifyEmail - see JBESB-1589. -- 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-570) Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces

by Pete Bennett (JIRA)

Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-570 URL: http://jira.jboss.com/jira/browse/JBESB-570 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Environment: Fedora Core 6 J2SE 5 Ant 1.6.5 Reporter: Pete Bennett Assigned To: Mark Little Priority: Minor In the Quickstart guide and the Trailblazers, one needs to configure the deployment.properties file to point at an installation of JBoss AS with EJB3 enabled. If the path specified includes a space then things will seem to work, but when you try to start up the JBoss AS server for the Quickstart example, you get an error in the JBoss AS console Window when the ESB service tries to parse this pass as follows: 11:14:06,973 INFO [DatabaseInitializer] Initializing java:/juddiDB from listed sql files 11:14:07,166 INFO [JuddiRMIService] starting juddi RMI service 11:14:07,171 WARN [ServiceController] Problem starting service jboss.esb:service=JuddiRMI java.net.URISyntaxException: Illegal character in path at index 31: file:/home/pbennett/JBoss/JBoss ESB/4.2MR2/jbossesb-server/server/default/deploy/jbossesb.sar/esb.juddi.properties at java.net.URI$Parser.fail(URI.java:2816) at java.net.URI$Parser.checkChars(URI.java:2989) at java.net.URI$Parser.parseHierarchical(URI.java:3073) at java.net.URI$Parser.parse(URI.java:3021) at java.net.URI.<init>(URI.java:578) at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:63) ... If you use a relative path rather than an absolute path, then the Quickstart example works when run from the original directory but the other Trailblazer examples fail to find the correct directory as they look relative to themselves rather than relative to the root. -- 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-1647) Management part of console only shows node entries

by Tom Cunningham (JIRA)

Management part of console only shows node entries -------------------------------------------------- Key: JBESB-1647 URL: http://jira.jboss.com/jira/browse/JBESB-1647 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Fix For: 4.2.1 CP3 The management part of the console is only showing entries for the current node. The monitoring part shows things correctly for all nodes. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBESB-1778) H2 remote database shutdown fails, STOP_SERVER not found

by Kevin Conner (JIRA)

H2 remote database shutdown fails, STOP_SERVER not found -------------------------------------------------------- Key: JBESB-1778 URL: http://jira.jboss.com/jira/browse/JBESB-1778 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 15:07:30,669 WARN [H2Database] Stopping failed jboss:service=HelloworldTxSqlDB org.h2.jdbc.JdbcSQLException: Function STOP_SERVER not found; SQL statement: CALL STOP_SERVER(?, ?, ?) [90022-68] -- 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