[JBoss JIRA] (WFLY-5907) NullPointerException during deployment ejb-ref with mappedName
by Marco Zanker (JIRA)
[ https://issues.jboss.org/browse/WFLY-5907?page=com.atlassian.jira.plugin.... ]
Marco Zanker updated WFLY-5907:
-------------------------------
Description:
If deploying a ejb3 SSB with a ejb reference to another bean (in my case an old ejb 2 SSB) with a mappedName-parameter, a NullPointerException occurs.
@EJBs({
@EJB(name = "ejb/MyOldEJB2LocalHome", beanInterface=MyOldEJB2LocalHome.class, beanName="oldejb.jar#MyOldEJB2"),
})
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.process(EjbResourceInjectionA
nnotationProcessor.java:166)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.processClass(EjbResourceInjec
tionAnnotationProcessor.java:146)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.deploy(EjbResourceInjectionAn
notationProcessor.java:106)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
Seems, if mappedName is declared, always a NullPointerException occurs.
was:
If deploying a ejb3 SSB with a ejb reference to another bean (in my case an old ejb 2 SSB) with a mappedName-parameter, a NullPointerException occurs.
@EJBs({
@EJB(name = "ejb/MyOldEJB2LocalHome", beanInterface=MyOldEJB2LocalHome.class, beanName="oldejb.jar#MyOldEJB2"),
})
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.process(EjbResourceInjectionA
nnotationProcessor.java:166)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.processClass(EjbResourceInjec
tionAnnotationProcessor.java:146)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.deploy(EjbResourceInjectionAn
notationProcessor.java:106)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> NullPointerException during deployment ejb-ref with mappedName
> --------------------------------------------------------------
>
> Key: WFLY-5907
> URL: https://issues.jboss.org/browse/WFLY-5907
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.2.Final
> Reporter: Marco Zanker
>
> If deploying a ejb3 SSB with a ejb reference to another bean (in my case an old ejb 2 SSB) with a mappedName-parameter, a NullPointerException occurs.
> @EJBs({
> @EJB(name = "ejb/MyOldEJB2LocalHome", beanInterface=MyOldEJB2LocalHome.class, beanName="oldejb.jar#MyOldEJB2"),
> })
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.process(EjbResourceInjectionA
> nnotationProcessor.java:166)
> at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.processClass(EjbResourceInjec
> tionAnnotationProcessor.java:146)
> at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.deploy(EjbResourceInjectionAn
> notationProcessor.java:106)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> Seems, if mappedName is declared, always a NullPointerException occurs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5907) NullPointerException during deployment ejb-ref with mappedName
by Marco Zanker (JIRA)
Marco Zanker created WFLY-5907:
----------------------------------
Summary: NullPointerException during deployment ejb-ref with mappedName
Key: WFLY-5907
URL: https://issues.jboss.org/browse/WFLY-5907
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 9.0.2.Final
Reporter: Marco Zanker
If deploying a ejb3 SSB with a ejb reference to another bean (in my case an old ejb 2 SSB) with a mappedName-parameter, a NullPointerException occurs.
@EJBs({
@EJB(name = "ejb/MyOldEJB2LocalHome", beanInterface=MyOldEJB2LocalHome.class, beanName="oldejb.jar#MyOldEJB2"),
})
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.process(EjbResourceInjectionA
nnotationProcessor.java:166)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.processClass(EjbResourceInjec
tionAnnotationProcessor.java:146)
at org.jboss.as.ejb3.deployment.processors.EjbResourceInjectionAnnotationProcessor.deploy(EjbResourceInjectionAn
notationProcessor.java:106)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-173) Collect and accumulate conditions not working together
by Massinissa BOUZIAD (JIRA)
[ https://issues.jboss.org/browse/DROOLS-173?page=com.atlassian.jira.plugin... ]
Massinissa BOUZIAD edited comment on DROOLS-173 at 12/23/15 4:01 AM:
---------------------------------------------------------------------
Hi guys,
Anyone can help is welcome.
I try to use the collect function within a rules like that :
{code:title=My rule not working |borderStyle=solid}
$combinedParts : List(size >= 2) // >= not work
from collect(CombinedPart(
/* here my eligibility checks */
)
)
{code}
{code:title=My rule working |borderStyle=solid}
$combinedParts : List(size == 2) // == work
from collect(CombinedPart(
/* here my eligibility checks */
)
)
{code}
The operator ">=" seems to not work whereas "==" work and ">" work also.
I got this stack trace wich make me confused :
{code:title=My stack | borderStyle=solid}
java.lang.NoSuchMethodError: org.mvel2.compiler.BlankLiteral.<init>(Ljava/lang/String;)V
at ConditionEvaluatore065b53056eb4e34a7d0e895676d67a1.evaluate(Unknown Source)
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:248)
at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:298)
at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:93)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:978)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260)
{code}
Thank you
was (Author: massinissa):
Hi guys,
Anyone can help is welcome.
I try to use the collect function within a rules like that :
{code:title=My rule not working |borderStyle=solid}
$combinedParts : List(size >= 2) // >= not work
from collect(CombinedPart(
/* here my eligibility checks */
)
)
{code}
{code:title=My rule working |borderStyle=solid}
$combinedParts : List(size == 2) // >= work
from collect(CombinedPart(
/* here my eligibility checks */
)
)
{code}
The operator ">=" seems to not work whereas "==" work and ">" work also.
I got this stack trace wich make me confused :
{code:title=My stack | borderStyle=solid}
java.lang.NoSuchMethodError: org.mvel2.compiler.BlankLiteral.<init>(Ljava/lang/String;)V
at ConditionEvaluatore065b53056eb4e34a7d0e895676d67a1.evaluate(Unknown Source)
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:248)
at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:494)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:384)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:298)
at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:93)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:978)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260)
{code}
Thank you
> Collect and accumulate conditions not working together
> ------------------------------------------------------
>
> Key: DROOLS-173
> URL: https://issues.jboss.org/browse/DROOLS-173
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.0.0.Beta3
> Reporter: Alvaro Pantoja
> Assignee: Mario Fusco
> Fix For: 6.0.0.Final
>
> Attachments: rule-test.log
>
>
> Running this example:
> {code}
> import java.util.ArrayList
> declare Item
> code: int
> price: int
> present: boolean
> end
> rule "Init"
> when
> then
> insert(new Item(1,40,false));
> insert(new Item(2,40,false));
> insert(new Item(3,40,false));
> insert(new Item(4,40,false));
> end
> rule "CollectAndAccumulateRule"
> when
> //At least two items that aren't presents
> objList: ArrayList(size>=2) from collect( Item(present==false))
> //Total price bigger than 100
> price: Number(intValue>=100) from accumulate( Item($w:price, present==false), sum($w))
> then
> System.out.println("Sum: "+price);
> System.out.println("Items size: "+objList.size());
>
> //Look for the minor price item
> Item min = null;
> for(Object obj: objList){
> if (min!=null){
> min = (min.getPrice()>((Item)obj).getPrice())?(Item)obj:min;
> }
> else {
> min = (Item)obj;
> }
> }
>
> //And make it a present
> if (min!=null){
> modify(min){setPresent(true)};
> }
> end
> {code}
> Leads to an extra activacion and execution of rule "CollectAndAccumulateRule". It doesn't matter wich order conditions are, as long as there are both "accumulate" and a "collect".
> Expected output would be:
> {quote}
> Sum: 160.0
> Items size: 4
> Sum: 120.0
> Items size: 3
> {quote}
> But is:
> {quote}
> Sum: 160.0
> Items size: 4
> Sum: 120.0
> Items size: 4
> Sum: 120.0
> Items size: 3
> {quote}
> Find attached agenda and working memory log snapshot
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JGRP-1999) TCP_NIO2: single selector slows down writes and reads
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1999?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1999:
--------------------------------
When we get a read for connection C and notify the reader thread for C to handle the read, since the processing is done by the reader thread for C (in the background, and possibly taking some time), we might get a number of more wakeups of the selector for the same data to be read for C.
To prevent this, C should be *unregistered with the selector* until the reader thread is done reading all of the data for connection C. When done, the reader thread should again register ({{OP_READ}}) with the selector, to get notified when new data is available.
> TCP_NIO2: single selector slows down writes and reads
> -----------------------------------------------------
>
> Key: JGRP-1999
> URL: https://issues.jboss.org/browse/JGRP-1999
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.7
>
>
> TCP_NIO2 has a single selector which looks like this:
> {noformat}
> x=select()
> if(read) -> read data from connection x, de-serialize data, pass to thread pool
> if(write) -> write data pending on connection x
> {noformat}
> This means that any operation (read,write) delays other operations. It seems that especially the de-serialization done in reads delays other reads and writes.
> A quick test showed that having a reader thread per connection (so that reads don't delay other reads or writes) improved perf from 15'000 reqs/sec to 22'000.
> The idea is to have a reader thread in {{NioConnection}} which reads and de-serializes as many messages as possible. When no more messages are ready to be read, it blocks for a max wait time and then terminates unless more messages are ready. This means that idle connections will have no threads allocated.
> Investigate: we might possibly also null the pre-allocated buffer when a thread terminates, reducing memory usage even more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-399) mod_cluster subsystem: convert operation handlers to use OperationDefinition
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-399?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-399:
------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> mod_cluster subsystem: convert operation handlers to use OperationDefinition
> ----------------------------------------------------------------------------
>
> Key: WFLY-399
> URL: https://issues.jboss.org/browse/WFLY-399
> Project: WildFly
> Issue Type: Sub-task
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Final
>
>
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/LoadMetricDefinition.java:[59,59] warning: [deprecation] PropertiesAttributeDefinition(java.lang.String,java.lang.String,boolean) in org.jboss.as.controller.PropertiesAttributeDefinition has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[277,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[280,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[283,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterConfigResourceDefinition.java:[286,29] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterSubsystemAdd.java:[160,19] warning: [deprecation] setProxyList(java.lang.String) in org.jboss.modcluster.config.impl.ModClusterConfig has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterSubsystemAdd.java:[166,15] warning: [deprecation] setExcludedContexts(java.lang.String) in org.jboss.modcluster.config.impl.ModClusterConfig has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[100,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[103,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[106,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[110,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[113,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[117,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[120,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean,java.util.EnumSet<org.jboss.as.controller.registry.OperationEntry.Flag>) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[124,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[127,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[130,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[134,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[137,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
> [WARNING] /home/rhusar/git/as-master-modcluster/modcluster/src/main/java/org/jboss/as/modcluster/ModClusterDefinition.java:[140,21] warning: [deprecation] registerOperationHandler(java.lang.String,org.jboss.as.controller.OperationStepHandler,org.jboss.as.controller.descriptions.DescriptionProvider,boolean) in org.jboss.as.controller.registry.ManagementResourceRegistration has been deprecated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-264) Add support for use1PcForAutoCommitTransactions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-264?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated WFLY-264:
------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Add support for use1PcForAutoCommitTransactions
> -----------------------------------------------
>
> Key: WFLY-264
> URL: https://issues.jboss.org/browse/WFLY-264
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> Since clustered web sessions/SFSBs won't ever incur inter-node concurrent access, we can tolerate a 1PC commit optimization - which will reduce the number of RPCs involved in replication/distribution. This should result it a significant performance gains for REPL_SYNC and DIST_SYNC caches.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months