[jboss-jira] [JBoss JIRA] (DROOLS-5180) Kie-scanner update container API doesn't refresh container with latest jar after new year

[Mario Fusco (Jira)]

    [ https://issues.redhat.com/browse/DROOLS-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010143#comment-14010143 ] 

Mario Fusco commented on DROOLS-5180:
-------------------------------------

[~mbhalodi_intuit] I'm not able to reproduce this problem in any way. We're using standard maven API to retrieve the highest version number. I believe that the new year's date is a red herring and the actual problem is totally unrelated with it. More likely you tried to upgrade to a corrupted jar and then the kiecontainer rolled it back to the previous version (maybe reporting the wrong version number at that point, but I also checked that part and couldn't reproduce this either). If I'm right, the fact that this happened at the beginning of the new year is probably just a coincidence. Please clarify if you have any evidence of the relationship with the new year day and if so let me know how to reproduce this issue.

> 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)