May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2345) NPE in ASYM_ENCRYPT

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2345?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2345. ---------------------------- Resolution: Done > NPE in ASYM_ENCRYPT > ------------------- > > Key: JGRP-2345 > URL: https://issues.jboss.org/browse/JGRP-2345 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 4.1.0 > > > Stack trace: > {noformat} > 2019-05-09 08:38:39,518 ERROR [org.jgroups.protocols.UDP] (jgroups-10,Clusterd6c8baf6-b087-4deb-a0b2-dbab8302a80atrunk-83693,umstest-win10-3-24714) failed processing batch: java.lang.NullPointerException > at org.jgroups.protocols.Encrypt.up(Encrypt.java:192) > at org.jgroups.protocols.ASYM_ENCRYPT.up(ASYM_ENCRYPT.java:176) > at org.jgroups.protocols.BARRIER.up(BARRIER.java:196) > at org.groups.stack.Protocol.up(Protocol.java:371) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:216) > at org.jgroups.stack.Protocol.up(Protocol.java:371) > at org.jgroups.stack.Protocol.up(Protocol.java:371) > at org.jgroups.stack.Protocol.up(Protocol.java:371) > at org.jgroups.protocols.TP.passBatchUp(TP.java:1276) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.passBatchUp(MaxOneThreadPerSender.java:284) > at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) > at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.run(MaxOneThreadPerSender.java:273) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2343) Change in IPv4 versus IPv6 picking algorithm

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2343?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2343. ---------------------------- Resolution: Done > Change in IPv4 versus IPv6 picking algorithm > -------------------------------------------- > > Key: JGRP-2343 > URL: https://issues.jboss.org/browse/JGRP-2343 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > When https://issues.jboss.org/browse/JGRP-2305 was implemented, IPv4 was favored unless {{java.net.preferIPv6Addresses}} was set. > However, this makes the following case fail: no {{java.net.preferXXX}} option is set and the configuration contains one or more IPv6 addresses, e.g. {{UDP bind_addr="::1"}}. > This will fail, as the new algorithm sets the stack type as IPv4 (it works when {{java.net.preferIPv6Addresses}} is set). > Change: > * Look at all IP addresses in a configuration > * If all addresses are IPv6 and the stack type is IPv4 (and IPv6 is available) -> switch to IPv6 as stack type > * If all addresses are IPv4 and the stack type is IPv6 (and IPv4 is available) -> switch to IPv4 stack type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4054) Classloader content is printed when kie.conf files are loaded

by Karel Suta (Jira)

