search

ismir-mirex / nemadiy

Automatically exported from code.google.com/p/nemadiy
0 stars 1 forks source link

Flow service exception #138

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
WARN [RMI TCP Connection(276)-128.174.154.86] (HttpMethodBase.java:685) - Going 
to buffer response body of large or unknown size. Using getResponseAsStream 
instead is recommended.
 INFO [RMI TCP Connection(242)-128.174.154.86] (AuthChallengeProcessor.java:100) - basic authentication scheme selected
 WARN [RMI TCP Connection(242)-128.174.154.86] (HttpMethodBase.java:685) - Going to buffer response body of large or unknown size. Using getResponseAsStream instead is recommended.
 INFO [RMI TCP Connection(276)-128.174.154.86] (AuthChallengeProcessor.java:100) - basic authentication scheme selected
 WARN [RMI TCP Connection(276)-128.174.154.86] (HttpMethodBase.java:685) - Going to buffer response body of large or unknown size. Using getResponseAsStream instead is recommended.
java.lang.NullPointerException
        at org.imirsel.nema.flowservice.notification.JobStatusNotificationCreator.jobStatusUpdate(JobStatusNotificationCreator.java:75)
        at org.imirsel.nema.flowservice.monitor.PollingJobStatusMonitor$StatusUpdateDetector.run(PollingJobStatusMonitor.java:236)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
2010.09.07 21:31:43.494::WARNING:  null   
[org.imirsel.nema.flowservice.monitor.PollingJobStatusMonitor$StatusUpdateDetect
or.run] <pool-2-thread-1:11>
 INFO [RMI TCP Connection(277)-128.174.154.86] (AuthChallengeProcessor.java:100) - basic authentication scheme selected
 WARN [RMI TCP Connection(277)-128.174.154.86] (HttpMethodBase.java:685) - Going to buffer response body of large or unknown size. Using getResponseAsStream instead is recommended.
java.lang.NullPointerException
        at org.imirsel.nema.flowservice.notification.JobStatusNotificationCreator.jobStatusUpdate(JobStatusNotificationCreator.java:75)
        at org.imirsel.nema.flowservice.monitor.PollingJobStatusMonitor$StatusUpdateDetector.run(PollingJobStatusMonitor.java:236)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
2010.09.07 21:32:13.545::WARNING:  null   
[org.imirsel.nema.flowservice.monitor.PollingJobStatusMonitor$StatusUpdateDetect
or.run] <pool-2-thread-1:11>

Original issue reported on code.google.com by kumarami...@gmail.com on 8 Sep 2010 at 5:30