[Red Hat JIRA] (WFLY-14384) Unable to set capacity-factor attribute in distributed cache in Infinispan
by Ivan Straka (Jira)
Ivan Straka created WFLY-14384:
----------------------------------
Summary: Unable to set capacity-factor attribute in distributed cache in Infinispan
Key: WFLY-14384
URL: https://issues.redhat.com/browse/WFLY-14384
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 22.0.0.Final, 23.0.0.Beta1
Reporter: Ivan Straka
Assignee: Ivan Straka
Attachments: standalone-full-ha.xml
Running with configured mod cluster extension (see attached xml) I get:
{code:java}
13:27:16,815 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 60) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("distributed-cache" => "dist")
]): java.lang.NumberFormatException: For input string: "1.0"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
at org.jboss.as.clustering.infinispan.subsystem.DistributedCacheServiceConfigurator.configure(DistributedCacheServiceConfigurator.java:53)
at org.jboss.as.clustering.infinispan.subsystem.CacheServiceHandler.installServices(CacheServiceHandler.java:85)
at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
{code}
The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (WFLY-14383) Unable to set decay attribute in modcluster subsystem
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14383?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14383:
-------------------------------
Summary: Unable to set decay attribute in modcluster subsystem (was: Unable to set decay attribute in modcluster extension)
> Unable to set decay attribute in modcluster subsystem
> -----------------------------------------------------
>
> Key: WFLY-14383
> URL: https://issues.redhat.com/browse/WFLY-14383
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 22.0.0.Final, 23.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
> Attachments: standalone-full-ha.xml
>
>
> Running with configured mod cluster extension (see attached xml) I get:
> {code:java}
> 13:27:16,733 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 76) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.NumberFormatException: For input string: "2.0"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.getLoadProvider(ModClusterSubsystemServiceHandler.java:129)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:95)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (WFLY-14383) Unable to set decay attribute in modcluster extension
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14383?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14383:
-------------------------------
Attachment: standalone-full-ha.xml
> Unable to set decay attribute in modcluster extension
> -----------------------------------------------------
>
> Key: WFLY-14383
> URL: https://issues.redhat.com/browse/WFLY-14383
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 22.0.0.Final, 23.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
> Attachments: standalone-full-ha.xml
>
>
> Running with configured mod cluster extension (see attached xml) I get:
> {code:java}
> 13:27:16,733 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 76) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.NumberFormatException: For input string: "2.0"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
> at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.getLoadProvider(ModClusterSubsystemServiceHandler.java:129)
> at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:95)
> at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
> at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (WFLY-14383) Unable to set decay attribute in modcluster extension
by Ivan Straka (Jira)
Ivan Straka created WFLY-14383:
----------------------------------
Summary: Unable to set decay attribute in modcluster extension
Key: WFLY-14383
URL: https://issues.redhat.com/browse/WFLY-14383
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 22.0.0.Final, 23.0.0.Beta1
Reporter: Ivan Straka
Assignee: Ivan Straka
Running with configured mod cluster extension (see attached xml) I get:
{code:java}
13:27:16,733 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 76) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]): java.lang.NumberFormatException: For input string: "2.0"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:142)
at org.jboss.dmr.ModelNode.asInt(ModelNode.java:288)
at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.getLoadProvider(ModClusterSubsystemServiceHandler.java:129)
at org.wildfly.extension.mod_cluster.ModClusterSubsystemServiceHandler.installServices(ModClusterSubsystemServiceHandler.java:95)
at org.jboss.as.clustering.controller.AddStepHandler.performRuntime(AddStepHandler.java:220)
at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:343)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
{code}
The problem is that the attribute is double, however in add operation handler is parsed as int.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (WFLY-14378) Generic JMS RA fails to authenticate
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-14378?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet reassigned WFLY-14378:
----------------------------------------
Assignee: Emmanuel Hugonnet
> Generic JMS RA fails to authenticate
> -------------------------------------
>
> Key: WFLY-14378
> URL: https://issues.redhat.com/browse/WFLY-14378
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 22.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Critical
>
> MDBs deployed in on WildFLy 22 using generic JMS resource adapter would fail to authenticate with external TIBCO broker due to missing password.
> {noformat}
> 2021-01-29 13:55:47,927 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 3) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@25f70034(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)4b294f76 destination=jms/topic/inTopic destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=quickuser maxMessages=1 minSession=1 maxSession=15 connectionFactory=jms/cf/XATopicConnectionFactory jndiParameters={java.naming.provider.url=tcp://aza:7222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory, java.naming.security.principal=quickuser, java.naming.security.credentials=<not shown>}): javax.jms.JMSSecurityException: authentication failed
> at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:744)
> at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1465)
> at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4412)
> at com.tibco.tibjms.TibjmsXAConnection.<init>(TibjmsXAConnection.java:30)
> at com.tibco.tibjms.TibjmsXATopicConnection.<init>(TibjmsXATopicConnection.java:29)
> at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:147)
> at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:255)
> at com.tibco.tibjms.TibjmsXAConnectionFactory.createXAConnection(TibjmsXAConnectionFactory.java:61)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:442)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:417)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:316)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.access$100(JmsActivation.java:58)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:546)
> at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
> at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
> at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
> at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
> at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
> at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
> at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> Authentication with TIBCO JNDI does works and JMS bridge would work only MDB are affected.
> This is due to missing getter() method on JMSActivationSpect class.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months