locked
csf 3.0 session problem RRS feed

  • Question

  • We have a little problem using csf 3.0 session and we would like to know if it’s possible to handle an error.

    This is the scenario: we use a persistent session and we route messages through this session. If one participant it’s not available we just have the error in the event viewer but session doesn’t send any fault to sender. We also tried to change routing table adding the following route:

     

    <Route>

            <Criteria> MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://www.w3.org/2003/05/soap-envelope/' OR MESSAGE EQ 'Fault' AND MESSAGENS EQ 'http://schemas.xmlsoap.org/soap/envelope/' </Criteria>

            <Destination>UIParticipant[http://schemas.xmlsoap.org/ws/2004/08/addressing/fault]</Destination>

          </Route>

     

     

    If we have an error in creating session we receive the fault by sessionmanager, but in routing message we don’t receive any error.

     

    We also try to change template manifest adding this property: ackOnRouteMsgToParticipants="true". The effect is that session always sends an ack also if the participant is not available.

    Any way to catch session errors during message routing???

     

    Thanks, Fabio

     

    Friday, March 9, 2007 3:07 PM