Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Error on undeploy/deploy

  1. #11
    Join Date
    Feb 2008
    Location
    Dublin - Ireland
    Posts
    102

    Default

    I just tried with 1.0.0.M3 and it gets rid of the loop and the NPE that was giving, it still gives the WebappClassLoader exception:

    09:13:12,474 INFO [WebappClassLoader] Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.spi.VectorWriter. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
    java.lang.IllegalStateException
    at org.apache.catalina.loader.WebappClassLoader.loadC lass(WebappClassLoader.java:1244)
    at org.apache.catalina.loader.WebappClassLoader.loadC lass(WebappClassLoader.java:1204)
    at java.lang.ClassLoader.loadClassInternal(ClassLoade r.java:319)
    at org.apache.log4j.spi.LoggingEvent.<init>(LoggingEv ent.java:154)
    at org.apache.log4j.Category.forcedLog(Category.java: 388)
    at org.apache.log4j.Category.log(Category.java:853)
    at org.apache.commons.logging.impl.Log4JLogger.warn(L og4JLogger.java:234)
    at org.springframework.integration.scheduling.Message PublishingErrorHandler.handle(MessagePublishingErr orHandler.java:55)
    at org.springframework.integration.scheduling.SimpleM essagingTaskScheduler$MessagingTaskRunner.run(Simp leMessagingTaskScheduler.java:140)
    at java.util.concurrent.Executors$RunnableAdapter.cal l(Executors.java:417)
    at java.util.concurrent.FutureTask$Sync.innerRunAndRe set(FutureTask.java:280)
    at java.util.concurrent.FutureTask.runAndReset(Future Task.java:135)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.access$101(ScheduledThreadPoolE xecutor.java:65)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.runPeriodic(ScheduledThreadPool Executor.java:142)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.run(ScheduledThreadPoolExecutor .java:166)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)

  2. #12
    Join Date
    Feb 2008
    Location
    Dublin - Ireland
    Posts
    102

    Default

    And now I'm getting *another* endless loop...

    15:37:22,224 INFO [STDOUT] - DefaultErrorChannel has reached capacity. Are any handlers subscribed?
    15:37:22,224 INFO [STDOUT] - DefaultErrorChannel has reached capacity. Are any handlers subscribed?
    15:37:22,224 INFO [STDOUT] - failure occurred in messaging task
    java.lang.NullPointerException
    at org.apache.commons.logging.LogFactory.getCachedFac tory(LogFactory.java:979)
    at org.apache.commons.logging.LogFactory.getFactory(L ogFactory.java:435)
    at org.apache.commons.logging.LogFactory.getLog(LogFa ctory.java:685)
    at org.springframework.integration.dispatcher.Default MessageDistributor.<init>(DefaultMessageDistributo r.java:43)
    at org.springframework.integration.dispatcher.Default MessageDispatcher.getDistributor(DefaultMessageDis patcher.java:195)
    at org.springframework.integration.dispatcher.Default MessageDispatcher.access$1(DefaultMessageDispatche r.java:191)
    at org.springframework.integration.dispatcher.Default MessageDispatcher$DispatcherTask.run(DefaultMessag eDispatcher.java:217)
    at org.springframework.integration.scheduling.SimpleM essagingTaskScheduler$MessagingTaskRunner.run(Simp leMessagingTaskScheduler.java:136)
    at java.util.concurrent.Executors$RunnableAdapter.cal l(Executors.java:417)
    at java.util.concurrent.FutureTask$Sync.innerRunAndRe set(FutureTask.java:280)
    at java.util.concurrent.FutureTask.runAndReset(Future Task.java:135)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.access$101(ScheduledThreadPoolE xecutor.java:65)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.runPeriodic(ScheduledThreadPool Executor.java:142)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.run(ScheduledThreadPoolExecutor .java:166)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)

  3. #13
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,854

    Default

    Are you using 1.0.0.M3 or the latest snapshot?

    -Mark

  4. #14
    Join Date
    Feb 2008
    Location
    Dublin - Ireland
    Posts
    102

    Default

    I do have the latest snapshot on my workspace, but since I'm using maven to build and the top pom has in the dependencyManagement

    <dependency>
    <groupId>org.springframework.integration</groupId>
    <artifactId>spring-integration-core</artifactId>
    <version>1.0.0.M3</version>
    </dependency>

    I assume that on runtime is the 1.0.0.M3 that's being used.

  5. #15
    Join Date
    Feb 2008
    Location
    Dublin - Ireland
    Posts
    102

    Default

    This probably has to do with the implementation I'm trying to do of a synchronous-that-falls-down-to-asynchronous-with-correlationId-when-timedout messages, because the same error (or at least a similar one) is occurring elsewhere besides hot-redeploying...

    It's very difficult to debug with time outs and futures!

    BTW, I also using modified versions of RequestReplyTemplate, MessageStore, RetrievalBlockingMessageStore ans SimpleMessage, but except for the first all I did was adding a iterator.
    Last edited by amsmota; Apr 21st, 2008 at 10:16 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •