[JBoss JIRA] (WFLY-12490) Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12490?page=com.atlassian.jira.plugin... ]
Eduardo Martins updated WFLY-12490:
-----------------------------------
Git Pull Request: https://github.com/wildfly/boms/pull/69, https://github.com/wildfly/quickstart/pull/358, https://github.com/wildfly/boms/pull/71, https://github.com/wildfly/quickstart/pull/360, https://github.com/wildfly/boms/pull/72, https://github.com/wildfly/boms/pull/73 (was: https://github.com/wildfly/boms/pull/69, https://github.com/wildfly/quickstart/pull/358, https://github.com/wildfly/boms/pull/71, https://github.com/wildfly/quickstart/pull/360, https://github.com/wildfly/boms/pull/72)
> Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
> ----------------------------------------------------------------------------
>
> Key: WFLY-12490
> URL: https://issues.jboss.org/browse/WFLY-12490
> Project: WildFly
> Issue Type: Sub-task
> Components: BOM, Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Blocker
> Fix For: 18.0.0.Final
>
>
> The Jakarta related component upgrades which changed groupId and/or artifactId of spec artifacts should be propagated to BOMs and Quickstarts projects.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (DROOLS-4565) MVELDialectRuntimeData is not thread safe
by Timo Gutjahr (Jira)
Timo Gutjahr created DROOLS-4565:
------------------------------------
Summary: MVELDialectRuntimeData is not thread safe
Key: DROOLS-4565
URL: https://issues.jboss.org/browse/DROOLS-4565
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.16.0.Final
Environment: Java 11.0.2
Different OS
Reporter: Timo Gutjahr
Assignee: Mario Fusco
Attachments: ForkJoinPool-1-worker-1.txt, NPE.txt
MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] )
If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (WFWIP-206) scale down isn't successful when there are in-doubt transaction on pod
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFWIP-206?page=com.atlassian.jira.plugin.... ]
Martin Simka edited comment on WFWIP-206 at 9/25/19 9:54 AM:
-------------------------------------------------------------
with latest operator ([915fbc2db39df10b65cbe164f34affb695edb830|https://github.com/wildfly/wildf...]) scale down again doesn't work at all, pods are never scaled down.
{noformat}
{"level":"info","ts":1569419086.5349486,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419086.5350897,"logger":"wildflyserver_controller","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.11","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Running"}
{"level":"info","ts":1569419086.6266701,"logger":"wildflyserver_controller","msg":"Verification the recovery listener is setup to run transaction recovery at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419089.6047068,"logger":"wildflyserver_controller","msg":"Query to find the transaction recovery port to force scan at pod tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419095.348274,"logger":"wildlfyserver_resources","msg":"Updating Resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server-0","Resource.Type":"*v1.Pod"}
{"level":"error","ts":1569419095.3573227,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server-0","Resource.Type":"*v1.Pod","error":"Operation cannot be fulfilled on pods \"tx-server-0\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1569419095.3575552,"logger":"wildflyserver_controller","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to update pod annotations, pod name tx-server-0, annotations to be set map[openshift.io/scc:restricted recovery-port:4712 wildfly.org/wildfly-server-generation:3], error: Operation cannot be fulfilled on pods \"tx-server-0\": the object has been modified; please apply your changes to the latest version and try again]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"info","ts":1569419095.3576174,"logger":"wildflyserver_controller","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
{"level":"info","ts":1569419095.3576312,"logger":"wildflyserver_controller","msg":"Statefulset was not fully scaled to the desired replica size 0 (current StatefulSet size: 1). Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
{"level":"info","ts":1569419095.3576558,"logger":"wildlfyserver_resources","msg":"Resource generations do not match","WildFlyServer.Name":"tx-server","WildFlyServer.Namespace":"msimka-namespace","Resource.Name":"tx-server","Resource.Type":"*v1.StatefulSet","WildFlyServer.Generation":3,"Resource.Generation":"2"}
{"level":"info","ts":1569419095.3577547,"logger":"wildlfyserver_resources","msg":"Updating Resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server","Resource.Type":"*v1.StatefulSet"}
{"level":"info","ts":1569419095.4202075,"logger":"wildlfyserver_resources","msg":"Updated resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server","Resource.Type":"*v1.StatefulSet"}
{"level":"info","ts":1569419095.4202409,"logger":"wildflyserver_controller","msg":"Updating StatefulSet to be up to date with the WildFlyServer Spec","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
{"level":"info","ts":1569419095.4203625,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419095.4204185,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419095.4204547,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419095.4205728,"logger":"wildflyserver_controller","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.11","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Running"}
{"level":"info","ts":1569419095.4491572,"logger":"wildflyserver_controller","msg":"Verification the recovery listener is setup to run transaction recovery at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419098.3074143,"logger":"wildflyserver_controller","msg":"Query to find the transaction recovery port to force scan at pod tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419104.2142792,"logger":"wildlfyserver_resources","msg":"Updating Resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server-0","Resource.Type":"*v1.Pod"}
{"level":"info","ts":1569419104.2362192,"logger":"wildlfyserver_resources","msg":"Updated resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server-0","Resource.Type":"*v1.Pod"}
{"level":"info","ts":1569419104.236247,"logger":"wildflyserver_controller","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.11","Recovery port":4712}
{"level":"info","ts":1569419120.079055,"logger":"wildlfyserver_resources","msg":"Updating status of WildFlyServer","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server"}
{"level":"info","ts":1569419120.0828912,"logger":"wildlfyserver_resources","msg":"Updated status of WildFlyServer","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server"}
{"level":"info","ts":1569419120.0829396,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419120.0829656,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.082995,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.0830805,"logger":"wildflyserver_controller","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
{"level":"info","ts":1569419120.083089,"logger":"wildflyserver_controller","msg":"Scaling down and updating replica size to 0","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
{"level":"info","ts":1569419120.0830944,"logger":"wildflyserver_controller","msg":"Updating statefulset","StatefulSet.Replicas":0}
{"level":"info","ts":1569419120.1033726,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419120.1035216,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.1035802,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.1036997,"logger":"wildflyserver_controller","msg":"Number of pods does not match the WildFlyServer specification. Waiting to get numbers in sync.","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","WildflyServer specification":"tx-server","Expected number of pods":0,"Number of deployed pods":1,"StatefulSet spec size":0}
{"level":"info","ts":1569419120.1235578,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419120.1236944,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.123772,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.1239598,"logger":"wildflyserver_controller","msg":"Number of pods does not match the WildFlyServer specification. Waiting to get numbers in sync.","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","WildflyServer specification":"tx-server","Expected number of pods":0,"Number of deployed pods":1,"StatefulSet spec size":0}
{"level":"info","ts":1569419120.1254933,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419120.1255758,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.1256313,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419120.1258724,"logger":"wildflyserver_controller","msg":"Number of pods does not match the WildFlyServer specification. Waiting to get numbers in sync.","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","WildflyServer specification":"tx-server","Expected number of pods":0,"Number of deployed pods":1,"StatefulSet spec size":0}
W0925 13:50:32.893831 1 reflector.go:270] pkg/mod/k8s.io/client-go@v0.0.0-20190228174230-b40b2a5939e4/tools/cache/reflector.go:95: watch of *v1.Route ended with: The resourceVersion for the provided watch is too old.
{"level":"info","ts":1569419433.9129002,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-client"}
{"level":"info","ts":1569419433.912962,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client"}
{"level":"info","ts":1569419433.9130015,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client"}
{"level":"info","ts":1569419433.9131017,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-loadbalancer"}
{"level":"info","ts":1569419433.9131217,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-loadbalancer"}
{"level":"info","ts":1569419433.9131458,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-headless"}
{"level":"info","ts":1569419433.9131584,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-headless"}
{"level":"info","ts":1569419433.913179,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-route"}
{"level":"info","ts":1569419433.913192,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-client","Resource.Name":"tx-client-route"}
{"level":"info","ts":1569419433.9132183,"logger":"wildflyserver_controller","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
{"level":"info","ts":1569419433.9132376,"logger":"wildlfyserver_resources","msg":"Getting resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419433.9132624,"logger":"wildlfyserver_resources","msg":"Got resource","WildFlyServer.Namespace":"msimka-namespace","WildFlyServer.Name":"tx-server","Resource.Name":"tx-server"}
{"level":"info","ts":1569419433.9133332,"logger":"wildflyserver_controller","msg":"Number of pods does not match the WildFlyServer specification. Waiting to get numbers in sync.","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","WildflyServer specification":"tx-server","Expected number of pods":0,"Number of deployed pods":1,"StatefulSet spec size":0}
{noformat}
was (Author: simkam):
with latest operator ([915fbc2db39df10b65cbe164f34affb695edb830|https://github.com/wildfly/wildf...]) scale down again doesn't work at all, pods are never scaled down.
> scale down isn't successful when there are in-doubt transaction on pod
> ----------------------------------------------------------------------
>
> Key: WFWIP-206
> URL: https://issues.jboss.org/browse/WFWIP-206
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: operator, built from [1984d98154f11a7473be065e4ae7f54b1812c9b0|https://github.com/wildfly/wildf...] :
> {noformat}
> docker-registry.engineering.redhat.com/jbossqe-eap/wildfly-operator:latest
> {noformat}
> EAP image:
> {noformat}
> docker-registry.engineering.redhat.com/ochaloup/wildfly18-snapshot:190909...
> {noformat}
> Reporter: Martin Simka
> Assignee: Ondrej Chaloupka
> Priority: Blocker
> Labels: operator
>
> While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful
> Scenario:
> *ejb client* (app tx-client, pod tx-client-0):
> * EJB business method
> ** lookup remote EJB
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ** call remote EJB
> *ejb server* (app tx-server, pod tx-server-0):
> * EJB business method
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}}
> Then the test calls scale down (size from 1 to 0) on tx-server pod. But scale down never completes.
> Log from operator:
> {noformat}
> {"level":"info","ts":1568905676.6303623,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905676.7313502,"logger":"controller_wildflyserver","msg":"Enabling recovery listener for processing scaledown at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905679.4325309,"logger":"controller_wildflyserver","msg":"Query to find the transaction recovery port to force scan at pod tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905686.7914035,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"info","ts":1568905702.0583296,"logger":"controller_wildflyserver","msg":"In-doubt transactions in object store","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","Message":"Recovery scan to be invoked as the transaction log storage is not empty for pod scaling down pod tx-server-0, transaction list: map[0:ffffac11000a:991c183:5d8399a1:13:map[age-in-seconds:23 id:0:ffffac11000a:991c183:5d8399a1:13 jmx-name:<nil> participants:map[java:/MockXAResource:map[eis-product-name:MockXAResource Test eis-product-version:0.1.Mock jmx-name:<nil> jndi-name:java:/MockXAResource status:PREPARED type:/StateManager/AbstractRecord/XAResourceRecord]] type:StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA]]"}
> {"level":"info","ts":1568905711.1034026,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905711.103548,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905711.109706,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905711.2608829,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Error to get response for command SCAN sending to 172.17.0.10:4712, error: EOF]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905711.2609518,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2609615,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2795022,"logger":"controller_wildflyserver","msg":"Updating StatefulSet to be up to date with the WildFlyServer Spec","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2795491,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905711.2796504,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905711.2937052,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905711.294249,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Cannot process TCP connection to 172.17.0.10:4712, error: dial tcp 172.17.0.10:4712: connect: connection refused]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905711.294342,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.294417,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"error","ts":1568905711.311673,"logger":"controller_wildflyserver","msg":"Failed to Update StatefulSet.","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server","error":"Operation cannot be fulfilled on statefulsets.apps \"tx-server\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1568905711.311745,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"msimka-namespace/tx-server","error":"Operation cannot be fulfilled on statefulsets.apps \"tx-server\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905712.3137681,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905712.3139439,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905712.3253288,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905712.3255754,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Cannot process TCP connection to 172.17.0.10:4712, error: dial tcp 172.17.0.10:4712: connect: connection refused]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905712.3256311,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905712.3256419,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (WFWIP-206) scale down isn't successful when there are in-doubt transaction on pod
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFWIP-206?page=com.atlassian.jira.plugin.... ]
Martin Simka commented on WFWIP-206:
------------------------------------
with latest operator ([915fbc2db39df10b65cbe164f34affb695edb830|https://github.com/wildfly/wildf...]) scale down again doesn't work at all, pods are never scaled down.
> scale down isn't successful when there are in-doubt transaction on pod
> ----------------------------------------------------------------------
>
> Key: WFWIP-206
> URL: https://issues.jboss.org/browse/WFWIP-206
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: operator, built from [1984d98154f11a7473be065e4ae7f54b1812c9b0|https://github.com/wildfly/wildf...] :
> {noformat}
> docker-registry.engineering.redhat.com/jbossqe-eap/wildfly-operator:latest
> {noformat}
> EAP image:
> {noformat}
> docker-registry.engineering.redhat.com/ochaloup/wildfly18-snapshot:190909...
> {noformat}
> Reporter: Martin Simka
> Assignee: Ondrej Chaloupka
> Priority: Blocker
> Labels: operator
>
> While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful
> Scenario:
> *ejb client* (app tx-client, pod tx-client-0):
> * EJB business method
> ** lookup remote EJB
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ** call remote EJB
> *ejb server* (app tx-server, pod tx-server-0):
> * EJB business method
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}}
> Then the test calls scale down (size from 1 to 0) on tx-server pod. But scale down never completes.
> Log from operator:
> {noformat}
> {"level":"info","ts":1568905676.6303623,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905676.7313502,"logger":"controller_wildflyserver","msg":"Enabling recovery listener for processing scaledown at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905679.4325309,"logger":"controller_wildflyserver","msg":"Query to find the transaction recovery port to force scan at pod tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905686.7914035,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"info","ts":1568905702.0583296,"logger":"controller_wildflyserver","msg":"In-doubt transactions in object store","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","Message":"Recovery scan to be invoked as the transaction log storage is not empty for pod scaling down pod tx-server-0, transaction list: map[0:ffffac11000a:991c183:5d8399a1:13:map[age-in-seconds:23 id:0:ffffac11000a:991c183:5d8399a1:13 jmx-name:<nil> participants:map[java:/MockXAResource:map[eis-product-name:MockXAResource Test eis-product-version:0.1.Mock jmx-name:<nil> jndi-name:java:/MockXAResource status:PREPARED type:/StateManager/AbstractRecord/XAResourceRecord]] type:StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA]]"}
> {"level":"info","ts":1568905711.1034026,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905711.103548,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905711.109706,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905711.2608829,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Error to get response for command SCAN sending to 172.17.0.10:4712, error: EOF]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905711.2609518,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2609615,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2795022,"logger":"controller_wildflyserver","msg":"Updating StatefulSet to be up to date with the WildFlyServer Spec","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.2795491,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905711.2796504,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905711.2937052,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905711.294249,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Cannot process TCP connection to 172.17.0.10:4712, error: dial tcp 172.17.0.10:4712: connect: connection refused]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905711.294342,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905711.294417,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"error","ts":1568905711.311673,"logger":"controller_wildflyserver","msg":"Failed to Update StatefulSet.","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server","error":"Operation cannot be fulfilled on statefulsets.apps \"tx-server\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1568905711.311745,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"msimka-namespace/tx-server","error":"Operation cannot be fulfilled on statefulsets.apps \"tx-server\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905712.3137681,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"msimka-namespace","Request.Name":"tx-server"}
> {"level":"info","ts":1568905712.3139439,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod Name":"tx-server-0","IP Address":"172.17.0.10"}
> {"level":"info","ts":1568905712.3253288,"logger":"controller_wildflyserver","msg":"Executing recovery scan at tx-server-0","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Pod IP":"172.17.0.10","Recovery port":4712}
> {"level":"error","ts":1568905712.3255754,"logger":"controller_wildflyserver","msg":"Failures during scaling down recovery processing","Request.Namespace":"msimka-namespace","Request.Name":"tx-server","Desired replica size":0,"Number of pods to be removed":1,"error":"Found 1 errors:\n [[Failed to run transaction recovery scan for scaling down pod tx-server-0. Please, verify the pod log file. Error: Cannot process TCP connection to 172.17.0.10:4712, error: dial tcp 172.17.0.10:4712: connect: connection refused]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"info","ts":1568905712.3256311,"logger":"controller_wildflyserver","msg":"Scaling down statefulset by verification if pods are clean by recovery","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {"level":"info","ts":1568905712.3256419,"logger":"controller_wildflyserver","msg":"Statefulset was not fully scaled to the desired replica size 0 while StatefulSet is to be at size 1. Some pods were not cleaned by recovery. Verify status of the WildflyServer tx-server","StatefulSet.Namespace":"msimka-namespace","StatefulSet.Name":"tx-server"}
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (DROOLS-4557) Missing semantic validation of DMN file
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4557?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4557:
-------------------------------------
Description:
If a semantically wrong file is parsed by the marshaller, exception may be thrown but they are not meaningfull.
As example, the attached file raise a NPE at _DMNMarshallerStandalone_ because at this line
{code:java}
Node sourceNode = Optional.ofNullable(elems.get(sourceId)).map(Entry::getValue).orElse(textAnnotations.get(sourceId));
{code}
_elements_ is empty.
So, even if the file is syntactically correct, it is semantically wrong; but this semantic check seems not implemented.
`
was:
If a semantically wrong file is parsed by the marshaller, exception may be thrown but they are not meaningfull.
As example, the attached file raise a NPE at `DMNMarshallerStandalone` because at this line ` Node sourceNode = Optional.ofNullable(elems.get(sourceId)).map(Entry::getValue).orElse(textAnnotations.get(sourceId));` elemens is empty.
So, even if the file is syntactically correct, it is semantically wrong; but this semantic check seems not implemented.
`
> Missing semantic validation of DMN file
> ---------------------------------------
>
> Key: DROOLS-4557
> URL: https://issues.jboss.org/browse/DROOLS-4557
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Gabriele Cardosi
> Assignee: Michael Anstis
> Priority: Major
> Attachments: E3083400-878D-49DB-8E72-105FDB6BAF44.dmn
>
>
> If a semantically wrong file is parsed by the marshaller, exception may be thrown but they are not meaningfull.
> As example, the attached file raise a NPE at _DMNMarshallerStandalone_ because at this line
> {code:java}
> Node sourceNode = Optional.ofNullable(elems.get(sourceId)).map(Entry::getValue).orElse(textAnnotations.get(sourceId));
> {code}
> _elements_ is empty.
> So, even if the file is syntactically correct, it is semantically wrong; but this semantic check seems not implemented.
> `
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (WFLY-12588) BeanManager.findBean(...) can return an expired bean.
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12588:
-----------------------------------
Summary: BeanManager.findBean(...) can return an expired bean.
Key: WFLY-12588
URL: https://issues.jboss.org/browse/WFLY-12588
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
If something prevents the expiration scheduler from timely expiration of a SFSB, BeanManager.findBean(...) can return an expired bean. A simple expiration check (like we do during SessionManager.findSession(...)) would solve the problem.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (WFLY-12587) Distributed web/SFSB expiration after failover schedules premature expiration
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12587:
-----------------------------------
Summary: Distributed web/SFSB expiration after failover schedules premature expiration
Key: WFLY-12587
URL: https://issues.jboss.org/browse/WFLY-12587
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Distributed web/SFSB expiration schedules expiration the corresponding session/bean is closed. When the request handling the session/bean is not the primary owner, the expiration is scheduled on the primary owner. However, because the command is dispatched synchronously, if the backing cache is transactional, the primary owner will schedule expiration for the previous last accessed time, instead of the current last accessed time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (DROOLS-4564) Reconnecting the Kie-server to the controller while using the WebSocket connection problem
by Marcin Kasza (Jira)
Marcin Kasza created DROOLS-4564:
------------------------------------
Summary: Reconnecting the Kie-server to the controller while using the WebSocket connection problem
Key: DROOLS-4564
URL: https://issues.jboss.org/browse/DROOLS-4564
Project: Drools
Issue Type: Bug
Components: integration, kie server
Affects Versions: 7.24.0.Final
Reporter: Marcin Kasza
Assignee: Mario Fusco
When the kie-server connects to the controller / workbench via web-sockets and this connection fails (e.g., due to network problems), the kie-server will try to reconnect.
Reconnect thread started in WebSocketClientImpl (kie-server-controller-websocket-common), fails with NPE with log message: _WebSocketClientImpl: Unable to reconnect to the controller through the Null socket because of null_
NPE is thrown because session.getRequestURI returns NULL value
at this.session = container.connectToServer(this, this.config, session.getRequestURI());
In my case kie-server (WebSocketContainer) running on tomcat 8.5
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months
[JBoss JIRA] (DROOLS-4563) Upgrade javax.validation from 1.0.0.GA to 2.0.1.Final
by Michael Biarnes Kiefer (Jira)
Michael Biarnes Kiefer created DROOLS-4563:
----------------------------------------------
Summary: Upgrade javax.validation from 1.0.0.GA to 2.0.1.Final
Key: DROOLS-4563
URL: https://issues.jboss.org/browse/DROOLS-4563
Project: Drools
Issue Type: Feature Request
Reporter: Michael Biarnes Kiefer
Assignee: Michael Biarnes Kiefer
To do the upgrade of javax.validation [(PR)|https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1055] it is needed to check all GWT reps (uberfire, errai,wb etc) because the javax.validation version is not supported in these reps.
The version upgrade is needed for spring-boot and quarkus - so it should be upgraded in kie-parent but overwritten in all poms of GWT reps that doesn't support this new version by the old version. It is thought to add a dependency overwite in the root pom in those repo's to overwrite it to use the original older version
On the other hand existing overrides like [this|https://github.com/kiegroup/droolsjbpm-integration/blob/81415ae5cdc4...] should be removed then.
All reps should be examined if they have an override or if the need the old version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 10 months