[jboss-dev-forums] [Design the new POJO MicroContainer] - HDScanner exception

[emuckenhuber]

Using AS trunk (rev. 74306) the HDScanner fails after while (lets say between 2 and 5 minutes idle) with this Exception:


  | 2008-06-09 13:27:34,689 WARN  [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Scan failed
  | java.lang.NullPointerException
  |         at java.util.Arrays$ArrayList.<init>(Arrays.java:2355)
  |         at java.util.Arrays.asList(Arrays.java:2341)
  |         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:67)
  |         at sun.net.www.protocol.file.FileURLConnection.initializeHeaders(FileURLConnection.java:90)
  |         at sun.net.www.protocol.file.FileURLConnection.getLastModified(FileURLConnection.java:151)
  |         at org.jboss.virtual.plugins.context.AbstractURLHandler.exists(AbstractURLHandler.java:119)
  |         at org.jboss.virtual.VirtualFile.exists(VirtualFile.java:179)
  |         at org.jboss.system.server.profile.basic.ProfileImpl.getModifiedDeployments(ProfileImpl.java:308)
  |         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:260)
  |         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
  |         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
  |         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
  |         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
  |         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
  |         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
  |         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  |         at java.lang.Thread.run(Thread.java:595)
  | 

Deployment does not seem to work after that anymore.
Furthermore running the testsuite with one-test ends up with in the following:


  | 2008-06-09 13:27:44,429 ERROR [org.jboss.naming.Naming] (JBoss System Threads(1)-2) Naming accept handler stopping
  | java.net.SocketException: Too many open files
  |         at java.net.PlainSocketImpl.socketAccept(Native Method)
  |         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
  |         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
  |         at java.net.ServerSocket.accept(ServerSocket.java:421)
  |         at org.jnp.server.Main$AcceptHandler.run(Main.java:482)
  |         at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  |         at java.lang.Thread.run(Thread.java:595)
  | 

Someone else experiencing the same problem? Any hints?

Thanks,
Emanuel

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156662#4156662

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156662