October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1093) Update JBossESB Server with JBossRemoting 2.2.2.SP1

by Tom Fennelly (JIRA)

Update JBossESB Server with JBossRemoting 2.2.2.SP1 --------------------------------------------------- Key: JBESB-1093 URL: http://jira.jboss.com/jira/browse/JBESB-1093 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transports Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2.1 IR1 http://repository.jboss.org/jboss/remoting/2.2.2.SP1/lib/jboss-remoting.jar -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-812) [junit] java.io.FileNotFoundException: /boot.log (Permission denied) - running quickstart tests

by Len DiMaggio (JIRA)

[junit] java.io.FileNotFoundException: /boot.log (Permission denied) - running quickstart tests ----------------------------------------------------------------------------------------------- Key: JBESB-812 URL: http://jira.jboss.com/jira/browse/JBESB-812 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Environment: RHEL5 ESB build from svn on 20070813 Reporter: Len DiMaggio Assigned To: Mark Little Priority: Minor I'm seeing this error running the quickstart tests - it doesn't seem to affect anything, but it's fairly ugly with 50+ lines written to stderr... [junit] ------------- Standard Error ----------------- [junit] Found log4j.properties: jar:file:/opt/ESB_svn/trunk/product/samples/quickstarts/tests/build/jbossesb-test/jbossesb-server/bin/run.jar!/log4j.properties [junit] log4j:ERROR setFile(null,false) call failed. [junit] java.io.FileNotFoundException: /boot.log (Permission denied) -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-1156) Reloading of jboss-esb.xml fails

by Burr Sutter (JIRA)

Reloading of jboss-esb.xml fails -------------------------------- Key: JBESB-1156 URL: http://jira.jboss.com/jira/browse/JBESB-1156 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR1 Reporter: Burr Sutter Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 >From SVN as of Oct 10, 2007: Steps: 1. in a command window cd over quickstart helloworld 2. ant run 3. open a new command window 4. ant runtest - see the message on the "ant run" window 5. open jboss-esb.xml, edit and save 6. revisit the window with "ant run" and see this stack trace [qsjava] 15:41:05,765 ERROR [Thread-9][ConfigurationController] Unexpected ex ception starting controller [qsjava] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: No appropriate courier can be obtained for EPR: PortReference < <wsa:Address jms:// localhost/queue/quickstart_helloworld_Request_esb/>, <wsa:ReferenceProperties jb ossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:109 9/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss. naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa :ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:Ref erenceProperties jbossesb:persistent : true/> > [qsjava] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doIn itialise(MessageAwareListener.java:205) [qsjava] at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycl e.initialise(AbstractManagedLifecycle.java:133) [qsjava] at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleControl ler.initialiseInstances(ManagedLifecycleController.java:150) [qsjava] at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleControl ler.start(ManagedLifecycleController.java:69) [qsjava] at org.jboss.soa.esb.listeners.config.ConfigurationController.st artController(ConfigurationController.java:366) [qsjava] at org.jboss.soa.esb.listeners.config.ConfigurationController.st artController(ConfigurationController.java:354) [qsjava] at org.jboss.soa.esb.listeners.config.ConfigurationController.pr ocessConfiguration(ConfigurationController.java:328) [qsjava] at org.jboss.soa.esb.listeners.config.ConfigurationController.ru n(ConfigurationController.java:150) [qsjava] at java.lang.Thread.run(Thread.java:595) [qsjava] Caused by: org.jboss.soa.esb.couriers.CourierException: Unexpected l ifecycle resource exception whiel registering courier [qsjava] at org.jboss.soa.esb.couriers.CourierFactory.registerCourier(Cou rierFactory.java:160) [qsjava] at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierF actory.java:134) [qsjava] at org.jboss.soa.esb.couriers.CourierFactory.getPickupCourier(Co urierFactory.java:120) [qsjava] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doIn itialise(MessageAwareListener.java:182) [qsjava] ... 8 more [qsjava] Caused by: org.jboss.soa.esb.lifecycle.LifecycleResourceException: R esource already destroyed [qsjava] at org.jboss.soa.esb.lifecycle.LifecycleResource.getLifecycleRes ource(LifecycleResource.java:113) [qsjava] at org.jboss.soa.esb.couriers.CourierFactory.registerCourier(Cou rierFactory.java:156) [qsjava] ... 11 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

