[Red Hat JIRA] (DROOLS-5966) [ONE-OFF] (7.9.1)RuntimeException: Unknown expression type: java.lang.String.class thrown by executable-model
by Rodrigo Ribeiro (Jira)
Rodrigo Ribeiro created DROOLS-5966:
---------------------------------------
Summary: [ONE-OFF] (7.9.1)RuntimeException: Unknown expression type: java.lang.String.class thrown by executable-model
Key: DROOLS-5966
URL: https://issues.redhat.com/browse/DROOLS-5966
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.46.0.Final
Reporter: Rodrigo Ribeiro
Assignee: Toshiya Kobayashi
Fix For: 7.47.0.Final
In case of executable-model, when a LHS has a method call and its argument is a class expression:
{noformat}
when
Primitives( eval(classAttr.equals( java.lang.String.class ) ) )
{noformat}
it throws RuntimeException
{noformat}
[ERROR] testJBRULES_2995[KieBase type=CLOUD_IDENTITY_MODEL_PATTERN](org.drools.mvel.integrationtests.JBRULESTest) Time elapsed: 1.001 s <<< ERROR!
java.lang.RuntimeException: Unknown expression type: java.lang.String.class
at org.drools.modelcompiler.builder.generator.DrlxParseUtil.getExpressionType(DrlxParseUtil.java:271)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.processFirstNode(ExpressionTyper.java:628)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionFromMethodCallOrField(ExpressionTyper.java:412)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.parseNodeArguments(ExpressionTyper.java:790)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.parseMethodCallExpr(ExpressionTyper.java:719)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.methodCallExpr(ExpressionTyper.java:707)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionFromMethodCallOrField(ExpressionTyper.java:443)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:221)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpression(ExpressionTyper.java:149)
at org.drools.modelcompiler.builder.generator.drlxparse.ConstraintParser.getDrlxParseResult(ConstraintParser.java:172)
at org.drools.modelcompiler.builder.generator.drlxparse.ConstraintParser.drlxParse(ConstraintParser.java:102)
at org.drools.modelcompiler.builder.generator.visitor.pattern.PatternDSL.findAllConstraint(PatternDSL.java:136)
at org.drools.modelcompiler.builder.generator.visitor.pattern.PatternDSL.buildPattern(PatternDSL.java:235)
at org.drools.modelcompiler.builder.generator.visitor.ModelGeneratorVisitor.visit(ModelGeneratorVisitor.java:145)
at org.drools.compiler.lang.descr.PatternDescr.accept(PatternDescr.java:288)
at org.drools.modelcompiler.builder.generator.visitor.AndVisitor.visit(AndVisitor.java:50)
at org.drools.modelcompiler.builder.generator.visitor.ModelGeneratorVisitor.visit(ModelGeneratorVisitor.java:86)
at org.drools.modelcompiler.builder.generator.ModelGenerator.processRule(ModelGenerator.java:187)
at org.drools.modelcompiler.builder.generator.ModelGenerator.generateModel(ModelGenerator.java:160)
at org.drools.modelcompiler.builder.ModelBuilderImpl.compileKnowledgePackages(ModelBuilderImpl.java:284)
at org.drools.modelcompiler.builder.ModelBuilderImpl.buildRules(ModelBuilderImpl.java:220)
at org.drools.modelcompiler.builder.ModelBuilderImpl.postBuild(ModelBuilderImpl.java:130)
at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:111)
at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:97)
at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:268)
at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:216)
at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:80)
at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:279)
at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:247)
at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:204)
at org.drools.testcoverage.common.util.KieUtil.getKieBuilderFromKieFileSystem(KieUtil.java:129)
at org.drools.testcoverage.common.util.KieUtil.buildAndInstallKieModuleIntoRepo(KieUtil.java:70)
at org.drools.testcoverage.common.util.KieUtil.buildAndInstallKieModuleIntoRepo(KieUtil.java:64)
at org.drools.testcoverage.common.util.KieUtil.getKieModuleFromResources(KieUtil.java:231)
at org.drools.testcoverage.common.util.KieUtil.getKieModuleFromResources(KieUtil.java:220)
at org.drools.testcoverage.common.util.KieBaseUtil.getKieBaseFromKieModuleFromResources(KieBaseUtil.java:99)
at org.drools.testcoverage.common.util.KieBaseUtil.getKieBaseFromKieModuleFromDrl(KieBaseUtil.java:112)
at org.drools.mvel.integrationtests.JBRULESTest.testJBRULES_2995(JBRULESTest.java:148)
{noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 2:01 PM:
---------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
https://docs.wildfly.org/20/Developer_Guide.html#ejb-kubernetes-configura...
The https://issues.redhat.com/browse/WFCORE-4668 has two point. I did only the first configuration ow wildfly-conf.xml.. the second point I didn't.
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
[https://docs.wildfly.org/20/Developer_Guide.html#ejb-kubernetes-configura...]
The https://issues.redhat.com/browse/WFCORE-4668 has two point. I did only the first configuration ow wildfly-conf.xml.. the second point I didn't.
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 2:00 PM:
---------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
[https://docs.wildfly.org/20/Developer_Guide.html#ejb-kubernetes-configura...]
The https://issues.redhat.com/browse/WFCORE-4668 has two point. I did only the first configuration ow wildfly-conf.xml.. the second point I didn't.
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
[https://docs.wildfly.org/20/Developer_Guide.html#create-a-remote-outbound...]
The https://issues.redhat.com/browse/WFCORE-4668 has two point. I did only the first configuration ow wildfly-conf.xml.. the second point I didn't.
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 1:36 PM:
---------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
[https://docs.wildfly.org/20/Developer_Guide.html#create-a-remote-outbound...]
The https://issues.redhat.com/browse/WFCORE-4668 has two point. I did only the first configuration ow wildfly-conf.xml.. the second point I didn't.
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
https://docs.wildfly.org/20/Developer_Guide.html#create-a-remote-outbound...
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 1:31 PM:
---------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
Is this the correct way ?
https://docs.wildfly.org/20/Developer_Guide.html#create-a-remote-outbound...
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
I tried it and received this exception
{code:java}
12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
{code}
I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf}}
{{ }}
{{-Dwildfly.config.url=/app/wildfly/domain/configuration/wildfly-config.xml}}
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<authentication-client xmlns="urn:elytron:1.0">
<authentication-rules>
<rule use-configuration="default" />
</authentication-rules>
<authentication-configurations>
<configuration name="default">
<set-user-name name="ejbserver" />
<credentials>
<clear-password password="ejb" />
</credentials>
</configuration>
</authentication-configurations>
</authentication-client>
</configuration>
{code}
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5956) Illegal reflective access
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5956?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-5956.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/a451d7d29881bac797159275ea64436...
> Illegal reflective access
> -------------------------
>
> Key: DROOLS-5956
> URL: https://issues.redhat.com/browse/DROOLS-5956
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.48.0.Final
> Reporter: Damon Horrell
> Assignee: Mario Fusco
> Priority: Minor
>
> Using Java 11, Drools MVEL is reporting an Illegal reflective access warning:
> {{WARNING: Illegal reflective access by org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer (file:/Users/damon/.m2/repository/org/drools/drools-mvel/7.48.0.Final/drools-mvel-7.48.0.Final.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.createDefineMethod(ClassGenerator.java:126)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.<clinit>(ClassGenerator.java:117)}}{{at org.drools.mvel.asm.ClassGenerator.generateClass(ClassGenerator.java:177)}}{{at org.drools.mvel.asm.ClassGenerator.newInstance(ClassGenerator.java:214)}}{{at org.drools.mvel.asm.ConsequenceGenerator.generate(ConsequenceGenerator.java:140)}}{{at defaultpkg.Rule_Expand_HealthCase181668088DefaultConsequenceInvoker.evaluate(Unknown Source)}}{{at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:434)}}{{at org.drools.core.phreak.RuleExecutor.fireActivation(RuleExecutor.java:382)}}{{at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:138)}}{{at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:90)}}{{at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:33)}}{{at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)}}{{at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1111)}}{{at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1058)}}{{at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1050)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1346)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1337)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1321)}}
>
> {{Is there a plan to update this code to avoid the warning (which will become an error in some future version of Java)?}}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14249) Ensure java.time/sql ProtoStream marshallers generate valid protobuf messages
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-14249?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-14249:
--------------------------------
Description:
Protobuf messages generated by the Externalizers from the org.wildfly.clustering.marshalling.spi module are not necessarily valid protobuf messages. This jira covers marshallers for the following classes:
* java.time*
* java.sql*
* java.util.Date/Calendar
Additionally, many java.time classes can be marshalled more efficiently using native protostream marshallers, which can optimize for loose precision and positive/future values.
was:
Protobuf messages generated by the Externalizers from the org.wildfly.clustering.marshalling.spi module are not necessarily valid protobuf messages.
Additionally, many java.time classes can be marshalled more efficiently using native protostream marshallers, which can optimize for loose precision and positive/future values.
> Ensure java.time/sql ProtoStream marshallers generate valid protobuf messages
> -----------------------------------------------------------------------------
>
> Key: WFLY-14249
> URL: https://issues.redhat.com/browse/WFLY-14249
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 22.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Protobuf messages generated by the Externalizers from the org.wildfly.clustering.marshalling.spi module are not necessarily valid protobuf messages. This jira covers marshallers for the following classes:
> * java.time*
> * java.sql*
> * java.util.Date/Calendar
> Additionally, many java.time classes can be marshalled more efficiently using native protostream marshallers, which can optimize for loose precision and positive/future values.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 12:47 PM:
----------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
I tried it and received this exception
{code:java}
12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
{code}
I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf}}
{{ }}
{{-Dwildfly.config.url=/app/wildfly/domain/configuration/wildfly-config.xml}}
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<authentication-client xmlns="urn:elytron:1.0">
<authentication-rules>
<rule use-configuration="default" />
</authentication-rules>
<authentication-configurations>
<configuration name="default">
<set-user-name name="ejbserver" />
<credentials>
<clear-password password="ejb" />
</credentials>
</configuration>
</authentication-configurations>
</authentication-client>
</configuration>
{code}
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
I tried it and received this exception
{code:java}
12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
{code}
I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf }}
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<authentication-client xmlns="urn:elytron:1.0">
<authentication-rules>
<rule use-configuration="default" />
</authentication-rules>
<authentication-configurations>
<configuration name="default">
<set-user-name name="ejbserver" />
<credentials>
<clear-password password="ejb" />
</credentials>
</configuration>
</authentication-configurations>
</authentication-client>
</configuration>
{code}
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14284) WildFly doesn't stop while waiting for PeriodicRecovery
by Adriano Teixeira de Souza (Jira)
[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ]
Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 12:46 PM:
----------------------------------------------------------------------------
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
I tried it and received this exception
{code:java}
12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
{code}
I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf }}
{code:java}
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<authentication-client xmlns="urn:elytron:1.0">
<authentication-rules>
<rule use-configuration="default" />
</authentication-rules>
<authentication-configurations>
<configuration name="default">
<set-user-name name="ejbserver" />
<credentials>
<clear-password password="ejb" />
</credentials>
</configuration>
</authentication-configurations>
</authentication-client>
</configuration>
{code}
was (Author: JIRAUSER147207):
Hi [~ochaloup]
I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands
{code:java}
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false)
/profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false)
{code}
And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}}
Can you put here some links to get the right way to use both?
I tried it and received this exception
{code:java}
12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
{code}
> WildFly doesn't stop while waiting for PeriodicRecovery
> -------------------------------------------------------
>
> Key: WFLY-14284
> URL: https://issues.redhat.com/browse/WFLY-14284
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 18.0.1.Final, 20.0.1.Final
> Reporter: Adriano Teixeira de Souza
> Assignee: Michael Musgrove
> Priority: Major
> Attachments: ejb-configs.sh, jboss-ejb-client.xml, server(transaction).log, thread-dump-stop-1.txt
>
>
> I'm testing wildfly 20.0.1 (and 21.0.2 was tested too) for replace our old version of Wildfly 10.
> it happens that frequently we have seen that the stop function of server does not work and we need to kill the process by manual operation on the OS.
> It sounds like a dead look.
> I attatch the thread dump on this.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months