esb-issues December 2011

esb-issues@lists.jboss.org

1 participants
46 discussions

[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

14 years, 2 months

2
1
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

14 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

14 years, 3 months

3
4
0 / 0

[JBoss JIRA] (JBESB-3722) ActionProcessingPipeline incorrectly uses LOGGER.debug() instead of LOGGER.error() for exceptions

by Ryan LaMothe (Created) (JIRA)

ActionProcessingPipeline incorrectly uses LOGGER.debug() instead of LOGGER.error() for exceptions ------------------------------------------------------------------------------------------------- Key: JBESB-3722 URL: https://issues.jboss.org/browse/JBESB-3722 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.10, 4.9, 4.8 Reporter: Ryan LaMothe For a long time now, we have been trying to figure out why exceptions in our action pipelines would never log any useful information. It turns out that in the file ActionProcessingPipeline lines 654-657 declare the wrong logging level. Current code: if (LOGGER.isDebugEnabled()) { LOGGER.debug("Unexpected exception caught while processing the action pipeline",ex); } Suggested fix: // if (LOGGER.isDebugEnabled()) // { LOGGER.error("Unexpected exception caught while processing the action pipeline",ex); // } Unfortunately, if we simply increase the logging level in JBoss globally for the package that this file is in, the logs quickly fill up with thousands of lines of unneeded messages. In production, logging these kinds of error messages really help with debugging. -- 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

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (JBESB-3720) Merge changes for JBESB-3712 to GSS-SOA-3619 branch

by Tom Cunningham (Created) (JIRA)

Merge changes for JBESB-3712 to GSS-SOA-3619 branch --------------------------------------------------- Key: JBESB-3720 URL: https://issues.jboss.org/browse/JBESB-3720 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.9 CP2 Merge changes for JBESB-3712 to GSS-SOA-3619 branch -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3717) Problem calling remote service using ServiceInvoker in GWT

by Fabio Campos (Created) (JIRA)

Problem calling remote service using ServiceInvoker in GWT ----------------------------------------------------------- Key: JBESB-3717 URL: https://issues.jboss.org/browse/JBESB-3717 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Fabio Campos Hi! I'm receiving an error during the deliverSync method of ServiceInvoker class. The GWT application cannot receive the response from the ESB. The ESB server receives the request and generates the response but it never reaches the destination. I'm not adding any parameters in the message header, only in the body. I have added all the dependencies informed on developers guide of Jboss ESB 4.9, however the following error message is displayed: [INFO] 22259 [btpool0-0] DEBUG org.jboss.soa.esb.client.ServiceInvoker - EPR=JM SEpr [ PortReference < <wsa:Address jms:RJ6660.webb.main:1099#queue/DeadMessageQ ueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp. interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming .provider.url : RJ6660.webb.main:1099/>, <wsa:ReferenceProperties jbossesb:java. naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbosses b:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:specification-ver sion : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionF actory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceP roperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperti es jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:j boss/esb/epr/type/jms/> > ] XML=<wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ ws/2004/08/addressing"><wsa:Address>jms:RJ6660.webb.main:1099#queue/DeadMessageQ ueue</wsa:Address><wsa:ReferenceProperties><jbossesb:java.naming.factory.initial xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">org.jnp.interface s.NamingContextFactory</jbossesb:java.naming.factory.initial><jbossesb:java.nami ng.provider.url xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">RJ 6629.webb.main:1099</jbossesb:java.naming.provider.url><jbossesb:java.naming.fac tory.url.pkgs xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">org. jnp.interfaces</jbossesb:java.naming.factory.url.pkgs><jbossesb:destination-type xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">queue</jbossesb:d estination-type><jbossesb:destination-name xmlns:jbossesb="http://schemas.jboss. com/ws/2007/01/jbossesb">queue/DeadMessageQueue</jbossesb:destination-name><jbos sesb:specification-version xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/j bossesb">1.1</jbossesb:specification-version><jbossesb:connection-factory xmlns: jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">ConnectionFactory</jboss esb:connection-factory><jbossesb:persistent xmlns:jbossesb="http://schemas.jboss .com/ws/2007/01/jbossesb">true</jbossesb:persistent><jbossesb:acknowledge-mode x mlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">AUTO_ACKNOWLEDGE</j bossesb:acknowledge-mode><jbossesb:transacted xmlns:jbossesb="http://schemas.jbo ss.com/ws/2007/01/jbossesb">false</jbossesb:transacted><jbossesb:type xmlns:jbos sesb="http://schemas.jboss.com/ws/2007/01/jbossesb">urn:jboss/esb/epr/type/jms</ jbossesb:type></wsa:ReferenceProperties></wsa:From> [INFO] 22268 [btpool0-0] DEBUG org.jboss.internal.soa.esb.couriers.JmsCourier - JMSCourier deliveryMode: 2, peristent:true [INFO] 22283 [btpool0-0] DEBUG org.jboss.soa.esb.notification.jms.DefaultJMSProp ertiesSetter - Setting outgoing JMSCorreletionID to : 15f771c6-5214-413f-88e9-8 3c1370aa5df [INFO] 22289 [btpool0-0] ERROR br.com.webb.soa.invoker.GenericServiceInvoker - ERROR DELIVERING SYNC MESSAGE:Caught unexpected throwable during send. Bailing-o ut! [ERROR] org.jboss.soa.esb.listeners.message.MessageDeliverException: Caught unex pected throwable during send. Bailing-out! [ERROR] at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDel ivery(ServiceInvoker.java:728) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200 (ServiceInvoker.java:569) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.j ava:359) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceIn voker.java:219) [ERROR] at br.com.webb.soa.invoker.GenericServiceInvoker.invokeSyncServi ce(GenericServiceInvoker.java:66) [ERROR] at br.com.webb.medicao.server.MedicaoServiceImpl.getSumario(Medi caoServiceImpl.java:209) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [ERROR] at java.lang.reflect.Method.invoke(Method.java:592) [ERROR] at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RP C.java:562) [ERROR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCa ll(RemoteServiceServlet.java:188) [ERROR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPo st(RemoteServiceServlet.java:228) [ERROR] at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.d oPost(AbstractRemoteServiceServlet.java:62) [ERROR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) [ERROR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:718) [ERROR] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder. java:488) [ERROR] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandle r.java:362) [ERROR] at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHan dler.java:216) [ERROR] at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandle r.java:181) [ERROR] at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandle r.java:729) [ERROR] at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.j ava:405) [ERROR] at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrappe r.java:152) [ERROR] at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLog Handler.java:49) [ERROR] at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrappe r.java:152) [ERROR] at org.mortbay.jetty.Server.handle(Server.java:324) [ERROR] at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection .java:505) [ERROR] at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpC onnection.java:843) [ERROR] at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647) [ERROR] at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:2 05) [ERROR] at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:3 80) [ERROR] at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEnd Point.java:395) [ERROR] at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThre adPool.java:488) [ERROR] Caused by: java.lang.RuntimeException: Caught XMLStreamException deseria lising Call [ERROR] at org.jboss.internal.soa.esb.message.format.serialized.HeaderIm pl.readObject(HeaderImpl.java:102) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [ERROR] at java.lang.reflect.Method.invoke(Method.java:592) [ERROR] at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass. java:946) [ERROR] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.ja va:1812) [ERROR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStrea m.java:1719) [ERROR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java: 1305) [ERROR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:3 48) [ERROR] at org.jboss.internal.soa.esb.message.format.serialized.MessageI mpl.readExternal(MessageImpl.java:219) [ERROR] at java.io.ObjectInputStream.readExternalData(ObjectInputStream. java:1756) [ERROR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStrea m.java:1717) [ERROR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java: 1305) [ERROR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:3 48) [ERROR] at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.j ava:154) [ERROR] at org.jboss.messaging.core.impl.message.MessageSupport.getPaylo ad(MessageSupport.java:246) [ERROR] at org.jboss.jms.message.JBossObjectMessage.getObject(JBossObjec tMessage.java:125) [ERROR] at org.jboss.jms.message.ObjectMessageProxy.getObject(ObjectMess ageProxy.java:64) [ERROR] at org.jboss.internal.soa.esb.couriers.helpers.JmsComposer.compo se(JmsComposer.java:71) [ERROR] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCour ier.java:461) [ERROR] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup( TwoWayCourierImpl.java:228) [ERROR] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup( TwoWayCourierImpl.java:204) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDel ivery(ServiceInvoker.java:675) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200 (ServiceInvoker.java:569) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.j ava:359) [ERROR] at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceIn voker.java:219) [ERROR] at br.com.webb.soa.invoker.GenericServiceInvoker.invokeSyncServi ce(GenericServiceInvoker.java:66) [ERROR] at br.com.webb.medicao.server.MedicaoServiceImpl.getSumario(Medi caoServiceImpl.java:209) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [ERROR] at java.lang.reflect.Method.invoke(Method.java:592) [ERROR] at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RP C.java:562) [ERROR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCa ll(RemoteServiceServlet.java:188) [INFO] [ERROR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPo st(RemoteServiceServlet.java:224) I have already tried to change the message type to JBOSS_XML unsucefully. Can someone help me in fixing this? -- 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

14 years, 4 months

2
1
0 / 0

← Newer
1
2
3
4
5
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2011