September 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3437) EBWS endpoints missing in jUDDI when there are no listener definitions in jboss-esb.xml.

by Marek Baluch (JIRA)

EBWS endpoints missing in jUDDI when there are no listener definitions in jboss-esb.xml. ---------------------------------------------------------------------------------------- Key: JBESB-3437 URL: https://jira.jboss.org/browse/JBESB-3437 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta, Web Services Affects Versions: 4.8, 4.7 CP2, 4.7 CP1 Reporter: Marek Baluch For ESB to publish EBWS services to jUDDI there must a provider and listener defined in jboss-esb.xml for that service. IMHO this may be valid for non EBWS endpoints but as soon as a service becomes EBWS then it's WSDL contract should be exposed no matter what. -- 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

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2218) Exception "javax.jms.IllegalStateException: Cannot find session with id ..." during clustered/failover testing.

by Pavel Macik (JIRA)

Exception "javax.jms.IllegalStateException: Cannot find session with id ..." during clustered/failover testing. ---------------------------------------------------------------------------------------------------------------- Key: JBESB-2218 URL: https://jira.jboss.org/jira/browse/JBESB-2218 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 CP4 Environment: Linux 2.6.18-53.1.14.el5xen, x86_64, SOA-P 4.2.0 CP03 CR5, "production" based configuration, jdk1.5.0_12 Reporter: Pavel Macik Performing cluster / failover test following this steps: http://jboss-wiki.brq.redhat.com/Cluster/failover_tests . I have to set the Clustered attribute of the org.jboss.messaging.core.jmx.MessagingPostOfficeService mbean to "true", if dbinstall tool doesn't. When I remove Failover2(1).esb archive (according to the 15 (17) step) the following exceptions appears: 2008-12-04 15:32:32,491 ERROR [org.jboss.messaging.util.ExceptionUtil] ConnectionEndpoint[vb4-md4bibof-1-0uf7ibof-qr6sza-a4wya] sendTransaction [sb9-vfvbibof-1-0uf7ibof-qr6sza-a4wya] javax.jms.IllegalStateException: Cannot find session with id ad4-sd4bibof-1-0uf7ibof-qr6sza-a4wya at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489) ... 2008-12-04 15:32:32,498 ERROR [org.jboss.jms.client.container.ClosedInterceptor] ClosedInterceptor.ClientSessionDelegate[ad4-sd4bibof-1-0uf7ibof-qr6sza-a4wya]: method redeliver() did not go through, the interceptor is CLOSED 2008-12-04 15:32:32,499 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] Failed to commit session transaction javax.jms.IllegalStateException: The object is closed at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:157) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) -- 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

13 years, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-3354) samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway

by Len DiMaggio (JIRA)

samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway ------------------------------------------------------------------------------------------------------ Key: JBESB-3354 URL: https://jira.jboss.org/browse/JBESB-3354 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.8 Reporter: Len DiMaggio Priority: Minor samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway samples/quickstarts/http_gateway/readme.txt: service. Will return some details about the request. This Service's <http-listener> does not refer -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3471) CamelGateway does not support JNDI lookups

by David Ward (JIRA)

CamelGateway does not support JNDI lookups ------------------------------------------ Key: JBESB-3471 URL: https://jira.jboss.org/browse/JBESB-3471 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.9 Reporter: David Ward Assignee: David Ward One of the more common Camel components that a user might want to employ is the JMS Component: http://camel.apache.org/jms.html To use this component, one needs to specify the JMS ConnectionFactory. There is a parameter called "connectionFactory", but unfortunately, it does not take a String, but an actual javax.jms.ConnectionFactory. This would be fine if we depended on Spring to wire together the Camel components, but we don't want to enforce that dependency. In the absense of a parameter that simply takes the JNDI name of the ConnectionFactory and does the lookup for us, the CamelGateway should register a Camel TypeConverter that can convert from String (the JNDI name) to a ConnectionFactory (via JNDI lookup). Without this fix, users cannot use the JMS Component. -- 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

13 years, 6 months

3
18
0 / 0

[JBoss JIRA] Created: (JBESB-2450) Integrate quickstarts into the CI system (again)

by Kevin Conner (JIRA)

