Can not get new version of JSP of a component in publish

[Xena_bcn]

hi there

I made changes to JSP of 1 component, precisely to JavaScript inside, some changes i get directly on 4503 after replicating.

but some hours ago I stopped getting the latest changes on 4503.

The JS code is the same as before on that page.

although the log says:

 *INFO* [127.0.0.1 [1457542043639] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.servlets.ReplicationServlet Processed replication action in 17ms: ACTIVATE of /<project>/components/documentationlist/cq:editConfig
 *INFO* [88.8.87.103 [1457542052015] GET /content/<project>/<path>/<page>.html HTTP/1.1] org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceManager cachename=versionBundleCache[ConcurrentCache@4908421b], elements=942, usedmemorykb=98, maxmemorykb=8192, access=24638, miss=942
*INFO* [127.0.0.1 [1457542102702] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.content.durbo.DurboImporter imported content in 266ms for durbo request on path: /content/<project>/<path>/<page>
*INFO* [127.0.0.1 [1457542102702] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.servlets.ReplicationServlet Processed replication action in 268ms: ACTIVATE of /content/<project>/<path>/<page>
*INFO* [pool-6-thread-1-null(null)] com.day.cq.workflow.impl.CQPayloadMap Getting all running workflows (0) for cache population took: 36ms
*INFO* [pool-6-thread-1-null(null)] com.day.cq.workflow.impl.CQPayloadMap Initial workflow payload cache population took 36ms

Please help,

Xena

[edubey]

Create a package using package manager and replicate it.

Check for replication logs.

Clear cache for 4503 server, browser cache, dispatcher cache

if you have access to crx/de of server 4503, login to that server and see code changes are there or not.

[Xena_bcn · Accepted solution]

thank you a lot.

I followed as you said.

I saw that JSP of the component on 4503 was updated.

After that I had to delete a folder "design" in this path var/clientlibs/etc/  in the CRXDE Lite.

Seems it was caching old JavaScript code.