[JBoss JIRA] (WFWIP-254) Changes in volumeClaimTemplate triggers creation of a new statefulset
by Petr Kremensky (Jira)
Petr Kremensky created WFWIP-254:
------------------------------------
Summary: Changes in volumeClaimTemplate triggers creation of a new statefulset
Key: WFWIP-254
URL: https://issues.jboss.org/browse/WFWIP-254
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Petr Kremensky
Assignee: Jeff Mesnil
Adding a volumeClaimTemplate, or existing an existing one leads to the re-creation of statefulset -> all pods are immediately terminated and route is unavailable until some of the pods is ready again.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy updatedquickstart project from operator repository {noformat}cat deploy/crds/quickstart-cr.yaml
apiVersion: wildfly.org/v1alpha1
kind: WildFlyServer
metadata:
name: quickstart
spec:
applicationImage: "quay.io/wildfly-quickstarts/wildfly-operator-quickstart:18.0"
replicas: 2
storage:
volumeClaimTemplate:
spec:
resources:
requests:
storage: 1Mi
oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready & print ss creation timestamp & verify application readiness {noformat}oc get pods
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 2m48s
quickstart-1 1/1 Running 0 2m48s
wildfly-operator-54455dbcd8-flnd4 1/1 Running 0 69m
oc get statefulset.apps/quickstart --template={{.metadata.creationTimestamp}}
2019-10-17T13:55:03Z
curl quickstart-route-wildfly.apps-crc.testing
{"ip":"10.128.1.36"}
{noformat}
* edit the storage field (e.g. storage: 1Mi -> storage: 2Mi)
* notice the both pods are terminating, stateful set creation timestamp has changed and application route is not available until one of the pods will start again (could take a minute){noformat}oc get pods
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Terminating 0 5m42s
quickstart-1 1/1 Terminating 0 5m42s
wildfly-operator-54455dbcd8-flnd4 1/1 Running 0 72m
oc get statefulset.apps/quickstart --template={{.metadata.creationTimestamp}}
2019-10-17T14:00:44Z
curl quickstart-route-wildfly.apps-crc.testing
...
Application is not available
...
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12671) Memory Leak of PersistenceUnitMetadataImpl
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12671?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12671:
-------------------------------------
[~rschimpf] if you follow the steps I gave above ([Choose Exclude all phantom/weak/soft etc. references|https://issues.jboss.org/browse/WFLY-12671?focusedCommentId=13...]), that should show only the strong references, which should be conclusive.
FYI, the [WFLY-12676] issue was introduced into WildFly 17.
> Memory Leak of PersistenceUnitMetadataImpl
> ------------------------------------------
>
> Key: WFLY-12671
> URL: https://issues.jboss.org/browse/WFLY-12671
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 17.0.1.Final
> Reporter: Robin Schimpf
> Assignee: Scott Marlow
> Priority: Major
> Attachments: Trying_to_catch_memory_leak_with_more_trace_logging.patch, jcaleakmarlow.txt, memory leak after 4 deployments.PNG, memory leak after 5 deployments.PNG, memory leak with directory scanner undeploy and deploy.PNG, persistence-unit-not-stopped.txt, persistence-unit-stopped.txt
>
>
> After updating from Wildfly 13 to Wildfly 17 we noticed a slowdown of our application after multiple deployments to the application server without restarting it between the deployments. Heapdumps are showing that after redeployment the number of {{PersistenceUnitMetadataImpl}} are growing (see screenshots).
> We are deploying 2 ear files and 2 war files. Only one ear has a database connection configured. We are using the bundeled hibernate version of Wildfly 17.
> The ear structure is like the following:
> {noformat}
> - app.ear
> |
> |- META-INF
> |
> |- lib
> | |
> | |- all dependencies
> |
> |- own jars and wars (e.g. jpa)
> {noformat}
> Since I failed to create a reproducing project for this behaviour I added some trace logging (Patch attached). The only difference I noticed was that sometimes the {{Stopping Persistence Unit}} logstatement is missing before the {{Stopped subdeployment}} logstatement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12671) Memory Leak of PersistenceUnitMetadataImpl
by Robin Schimpf (Jira)
[ https://issues.jboss.org/browse/WFLY-12671?page=com.atlassian.jira.plugin... ]
Robin Schimpf commented on WFLY-12671:
--------------------------------------
I didn't had enough time today as I would need to go further. A quick look at the heapdumps with an undeployed application showed only the PersistenceUnitMetadataImpl to be hold by Quartz in the ApplicationShutdownHooks.
I also want to go back to Wildfly 13 and check some heapdumps from this version as we didn't had the problem here.
Maybe I can also check the fix you made for WFLY-12676 and package a self built version into Wildfly 17 and see what happens.
> Memory Leak of PersistenceUnitMetadataImpl
> ------------------------------------------
>
> Key: WFLY-12671
> URL: https://issues.jboss.org/browse/WFLY-12671
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 17.0.1.Final
> Reporter: Robin Schimpf
> Assignee: Scott Marlow
> Priority: Major
> Attachments: Trying_to_catch_memory_leak_with_more_trace_logging.patch, jcaleakmarlow.txt, memory leak after 4 deployments.PNG, memory leak after 5 deployments.PNG, memory leak with directory scanner undeploy and deploy.PNG, persistence-unit-not-stopped.txt, persistence-unit-stopped.txt
>
>
> After updating from Wildfly 13 to Wildfly 17 we noticed a slowdown of our application after multiple deployments to the application server without restarting it between the deployments. Heapdumps are showing that after redeployment the number of {{PersistenceUnitMetadataImpl}} are growing (see screenshots).
> We are deploying 2 ear files and 2 war files. Only one ear has a database connection configured. We are using the bundeled hibernate version of Wildfly 17.
> The ear structure is like the following:
> {noformat}
> - app.ear
> |
> |- META-INF
> |
> |- lib
> | |
> | |- all dependencies
> |
> |- own jars and wars (e.g. jpa)
> {noformat}
> Since I failed to create a reproducing project for this behaviour I added some trace logging (Patch attached). The only difference I noticed was that sometimes the {{Stopping Persistence Unit}} logstatement is missing before the {{Stopped subdeployment}} logstatement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12676) memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12676?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12676:
-------------------------------------
[https://github.com/ironjacamar/ironjacamar/pull/692] is merged, we just need a new IronJacamar release that includes that change. Assigned to [~maeste] for handling that.
> memory leak, org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is keeping deployment in memory after undeployment
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12676
> URL: https://issues.jboss.org/browse/WFLY-12676
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 18.0.0.Final
> Reporter: Scott Marlow
> Assignee: Stefano Maestri
> Priority: Blocker
> Fix For: 19.0.0.Beta1
>
> Attachments: 2lc.jar, java_pid12802.0001.zip, jcaleakmarlow.txt
>
>
> As part of looking at [WFLY-12671], I found that org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner is leaking the application classloader (after undeployment) via org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory originalTCCL being kept after undeployment.
> See attached jcaleakmarlow.txt (also attached to [WFLY-12671]), which shows the leak.
> I tried waiting a few minutes after undeployment and the leak was still there. I also tried an even simpler app (2lc.jar) and still there is a leak. I also attached the heapdump (java_pid12802.0001.zip)
> To recreate:
> * Deploy simple (no app code will be executed) 2lc.jar app.
> * Undeploy by doing "rm 2lc.jar.deployed" in wildfly/standalone/deployments
> * Look at memory with MAT or other memory leak tool.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12681) Create 'microprofile' layer spec
by Radoslav Husar (Jira)
Radoslav Husar created WFLY-12681:
-------------------------------------
Summary: Create 'microprofile' layer spec
Key: WFLY-12681
URL: https://issues.jboss.org/browse/WFLY-12681
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Radoslav Husar
Assignee: Radoslav Husar
We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774.
With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4569) XLS editor should have a save button
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4569:
--------------------------------
Description:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf (/)
- Test Scenario, Test Scenario Legacy (/)
- Work Item Definition (/)
- Case Definition Legacy (x) - no changes dialog
- Other - png,svg (/)
- Plain text - pom.xml (/)
was:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf (/)
- Test Scenario, Test Scenario Legacy (/)
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
> XLS editor should have a save button
> ------------------------------------
>
> Key: DROOLS-4569
> URL: https://issues.jboss.org/browse/DROOLS-4569
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: form-load-fail.png, form-load.log
>
>
> It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
> h2. Manual acceptance test
> Save metadata of:
> - Business Process (/)
> - Business process legacy (x) no changes dialog
> - Data Object (/)
> - DT spreadsheet (/)
> - Scorecard spreadsheet (/)
> - Guided DT, Guided DT Graph (/)
> - DMN (/)
> - DRL, Guided Rule Template, Guided Rule (/)
> - DSL (/)
> - Enum (/)
> - Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
> - Global variable (/)
> - Guided Decision Tree (/)
> - Guided Scorecard (/)
> - Solver conf (/)
> - Test Scenario, Test Scenario Legacy (/)
> - Work Item Definition (/)
> - Case Definition Legacy (x) - no changes dialog
> - Other - png,svg (/)
> - Plain text - pom.xml (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4569) XLS editor should have a save button
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4569:
--------------------------------
Description:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf (/)
- Test Scenario, Test Scenario Legacy (/)
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
was:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf (/)
- Test Scenario, Test Scenario Legacy
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
> XLS editor should have a save button
> ------------------------------------
>
> Key: DROOLS-4569
> URL: https://issues.jboss.org/browse/DROOLS-4569
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: form-load-fail.png, form-load.log
>
>
> It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
> h2. Manual acceptance test
> Save metadata of:
> - Business Process (/)
> - Business process legacy (x) no changes dialog
> - Data Object (/)
> - DT spreadsheet (/)
> - Scorecard spreadsheet (/)
> - Guided DT, Guided DT Graph (/)
> - DMN (/)
> - DRL, Guided Rule Template, Guided Rule (/)
> - DSL (/)
> - Enum (/)
> - Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
> - Global variable (/)
> - Guided Decision Tree (/)
> - Guided Scorecard (/)
> - Solver conf (/)
> - Test Scenario, Test Scenario Legacy (/)
> - Work Item Definition
> - Case Definition Legacy (x) - no changes dialog
> - Other
> - Plain text
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4569) XLS editor should have a save button
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4569:
--------------------------------
Description:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf (/)
- Test Scenario, Test Scenario Legacy
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
was:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf
- Test Scenario, Test Scenario Legacy
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
> XLS editor should have a save button
> ------------------------------------
>
> Key: DROOLS-4569
> URL: https://issues.jboss.org/browse/DROOLS-4569
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: form-load-fail.png, form-load.log
>
>
> It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
> h2. Manual acceptance test
> Save metadata of:
> - Business Process (/)
> - Business process legacy (x) no changes dialog
> - Data Object (/)
> - DT spreadsheet (/)
> - Scorecard spreadsheet (/)
> - Guided DT, Guided DT Graph (/)
> - DMN (/)
> - DRL, Guided Rule Template, Guided Rule (/)
> - DSL (/)
> - Enum (/)
> - Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
> - Global variable (/)
> - Guided Decision Tree (/)
> - Guided Scorecard (/)
> - Solver conf (/)
> - Test Scenario, Test Scenario Legacy
> - Work Item Definition
> - Case Definition Legacy (x) - no changes dialog
> - Other
> - Plain text
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4569) XLS editor should have a save button
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4569?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4569:
--------------------------------
Description:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Scorecard spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf
- Test Scenario, Test Scenario Legacy
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
was:
It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
h2. Manual acceptance test
Save metadata of:
- Business Process (/)
- Business process legacy (x) no changes dialog
- Data Object (/)
- DT spreadsheet (/)
- Guided DT, Guided DT Graph (/)
- DMN (/)
- DRL, Guided Rule Template, Guided Rule (/)
- DSL (/)
- Enum (/)
- Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
- Global variable (/)
- Guided Decision Tree (/)
- Guided Scorecard (/)
- Solver conf
- Test Scenario, Test Scenario Legacy
- Work Item Definition
- Case Definition Legacy (x) - no changes dialog
- Other
- Plain text
> XLS editor should have a save button
> ------------------------------------
>
> Key: DROOLS-4569
> URL: https://issues.jboss.org/browse/DROOLS-4569
> Project: Drools
> Issue Type: Bug
> Components: XLS Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: form-load-fail.png, form-load.log
>
>
> It is impossible to save metadata changes without a Save button. You can however update the XLS file by uploading it each time.
> h2. Manual acceptance test
> Save metadata of:
> - Business Process (/)
> - Business process legacy (x) no changes dialog
> - Data Object (/)
> - DT spreadsheet (/)
> - Scorecard spreadsheet (/)
> - Guided DT, Guided DT Graph (/)
> - DMN (/)
> - DRL, Guided Rule Template, Guided Rule (/)
> - DSL (/)
> - Enum (/)
> - Form (x) !form-load-fail.png|thumbnail! [^form-load.log]
> - Global variable (/)
> - Guided Decision Tree (/)
> - Guided Scorecard (/)
> - Solver conf
> - Test Scenario, Test Scenario Legacy
> - Work Item Definition
> - Case Definition Legacy (x) - no changes dialog
> - Other
> - Plain text
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months