Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
No replies
wester
wester
1 Post
ACCEPTED ANSWER

Pinned topic Monitored directory not working on Solaris

‏2011-04-04T11:34:57Z |
Hi all,

while the deployment via a monitored directory in 8 beta3 is running perfectly under Windows, the same settings don't work on Solaris. On Windows the trace com.ibm.ws.management.dragdrop.*=all
shows this result at server startup:

01.04.11 11:34:08:272 CEST 00000000 WatchService 3 watchServiceInit
01.04.11 11:34:08:272 CEST 00000000 WatchService 3 tempDirStr=C:\Daten\WAS8\WebSphere\AppServer\profiles\profile1\wstemp\dragdrop_12f10699f90_1\
01.04.11 11:34:08:272 CEST 00000000 WatchService < watchServiceInit Exit
01.04.11 11:34:08:303 CEST 00000000 WatchService 3 add event listener: com.ibm.ws.management.dragdrop.AppManagementListener@1b91795
01.04.11 11:34:08:303 CEST 00000000 WatchService > start Entry
01.04.11 11:34:08:303 CEST 00000000 WatchService > <init> Entry

On Solaris with the same settings there are no entries in the tracefile indicating that the WatchService is initialized.

Settings in AdminConsole:
Applications -> Global Deployment Settings -> Monitor Directory is checked, monitoredDirectory is ${USER_INSTALL_ROOT}/monitoredDeployableApps
and Polling interval is 5 seconds

On Windows an ear dropped in the directory is installed immediately, on Solaris nothing happens.
Does anyone face the same issue?