February 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3179) "org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction" exception occures over and over again and flood server

by Pavel Macik (JIRA)

"org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction" exception occures over and over again and flood server --------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3179 URL: https://jira.jboss.org/jira/browse/JBESB-3179 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.7 CP1 Reporter: Pavel Macik Priority: Critical See SOA-1942... -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3174) Unable to retreive services using jUDDI client with JAXWSTransport.

by Kevin Conner (JIRA)

Unable to retreive services using jUDDI client with JAXWSTransport. ------------------------------------------------------------------- Key: JBESB-3174 URL: https://jira.jboss.org/jira/browse/JBESB-3174 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 We need to expose the endpoints differently -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3176) Possibility of XsltAction creating an XMLReader on every invocation, which can negatively effect performance

by Tom Fennelly (JIRA)

Possibility of XsltAction creating an XMLReader on every invocation, which can negatively effect performance ------------------------------------------------------------------------------------------------------------- Key: JBESB-3176 URL: https://jira.jboss.org/jira/browse/JBESB-3176 Project: JBoss ESB Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 CP2 Reporter: Tom Fennelly Fix For: 4.8 Pavel noticed that XsltAction was now 29% slower than the SmooksAction+Xslt (Smooks v1.2.5), which seemed strange... if anything XsltAction should be marginally faster. Looking at the code, looks like XsltAction may be creating an XMLReader on each invocation (in the ValidationHandler). This might account for the difference. WOuld need to profile it to be sure. (Also... in light of the system property fix found for Xalan.... does XsltAction really need to pool transformers?) -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3175) Hibernate Interceptor onLoad event - fields in restored object contain null value.

by Boris Belovic (JIRA)

Hibernate Interceptor onLoad event - fields in restored object contain null value. ---------------------------------------------------------------------------------- Key: JBESB-3175 URL: https://jira.jboss.org/jira/browse/JBESB-3175 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Boris Belovic Attachments: hibernate_mySQL.tar.bz2 I wrote a service with Hibernate transport (Hibernate listener) and I am listening for onLoad and onSave events. When saving simple POJO (Person.java) into database, this object is correctly intercepted and passed to the message body. (I am using mySQL 5.1). 14:29:07,059 INFO [MyAction] @@@ Found person object in the intercepted message! @@@ 14:29:07,059 INFO [MyAction] [Id: 1, Name: John Smith] When retrieving object from DB, object is passed to the message but its fields have null value (only Id field contains correct value). 14:42:07,583 INFO [MyAction] @@@ Found person object in the intercepted message! @@@ 14:42:07,583 INFO [MyAction] [Id: 1, Name: null null] -- 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

14 years, 9 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-3173) Invalid pattern processing in HttpContentTypeUtil and jbossesb-properties.xml for SOAP messages

by Jiri Pechanec (JIRA)

Invalid pattern processing in HttpContentTypeUtil and jbossesb-properties.xml for SOAP messages ----------------------------------------------------------------------------------------------- Key: JBESB-3173 URL: https://jira.jboss.org/jira/browse/JBESB-3173 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP1 Reporter: Jiri Pechanec Priority: Critical 1) Support for application application/soap+xml standard content ype is missing 2) If the header also contains charset, then pattern matching does not work -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3168) HttpProtocol references static protocol

by Kevin Conner (JIRA)

HttpProtocol references static protocol --------------------------------------- Key: JBESB-3168 URL: https://jira.jboss.org/jira/browse/JBESB-3168 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 It then appears to rely on this given the comment // these lines have to happen after registerProtocol, otherwise they pick up the wrong static value Need to find out why this is relying on the static and fix the race (or remove). ProxyHost pulls Protocol.getProtocol("http") but the default should be sufficient for HTTP and HTTPS proxying. -- 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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3021) SOAPProxies on different services shares configuration

by Jiri Pechanec (JIRA)

SOAPProxies on different services shares configuration ------------------------------------------------------ Key: JBESB-3021 URL: https://jira.jboss.org/jira/browse/JBESB-3021 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: ER4 Reporter: Jiri Pechanec Priority: Critical Attachments: soapproxy-breaker.zip If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then the configuration is shared between them. Check the attached example 1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The execution is performed correctly and target service is invoked. 2) Enable Proxy-breaker service but disable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. Although you are invoking the first service the invocation will fail due to strict SSL setting. 3) Enable Proxy-breaker service and enable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. The execution is performed correctly and target service is invoked. It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy settings of Proxy service. -- 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

14 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-3166) non-http or https import schemes' (file, classpath, internal) locations not rewritten by SOAPProxyWsdlLoader

by David Ward (JIRA)

non-http or https import schemes' (file, classpath, internal) locations not rewritten by SOAPProxyWsdlLoader ------------------------------------------------------------------------------------------------------------ Key: JBESB-3166 URL: https://jira.jboss.org/jira/browse/JBESB-3166 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Fix For: 4.7 CP1 Imports were only being rewritten if the protocol was http or https. If it was file, classpath or internal, the imports were simply left alone - not really that they were "malformed" *by* anything. There are two parts to the fix: 1) rewrite the imports by prepending the import locations with the appropriate scheme, 2) add the scheme check *and* relative import fixing to the import recursion. -- 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

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3161) WSDL/schema import locations improperly rewritten by HttpSOAPProxyWsdlLoader in contract application when using JBRGateway+HTTP

by David Ward (JIRA)

WSDL/schema import locations improperly rewritten by HttpSOAPProxyWsdlLoader in contract application when using JBRGateway+HTTP ------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3161 URL: https://jira.jboss.org/jira/browse/JBESB-3161 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Fix For: 4.7 CP1 The only two endpoints we expose contract information for via the contract JSP application are both HTTP protocol based: one using the new HTTPGateway, and one using the JBossRemotingGateway/HTTP. JBESB-3076 fixed an issue where the imports within the WSDL or XSD were not working properly. However, whereas many different import scenarios were tested (see that jira's comments), all testing was done using the HTTPGateway. Upon further testing, it was discovered that the WSDL/schema import locations are being improperly rewritten *when* using the JBossRemotingGateway/HTTP instead. -- 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

14 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-2947) InternalSOAPProxyWsdlLoader hangs on ESB restart

by David Ward (JIRA)

InternalSOAPProxyWsdlLoader hangs on ESB restart ------------------------------------------------ Key: JBESB-2947 URL: https://jira.jboss.org/jira/browse/JBESB-2947 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Fix For: 4.7 Tom F. and I noticed a problem with the InternalSOAPProxyWsdlLoader's use of JBossWS's internal SPI, where it is *still* using an http URLConnection under-the-hood. This is an issue since on restart, Tomcat's http connector is not be available yet. This causes the main thread of the boot-up to hang. -- 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

14 years, 10 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2010