[
https://issues.apache.org/jira/browse/IGNITE-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625622#comment-16625622
]
Alexey Goncharuk commented on IGNITE-9381:
------------------------------------------
[~antonovsergey93], I am afraid that javadoc is outdated, and we need to clear
the whole dynamic loader from the cache.
Please make the following changes to the test:
1) Move TestPredicate to p2p module. The flow of the test may be different if
the classes are available from the classpath
2) In the code of the predicate make use of some other classes from the p2p
module (create a new object, etc)
3) Inside the test make an update to trigger additional class loading
4) After undeploy, check that additional classes are not present in the class
cache.
5) In your test, there is no need to do a broadcast for
{{call(MessageCountingCommunicationSpi::deploymentRequestCount)}} because the
field is static and you can read it right away.
> p2p does not undeploy ScanQuery IgniteBiPredicate filter on client node
> disconnect
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-9381
> URL: https://issues.apache.org/jira/browse/IGNITE-9381
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrew Medvedev
> Assignee: Sergey Antonov
> Priority: Major
> Fix For: 2.7
>
> Attachments: AndmedScanFilterClassLoadingTest.java, snapshots.xml
>
>
> Once deployed via scan query, an IgniteBiPredicate filter does not change if
> client reconnects (with a modified filter)
> Steps to reproduce:
> * start server node in separate jvm with attached configuration (persistence
> enabled)
> * run attached reproducer AndmedScanFilterClassLoadingTest. It includes a
> task and a scan filter, both print "FOO" on server side
> * modify FOO -> BAR for both
> * re-run modifed AndmedScanFilterClassLoadingTest .
> Expected: Both print "BAR".
> Actual behavior: task prints "BAR", scan filter prints "FOO"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
