October 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3351) ConcurrentModificationException on PortReference

by Toshiya Kobayashi (JIRA)

ConcurrentModificationException on PortReference ------------------------------------------------ Key: JBESB-3351 URL: https://jira.jboss.org/browse/JBESB-3351 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP3 Reporter: Toshiya Kobayashi org.jboss.soa.esb.addressing.PortReference throws ConcurrentModificationException. 2010-06-10 07:24:30,255 INFO [xxx.XXX] FaultMessageException org.jboss.soa.esb.couriers.FaultMessageException: java.util.ConcurrentModificationException org.jboss.soa.esb.couriers.FaultMessageException: java.util.ConcurrentModificationException at org.jboss.soa.esb.listeners.message.errors.Factory.createExceptionFromFault(Factory.java:50) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:207) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:584) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:493) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:343) at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:204) at xxx.XXX.appCheckin(XXX.java:147) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:102) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:223) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:421) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:286) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:196) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.util.ConcurrentModificationException at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761) at java.util.LinkedList$ListItr.next(LinkedList.java:696) at org.jboss.soa.esb.addressing.PortReference.extendedToString(PortReference.java:208) at org.jboss.soa.esb.addressing.eprs.InVMEpr.toString(InVMEpr.java:261) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.jboss.soa.esb.addressing.Call.toString(Call.java:287) at org.jboss.internal.soa.esb.message.format.xml.HeaderImpl.toString(HeaderImpl.java:77) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:613) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) ... 1 more I guess org.jboss.soa.esb.addressing.PortReference._extensions should be protected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3515) Upgrade PicketLink to 1.0.4.final

by Daniel Bevenius (JIRA)

Upgrade PicketLink to 1.0.4.final --------------------------------- Key: JBESB-3515 URL: https://jira.jboss.org/browse/JBESB-3515 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3512) Fix uddi_v3replication.xsd within juddiv3.war

by Kevin Conner (JIRA)

Fix uddi_v3replication.xsd within juddiv3.war --------------------------------------------- Key: JBESB-3512 URL: https://jira.jboss.org/browse/JBESB-3512 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3513) confilct between jboss esb and infinispan hotrod client

by Samuele Dell'Angelo (JIRA)

confilct between jboss esb and infinispan hotrod client ------------------------------------------------------- Key: JBESB-3513 URL: https://jira.jboss.org/browse/JBESB-3513 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.8 Environment: jboss 5.1.0.GA with jboss esb 4.8 deployed on it. Reporter: Samuele Dell'Angelo infinispan hotrod client uses common-pool 1.5.4 and it conflicts with spring.esb that uses commons-pool 1.3. If you try to deploy a project that include infinispan hotrod client 4.1.0.FINAL, you will get an exception like this one: java.lang.NoSuchFieldError: _lifo at org.infinispan.client.hotrod.impl.transport.tcp.PropsKeyedObjectPoolFactory.<init>(PropsKeyedObjectPoolFactory.java:32) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:51) at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:282) at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:224) at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:231) at it.seat.igluCache.infinispan.loaders.InfinispanServletListener.contextInitialized(InfinispanServletListener.java:31) I've found a workaround: substitute commons-pool-1.3.jar with commons-pool-1.5.4.jar in in spring.esb directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3510) SOAPProxy handles WSDL with import incorrectly when proxying webservice through internal://

by Boris Belovic (JIRA)

SOAPProxy handles WSDL with import incorrectly when proxying webservice through internal:// ------------------------------------------------------------------------------------------- Key: JBESB-3510 URL: https://jira.jboss.org/browse/JBESB-3510 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9 Environment: SOA-P 5.1 ER2, ESB version 4.9 Reporter: Boris Belovic SOAPProxy handles WSDL import incorrectly when proxying through internal:// keyword. I have WAR file with two webservices, one of which uses WSDL import - it imports external XSD schema. When I try to display WSDL of the webservice without import through SOAPProxy URL, I've got WSDL of the webservice with import This is the URL for WSDL document of the proxied service without import http://localhost:8080/Contract_publisher_soapproxy/http/Proxy_Basic/inter... but this URL refers to WSDL of the service with import (it should display WSDL of the webservice without import) This URL is for webservice with WSDL import and it displays correct WSDL http://localhost:8080/Contract_publisher_soapproxy/http/Proxy_Basic/inter... The result is that both URLs refers to WSDL with import element, but first URL should refer to WSDL of the service without import element and second URL should refer to the WSDL of the service with WSDL import element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3509) Error message seen on the console during bootup 'ERROR [JBossDeployerUtil] Could not create directory ...'

by Kevin Conner (JIRA)

Error message seen on the console during bootup 'ERROR [JBossDeployerUtil] Could not create directory ...' ---------------------------------------------------------------------------------------------------------- Key: JBESB-3509 URL: https://jira.jboss.org/browse/JBESB-3509 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3507) juddi webservice service names now differ from those expected by JAXWSTransport

by Kevin Conner (JIRA)

juddi webservice service names now differ from those expected by JAXWSTransport ------------------------------------------------------------------------------- Key: JBESB-3507 URL: https://jira.jboss.org/browse/JBESB-3507 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The WSDL was previously changed to match the annotations in the juddi definitions but JAXWSTransport uses different names. I'm going to revert the wsdl names and override the annotation values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3504) quickstart_proxy_security fails with SunCertPathBuilderException: unable to find valid certification path to requested target

by Kevin Conner (JIRA)

quickstart_proxy_security fails with SunCertPathBuilderException: unable to find valid certification path to requested target ----------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3504 URL: https://jira.jboss.org/browse/JBESB-3504 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The reason this fails is that the factory configured in the Protocol is always replaced by the HttpClient when it executes the following line. hostconfig.setHost(uri); Any defined protocol-socket-factory is then ignored, with the factory defaulting to the underlying Protocol configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3505) ProtocolSocketFactoryBuilders cannot read an encrypted password from a file

by Kevin Conner (JIRA)

ProtocolSocketFactoryBuilders cannot read an encrypted password from a file --------------------------------------------------------------------------- Key: JBESB-3505 URL: https://jira.jboss.org/browse/JBESB-3505 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The keystore and truststore passwords must be specific in plain text. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3506) jBPM RetryExecutor does not revert idle interval after success

by Kevin Conner (JIRA)

jBPM RetryExecutor does not revert idle interval after success -------------------------------------------------------------- Key: JBESB-3506 URL: https://jira.jboss.org/browse/JBESB-3506 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2010