[JBoss JIRA] (JGRP-2094) Add convenience method Rsp.readIn
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2094?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2094:
---------------------------
Fix Version/s: 3.6.11
4.0
> Add convenience method Rsp.readIn
> ---------------------------------
>
> Key: JGRP-2094
> URL: https://issues.jboss.org/browse/JGRP-2094
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.6.10, 4.0
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Minor
> Fix For: 3.6.11, 4.0
>
>
> In Infinispan, during a staggered get we prepare several {{Rsp}} s in {{RspList}} and then for each {{Rsp}} we send one message. As the {{RspList}} can be accessed by multiple threads but we don't want to synchronize the access, we just get the {{Rsp}} and fill it from the (other) received {{Rsp}}. However the fill requires several ifs:
> {code}
> if (rsp.hasException()) {
> futureRsp.setException(rsp.getException());
> } else if (rsp.wasSuspected()) {
> futureRsp.setSuspected();
> } else if (rsp.wasUnreachable()) {
> futureRsp.setUnreachable();
> } else {
> futureRsp.setValue(rsp.getValue());
> }
> {code}
> Let's add a convenience method that will just read in the flags and value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1707) Deploying an unmanaged deployment with force makes it managed
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1707?page=com.atlassian.jira.plugi... ]
Michal Jurc deleted WFCORE-1707:
--------------------------------
> Deploying an unmanaged deployment with force makes it managed
> -------------------------------------------------------------
>
> Key: WFCORE-1707
> URL: https://issues.jboss.org/browse/WFCORE-1707
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Michal Jurc
> Assignee: ehsavoie Hugonnet
>
> For an unmanaged deployment if you replace it using the CLI deploy command it becomes managed.
> To reproduce:
> {code:java}
> deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged
> deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged --force
> {code}
> After the second command the deployment is managed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1707) Deploying an unmanaged deployment with force makes it managed
by Michal Jurc (JIRA)
Michal Jurc created WFCORE-1707:
-----------------------------------
Summary: Deploying an unmanaged deployment with force makes it managed
Key: WFCORE-1707
URL: https://issues.jboss.org/browse/WFCORE-1707
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Alpha4
Reporter: Michal Jurc
Assignee: ehsavoie Hugonnet
For an unmanaged deployment if you replace it using the CLI deploy command it becomes managed.
To reproduce:
{code:java}
deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged
deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged --force
{code}
After the second command the deployment is managed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1702) WF Core StringBytesLengthValidator should not use error message considering characters
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1702?page=com.atlassian.jira.plugi... ]
Chao Wang reassigned WFCORE-1702:
---------------------------------
Assignee: Chao Wang
> WF Core StringBytesLengthValidator should not use error message considering characters
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1702
> URL: https://issues.jboss.org/browse/WFCORE-1702
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ondra Chaloupka
> Assignee: Chao Wang
> Priority: Minor
> Fix For: 3.0.0.CR1
>
>
> Current implementation of class {{StringBytesLengthValidator}} which is used by {{TransactionSubsystemRootResourceDefinition}} for validation of {{node-identifier}} element prints error message in format
> {code}
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
> Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"
> {code}
> but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the {{node id}} that the string has length smaller than {{23}} but the message says that it's bigger.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1705) A system dependency sun/security/provider/certpath is missing from wildfly's module.xml
by Peter Nalyvayko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1705?page=com.atlassian.jira.plugi... ]
Peter Nalyvayko updated WFCORE-1705:
------------------------------------
Labels: jboss (was: )
> A system dependency sun/security/provider/certpath is missing from wildfly's module.xml
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1705
> URL: https://issues.jboss.org/browse/WFCORE-1705
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Modules, Server
> Affects Versions: 2.2.0.Final
> Reporter: Peter Nalyvayko
> Assignee: David Lloyd
> Labels: jboss
>
> There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there:
> {{<module xmlns="urn:jboss:module:1.3" name="sun.jdk">
> <resources>
> <!-- currently jboss modules has not way of importing services from
> classes.jar so we duplicate them here -->
> <resource-root path="service-loader-resources"/>
> </resources>
> <dependencies>
> <module name="sun.scripting" export="true"/>
> <system export="true">
> <paths>
> ...
> <path name="sun/security/action"/>
> <path name="sun/security/pkcs"/>
> <path name="sun/security/x509"/>
> <path name="sun/security"/>
> <path name="sun/security/util"/>
> <path name="sun/security/krb5"/>
> <path name="sun/security/krb5/internal"/>
> <path name="sun/security/pkcs11"/>
> <path name="sun/security/provider"/>
> ...
> </paths>
> <exports>
> <include-set>
> <path name="META-INF/services"/>
> </include-set>
> </exports>
> </system>
> </dependencies>
> </module>
> }}Manually adding the missing system dependency path fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1705) A system dependency sun/security/provider/certpath is missing from wildfly's module.xml
by Peter Nalyvayko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1705?page=com.atlassian.jira.plugi... ]
Peter Nalyvayko updated WFCORE-1705:
------------------------------------
Component/s: Server
> A system dependency sun/security/provider/certpath is missing from wildfly's module.xml
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1705
> URL: https://issues.jboss.org/browse/WFCORE-1705
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Modules, Server
> Affects Versions: 2.2.0.Final
> Reporter: Peter Nalyvayko
> Assignee: David Lloyd
>
> There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there:
> {{<module xmlns="urn:jboss:module:1.3" name="sun.jdk">
> <resources>
> <!-- currently jboss modules has not way of importing services from
> classes.jar so we duplicate them here -->
> <resource-root path="service-loader-resources"/>
> </resources>
> <dependencies>
> <module name="sun.scripting" export="true"/>
> <system export="true">
> <paths>
> ...
> <path name="sun/security/action"/>
> <path name="sun/security/pkcs"/>
> <path name="sun/security/x509"/>
> <path name="sun/security"/>
> <path name="sun/security/util"/>
> <path name="sun/security/krb5"/>
> <path name="sun/security/krb5/internal"/>
> <path name="sun/security/pkcs11"/>
> <path name="sun/security/provider"/>
> ...
> </paths>
> <exports>
> <include-set>
> <path name="META-INF/services"/>
> </include-set>
> </exports>
> </system>
> </dependencies>
> </module>
> }}Manually adding the missing system dependency path fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint
by Tianwei Chen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ]
Tianwei Chen commented on DROOLS-785:
-------------------------------------
I got the same error in Drools plugin in Eclipse with 6.4.0.Final as runtime.
Any updates on the issue?
> no MVEL debugger registered to handle breakpoint
> ------------------------------------------------
>
> Key: DROOLS-785
> URL: https://issues.jboss.org/browse/DROOLS-785
> Project: Drools
> Issue Type: Bug
> Components: core engine, eclipse plugin
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76
> Reporter: Maurice Betzel
> Assignee: Petr Široký
> Priority: Blocker
>
> Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception:
> 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml
> 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes]
> Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint
> at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76)
> at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
> at org.mvel2.MVEL.executeExpression(MVEL.java:930)
> at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422)
> at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Tianwei Chen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Tianwei Chen commented on DROOLS-1250:
--------------------------------------
I fixed the issue by adding _*dialect "mvel" *_ at the two rules in Sample.drl.
Is it a bug in the drools wizard that dialet is missing in the examples? or It supposes to work without dialet?
Thanks.
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1706) Deploying with force an unmanaged deployment makes it managed
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1706?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet commented on WFCORE-1706:
-------------------------------------------
The redeploy command created from the CLI passes the deployment content as a stream even if it there is the unmanaged flag thus making the new deployment managed.
> Deploying with force an unmanaged deployment makes it managed
> -------------------------------------------------------------
>
> Key: WFCORE-1706
> URL: https://issues.jboss.org/browse/WFCORE-1706
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha4
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
>
> For an unmanaged deployment if you replace it using the CLI deploy command it becomes managed.
> To reproduce:
> {code:java}
> deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged
> deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged --force
> {code}
> After the second command the deployment is managed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1706) Deploying with force an unmanaged deployment makes it managed
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-1706:
-----------------------------------------
Summary: Deploying with force an unmanaged deployment makes it managed
Key: WFCORE-1706
URL: https://issues.jboss.org/browse/WFCORE-1706
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Alpha4
Reporter: ehsavoie Hugonnet
Assignee: Alexey Loubyansky
For an unmanaged deployment if you replace it using the CLI deploy command it becomes managed.
To reproduce:
{code:java}
deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged
deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged --force
{code}
After the second command the deployment is managed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months