January 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3629) Provide alternative registry implementation

by Tom Cunningham (JIRA)

Provide alternative registry implementation ------------------------------------------- Key: JBESB-3629 URL: https://issues.jboss.org/browse/JBESB-3629 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 The issue here is: in a cluster environment, after a malfunction on JBoss (e.g. JVM crash, erroneous deployment etc) the registry remains with invalid endpoints and the ESB has an erroneous behavior by using those endpoints. Even your removeDeadEPR property is unusable, because as stated in the documentation the "the end-point reference for a service that is [...] slow to respond may, inadvertently, be removed from the registry by mistake". Since we have a cluster and to manually clean the DB is not just to drop the tables and restart the server, this is a major issue for us, because it can lead to erroneous service calls if a server node crashes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3644) Create pom for rosetta JAR

by Tom Cunningham (JIRA)

Create pom for rosetta JAR -------------------------- Key: JBESB-3644 URL: https://issues.jboss.org/browse/JBESB-3644 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Need a pom.xml detailing the dependencies of the rosetta JAR so that we can release this to maven repositories. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (JBESB-3730) BaseWebService: DOMException: WRONG_DOCUMENT_ERR when when running with JBoss AS 6.1.0.GA

by Daniel Bevenius (JIRA)

Daniel Bevenius created JBESB-3730: -------------------------------------- Summary: BaseWebService: DOMException: WRONG_DOCUMENT_ERR when when running with JBoss AS 6.1.0.GA Key: JBESB-3730 URL: https://issues.jboss.org/browse/JBESB-3730 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Environment: JBoss AS 6.1.0.GA JBoss ESB 4.10 Mac OS X/Linux Reporter: Daniel Bevenius When running on JBoss AS 6.1.0.GA the following exception was logged with a warn log level: {noformat} 14:16:10,140 WARN [org.jboss.internal.soa.esb.webservice.BaseWebService] Failed to parse fault detail: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it. at com.sun.org.apache.xerces.internal.dom.ParentNode.internalInsertBefore(ParentNode.java:352) [:1.6.0_29] at com.sun.org.apache.xerces.internal.dom.ParentNode.insertBefore(ParentNode.java:284) [:1.6.0_29] at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(NodeImpl.java:235) [:1.6.0_29] at org.jboss.internal.soa.esb.webservice.BaseWebService.invoke(BaseWebService.java:243) [:] at org.jboss.internal.soa.esb.webservice.BaseWebService.invoke(BaseWebService.java:88) [:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29] at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:102) [:1.4.1.SP1] at org.jboss.wsf.stack.cxf.AbstractInvoker._invokeInternal(AbstractInvoker.java:164) [:3.4.1.GA] at org.jboss.wsf.stack.cxf.AbstractInvoker.invoke(AbstractInvoker.java:112) [:3.4.1.GA] at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) [:2.3.1-patch-01] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_29] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_29] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_29] at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) [:2.3.1-patch-01] at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) [:2.3.1-patch-01] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [:2.3.1-patch-01] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113) [:2.3.1-patch-01] at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97) [:2.3.1-patch-01] at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461) [:2.3.1-patch-01] at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:172) [:3.4.1.GA] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:57) [:3.4.1.GA] at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156) [:3.4.1.GA] at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:90) [:3.4.1.GA] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) [:2.3.1-patch-01] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) [:2.3.1-patch-01] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [:1.0.0.Final] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) [:2.3.1-patch-01] {noformat} The offending code in BaseWebService: {code} final Body body = faultMessage.getBody() ; final QName faultCode = (QName)body.get(Fault.DETAIL_CODE_CONTENT) ; final String faultDescription = (String)body.get(Fault.DETAIL_DESCRIPTION_CONTENT) ; final String faultDetail = (String)body.get(Fault.DETAIL_DETAIL_CONTENT) ; if (faultCode != null) { faultMsg = SOAP_MESSAGE_FACTORY.createMessage() ; final SOAPFault fault = faultMsg.getSOAPBody().addFault(faultCode, faultDescription) ; if (faultDetail != null) { try { final Document detailDoc = parseAsDom(faultDetail) ; final Detail detail = fault.addDetail() ; detail.appendChild(detailDoc.getDocumentElement()) ; } catch (final Exception ex2) { LOGGER.warn("Failed to parse fault detail", ex2) ; } } } {code} The code first creating a SoapMessage using the SOAP_MESSAGE_FACTORY and later one is created from the parseAsDom method. The latter is then added to the first which is the cause of this exception. The DOM spec contains the following about this: ??The DOM Recommendation specifies that appendChild Must throw DOMException (WRONG_DOCUMENT_ERR) if an attempt is made to insert a node from one ownerDocument into a tree with a different ownerDocument.?? Modifying the above method and changing the appendChild call to the following: {code} detail.appendChild(detail.getOwnerDocument().importNode(detailDoc.getDocumentElement(), true)) ; {code} Please see attached unit test which reproduces this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] (JBESB-3729) Merge JBESB_4_10_CP changes to trunk for 4.11

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3729: ------------------------------------- Summary: Merge JBESB_4_10_CP changes to trunk for 4.11 Key: JBESB-3729 URL: https://issues.jboss.org/browse/JBESB-3729 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Merge JBESB_4_10_CP changes to trunk for 4.11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3718) ESB Web Service Authentication

