[JBoss JIRA] (WFCORE-2159) worker=default:read-resource(include-runtime) wrong values in domain mode
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2159?page=com.atlassian.jira.plugi... ]
Tomaz Cerar reassigned WFCORE-2159:
-----------------------------------
Assignee: Tomaz Cerar (was: David Lloyd)
> worker=default:read-resource(include-runtime) wrong values in domain mode
> -------------------------------------------------------------------------
>
> Key: WFCORE-2159
> URL: https://issues.jboss.org/browse/WFCORE-2159
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Reporter: Claudio Miranda
> Assignee: Tomaz Cerar
>
> In domain mode the following command assigns error message to values.
> {code}
> /profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
> {
> "outcome" => "success",
> "result" => {
> "io-threads" => "WFLYIO006: no metrics available",
> "stack-size" => "WFLYIO006: no metrics available",
> "task-keepalive" => "WFLYIO006: no metrics available",
> "task-max-threads" => "WFLYIO006: no metrics available",
> "server" => undefined
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2159) worker=default:read-resource(include-runtime) wrong values in domain mode
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2159?page=com.atlassian.jira.plugi... ]
Tomaz Cerar updated WFCORE-2159:
--------------------------------
Description:
In domain mode the following command assigns error message to values.
{code}
/profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
{
"outcome" => "success",
"result" => {
"io-threads" => "WFLYIO006: no metrics available",
"stack-size" => "WFLYIO006: no metrics available",
"task-keepalive" => "WFLYIO006: no metrics available",
"task-max-threads" => "WFLYIO006: no metrics available",
"server" => undefined
}
}
{code}
it should show configured values when it is executed on profile
was:
In domain mode the following command assigns error message to values.
{code}
/profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
{
"outcome" => "success",
"result" => {
"io-threads" => "WFLYIO006: no metrics available",
"stack-size" => "WFLYIO006: no metrics available",
"task-keepalive" => "WFLYIO006: no metrics available",
"task-max-threads" => "WFLYIO006: no metrics available",
"server" => undefined
}
}
{code}
> worker=default:read-resource(include-runtime) wrong values in domain mode
> -------------------------------------------------------------------------
>
> Key: WFCORE-2159
> URL: https://issues.jboss.org/browse/WFCORE-2159
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Reporter: Claudio Miranda
> Assignee: Tomaz Cerar
>
> In domain mode the following command assigns error message to values.
> {code}
> /profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
> {
> "outcome" => "success",
> "result" => {
> "io-threads" => "WFLYIO006: no metrics available",
> "stack-size" => "WFLYIO006: no metrics available",
> "task-keepalive" => "WFLYIO006: no metrics available",
> "task-max-threads" => "WFLYIO006: no metrics available",
> "server" => undefined
> }
> }
> {code}
> it should show configured values when it is executed on profile
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2159) worker=default:read-resource(include-runtime) wrong values in domain mode
by Claudio Miranda (JIRA)
Claudio Miranda created WFCORE-2159:
---------------------------------------
Summary: worker=default:read-resource(include-runtime) wrong values in domain mode
Key: WFCORE-2159
URL: https://issues.jboss.org/browse/WFCORE-2159
Project: WildFly Core
Issue Type: Bug
Components: IO
Reporter: Claudio Miranda
Assignee: David Lloyd
In domain mode the following command assigns error message to values.
{code}
/profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
{
"outcome" => "success",
"result" => {
"io-threads" => "WFLYIO006: no metrics available",
"stack-size" => "WFLYIO006: no metrics available",
"task-keepalive" => "WFLYIO006: no metrics available",
"task-max-threads" => "WFLYIO006: no metrics available",
"server" => undefined
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (DROOLS-1399) Comparison of DRL changes should not consider spaces during incremental compilation
by Marcus Carvalho (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1399?page=com.atlassian.jira.plugi... ]
Marcus Carvalho commented on DROOLS-1399:
-----------------------------------------
Hi Matteo, please confirm if I am correct. In that pull request, when a drl file is changed with blank spaces the matched rule will not be fired again after a incremental compilation. Am I right?
> Comparison of DRL changes should not consider spaces during incremental compilation
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1399
> URL: https://issues.jboss.org/browse/DROOLS-1399
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta5
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Minor
>
> During incremental compilation the equivalent DRL file contains only a modification with a new space character in a non-rule, non-resource line. Currently, this triggers the incremental compilation to rebuild all the resources associated in that DRL file anyway. Consequently, a rule in that DRL file might be actually UNchanged; but following the explanation above, it will match and fire again, like it's a new/modified rule.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (DROOLS-329) ClassFormatException when compile template with latest JDK8 (b114)
by Jitesh Jadav (JIRA)
[ https://issues.jboss.org/browse/DROOLS-329?page=com.atlassian.jira.plugin... ]
Jitesh Jadav edited comment on DROOLS-329 at 1/6/17 4:53 AM:
-------------------------------------------------------------
Dear [~mfusco]
It is working fine if I added the ecj version 4.4 to maven dependency. But the thing is if I tried to deploy the war file into tomcat 8 it is again giving error.
Drools Version: 5.0.1
JDK Version: 1.8.0_111-b14
Tomcat Version: Apache Tomcat 8.0.32
Better to use workaround given using JANINO in this issue description which is working fine on eclipse as well as on tomcat
was (Author: jitesh0149):
It is working fine if I added the ecj version 4.4 to maven dependency. But the thing is if I tried to deploy the war file into tomcat 8 it is again giving error.
Drools Version: 5.0.1
JDK Version: 1.8.0_111-b14
Tomcat Version: Apache Tomcat 8.0.32
> ClassFormatException when compile template with latest JDK8 (b114)
> ------------------------------------------------------------------
>
> Key: DROOLS-329
> URL: https://issues.jboss.org/browse/DROOLS-329
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 6.0.0.CR5
> Environment: Ubuntu linux, latest JDK1.8 (b114) downloaded from https://jdk8.java.net/download.html
> Reporter: Marek Posolda
> Assignee: Mario Fusco
> Fix For: 5.5.1.Final, 6.3.0.CR1
>
>
> When trying to run code for compile templates with latest JDK8 (For instance this example https://github.com/droolsjbpm/drools/blob/master/drools-examples/src/main... )
> it will throw an exception like this:
> {code}
> Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: wrong class format
> at org.drools.template.parser.DefaultTemplateRuleBase.readRule(DefaultTemplateRuleBase.java:148)
> at org.drools.template.parser.DefaultTemplateRuleBase.<init>(DefaultTemplateRuleBase.java:62)
> at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:74)
> at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:95)
> at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:81)
> at org.drools.examples.templates.SimpleRuleTemplateExample.buildKBase(SimpleRuleTemplateExample.java:84)
> at org.drools.examples.templates.SimpleRuleTemplateExample.executeExample(SimpleRuleTemplateExample.java:49)
> at org.drools.examples.templates.SimpleRuleTemplateExample.main(SimpleRuleTemplateExample.java:43)
> 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:483)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> Caused by: java.lang.RuntimeException: wrong class format
> at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:263)
> at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:203)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:102)
> at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:49)
> at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:122)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromTypeSignature(LookupEnvironment.java:1188)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromVariantTypeSignature(LookupEnvironment.java:1244)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeArgumentsFromSignature(LookupEnvironment.java:1031)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromTypeSignature(LookupEnvironment.java:1193)
> at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethod(BinaryTypeBinding.java:495)
> at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethods(BinaryTypeBinding.java:577)
> at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.cachePartsFrom(BinaryTypeBinding.java:327)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:640)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:619)
> at org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:295)
> at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:133)
> at org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage(PackageBinding.java:183)
> at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findImport(CompilationUnitScope.java:465)
> at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findSingleImport(CompilationUnitScope.java:519)
> at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInImports(CompilationUnitScope.java:368)
> at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInTypes(CompilationUnitScope.java:444)
> at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:752)
> at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:464)
> at org.drools.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJavaCompiler.java:389)
> at org.drools.commons.jci.compilers.AbstractJavaCompiler.compile(AbstractJavaCompiler.java:49)
> at org.drools.rule.builder.dialect.java.JavaDialect.compileAll(JavaDialect.java:371)
> at org.drools.compiler.DialectCompiletimeRegistry.compileAll(DialectCompiletimeRegistry.java:46)
> at org.drools.compiler.PackageRegistry.compileAll(PackageRegistry.java:102)
> at org.drools.compiler.PackageBuilder.compileAll(PackageBuilder.java:1006)
> at org.drools.compiler.PackageBuilder.compileAllRules(PackageBuilder.java:842)
> at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:831)
> at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:441)
> at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:419)
> at org.drools.template.parser.DefaultTemplateRuleBase.readRule(DefaultTemplateRuleBase.java:139)
> ... 12 more
> Caused by: org.eclipse.jdt.internal.compiler.classfmt.ClassFormatException
> at org.eclipse.jdt.internal.compiler.classfmt.ClassFileReader.<init>(ClassFileReader.java:372)
> at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.createNameEnvironmentAnswer(EclipseJavaCompiler.java:287)
> at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:258)
> ... 45 more
> {code}
> Workaround, which worked for me is to switch to Janino compiler (See Workaround description)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2158) Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-2158:
-----------------------------------------
Summary: Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists
Key: WFCORE-2158
URL: https://issues.jboss.org/browse/WFCORE-2158
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha16
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
21:24:18,013 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 56) WFLYCTL0190: Step
> handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@6f678cd for operation {"operation" => "full-replace-deployment","name" =>
> "drmk22.ear","enabled" => true,"content" => [{"hash" => bytes { 0x40, 0xde, 0xe4, 0x1d, 0xdd, 0xd0, 0xa7, 0x9f, 0xa9, 0x7a, 0x92, 0x84,
> 0xee, 0x92, 0x81, 0xea, 0x5d, 0x7b, 0xa3, 0x2a }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" =>
> "cf11aeb2-70b8-4f64-aa64-67fffd9c8080"},"address" => [],"runtime-name" => undefined,"persistent" => true,"owner" => undefined} at address []
> failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child
> 'name' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387)
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302)
> at org.jboss.dmr.ModelNode.require(ModelNode.java:875)
> at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:331)
> at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1435)
> at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1417)
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1379)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2157) Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-2157:
-----------------------------------------
Summary: Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists
Key: WFCORE-2157
URL: https://issues.jboss.org/browse/WFCORE-2157
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha16
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
21:24:18,013 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 56) WFLYCTL0190: Step
> handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@6f678cd for operation {"operation" => "full-replace-deployment","name" =>
> "drmk22.ear","enabled" => true,"content" => [{"hash" => bytes { 0x40, 0xde, 0xe4, 0x1d, 0xdd, 0xd0, 0xa7, 0x9f, 0xa9, 0x7a, 0x92, 0x84,
> 0xee, 0x92, 0x81, 0xea, 0x5d, 0x7b, 0xa3, 0x2a }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" =>
> "cf11aeb2-70b8-4f64-aa64-67fffd9c8080"},"address" => [],"runtime-name" => undefined,"persistent" => true,"owner" => undefined} at address []
> failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child
> 'name' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387)
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302)
> at org.jboss.dmr.ModelNode.require(ModelNode.java:875)
> at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:331)
> at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1435)
> at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1417)
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1379)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-5196) Downgrade PicketLink to 2.5.5.CR1
by Vitaly Gorbunov (JIRA)
[ https://issues.jboss.org/browse/WFLY-5196?page=com.atlassian.jira.plugin.... ]
Vitaly Gorbunov commented on WFLY-5196:
---------------------------------------
In fact wouldn't it be better to put last stable picketlink version in distributive before announcing full deprecation? Considering that maintenance fixes were done to PL.
> Downgrade PicketLink to 2.5.5.CR1
> ---------------------------------
>
> Key: WFLY-5196
> URL: https://issues.jboss.org/browse/WFLY-5196
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Affects Versions: 10.0.0.Beta2
> Reporter: Peter Skopek
> Assignee: Peter Skopek
> Fix For: 10.0.0.CR1
>
>
> We have to downgrade PicketLink to 2.5.x to be in sync with EAP 7 and deprecation of PicketLink in WildFly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-5196) Downgrade PicketLink to 2.5.5.CR1
by Vitaly Gorbunov (JIRA)
[ https://issues.jboss.org/browse/WFLY-5196?page=com.atlassian.jira.plugin.... ]
Vitaly Gorbunov commented on WFLY-5196:
---------------------------------------
I get that it's deprecated, but it's not the good reason for downgrade. We have several bugs with picketlink 2.6.0 and were waiting wildfly upgrade to get fixes with newer version. And now we can potentially have more bugs because picketlink was downgraded.
We will upgrade it manually in wildfly distributive and plan migration to keycloak, but please consider to avoid such changes.
> Downgrade PicketLink to 2.5.5.CR1
> ---------------------------------
>
> Key: WFLY-5196
> URL: https://issues.jboss.org/browse/WFLY-5196
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Affects Versions: 10.0.0.Beta2
> Reporter: Peter Skopek
> Assignee: Peter Skopek
> Fix For: 10.0.0.CR1
>
>
> We have to downgrade PicketLink to 2.5.x to be in sync with EAP 7 and deprecation of PicketLink in WildFly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months