July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-635) Documentation does not include information on running ESB Server and JBossAS on same machine

by Mark Little (JIRA)

Documentation does not include information on running ESB Server and JBossAS on same machine -------------------------------------------------------------------------------------------- Key: JBESB-635 URL: http://jira.jboss.com/jira/browse/JBESB-635 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-611) org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work

by Len DiMaggio (JIRA)

org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work ----------------------------------------------------------------------------------- Key: JBESB-611 URL: http://jira.jboss.com/jira/browse/JBESB-611 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Environment: RHEL5 Sun Java 1.5 ESB built from svn on June 6 Reporter: Len DiMaggio Assigned To: Mark Little Priority: Minor Potential bug: In trying a simple static router - with org.jboss.soa.esb.actions.StaticRouter - and text messages going thru a gateway listener - I'm seeing this error in the server log: ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog. This is with code and a jboss-esb.xml that worked with MR2 - also - although the error says fatal, the router seems to be working fine. A known problem? Thanks! Note - commenting out all the: [code] <target class="NotifyConsole" /> [/code] statements in the jboss-esb has no effect. See also: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110548 -- 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, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-589) Smooks decoders do not handle superclasses/interfaces of a specified type

by Kevin Conner (JIRA)

Smooks decoders do not handle superclasses/interfaces of a specified type ------------------------------------------------------------------------- Key: JBESB-589 URL: http://jira.jboss.com/jira/browse/JBESB-589 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Kevin Conner Assigned To: Tom Fennelly Fix For: 4.2 The XML2POJO and XML2XML_date_manipulation QSes have recently been changed to decode types related to the target class. One of the changes was to decode a Calendar object in the OrderDate class. Unfortunately smooks fails to identify the setter as the CalendarDecoder returns a GregorianCalendar which AbstractBeanPopulator uses to identify the setter. I have spoken with Tom and he has a fix for this. In the meantime I have updated the QSes to use Dates instead of Calendars. -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-638) Transient registry errors caused by jUDDI race condition

by Kevin Conner (JIRA)

Transient registry errors caused by jUDDI race condition -------------------------------------------------------- Key: JBESB-638 URL: http://jira.jboss.com/jira/browse/JBESB-638 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Kevin Conner Assigned To: Kurt Stam Fix For: 4.2 Kurt, can you raise the following with jUDDI and have it fixed? Thanks. There is a race condition in the jUDDI codebase which causes transient registry failures. The symptom of the race condition is the following error message E_busy (10400) The request cannot be processed at the current time. The Registry is currently unavailable. The class containing the race condition is org.apache.juddi.registry.local.Registry Every call to Registry.getRegistry() results in the recreation and initialisation of a global variable (registry). As the assignment of the global variable is made *before* the initialisation method is called there exists a window of opportunity whereby a caller can obtain a reference to an uninitialised registry. The consequence of this is that calls to RegistryEngine.isAvailable() can return false. I'm not sure why the RegistryEngine is being recreated on every call but the current code is unsafe (even if ignoring multiprocessor memory models). There should be not be a global reference to the registry if it is a requirement to recreate it on every invocation. If it is not a requirement then the initialisation should really be occurring within a static block. -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-578) Quickstarts still refer to jbosshome.dir

by Kevin Conner (JIRA)

Quickstarts still refer to jbosshome.dir ---------------------------------------- Key: JBESB-578 URL: http://jira.jboss.com/jira/browse/JBESB-578 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 The jbosshome.dir property was renamed to org.jboss.esb.server.home but it is still referenced in at least two of the quickstarts. fun_cbr and webservice_war1 need updating, the others double checking. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-616) Fix quickstart tests

by Kevin Conner (JIRA)

Fix quickstart tests -------------------- Key: JBESB-616 URL: http://jira.jboss.com/jira/browse/JBESB-616 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 The quickstart/tests directory contains a build script which drives the build of certain quickstarts. This script no longer functions after the consolidation of the base build script. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-633) jboss-esb-console pages don't load in jboss-4.2.0.GA

by Tom Cunningham (JIRA)

jboss-esb-console pages don't load in jboss-4.2.0.GA ---------------------------------------------------- Key: JBESB-633 URL: http://jira.jboss.com/jira/browse/JBESB-633 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 The jboss-esb-console pages other than home.seam aren't loading in jboss-4.2.0.GA. Here's the error: javax.servlet.ServletException: javax.servlet.ServletException: No active event context org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:61) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-621) Add spring.esb to AS installation

by Kevin Conner (JIRA)

Add spring.esb to AS installation --------------------------------- Key: JBESB-621 URL: http://jira.jboss.com/jira/browse/JBESB-621 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 Spring.esb is not currently deployed into an AS environment. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-593) Upgrade of Smooks JARs broke jboss-esb-console

by Tom Cunningham (JIRA)

Upgrade of Smooks JARs broke jboss-esb-console ---------------------------------------------- Key: JBESB-593 URL: http://jira.jboss.com/jira/browse/JBESB-593 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 The upgrade of smooks JARs seems to have broken the jboss-esb-console (the JARs are listed as modules inside the application.xml for jboss-esb-console.ear). I'm fixing this now. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-656) JMSCorrelationID pulled from message body when it should be the header

by Mark Little (JIRA)

JMSCorrelationID pulled from message body when it should be the header ---------------------------------------------------------------------- Key: JBESB-656 URL: http://jira.jboss.com/jira/browse/JBESB-656 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2 Milestone Release 3 if (message.getBody().get("MessageId")!=null) { oMsg.setJMSCorrelationID((String)message.getBody().get("MessageId")); } Does not make sense, because the MessageId is from the EPR, which is within the header. -- 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, 11 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007