Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR ( - No match for watch event #223

ThueGram-Hansen opened this issue Dec 22, 2017 · 2 comments


Copy link

@ThueGram-Hansen ThueGram-Hansen commented Dec 22, 2017

Hi Hotswap agents,

thanks for a great plugin! However, I'm experiencing some issues I hope you can help me resolve. I've got:
• Java v. 1.8.0_144
• Spring 4.2.3 multi module system
• running on Apache Tomcat (TomEE)/7.0.62 (1.7.2)
and the hotswap agent plugin Version: 1.2 installed through IntelliJ 2016.3.7 Unlimited. The plugin is working well for hotswapping java classes, but an error messages is constantly printed as output, after application deployment:

HOTSWAP AGENT: 15:08:43.469 ERROR ( - No match for watch event 'sun.nio.fs.AbstractWatchKey$Event@58f34039', path '...\tomee\apache-tomee-plume-1.7.2\logs\core.log'

I've tried various, but can't seem to ignore the tomee .log files.

I’m also not able to hot swap resources. I’ve tried multiple paths for the watchResources property, but it still doesn’t seem to work. As I said, there are quite a few modules and therefore also different resource folders, so I’m unsure about the correct approach. Hope you can help me swapping it like it hot, and keep up the excellent work.

Best regards

Copy link

@edudant edudant commented Dec 29, 2017

Can you please create a sample project in repo?

@edudant edudant added the bug label Dec 29, 2017
@edudant edudant self-assigned this Dec 29, 2017
edudant pushed a commit that referenced this issue May 4, 2018
…r parent directory instead of actual directory.
Copy link

@edudant edudant commented May 7, 2018

TreeWatcherNIO registered events in parent directory instead of actual directory. Solved.

@edudant edudant closed this May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.