October 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2918) NullPointerException in ServiceComponent

by Kevin Conner (JIRA)

NullPointerException in ServiceComponent ---------------------------------------- Key: JBESB-2918 URL: https://jira.jboss.org/jira/browse/JBESB-2918 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 The eventContext is null because the configuration specifies the event element in the wrong service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2907) Build the JBoss ESB JON plugin within the build

by Tom Cunningham (JIRA)

Build the JBoss ESB JON plugin within the build ----------------------------------------------- Key: JBESB-2907 URL: https://jira.jboss.org/jira/browse/JBESB-2907 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.7 Build the JBoss ESB JON plugin within the ESB build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2917) Schema Validation - typo in error message

by Jiri Pechanec (JIRA)

Schema Validation - typo in error message ----------------------------------------- Key: JBESB-2917 URL: https://jira.jboss.org/jira/browse/JBESB-2917 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Jiri Pechanec Priority: Optional Fix For: 4.7 In SchemaValidationAction final String errorMsg = "SAXExcption while trying to validate against schema '" + xsd + "'"; should be final String errorMsg = "SAXException while trying to validate against schema '" + xsd + "'"; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2915) Replace as4/as5 embedded consoles with clean versions

by Kevin Conner (JIRA)

Replace as4/as5 embedded consoles with clean versions ----------------------------------------------------- Key: JBESB-2915 URL: https://jira.jboss.org/jira/browse/JBESB-2915 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 Current versions contain esb plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Noel Rocher (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2813?page=com.atlassian.jira.plu... ] Noel Rocher updated JBESB-2813: ------------------------------- Comment: was deleted > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://jira.jboss.org/jira/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Putz > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Noel Rocher (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2813?page=com.atlassian.jira.plu... ] Noel Rocher commented on JBESB-2813: ------------------------------------ Agree with Kevin's last comment. If you look at the new code attached here, you'll see that it's a configuration option (lazy-ejb-init = true or false, default false) and default is preserving the current behavior. Maybe some more loop code should be added to allow a reconnect when no HA remote EJBs are configured but for me it's less priority and need more configs for # of loops and sleeping time. For sure something should be done to avoid JBoss AS instances dependencies. > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://jira.jboss.org/jira/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Putz > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2093) Unexpected error from doRun() - java.util.concurrent.RejectedExecutionException during running manual cluster/failover tests.

by Pavel Macik (JIRA)

Unexpected error from doRun() - java.util.concurrent.RejectedExecutionException during running manual cluster/failover tests. ----------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2093 URL: https://jira.jboss.org/jira/browse/JBESB-2093 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Pavel Macik Assignee: Kevin Conner Running manual cluster/filover test following the http://jboss-wiki.brq.redhat.com/Cluster/failover_tests and when I delete a *.esb archive (step 15 or 17) the exception arises. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2911) Web Service without context-root inside ESB archive has inaccessible WSDL

by Lukáš Petrovický (JIRA)

Web Service without context-root inside ESB archive has inaccessible WSDL ------------------------------------------------------------------------- Key: JBESB-2911 URL: https://jira.jboss.org/jira/browse/JBESB-2911 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Lukáš Petrovický When a web service inside an ESB archive is deployed in a way that the WAR doesn't contain the WEB-INF/jboss-web.xml file (SEE JBESB-2910 for a full description of the problem), the WSDL of the web service becomes inaccessible. As an example, take the webservice_consumer1 quickstart with its WAR updated, so that it doesn't contain the file above. (I can attach it, if necessary.) When we deploy it, we see the following (using JBossWS console) as an endpoint address for the WS: http://localhost:8080/Quickstart_webservice_consumer1-Quickstart_webservi... This address, when accessed with a browser, returns HTTP 404. When we blindly try the address that this WS would've had in SOA-P 4.x, we get HTTP 500 (Servlet Exception): http://localhost:8080/Quickstart_webservice_consumer1/HelloWorldWS?wsdl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2914) Reduce number of connections for RemoteFileSystemListener

by Niels Lippke (JIRA)

Reduce number of connections for RemoteFileSystemListener --------------------------------------------------------- Key: JBESB-2914 URL: https://jira.jboss.org/jira/browse/JBESB-2914 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Niels Lippke The RemoteFileSystemListener (FTP, SFTP, FTP-S) open a connection on each file action and close them afterwards. This leads to a lot of connection for a single schedule which is not suitable for productive use. In a better approach the listener should keep its connection open until the last file is processed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2908) webservice_consumer1's documentation

by Jehudi Castro (JIRA)

webservice_consumer1's documentation ------------------------------------ Key: JBESB-2908 URL: https://jira.jboss.org/jira/browse/JBESB-2908 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: JBI Affects Versions: 4.6 Reporter: Jehudi Castro Priority: Minor according to the documentation the output of this QS should be: &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 12:35:47,991 INFO [STDOUT] Response Map is: <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> <env:Header></env:Header> <env:Body> <hel:sayHelloResponse xmlns:hel='http://webservice_consumer1/helloworld'> <return>Hello World Greeting for 'Jimbo' on Sat Jul 14 12:35:47 EDT 2007</return> </hel:sayHelloResponse></env:Body></env:Envelope> 12:35:47,991 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& the actual output is: 07:46:33,055 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 07:46:33,055 INFO [STDOUT] Response Map is: {sayHelloResponse.return=Hello World Greeting for 'Jimbo' on Sun Oct 25 07:46:32 CET 2009} 07:46:33,055 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2009