March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3747) KNative + Quarkus Drools/jBPM demo

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3747?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3747: ----------------------------------- Description: Try and setup a small, limited knative demo with either drools or jbpm using quarkus to expose an endpoint Expected deliverable: a github repository with scripts to start the demo on minishift/minikube was:Try and setup a small, limited knative demo with either drools or jbpm using quarkus to expose an endpoint > KNative + Quarkus Drools/jBPM demo > ---------------------------------- > > Key: DROOLS-3747 > URL: https://issues.jboss.org/browse/DROOLS-3747 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Try and setup a small, limited knative demo with either drools or jbpm using quarkus to expose an endpoint > Expected deliverable: a github repository with scripts to start the demo on minishift/minikube -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBSER-133) Infinite Stack trace getting logged using jboss-serialization.jar - 1.0.3 GA ( in jboss 5.x )

by Suresh Ragala (Jira)

[ https://issues.jboss.org/browse/JBSER-133?page=com.atlassian.jira.plugin.... ] Suresh Ragala commented on JBSER-133: ------------------------------------- Now a days, this issue is coming once for every 2 weeks. It's impacting heavily our crucial customer during business hours also. Can you please address this issue on priority ? > Infinite Stack trace getting logged using jboss-serialization.jar - 1.0.3 GA ( in jboss 5.x ) > ---------------------------------------------------------------------------------------------- > > Key: JBSER-133 > URL: https://issues.jboss.org/browse/JBSER-133 > Project: JBoss Serialization > Issue Type: Bug > Environment: Jboss as 5.x , JDK 1.7 > Reporter: Suresh Ragala > Assignee: Clebert Suconic > Priority: Critical > > - When we get extensive OptimisticLockExceptions related to business entity changes from parallel processes, we are getting this infinite stack trace. > version we are using : jboss Serialization 1.0.3 GA ( in jboss as 5.x ) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2316) DNS_PING is not using correct ports with SRV based service discovery

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2316: -------------------------------- [~ethompson] I suggest create a new JIRA (with instructions to reproduce) and link this one. Logs at TRACE level for discovery/GMS should be included, too. > DNS_PING is not using correct ports with SRV based service discovery > -------------------------------------------------------------------- > > Key: JGRP-2316 > URL: https://issues.jboss.org/browse/JGRP-2316 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: dmcnair > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.16 > > > This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery. > Here are the log entries using *4.0.15* > {noformat} > 2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105] > 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600] > {noformat} > Since the port was found via the SRV record, it should be used instead of the *transportPort* port. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4365) Remove READ_TIMEOUT from cannel configuration options

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4365?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4365: ------------------------------------------ Is this about the EJB subsystem? {code} <remote connector-ref="http-remoting-connector" thread-pool-name="default"> <channel-creation-options> <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/> <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> </channel-creation-options> </remote> {code} If so, please move to WFLY and change the component to EJB3. Thanks. > Remove READ_TIMEOUT from cannel configuration options > ----------------------------------------------------- > > Key: WFCORE-4365 > URL: https://issues.jboss.org/browse/WFCORE-4365 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 8.0.0.Final > Reporter: Teresa Miyar > Assignee: Teresa Miyar > Priority: Major > > The only configuration options allowed on the channel are > RemotingOptions.TRANSMIT_WINDOW_SIZE, > RemotingOptions.MAX_OUTBOUND_MESSAGES > RemotingOptions.RECEIVE_WINDOW_SIZE > RemotingOptions.MAX_INBOUND_MESSAGES > RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE > RemotingOptions.MAX_INBOUND_MESSAGE_SIZE. > Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11808?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-11808: ----------------------------------- Starting a batch job operation from web console follows a different path than starting a batch job by application. The following is the stack trace for management-initiated batch job execution: {code} "External Management Request Threads -- 1@16187" prio=5 tid=0xa0 nid=NA runnable java.lang.Thread.State: RUNNABLE at org.wildfly.extension.batch.jberet.deployment.JobOperatorService.start(JobOperatorService.java:219) at org.wildfly.extension.batch.jberet.deployment.BatchDeploymentResourceDefinition$1.execute(BatchDeploymentResourceDefinition.java:105) at org.wildfly.extension.batch.jberet.deployment.JobOperationStepHandler.executeRuntime(JobOperationStepHandler.java:75) at org.wildfly.extension.batch.jberet.deployment.JobOperationStepHandler$$Lambda$979.35215319.execute(Unknown Source:-1) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) at org.jboss.as.controller.ModelControllerImpl$$Lambda$631.1055034970.run(Unknown Source:-1) at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$632.1532149905.run(Unknown Source:-1) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$977.1385167113.run(Unknown Source:-1) at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$978.2116813432.run(Unknown Source:-1) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:834) at org.jboss.threads.JBossThread.run(JBossThread.java:485) {code} > Unable to do jndi lookup when starting batch job from web console > ----------------------------------------------------------------- > > Key: WFLY-11808 > URL: https://issues.jboss.org/browse/WFLY-11808 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 16.0.0.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Attachments: Screen Shot 2019-03-04 at 10.38.47 PM.png > > > when starting a batch job from web console, jndi lookup inside the application's batch artifacts failed with NameNotFoundException. When the same job is started by the application, the lookups all go well. Need to check if the naming context is properly propagated when starting job from the web console. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11835) Expand ha-singleton-service to demonstrate using CLI to determine primary provider

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11835?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11835: ---------------------------------- Summary: Expand ha-singleton-service to demonstrate using CLI to determine primary provider (was: Extend ha-singleton-service to demonstrate using CLI to determine primary provider) > Expand ha-singleton-service to demonstrate using CLI to determine primary provider > ---------------------------------------------------------------------------------- > > Key: WFLY-11835 > URL: https://issues.jboss.org/browse/WFLY-11835 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Demonstrate feature implemented in EAP7-1088. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11836) Expand ha-singleton-service to demonstrate Singleton service election listeners

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11836?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11836: ---------------------------------- Summary: Expand ha-singleton-service to demonstrate Singleton service election listeners (was: Extend ha-singleton-service to demonstrate Singleton service election listeners) > Expand ha-singleton-service to demonstrate Singleton service election listeners > ------------------------------------------------------------------------------- > > Key: WFLY-11836 > URL: https://issues.jboss.org/browse/WFLY-11836 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Demonstrate feature implemented in EAP7-1115. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11836) Extend ha-singleton-service to demonstrate Singleton service election listeners

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-11836: ------------------------------------- Summary: Extend ha-singleton-service to demonstrate Singleton service election listeners Key: WFLY-11836 URL: https://issues.jboss.org/browse/WFLY-11836 Project: WildFly Issue Type: Task Components: Clustering, Quickstarts Affects Versions: 16.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11836) Extend ha-singleton-service to demonstrate Singleton service election listeners

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11836?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11836: ---------------------------------- Description: Demonstrate feature implemented in EAP7-1115. > Extend ha-singleton-service to demonstrate Singleton service election listeners > ------------------------------------------------------------------------------- > > Key: WFLY-11836 > URL: https://issues.jboss.org/browse/WFLY-11836 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Demonstrate feature implemented in EAP7-1115. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11835) Expand HA singleton quickstart to demonstrate using CLI to determine primary provider

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11835?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11835: ---------------------------------- Description: Demonstrate feature implemented in EAP7-1088. > Expand HA singleton quickstart to demonstrate using CLI to determine primary provider > ------------------------------------------------------------------------------------- > > Key: WFLY-11835 > URL: https://issues.jboss.org/browse/WFLY-11835 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Demonstrate feature implemented in EAP7-1088. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019