Hi Claus,

Thank you for responding

by the way - hope you had a nice trip home from Frankfurt...

How would i configure an exception listener explicitly on the MQ Endpoint?
or let's say it in another way: Not that i know :-(

In the meantime i found out, that it has nothing to do with the
onException-Statement in 
or before the route. 
My MQ-Endpoint is, as far i can see, equally defined as those others that
actually work.

Maybe you could give me a hint, what probably could have gone wrong in my
configuration?

If you need more details: This is the spring config (both are Routebuilders
and embedded in the Camelcontext). The second Routes are only there, because
i hoped it would change anything separating
the MQ-Endpoint. Those spring-config properties are just queue-names.

        <!-- is the route of the workpartitioner, building chunks of
vertragsnummern -->
        <bean id="pserunwproute"
class="com.innoq.zifs.konto.camel.postensatzerstellung.WorkPartitionerRoute"
>
                <property name="bean" ref="pserunejbdelegate" />
                <property name="wlDistributor" value="seda:WLonQCreator"  />
                <property name="sizeofchunk" value="5" />
        </bean>
        
        <bean id="wlonqcreator"
class="com.innoq.zifs.konto.camel.postensatzerstellung.WLonQCreator" >
                <property name="inputFrom" value="seda:WLonQCreator"/>
                <property name="wlDistributor"
value="ibmmqvsl:queue:#{zifs.s2.facade.konto.pserunwl}?testConnectionOnStartup=true&amp;cacheLevelName=CACHE_NONE"
 
/>
        </bean>


best wishes,
Martin



Claus Ibsen-2 wrote:
> 
> Hi
> 
> Have you configured an exception listener explicit on the MQ endpoint?
> 
> By debugging a simple JmsInOut unit test with embedded AMQ there is no
> exeption listener set when that Requester is started.
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Method-setExceptionListener-not-permitted-in-J2EE-Servers-tp28693246p28697275.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to