esb-issues February 2012

esb-issues@lists.jboss.org

1 participants
65 discussions

[JBoss JIRA] Created: (JBESB-2272) ESB testable against external binaries (product test suite)

by Aleksandar Kostadinov (JIRA)

ESB testable against external binaries (product test suite) ----------------------------------------------------------- Key: JBESB-2272 URL: https://jira.jboss.org/jira/browse/JBESB-2272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4 Reporter: Aleksandar Kostadinov When running the ESB test suite against external binaries, there is currently a mismatch between libraries downloaded by the test suite and libraries found in the external distribution. This makes running the suite against the external JBoss AS distribution meaningless because doesn't prove ESB will work with the libraries found in the JBoss AS server. As a solution I see, the various junit tasks run by the testsuite should have classpath point at the libraries in the JBoss AS rather than these generated during build and downloaded by the build script. Running the test suite against external binaries should be the same as verifying an ESB installation (be it on top of JBoss AS or standalone). The issue supersedes JBESB-1513 and is the cause of JBESB-1711. -- 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

12 years, 3 months

4
17
0 / 0

[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

← Newer
1
2
3
4
5
6
7
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2012