16 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1120) Check DataFilerJob context classloader initialisation

by Kevin Conner (JIRA)

Check DataFilerJob context classloader initialisation ----------------------------------------------------- Key: JBESB-1120 URL: http://jira.jboss.com/jira/browse/JBESB-1120 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2.1 IR2 DataFilerJob is a quartz Job but it does not look as if it reinitialises the context classloader before executing. Need to check if this is the case and, if so, fix. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1144) ClassCastException within Aggregator timeout thread.

by Kevin Conner (JIRA)

ClassCastException within Aggregator timeout thread. ---------------------------------------------------- Key: JBESB-1144 URL: http://jira.jboss.com/jira/browse/JBESB-1144 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR2 The aggregator timeout thread examines expired messages for an AGGEGRATOR_TAG (sic) property and casts this value to a String. The thread assumes this is a ':' separated list of tags. The remainder of the ESB code initialises (and utilises) this property as an instance of ArrayList<String>. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-837) Add CI task for the QSs back in

by Kurt Stam (JIRA)

Add CI task for the QSs back in ------------------------------- Key: JBESB-837 URL: http://jira.jboss.com/jira/browse/JBESB-837 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Kevin Conner Priority: Critical Fix For: 4.2 Hi Kev, Just a reminder since I think this is of crucial importance to the QA effort. The build machines seem to have a problem with running the ci target for the QSs. Someone with access to the build machines (Kev?) need to take a look at that and put this back in pace. The lines: <ant dir="product/samples/quickstarts/tests" target="qs-test"/> and <ant dir="product/samples/quickstarts/tests" target="qs-clean"/> should be put back into action. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBESB-864) Check MessageStore text in Programmers Guide

by Mark Little (JIRA)

Check MessageStore text in Programmers Guide -------------------------------------------- Key: JBESB-864 URL: http://jira.jboss.com/jira/browse/JBESB-864 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Message Store Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2.1 On behalf of intern: "The MessageStore interface described in the Programmers Guide does not conform to what's in the source tree. It looks like it has evolved quite a bit since the text was written. It should be updated." -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1088) Make trailblazer work correctly in jbossesb-server

by Kevin Conner (JIRA)

Make trailblazer work correctly in jbossesb-server -------------------------------------------------- Key: JBESB-1088 URL: http://jira.jboss.com/jira/browse/JBESB-1088 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 The trailblazer only works in the source or jbossesb artifact. The build file needs to change so that it can function in the jbossesb-server. The default target in the build.xml file is also incorrect. -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-878) Clustered jUDDI

by Mark Little (JIRA)

Clustered jUDDI --------------- Key: JBESB-878 URL: http://jira.jboss.com/jira/browse/JBESB-878 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Registry and Repository Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Intern: "Can we add some tips to cluster juddi? I don't know if there's anything within juddi to help do this, but minimally it seems that just using something like clustered Oracle as a back end would help?" -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1128) No Oracle SQL scripts for message store are included

by Jiri Pechanec (JIRA)

No Oracle SQL scripts for message store are included ---------------------------------------------------- Key: JBESB-1128 URL: http://jira.jboss.com/jira/browse/JBESB-1128 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR1 Reporter: Jiri Pechanec Assigned To: Mark Little The create_database.sql script can look like this example CREATE TABLE message ( uuid varchar2(128) NOT NULL, type varchar2(128) NOT NULL, message varchar2(4000) NOT NULL, delivered varchar2(10) NOT NULL, classification varchar2(10), PRIMARY KEY (uuid) ); -- 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

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007