Integrate quickstarts into the CI system (again) ------------------------------------------------ Key: JBESB-2450 URL: https://jira.jboss.org/jira/browse/JBESB-2450 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 A lot of quickstarts have been added to the codebase without being integrated into the CI system. We need to identify those which are not integrated and look at adding tests for them. -- 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

13 years, 6 months

3
17
0 / 0

[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

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3487) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

by Toshiya Kobayashi (JIRA)

ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB -------------------------------------------------------------------------------------------------------------- Key: JBESB-3487 URL: https://jira.jboss.org/browse/JBESB-3487 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP4, 4.7 CP2 Reporter: Toshiya Kobayashi Log events won't be saved when they are triggered by Timer. This issue was fixed in JobExecutorThread ( JBPM-1015 ). But regarding SOA integration, only org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand includes the fix. org.jboss.soa.esb.services.jbpm.integration.job.ExecuteTimerCommand should follow. # Snippet from org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand // register process instance for automatic save // see https://jira.jboss.org/jira/browse/JBPM-1015 ProcessInstance processInstance = job.getProcessInstance(); jbpmContext.addAutoSaveProcessInstance(processInstance); -- 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

13 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-3201) javax.jms.IllegalStateException thrown when invoking proxied service with SyncServiceInvoker

by Boris Belovic (JIRA)

javax.jms.IllegalStateException thrown when invoking proxied service with SyncServiceInvoker -------------------------------------------------------------------------------------------- Key: JBESB-3201 URL: https://jira.jboss.org/jira/browse/JBESB-3201 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Boris Belovic Attachments: ssi.tar.bz2 java.lang.reflect.UndeclaredThrowableException (with javax.jms.IllegalStateException as cause) was thrown when invoking service with SyncServiceInvoker action. SyncServiceInvoker action was configured with suspendTransaction property set to true. The exception stacktrace follows: java.lang.reflect.UndeclaredThrowableException at $Proxy246.getXAResource(Unknown Source) at org.jboss.internal.soa.esb.rosetta.pooling.JmsXASession.associate(JmsXASession.java:172) at org.jboss.internal.soa.esb.rosetta.pooling.JmsXASession$AssociationHandler.invoke(JmsXASession.java:244) at $Proxy243.close(Unknown Source) at sun.reflect.GeneratedMethodAccessor511.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession$ExceptionHandler.invoke(JmsSession.java:479) at $Proxy243.close(Unknown Source) at org.jboss.internal.soa.esb.couriers.JmsCourier.cleanup(JmsCourier.java:115) at org.jboss.soa.esb.couriers.CourierUtil.cleanCourier(CourierUtil.java:242) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.cleanup(TwoWayCourierImpl.java:237) at org.jboss.soa.esb.couriers.CourierUtil.cleanCourier(CourierUtil.java:242) at org.jboss.soa.esb.listeners.message.MessageAwareListener.cleanCourier(MessageAwareListener.java:507) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:344) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:253) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:619) Caused by: javax.jms.IllegalStateException: The object is closed at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:157) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.jms.client.delegate.ClientSessionDelegate$getXAResource_5045584642641131496.invokeNext(ClientSessionDelegate$getXAResource_5045584642641131496.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.getXAResource(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.getXAResource(JBossSession.java:389) at sun.reflect.GeneratedMethodAccessor516.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession$ExceptionHandler.invoke(JmsSession.java:479) Standalone example for reproducing is attached, the archive with example also contains log from server. -- 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

13 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-3449) Service Invoker load balance policy that prefers local EPRs

by Kevin Conner (JIRA)

Service Invoker load balance policy that prefers local EPRs ----------------------------------------------------------- Key: JBESB-3449 URL: https://jira.jboss.org/browse/JBESB-3449 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.4 CP5 -- 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

13 years, 7 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-1914) HttpRouter does not support unwrap/wrap switch

by Jiri Pechanec (JIRA)

HttpRouter does not support unwrap/wrap switch ---------------------------------------------- Key: JBESB-1914 URL: https://jira.jboss.org/jira/browse/JBESB-1914 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 Athough the HttpRouter is derived from abstract router it does not use switch wrap/unwrap. I guess it was accidentaly omitted. -- 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

13 years, 7 months

5
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2010