[
https://issues.redhat.com/browse/DROOLS-5180?page=com.atlassian.jira.plug...
]
Minal Bhalodi commented on DROOLS-5180:
---------------------------------------
we have seen this issue continuously last two year when year changes. so this is not a
co-incident. Also, issue was fixed when we restarted server, when we restart server it
will first create container with latest jar and after that server was able to update
container with other jars. Somehow create container fixes the issue but update container
API was not able to update container with new year date.
Kie-scanner update container API doesn't refresh container with
latest jar after new year
-----------------------------------------------------------------------------------------
Key: DROOLS-5180
URL:
https://issues.redhat.com/browse/DROOLS-5180
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.18.0.Final
Reporter: Minal Bhalodi
Assignee: Mario Fusco
Priority: Critical
We are using kie-server as a stand alone application. we use kie scanner to update kie
container when there is a new DRL file in our .m2 folder.
we don't have scanner polling but we use Scanner update container API to update kie
container.
Every year when date changes after new year, we are facing issue where kie scanner is not
able to update container with latest jar in m2 with new year date.
When we check the container version it shows latest with new year date but internally kie
is still using old jar.
We fixed this issue with create container API instead update container.
kie-server-spring-boot-starter-drools :7.18.0.Final
Please let me know if this issue is already fixed or discussed before or if you need more
details.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)