TeamDev Support : Thread List - JxFileWatcher

JxFileWatcher and Network Drives

forum-admin@teamdev.com — Mon, 02 Aug 2010 22:34:58 GMT

Does this library support watching network drives? E.g. IF there are 500K files on a network share, can they all be "watched"?

Thanks!

Client-Server issues, remote filewatcher invocation

forum-admin@teamdev.com — Thu, 15 Jul 2010 09:21:56 GMT

I bought license for filewatcher;

Tests work well on my local computer;

However, when it's integrated in web-site, I get an error that says the operation is not supported. I did some additional testing to narrow down the problem. When I run the Online Demo at http://www.teamdev.com/jxfilewatcher/ , the demo works, and I see the events being logged in the demo output window. Then when I attempt to run from the web-site, I get the operation not supported error. So, it seems like there is some difference in the online demo vs the way the plugin is calling jxfilewatcher.

Could possibly be a version difference in jxfilewatcher, or just some way it is being called differently, or maybe the filters?

Regards

Problem: "ATTENTION: Failed to open file:"

forum-admin@teamdev.com — Thu, 08 Jul 2010 10:23:08 GMT

Hi,

I'm using jxFileWatcher-1.0.2 on Mac OS X Server 10.6.

When I add a lot of file in the directory watched, indications after appear:

8 juil. 2010 12:01:42 com.teamdev.filewatch.mac.KEventWatcher a

ATTENTION: Failed to open file: /xxx/lol.jpg

8 juil. 2010 12:01:42 watch.WatchingAllFileEvents$1 fileAdded

Added[file=/xxx/lol.jpg]

But sometimes, the file isn't added.

So, how I can do to manage this problem.

Thanks.

deleted after renamed

forum-admin@teamdev.com — Thu, 29 Apr 2010 17:11:45 GMT

Hi, i'm testing de WatchingAllFileEvents demo file on macosx 10.6, when i'm renamed a file, the log is "renamed" and "deleted".

Why ?

...WatchingAllFileEvents$1 fileRenamed

INFO: Renamed[old name=/image/toto.jpg, new name=/image/tata.jpg]

... WatchingAllFileEvents$1 fileDeleted

INFO: Deleted[file=/image/tata.jpg]

thanks.

Problem while redeploying j2ee web application using jxfile watcher

vaibhav.vyas@thepsi.com — Fri, 23 Apr 2010 12:46:24 GMT

Hi,

We use JxFileWatcher for keep watch on system folders for any update, for the first time we deploy the application to tomcat6, everthing works well, but if we try to undeploy and redeploy it using admin interface of tomcat then we face following error in running tomcat:

Caused by:
java.lang.UnsatisfiedLinkError: Cannot load native JNIWrapper library (jniwrap.dll).
    at com.jniwrapper.Library.a(SourceFile:112)
    at com.jniwrapper.PlatformContext.u(SourceFile:452)
    at com.jniwrapper.PlatformContext.t(SourceFile:490)
    at com.teamdev.filewatch.a.a(SourceFile:43)
    at com.teamdev.filewatch.FileWatcher.create(SourceFile:369)
    at com.hybrid.jmsclient.bo.Impl.FileEventManager.startWatchedFolder(FileEventManager.java:116)
    at com.hybrid.jmsclient.bo.Impl.FileEventManager.setPreferenceDAO(FileEventManager.java:52)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:786)
    at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:606)
    at org.springframework.beans.AbstractPropertyAccessor.setPropertyValue(AbstractPropertyAccessor.java:49)
    at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:74)
    at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:57)
    at org.springframework.beans.factory.support.AbstractBeanFactory.applyPropertyValues(AbstractBeanFactory.java:840)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1026)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:809)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:250)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:141)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:247)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:161)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
    at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:905)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:525)
    at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1359)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1475)
    at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:250)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859)
    at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
    at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1555)
    at java.lang.Thread.run(Thread.java:595)

which ultimately causes failing in deployment of the web application.

