October 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3858) Uncommenting GenericPipelineInterceptors in jboss-esb-properties.xml causes NullPointerException at startup

by Tadayoshi Sato (JIRA)

Tadayoshi Sato created JBESB-3858: ------------------------------------- Summary: Uncommenting GenericPipelineInterceptors in jboss-esb-properties.xml causes NullPointerException at startup Key: JBESB-3858 URL: https://issues.jboss.org/browse/JBESB-3858 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Reporter: Tadayoshi Sato When the following "interceptors" properties in jbossesb-properties.xml are uncommented, the JBoss ESB throws java.lang.NullPointerException and fails to start up. {code:xml} <properties name="interceptors"> <property name="org.jboss.soa.esb.pipeline.failure.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/> <property name="org.jboss.soa.esb.pipeline.instantiate.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/> <property name="org.jboss.soa.esb.pipeline.start.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/> <property name="org.jboss.soa.esb.pipeline.end.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/> </properties> {code} The error stacktrace is as follows: {code} 2012-10-15 14:50:42,708 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.esb.vfsfile:/opt/jboss-soa-p-5.3.0/jboss-as/server/default/deploy/jbossesb.esb/ state=Create java.lang.RuntimeException: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected exception while instantiating managed instance at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:185) at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:223) at org.jboss.Main$1.run(Main.java:574) at java.lang.Thread.run(Thread.java:722) Caused by: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected exception while instantiating managed instance at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:166) at org.jboss.soa.esb.listeners.LifecycleUtil.getListeners(LifecycleUtil.java:76) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:124) ... 63 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:162) ... 65 more Caused by: java.lang.NullPointerException at org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor.processMessage(GenericPipelineInterceptor.java:33) at org.jboss.soa.esb.listeners.message.InterceptorManager.interceptInstantiate(InterceptorManager.java:126) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:381) at org.jboss.soa.esb.listeners.ScheduleListener.<init>(ScheduleListener.java:90) ... 70 more 2012-10-15 14:50:42,710 INFO [org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment] (main) Destroying 'jbossesb.esb' {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
11
0 / 0

[JBoss JIRA] (JBESB-3871) Wrong CSS in the modal dialogue of downloads2 paragraph

by David Hladky (JIRA)

David Hladky created JBESB-3871: ----------------------------------- Summary: Wrong CSS in the modal dialogue of downloads2 paragraph Key: JBESB-3871 URL: https://issues.jboss.org/browse/JBESB-3871 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Hladky Assignee: Cheyenne Weaver There has been a problem [here|https://engineering.redhat.com/rt/Ticket/Display.html?id=175178], that forced me to remove id of the dialog. The problem was the id is supposed to be unique, which was not the case and when both downloads and downloads2 paragraphs were on the same page, it caused the first one not to work at all. This is now fixed, however the styles of the popup dialogue are supposed to use #dialog as the selector, but that is no more possible. Try the first and the last download paragraph and you will see the difference. We need to find another way to apply the styles. See the page, where it happens https://www.jboss.org/drools/downloads.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3870) Need to create the build/lib directory

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3870: ------------------------------------- Summary: Need to create the build/lib directory Key: JBESB-3870 URL: https://issues.jboss.org/browse/JBESB-3870 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Fix For: 4.11 CP2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-3597) DLQ handling on JCA side causes duplicate redelivery to DLQ

by Toshiya Kobayashi (JIRA)

DLQ handling on JCA side causes duplicate redelivery to DLQ ----------------------------------------------------------- Key: JBESB-3597 URL: https://issues.jboss.org/browse/JBESB-3597 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Examples Affects Versions: 4.9 CP1 Reporter: Toshiya Kobayashi JCA DLQ handling interferes with JBM DLQ handling and may end up with unexpected results. You can find discussions in JBAS-7465 and JBPAPP-3352. In ESB, you can reproduce the issue with jms_transacted quickstart. ==================== - Edit jboss-esb.xml to set dLQMaxResent=3 <property name="dLQMaxResent" value="3"/> - ant deplpy - ant runtest The message will be sent to DLQ. - Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console You will see MessageCount=1 - Check jboss.esb.quickstart.destination:name=quickstart_jms_transacted_Request_esb,service=Queue via jmx-console You will see MessageCount=1, DeliveringCount=1 though the message has been sent to DLQ. - ant deploy Redeploying the queue causes re-delivering the message to DLQ - Check jboss.messaging.destination:name=DLQ,service=Queue via jmx-console You will see MessageCount=2 (duplicate). ===================== Looking at JBAS-7465 and JBPAPP-3352, there is less chance to resolve the root issue from AS/JBM side. I filed this JIRA for something we can address from ESB side. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] (JBESB-3866) jbpm5 integration : Allow mappings from different parts of the message

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3866: ------------------------------------- Summary: jbpm5 integration : Allow mappings from different parts of the message Key: JBESB-3866 URL: https://issues.jboss.org/browse/JBESB-3866 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Fix For: 4.11 CP2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
8
0 / 0