Karel Suta created DROOLS-4054: ---------------------------------- Summary: Classloader content is printed when kie.conf files are loaded Key: DROOLS-4054 URL: https://issues.jboss.org/browse/DROOLS-4054 Project: Drools Issue Type: Bug Environment: WebSphere 9 latest Kie server Reporter: Karel Suta Assignee: Mario Fusco Attachments: SystemOut.log JBPM-8506 fixes logging issues related to Kie server. However it also reveals that [ServiceDiscoveryImpl|https://github.com/kiegroup/droolsjbpm-knowledge/blo...] logs content of classloader into application server log. This becomes quite annoying specially on WebSphere as the log contain all the classpath entries. You can see the result the logging in attachment, search for entries done by ServiceDiscoveryImpl. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4050) Error is thrown when DMN expected date value differs from the actual value

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4050?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4050: ---------------------------------- Sprint: 2019 Week 20-22 > Error is thrown when DMN expected date value differs from the actual value > -------------------------------------------------------------------------- > > Key: DROOLS-4050 > URL: https://issues.jboss.org/browse/DROOLS-4050 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-05-20 11-48-39.png, error.log, outage.zip > > > If the test scenario computes with date fields, there is an exceptio0n if the expected value differs from the actual. If the expected value is same as actual, scenario works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4050) Error is thrown when DMN expected date value differs from the actual value

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4050?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4050: ---------------------------------- Story Points: 5 > Error is thrown when DMN expected date value differs from the actual value > -------------------------------------------------------------------------- > > Key: DROOLS-4050 > URL: https://issues.jboss.org/browse/DROOLS-4050 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-05-20 11-48-39.png, error.log, outage.zip > > > If the test scenario computes with date fields, there is an exceptio0n if the expected value differs from the actual. If the expected value is same as actual, scenario works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4053) JUnit 5: Migrate Runtimes > Drools > drools-model-compiler

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-4053: ---------------------------------------- Summary: JUnit 5: Migrate Runtimes > Drools > drools-model-compiler Key: DROOLS-4053 URL: https://issues.jboss.org/browse/DROOLS-4053 Project: Drools Issue Type: Task Reporter: Lukáš Petrovický Assignee: Lukáš Petrovický When JUnit 5 gains support for parameterized constructors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4052) JUnit 5: Migrate Runtimes > jBPM Modules

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-4052: ---------------------------------------- Summary: JUnit 5: Migrate Runtimes > jBPM Modules Key: DROOLS-4052 URL: https://issues.jboss.org/browse/DROOLS-4052 Project: Drools Issue Type: Task Reporter: Lukáš Petrovický Assignee: Lukáš Petrovický -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4478) Eliminate CapabilityServiceTarget & CapabilityServiceBuilder deprecated methods usages

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4478: -------------------------------------- Summary: Eliminate CapabilityServiceTarget & CapabilityServiceBuilder deprecated methods usages Key: WFCORE-4478 URL: https://issues.jboss.org/browse/WFCORE-4478 Project: WildFly Core Issue Type: Enhancement Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12097) Cache fails to stop due to unreleased persistence manager semaphore permits

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12097: ----------------------------------- Summary: Cache fails to stop due to unreleased persistence manager semaphore permits Key: WFLY-12097 URL: https://issues.jboss.org/browse/WFLY-12097 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 15.0.1.Final Environment: Windows 10 x64 java version "1.8.0_212" Java(TM) SE Runtime Environment (build 1.8.0_212-b10) Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode) Wildfly 15.0.1 Reporter: Paul Ferraro Assignee: Paul Ferraro Wildfly 15.0.1 fails to stop on shutdown command due to Infinispan subsystem failing to stop it's persisted caches successfully due to a possible bug in Infinispan's PersistenceManagerImpl.publishEntries not releasing Semaphore permit after finishing, so that the stop method waits forever because it lacks one more permit. !third_semaphore.png|thumbnail! !forth_semaphore.png|thumbnail! Use following application to reproduce the issue: [^web-java-wildfly.zip] standalone Infinispan caches: {code} <cache-container name="testMetaData"> <local-cache name="testCache"> <locking concurrency-level="3"/> <transaction locking="OPTIMISTIC" mode="FULL_XA"/> <object-memory size="1000000"/> <file-store path="testCH/testCache" passivation="false" preload="false" purge="false"/> </local-cache> <local-cache name="testComponentCache"> <locking concurrency-level="3"/> <transaction locking="OPTIMISTIC" mode="FULL_XA"/> <object-memory size="1000000"/> <file-store path="testCH/testComponentCache" passivation="false" preload="false" purge="false"/> </local-cache> </cache-container> {code} {code} 11:02:00,103 INFO [stdout] (default task-1) bla blanull 11:02:00,103 INFO [stdout] (default task-1) bla blanull 11:03:17,748 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout. 11:03:17,750 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete 11:03:17,752 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' 11:03:17,785 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0099: Unbound non-transactional data source: java:jboss/datasources/myprojdb1 11:03:17,785 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:/mail/myproject] 11:03:17,785 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0099: Unbound non-transactional data source: java:jboss/datasources/myprojdb2 11:03:17,787 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0099: Unbound non-transactional data source: java:jboss/datasources/myprojdb3 11:03:17,789 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory 11:03:17,790 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default] 11:03:17,790 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0099: Unbound non-transactional data source: java:jboss/datasources/myprojdb4 11:03:17,797 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = ojdbc.jar 11:03:17,800 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 101) WFLYUT0022: Unregistered web context: '/wildfly-helloworld' from server 'default-server' 11:03:17,821 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 101) MODCLUSTER000002: Initiating mod_cluster shutdown 11:03:17,823 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping 11:03:17,840 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory 11:03:17,841 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] 11:03:17,842 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] 11:03:17,842 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 11:03:17,846 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 101) WFLYCLINF0003: Stopped client-mappings cache from ejb container 11:03:17,864 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending 11:03:17,864 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow AJP listener ajp suspending 11:03:17,870 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment ojdbc.jar (runtime-name: ojdbc.jar) in 108ms 11:03:17,883 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment wildfly-helloworld.war (runtime-name: wildfly-helloworld.war) in 120ms 11:03:17,875 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to 192.168.1.2:8009 11:03:17,874 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 192.168.1.2:8080 11:03:17,872 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 104) AMQ151003: resource adaptor stopped 11:03:17,932 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 104) AMQ221002: Apache ActiveMQ Artemis Message Broker version 2.6.3.jbossorg-00014 [7b985d04-761e-11e9-bb4e-0a0027000008] stopped, uptime 1 minute 11:03:17,933 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTPS listener default-ssl suspending 11:03:17,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTPS listener default-ssl stopped, was bound to 192.168.1.2:8443 11:03:17,935 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 2.0.15.Final stopping {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-739) Update Upstream Pipeline and Convert it do DSL

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-739?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-739: ------------------------------------------ Description: Convert Istio-and-Kiali to DSL job. > Update Upstream Pipeline and Convert it do DSL > ---------------------------------------------- > > Key: SWSQE-739 > URL: https://issues.jboss.org/browse/SWSQE-739 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Convert Istio-and-Kiali to DSL job. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019