Specifically we are using jxfilewatcher-1.0.1 version and application server is Tomcat 6.0.24

We can see some errors that may cause the issue while undeploying the application that is

SEVERE: A web application registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-4] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-5] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-7] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-8] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-9] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [com.jniwrapper.n] but has failed to stop it. This is very likely to create a memory leak.
Apr 23, 2010 5:08:22 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

I think the jniwrapper thread is not exiting and holding the instance in the memory which is causing the issue, but question is how can we make this thread exit, or there is any other way to deal this problem

Any help is appreciable.

Thanks in advance.

FileWatcher release file

forum-admin@teamdev.com — Wed, 28 Apr 2010 10:56:20 GMT

Hello,

How i'm using watcher now is"

-watcher is started and all folders get related log files;

-collecting logs...
-watcher is stopped, released and all files are parsed;
-watcher is started again and all folders get related log files, again;

What i want to switch to:

-watcher is started and all folders get related log file;

-collecting logs...

onButtonPress()

{

-all folders get another related duplicate log file;
-old watcher is stopped, released and all released files are parsed while new duplicates are monitoring;

}

On 2) way there wouldn't be missed logs that might happen during parsing in 1) scenario;

So, when more than 1 logfile is assigned to 1 folder there is trouble with releasing the logfile(s);

File that is assigned to the folder, that's already under monitoring, is not released properly later, and require application restart or sometimes even environement restart to become unlocked so can be deleted.

I tried already with sequence logFile1.log, logFile1.log.1, logFile1.log.2..., but run into same issue.

Each File handler inside the watcher is initialized:

fh = new FileHandler(log);

And file handler is released manually (event if it's not required in Eclipse)

fh.close();

Any ideas about this issue, please?

Regards

setFilter & WatchingAttributes

forum-admin@teamdev.com — Mon, 26 Apr 2010 16:29:30 GMT

Hello,

In the folder that's selected for watching, my aim is to:

-watch files with extension .pdf and .doc

-watch subfolders

Tried to rework example that i downloaded and found in samples folder: WatchingFilteredFileEvents.java

This part of the code can be reworked for this idea, i think:

// Monitor all events excluding directories
Set<WatchingAttributes> watchingAttributes = EnumSet.allOf(WatchingAttributes.class);
watchingAttributes.remove(WatchingAttributes.DirectoryName);
watcher.setOptions(watchingAttributes);

// Specify monitoring only java and class files
watcher.setFilter(new FileMaskFilter("*.java;*.class"));

But it seems that whenever I set watcher.setFilter, WatchingAttributes are ignored!? Why? Does setFilter method has higher priority than WatchingAttributes, maybe?

How to use setFilter together with WatchingAttributes?

Regards

Issue with JxFileWatcher and TextEdit on OSX?

forum-admin@teamdev.com — Fri, 30 Oct 2009 16:31:36 GMT

I recently spotted that notifications within our application were missing when editing files using TextEdit on OSX. Trying to narrow the cause of this I launched the java ws sample for jxFileWatcher from you're site and see the same behaviour.

It's hard to tell whether this would be a bug within jxFileWatcher itself or unexpected behaviour from Apple's TextEdit application, so I was wondering if anyone else can reproduce this and shed any light upon what may be causing it. For reference I'm using TextEdit Version 1.5 (244) on Mac OS X 10.5.8.

Steps to Reproduce (requires Mac)

Launch jxFileWatcher sample (via teamdev.com)
Create a new folder on disk
Start the sample monitoring the created folder
touch a file in that folder (file watcher correctly shows it as added)
echo content to the file via terminal e.g. echo "1" >> file.txt (file watcher correctly shows updates)
repeat as desired
Open the file with TextEdit, change and save (file watcher shows updates)
Repeat changing the file with TextEdit ~3-4 times more
At this point I no longer see updates appearing from jxFileWatcher
echo content to file again via terminal
Still see no updates appearing

If there's a way to generate more detailed debug from within jxFileWatcher that I can enable to capture more information about this I'm happy to try that.

Cheers,

Ian