October 2010 - esb-issues - Jboss List Archives

[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

15 years, 3 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

15 years, 3 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

15 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3501) Cache service hashcode

by Kevin Conner (JIRA)

Cache service hashcode ---------------------- Key: JBESB-3501 URL: https://jira.jboss.org/browse/JBESB-3501 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.9 CP1 Cache hashcode for reuse, minor change. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3500) Remove JBoss Remoting HttpRouter documentation

by Magesh Bojan (JIRA)

Remove JBoss Remoting HttpRouter documentation ---------------------------------------------- Key: JBESB-3500 URL: https://jira.jboss.org/browse/JBESB-3500 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 Reporter: Magesh Bojan Assignee: Magesh Bojan Priority: Optional Fix For: 4.9 CP1 Remove section 12.5.3.1 in Programmers Guide, as this class no longer exists. -- 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, 3 months

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

15 years, 3 months

5
14
0 / 0

[JBoss JIRA] Created: (JBESB-3498) Quickstart security_saml has problems with different versions of jbossws

by Gary Brown (JIRA)

Quickstart security_saml has problems with different versions of jbossws ------------------------------------------------------------------------ Key: JBESB-3498 URL: https://jira.jboss.org/browse/JBESB-3498 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9 Environment: JBossAS 3.1.0.GA, ESB 4.9 Reporter: Gary Brown The security_saml example works fine when run within AS+ESB without upgrading the web service stack. However, if the web service stack is upgraded to jbossws-native 3.2.2.GA, the server console has the following exception: 10:13:38,390 WARN [EnvelopeBuilderDOM] Ignore child type: 3 10:13:38,391 WARN [EnvelopeBuilderDOM] Ignore child type: 3 10:13:38,394 ERROR [InjectionException] Cannot lookup JNDI context: java:comp/env/ javax.naming.NameNotFoundException: env not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.lookup(NamingServer.java:396) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:833) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.wsf.common.injection.InjectionHelper.getContext(InjectionHelper.java:230) at org.jboss.wsf.common.injection.InjectionHelper.injectResourceAnnotatedAccessibleObjects(InjectionHelper.java:307) at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:108) at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.addHandler(HandlerResolverImpl.java:174) at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.initHandlerChain(HandlerResolverImpl.java:152) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:89) at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:172) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.soa.esb.actions.soap.NativeSOAPProcessor.process(NativeSOAPProcessor.java:108) at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:118) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.access$000(ActionProcessingPipeline.java:84) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline$1.run(ActionProcessingPipeline.java:1021) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline$1.run(ActionProcessingPipeline.java:1019) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:454) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 10:13:38,396 ERROR [SOAPFaultHelperJAXWS] SOAP request exception org.jboss.wsf.common.injection.InjectionException: Cannot lookup JNDI context: java:comp/env/ at org.jboss.wsf.common.injection.InjectionException.rethrow(InjectionException.java:106) at org.jboss.wsf.common.injection.InjectionHelper.getContext(InjectionHelper.java:234) at org.jboss.wsf.common.injection.InjectionHelper.injectResourceAnnotatedAccessibleObjects(InjectionHelper.java:307) at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:108) at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.addHandler(HandlerResolverImpl.java:174) at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.initHandlerChain(HandlerResolverImpl.java:152) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:89) at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:172) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.soa.esb.actions.soap.NativeSOAPProcessor.process(NativeSOAPProcessor.java:108) at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:118) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.access$000(ActionProcessingPipeline.java:84) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline$1.run(ActionProcessingPipeline.java:1021) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline$1.run(ActionProcessingPipeline.java:1019) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:454) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.naming.NameNotFoundException: env not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.lookup(NamingServer.java:396) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:833) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.wsf.common.injection.InjectionHelper.getContext(InjectionHelper.java:230) And if jbossws-native 3.3.1.GA is installed, the deploy script fails: /home/gbrown/NotBackedUp/testing/riftsaw/current/jbossesb-4.9/samples/quickstarts/conf/base-build.xml:667: **** DEPLOYMENT FAILED... Sorry, this Quickstart requires a modified JBoss Webservice container, please refer to the 'Configuring Webservice Integration' section of the Administration Guide. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3499) upgrade jbossws support to latest public versions.

by Kevin Conner (JIRA)

upgrade jbossws support to latest public versions. -------------------------------------------------- Key: JBESB-3499 URL: https://jira.jboss.org/browse/JBESB-3499 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.9 Reporter: Kevin Conner -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3355) Relax Http Header Validation to just "not null"

by Stelios Koussouris (JIRA)

Relax Http Header Validation to just "not null" ----------------------------------------------- Key: JBESB-3355 URL: https://jira.jboss.org/browse/JBESB-3355 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 CP1 Reporter: Stelios Koussouris The code http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_7_CP2_ER4/... checks AssertArgument.isNotNullAndNotEmpty(name, "name"); AssertArgument.isNotNullAndNotEmpty(value, "value"); However, there can be occasions where the value is empty. The condition should be relaxed to "not null" (not sure if it could ever be null) -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3491) Reintroduce deployment state in MBean

by Kevin Conner (JIRA)

Reintroduce deployment state in MBean ------------------------------------- Key: JBESB-3491 URL: https://jira.jboss.org/browse/JBESB-3491 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.9 CP1 We should reintroduce the deployment state for AS5, present in AS4 deployments, so that the state can be queried via the JMX console. -- 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, 3 months

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