[JBoss JIRA] (JBESB-3869) Broken links for JBoss ESB Documentation

by David Hladky (JIRA)

David Hladky created JBESB-3869: ----------------------------------- Summary: Broken links for JBoss ESB Documentation Key: JBESB-3869 URL: https://issues.jboss.org/browse/JBESB-3869 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Hladky The last link on http://www.jboss.org/jbossesb/docs is broken. Also if you hover the mouse over the links, the background colour is not reverted back. I originally thought it is a problem of some Magnolia paragraph, but it is a hard coded paragraph. Inline styles have been used. Cheyenne changed them to normal style, but did not published the changes to public instance in case you want to check the colours first. I created this issue as a reaction on: https://engineering.redhat.com/rt/Ticket/Display.html?id=172304 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3867) Create javadoc JAR for jbpm5 integration classes

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3867: ------------------------------------- Summary: Create javadoc JAR for jbpm5 integration classes Key: JBESB-3867 URL: https://issues.jboss.org/browse/JBESB-3867 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP2 Create javadoc JAR for jbpm5 integration classes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] (JBESB-3865) AbstractBpm5Action is registering handlers too freely

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3865: ------------------------------------- Summary: AbstractBpm5Action is registering handlers too freely Key: JBESB-3865 URL: https://issues.jboss.org/browse/JBESB-3865 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Explanation from Rick Wagner's BZ : AbstractBpm5Action is doing some handler registration for *each* process instance start and service callback: .... ksession.getWorkItemManager().registerWorkItemHandler("JBossESB", esbhandler); ksession.getWorkItemManager().registerWorkItemHandler("ESBAction", actionhandler); ksession.getWorkItemManager().registerWorkItemHandler("Human Task", khandler); 'khandler' in particular is an instance of CommandBasedHornetQWSHumanTaskHandler by default. So when the user goes to close a task, all those handlers fire (JPA trips up, too): 012-08-22 12:32:06,006 INFO [STDOUT] (Thread-32) Notification of completed task 132 2012-08-22 12:32:06,017 INFO [STDOUT] (Thread-34) Notification of completed task 132 2012-08-22 12:32:06,025 INFO [STDOUT] (Thread-35) Notification of completed task 132 2012-08-22 12:32:06,033 INFO [STDOUT] (Thread-36) Notification of completed task 132 2012-08-22 12:32:06,042 INFO [STDOUT] (Thread-37) Notification of completed task 132 2012-08-22 12:32:06,049 INFO [STDOUT] (Thread-37) Notification of completed task 132 2012-08-22 12:32:06,056 INFO [STDOUT] (Thread-38) Notification of completed task 132 2012-08-22 12:32:06,063 INFO [STDOUT] (Thread-39) Notification of completed task 132 2012-08-22 12:32:06,069 INFO [STDOUT] (Thread-40) Notification of completed task 132 2012-08-22 12:32:06,076 INFO [STDOUT] (Thread-41) Notification of completed task 132 2012-08-22 12:32:06,082 INFO [STDOUT] (Thread-41) Notification of completed task 132 2012-08-22 12:32:05,985 INFO [STDOUT] (Thread-31) Notification of completed task 132 2012-08-22 12:32:05,998 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (Thread-31) Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#44] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1782) ....... at org.jbpm.task.service.hornetq.CommandBasedHornetQWSHumanTaskHandler$GetCompletedTaskResponseHandler.execute(CommandBasedHornetQWSHumanTaskHandler.java:273) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] (JBESB-3864) Incorporate camel gateway esbschedule quickstart

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3864: ------------------------------------- Summary: Incorporate camel gateway esbschedule quickstart Key: JBESB-3864 URL: https://issues.jboss.org/browse/JBESB-3864 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 >From Robert Balent : https://bugzilla.redhat.com/show_bug.cgi?id=821672 I think it would be great to have quickstart to "esbschedule" feature of CamelGateway[1]. This feature invokes Camel endpoints which can't be invoked externally. For example Class gateway[2], Http gateway[3], SQL gateway[4]. So the Camel gateway url will look like this: <from uri="esbschedule:5000:class:org.jboss.soa.esb.samples.quickstart.camelesbschedule.SimpleBean?method=getOutput"/> This quickstart invokes bean's method "getOutput" every 5 seconds and prints output to server log. I'm attaching complete quickstart which can be included. [1] https://community.jboss.org/wiki/CamelGateway [2] http://camel.apache.org/class.html [3] http://camel.apache.org/http.html [4] http://camel.apache.org/sql-component.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3860) Incorporate camel gateway esbschedule feature

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3860: ------------------------------------- Summary: Incorporate camel gateway esbschedule feature Key: JBESB-3860 URL: https://issues.jboss.org/browse/JBESB-3860 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

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