by António Ribeiro (Created) (JIRA)

ESB Web Service Authentication ------------------------------ Key: JBESB-3718 URL: https://issues.jboss.org/browse/JBESB-3718 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.9 Environment: Windows 7 Professional running on a Intel(R) Core(TM) i3-2100T CPU @2.50GHz, RAM @ 4,00Gb, 64-bit OS Reporter: António Ribeiro While invoking a JBoss ESB web service through SOAP UI (or Eclipse) using the authentication features of ESB (configuration of both login-config.xml and jbossesb.xml files), the request credentials were ignored. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBESB-3731) Upgrade jUDDI to 3.1.3 and Scout to 1.2.4

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3731: ------------------------------------- Summary: Upgrade jUDDI to 3.1.3 and Scout to 1.2.4 Key: JBESB-3731 URL: https://issues.jboss.org/browse/JBESB-3731 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Upgrade juddi to 3.1.3 and Scout to 1.2.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3719) SoapUIClientService throws NullPointerException when parsing WSDL with http:binding

by Magesh Bojan (Created) (JIRA)

SoapUIClientService throws NullPointerException when parsing WSDL with http:binding ----------------------------------------------------------------------------------- Key: JBESB-3719 URL: https://issues.jboss.org/browse/JBESB-3719 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Magesh Bojan Assignee: Magesh Bojan When WSDL contains http:binding definitions, NPE is thrown and the WSDL becomes unusable. <wsdl:binding name="SimpleHttpPost" type="tns:SimpleHttpPost"> <http:binding verb="POST" /> ... </wsdl:binding> Previous versions worked fine with such WSDls. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3669) Don't copy AS 5 admin-console.war for AS 6 deployments

by Tom Cunningham (JIRA)

Don't copy AS 5 admin-console.war for AS 6 deployments ------------------------------------------------------ Key: JBESB-3669 URL: https://issues.jboss.org/browse/JBESB-3669 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 We're copying in the AS 5 admin-console.war into AS 6 in AS 6 deployment scenarios. We need to copy the ESB plugin into common/deploy/admin-console.war/plugins instead. This is causing a StackOverflowError : Caused by: java.lang.StackOverflowError at java.util.logging.Logger.getResourceBundle(Logger.java:409) [:1.6.0_20] at org.jboss.logmanager.Logger.logRaw(Logger.java:626) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.log4j.BridgeLogger.error(BridgeLogger.java:72) [:] at org.jboss.seam.interop.jul.Log4JConversionFilter.logWithThro ... at org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:68) [:2.1.0.SP1] at org.jboss.logmanager.Logger.logRaw(Logger.java:640) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager.jar:1.2.0.CR9] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager.jar:1.2.0.CR9] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
4
0 / 0

[JBoss JIRA] (JBESB-377) Add MySQL support to the admin console.

by Tom Cunningham (Resolved) (JIRA)

[ https://issues.jboss.org/browse/JBESB-377?page=com.atlassian.jira.plugin.... ] Tom Cunningham resolved JBESB-377. ---------------------------------- Assignee: Tom Cunningham (was: Tom Fennelly) Resolution: Out of Date Closing as Out-of-Date - the esb-console has been deprecated and obsoleted. > Add MySQL support to the admin console. > --------------------------------------- > > Key: JBESB-377 > URL: https://issues.jboss.org/browse/JBESB-377 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 CR2 > Reporter: Tom Fennelly > Assignee: Tom Cunningham > Fix For: 5.0 > > Attachments: build.xml, db.application.modules.xml, distro-build.xml, import.sql, jboss-esb-console-ds.xml, MessageContract.java, persistence.xml > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3726) Remove outdated activemq jars from source

by Kevin Conner (Created) (JIRA)

Remove outdated activemq jars from source ----------------------------------------- Key: JBESB-3726 URL: https://issues.jboss.org/browse/JBESB-3726 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.10 Reporter: Kevin Conner There are outdated activemq jars under product/lib/ext/jms. These should be removed as they are not a direct dependency of the codebase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2012