wsit
  1. wsit
  2. WSIT-539

WS-AT txn registration fails silently, only SEVERE event in server.log

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Won't Fix
    • Affects Version/s: current
    • Fix Version/s: 2.1
    • Component/s: transaction
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      539

      Description

      A WSIT client is not informed explicitly when its WS-AtomicTransaction enabled
      request is not working as expected. Specifically, when a wscoor:register fails
      due to such reasons as (1) firewall blocking request (2) misconfigured security
      certificates on client or transacted web service side (3) .....

      Currently, the following SEVERE message is printed in server log of
      transacted web service when a wscoor:register fails.

      SEVERE WSTX-AT-0022: Registration with durable parent failed:

      This it is not obvious on client side when a distributed WS-Atomic Transaction
      that should be in effect is not working properly w/o analyzing sevver log.

      Recommended remedy is to also throw a WebServiceException. The Exception
      message would contain text as SEVERE message and the exception that
      caused the register to fail would be nested within the WebServiceException.
      The client benefits from the more immediate feedback that WS-AT 2 phase commit
      is not possible due to some network configuration issue.

        Activity

        Hide
        jfialli added a comment -

        Throwing a WebServiceException is too big a change to make this close to FCS.
        Additionally, server log does have a SEVERE event log message when this occurs.
        Typically only occurs when client-side firewall is not properly configured to
        allow communications.

        Show
        jfialli added a comment - Throwing a WebServiceException is too big a change to make this close to FCS. Additionally, server log does have a SEVERE event log message when this occurs. Typically only occurs when client-side firewall is not properly configured to allow communications.
        Hide
        m_potociar added a comment -

        Reassigning to the component owner

        Show
        m_potociar added a comment - Reassigning to the component owner
        Hide
        Marek Potociar added a comment -

        This issue report does not apply to the new WS-AT implementation in Metro 2.1

        Show
        Marek Potociar added a comment - This issue report does not apply to the new WS-AT implementation in Metro 2.1

          People

          • Assignee:
            paul_parkinson
            Reporter:
            jfialli
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: