[jboss-jira] [JBoss JIRA] (DROOLS-5180) Kie-scanner update container API doesn't refresh container with latest jar after new year
[
https://issues.redhat.com/browse/DROOLS-5180?page=com.atlassian.jira.plug...
]
Minal Bhalodi edited comment on DROOLS-5180 at 4/3/20 3:59 PM:
---------------------------------------------------------------
I am able to reproduce this problem.
1)First in .m2 folder first I added jar with version name person-10.23.2019-06-30-00.jar
and started kie server.
Kie-server created container with jar version 10.23.2019-06-30-00.
2)While server was running, I added person-10.23.2019-20-30-00.jar and kie container was
updated with latest jar. Though I was adding this jar manually in S3, I also updated
maven-metadata-local.xml manually to modify release and version with
person-10.23.2019-20-30-00.jar
3)Then again without stopping server, I added person-04.02.2020-15-00-04.jar and updated
release and version in maven-metadata-local.xml. This time kie server was not updated with
version 04.02.2020-15-00-04.
our maven-metadata-local.xml
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId><value></groupId>
<artifactId><value></artifactId>
<versioning>
<release>10.23.2019-20-30-00</release>
<versions>
<version>10.23.2019-06-30-00</version>
<version>04.02.2020-15-00-04</version>
<version>10.23.2019-20-30-00</version>
</versions>
<lastUpdated>1585869333000</lastUpdated>
</versioning>
</metadata>
I don't have sample code to reproduce this issue but if you can share a sample code
where kie-server updates container in reference to .m2 folder then I might be able to
reproduce this issue
was (Author: mbhalodi_intuit):
I am able to reproduce this problem.
1)First in .m2 folder first I added jar with version name person-10.23.2019-06-30-00.jar
and started kie server.
Kie-server created container with jar version 10.23.2019-06-30-00.
2)While server was running, I added person-10.23.2019-20-30-00.jar and kie container was
updated with latest jar. Though I was adding this jar manually in S3, I also updated
maven-metadata-local.xml manually to modify release and version with
person-10.23.2019-20-30-00.jar
3)Then again without stopping server, I added person-04.02.2020-15-00-04.jar and updated
release and version in maven-metadata-local.xml. This time kie server was not updated with
version 04.02.2020-15-00-04.
our maven-metadata-local.xml
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId><value></groupId>
<artifactId><value></artifactId>
<versioning>
<release>10.23.2019-20-30-00</release>
<versions>
<version>10.23.2019-06-30-00</version>
<version>04.02.2020-15-00-04</version>
<version>10.23.2019-20-30-00</version>
</versions>
<lastUpdated>1585869333000</lastUpdated>
</versioning>
</metadata>
I don't sample code to reproduce this issue but if you can share a sample code where
kie-server updates container in reference to .m2 folder then I might be able to reproudce
this issue there
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)