Announcement Announcement Module
No announcement yet.
Dispatcher has no subscribers: Not in IDE, only when deployed to Websphere?! Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Dispatcher has no subscribers: Not in IDE, only when deployed to Websphere?!

    i have a junit test and a webapp which execute the same SI 2.0.5 (Spring 3.0.5) code successfully in STS and RAD
    (war under tomcat in STS, ear under websphere in RAD),
    but when i build the code into an ear using ant and deploy to websphere (6.1.x) "proper",
    i get:

    [1/19/12 12:58:08:690 EST] 0000004f SystemErr     R Caused by: org.springframework.integration.MessageDeliveryException: Dispatcher has no subscribers.
    	at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(
    	at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(
    	at org.springframework.integration.core.MessagingTemplate.doSend(
    	at org.springframework.integration.core.MessagingTemplate.doSendAndReceive(
    	at org.springframework.integration.core.MessagingTemplate.sendAndReceive(
    	at org.springframework.integration.core.MessagingTemplate.sendAndReceive(
    there are some specific details about code, build scripts and websphere that i can look into,
    but before i potentially go on a witch hunt, i figured i'd go bumming for suggestions as to what might lead to
    this disparate behavior across environments (vs i just flubbed the configuration and it has never worked).

    for instance, in my preliminary investigation, i came across some mention of SmartLifecycle. I'm not familiar with this,
    so i haven't made use of it explicitly, could not paying attention to that cause subtle timing differences in different environments that could lead to this condition? if so, how might i hook into the SmartLifecycle to affect this?

    any suggestions appreciated,
    Last edited by tony_k; Jan 19th, 2012, 06:41 PM.

  • #2
    after a few bounces of the websphere jvm this issue seems to have resolved itself.

    i'm going to chalk this one up to websphere gremlins and move on