[EJB 3.0 Development] - Error on integrating ejb3-singleton 1.0.0-alpha-7
by Andrew Rubinger
Andrew Rubinger [http://community.jboss.org/people/ALRubinger] created the discussion
"Error on integrating ejb3-singleton 1.0.0-alpha-7"
To view the discussion, visit: http://community.jboss.org/message/552395#552395
--------------------------------------------------------------
Putting the new ejb3-async and ejb3-singleton into AS I'm now booting with the error below.
The errors can be reproduced by checking out:
https://svn.jboss.org/repos/jbossas/branches/TEMP_ALR_JBAS-8146_ASYNC_EJB... https://svn.jboss.org/repos/jbossas/branches/TEMP_ALR_JBAS-8146_ASYNC_EJB...
Ideas? :)
S,
ALR
15:35:20,398 ERROR [AbstractKernelController] Error installing to Configured: name=SingletonBeanTimeoutMethodStack$10 state=Instantiated: java.lang.RuntimeException: Error configuring property: forStack for SingletonBeanTimeoutMethodStack$10
at org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:112) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.ConfigureAction.setAttributes(ConfigureAction.java:85) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.ConfigureAction.installActionInternal(ConfigureAction.java:44) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer$MyBeanMetaDataDeployer.deploy(AbstractAopMetaDataDeployer.java:366) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer$MyBeanMetaDataDeployer.access$100(AbstractAopMetaDataDeployer.java:332) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.deployBeans(AbstractAopMetaDataDeployer.java:272) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.deploy(AbstractAopMetaDataDeployer.java:133) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer.deploy(AOPDeploymentAopMetaDataDeployer.java:46) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer.deploy(AOPDeploymentAopMetaDataDeployer.java:36) [jboss-aop-deployers-2.2.1.Alpha3.jar:2.2.1.Alpha3]
at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.deploy(AbstractSimpleVFSRealDeployer.java:56) [jboss-deployers-vfs-spi-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [jboss-deployers-spi-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [jboss-deployers-spi-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [jboss-deployers-impl-2.2.0.Alpha6.jar:2.2.0.Alpha6]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [jboss-as-system.jar:6.0.0-SNAPSHOT]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:148) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.profileservice.dependency.ProfileServiceController.activate(ProfileServiceController.java:188) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.AbstractProfileService.activateProfile(AbstractProfileService.java:170) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:117) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:89) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:97) [jboss-profileservice-core-0.1.0.Alpha1.jar:0.1.0.Alpha1]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:130) [jboss-as-system.jar:6.0.0-SNAPSHOT]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [jboss-as-system.jar:6.0.0-SNAPSHOT]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base-2.1.0-alpha-5.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base-2.1.0-alpha-5.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.IllegalArgumentException: No such property forStack for bean org.jboss.aop.microcontainer.beans.StackEntry available [class, binding, interceptorFactories, manager, stack, name]
at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:147) [jboss-reflect-2.2.0.Alpha7.jar:2.2.0.Alpha7]
at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedPropertyInfo(BeanInfoUtil.java:111) [jboss-reflect-2.2.0.Alpha7.jar:2.2.0.Alpha7]
at org.jboss.beans.info.plugins.BeanInfoUtil.getPropertyInfo(BeanInfoUtil.java:197) [jboss-reflect-2.2.0.Alpha7.jar:2.2.0.Alpha7]
at org.jboss.kernel.plugins.dependency.PropertyDispatchWrapper.execute(PropertyDispatchWrapper.java:77) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
at org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:107) [jboss-kernel-2.2.0.Alpha10.jar:2.2.0.Alpha10]
... 66 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552395#552395]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 8 months
[jBPM Development] - Error deleting SwimlaneImpl when a task has swimlanes and events with timer
by Jorge Ferreira
Jorge Ferreira [http://community.jboss.org/people/imjorge] created the discussion
"Error deleting SwimlaneImpl when a task has swimlanes and events with timer"
To view the discussion, visit: http://community.jboss.org/message/552375#552375
--------------------------------------------------------------
Hello,
+jBPM 4.3 running on a Windows XP SP2 box (same behavior for a Windows 7).+
We are having some difficulties configuring events together with timers and swimlanes. There seems to be a problem when jBPM tries to delete a swimlane when completeTask is called.
We configured a console application (attached to post) that reproduces this error. After running the application the following error is shown:
org.hibernate.exception.ConstraintViolationException: could not delete: org.jbpm.pvm.internal.task.SwimlaneImpl#15 org.jbpm.pvm.internal.task.SwimlaneImpl#15 http://community.jboss.org/message/552375#552375/... http://community.jboss.org/message/552375#552375/... at org.jbpm.pvm.internal.svc.TaskServiceImpl.completeTask(TaskServiceImpl.java:88) at com.test.Main.main(Main.java:83)Caused by: java.sql.SQLException: Integrity constraint violation FK_TASK_SWIML table: JBPM4_TASK in statement http://community.jboss.org/message/552375#552375/delete from JBPM4_SWIMLANE where DBID_=? and DBVERSION_=? http://community.jboss.org/message/552375#552375/delete from JBPM4_SWIMLANE where DBID_=? and DBVERSION_=? at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2551) ... 54 moreException in thread "main" org.hibernate.exception.ConstraintViolationException: could not delete: org.jbpm.pvm.internal.task.SwimlaneImpl#15 org.jbpm.pvm.internal.task.SwimlaneImpl#15 http://community.jboss.org/message/552375#552375/... http://community.jboss.org/message/552375#552375/... at org.jbpm.pvm.internal.svc.TaskServiceImpl.completeTask(TaskServiceImpl.java:88) at com.test.Main.main(Main.java:83)Caused by: java.sql.SQLException: Integrity constraint violation FK_TASK_SWIML table: JBPM4_TASK in statement http://community.jboss.org/message/552375#552375/delete from JBPM4_SWIMLANE where DBID_=? and DBVERSION_=? http://community.jboss.org/message/552375#552375/delete from JBPM4_SWIMLANE where DBID_=? and DBVERSION_=? at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2551) ... 54 more
The sequence of SQL statements (as logged by p6spy) are:
update JBPM4_TASK set DBVERSION_=3, NAME_='task2', DESCR_='', STATE_='open', SUSPHISTSTATE_='', ASSIGNEE_='b', FORM_='', PRIORITY_=0, CREATE_='2010-07-13 16:36:53.007', DUEDATE_='', PROGRESS_='', SIGNALLING_='false', EXECUTION_ID_='test3.7.task2', ACTIVITY_NAME_='task2', HASVARS_='false', SUPERTASK_='', EXECUTION_=12, PROCINST_=7, SWIMLANE_=15, TASKDEFNAME_='task2' where DBID_=14 and DBVERSION_=2
update JBPM4_EXECUTION set DBVERSION_=3, ACTIVITYNAME_='end1', PROCDEFID_='test3-1', HASVARS_='true', NAME_='', KEY_='', ID_='test3.7', STATE_='ended', SUSPHISTSTATE_='', PRIORITY_=0, HISACTINST_=11, PARENT_='', INSTANCE_=7, SUPEREXEC_='', SUBPROCINST_='' where DBID_=7 and DBVERSION_=2
update JBPM4_HIST_ACTINST set DBVERSION_=1, HPROCI_=7, TYPE_='task', EXECUTION_='test3.7.task2', ACTIVITY_NAME_='task2', START_='2010-07-13 16:36:53.007', END_='2010-07-13 16:39:56.991', DURATION_=183984, TRANSITION_='jbpm_no_task_outcome_specified_jbpm', NEXTIDX_=1, HTASK_=14 where DBID_=20 and DBVERSION_=0
update JBPM4_HIST_TASK set DBVERSION_=2, EXECUTION_='test3.7.task2', OUTCOME_='jbpm_no_task_outcome_specified_jbpm', ASSIGNEE_='b', PRIORITY_=0, STATE_='completed', CREATE_='2010-07-13 16:36:53.007', END_='2010-07-13 16:39:56.991', DURATION_=183984, NEXTIDX_=1 where DBID_=14 and DBVERSION_=1
update JBPM4_HIST_PROCINST set DBVERSION_=1, ID_='test3.7', PROCDEFID_='test3-1', KEY_='', START_='2010-07-13 16:36:52.337', END_='2010-07-13 16:39:57.101', DURATION_=184764, STATE_='ended', ENDACTIVITY_='end1', NEXTIDX_=1 where DBID_=7 and DBVERSION_=0
update JBPM4_SWIMLANE set EXECUTION_=null, NAME_=null where EXECUTION_=12
update JBPM4_PARTICIPATION set SWIMLANE_=null where SWIMLANE_=15
update JBPM4_EXECUTION set PARENT_=null, PARENT_IDX_=null where PARENT_=7
delete from JBPM4_PARTICIPATION where DBID_=17 and DBVERSION_=0
delete from JBPM4_PARTICIPATION where DBID_=16 and DBVERSION_=0
delete from JBPM4_SWIMLANE where DBID_=15 and DBVERSION_=1
The problem appears when the last line:
delete from JBPM4_SWIMLANE where DBID_=15 and DBVERSION_=1
is executed. This is caused because a record in table JBPM4_TASK still exists that points to the JBPM4_SWIMLANE record that is being deleted. In this case I would guess that the first SQL statement:
update JBPM4_TASK set DBVERSION_=3, NAME_='task2', DESCR_='', STATE_='open', SUSPHISTSTATE_='', ASSIGNEE_='b', FORM_='', PRIORITY_=0, CREATE_='2010-07-13 16:36:53.007', DUEDATE_='', PROGRESS_='', SIGNALLING_='false', EXECUTION_ID_='test3.7.task2', ACTIVITY_NAME_='task2', HASVARS_='false', SUPERTASK_='', EXECUTION_=12, PROCINST_=7, SWIMLANE_=15, TASKDEFNAME_='task2' where DBID_=14 and DBVERSION_=2
should have set swimlane_ to null so that the last delete would suceed. These SQL statements are automatically generated by Hibernate. Is there something missing from the hbm files that come with the jBPM distribution?
This only happens if the task has an <on event> with a timer configured and a swimlane. If the <timer> is commented or if the swimlane is replaced by the equivalent candidate-users the application does not fail with this error.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552375#552375]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 8 months
Re: [jboss-dev-forums] [JBoss ESB Development] - httprouter issues with GET/POST WADL Services and Web Routing
by jack lista
jack lista [http://community.jboss.org/people/jackalista] replied to the discussion
"httprouter issues with GET/POST WADL Services and Web Routing"
To view the discussion, visit: http://community.jboss.org/message/552344#552344
--------------------------------------------------------------
Hi Dave, saw your post and have been looking for similar facilities. I want to consume (what would be along the lines of message enhancing) RESTful services (*not* built with RESTEasy, essentially just HTTP calls that return XML) from within my action pipeline. I was looking for something *similar* to SOAPCLient, maybe called HTTPClient, but didn't find it. What is the best practice for consuming RESTful services from an action pipeline, can you shed some light here? Also, I'm curious about what happened to your HTTPRouter src, I don't really need a router but if there's nothing else perhaps I can make due. Also, I saw posts talking about abstracting an HTTPClient and making it a parent of SOAPCLient, has anything happened on that? Should I do it? Sorry to pelt you with questions, I've been having a hard time finding ino on this... thx!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552344#552344]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 8 months
[JBoss Remoting Development] - Remoting 2 bug: No reuse of ClientInvoker with params invokerDestructionDelay and socketFactoryClassName
by Patrick Speer
Patrick Speer [http://community.jboss.org/people/qliphot] created the discussion
"Remoting 2 bug: No reuse of ClientInvoker with params invokerDestructionDelay and socketFactoryClassName"
To view the discussion, visit: http://community.jboss.org/message/552308#552308
--------------------------------------------------------------
Hello,
I think I found a bug in InvokerRegistry.createClientInvoker(InvokerLocator locator, Map configuration) which leads to superflous instances of ClientInvoker (and therefore no reusing of an existing one).
I'm using JBoss AS 4.2.2.GA with JBoss Remoting 2.2.3-SP2. My ClientInvoker is configured via params with the following options:
<attribute name="socketFactoryClassName" isParam="true">package.of.MySSLSocketFactory</attribute>
<attribute name="invokerDestructionDelay" isParam="true">30000</attribute>
I was wondering why my application opened up new sockets for every remote call. The problem is, that for every call a new ClientInvoker is created and no reusing takes place:
In class InvokerRegistry.createClientInvoker line "ClientInvoker invoker = getRegisteredClientInvoker(locator, configuration);" checks for a suitable Invoker. If none is found, a new invoker is created and via "addRegisteredClientInvoker(invoker, l, configuration);" added to the holderList of the clientLocator. The problem is, that e.g. the constructor of RemoteClientInvoker modifies the configuration map. Then this modified map is passed to addRegisteredClientInvoker. But this map is used to identifiy the specific invoker in getRegisteredClientInvoker => so getRegisteredClientInvoker will never return an existing invoker.
Attached is a patch which fixes this problem. This all sounds a little bit confused, but I'm sure, if you have a look at the attached patch, you will understand my problem.
Regards,
Patrick
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552308#552308]
Start a new discussion in JBoss Remoting Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 8 months