glassfish
  1. glassfish
  2. GLASSFISH-19063

Web-service client deployment fails with NullPointerException in WSATGatewayRM.setTxLogDirs(WSATGatewayRM.java:430)

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Works as designed
    • Affects Version/s: 3.1.2
    • Fix Version/s: None
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      Glassfish 3.1.2.2

      Description

      I have the following situation
      Webservice client (Glassfish 3.1.2.2) ----> Webservice server (up & running)

      During the deployment phase I am getting exception as indicated in the attached file.
      I want to underline that the same application (the deployment) is working fine with Glassfish 3.1.1

      The exception is

      java.lang.RuntimeException: EJB Container initialization error
      	at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:242)
      ...
      Caused by: java.lang.NullPointerException
      	at java.io.File.<init>(File.java:222)
      	at com.sun.xml.ws.tx.at.internal.WSATGatewayRM.setTxLogDirs(WSATGatewayRM.java:430)
      

        Activity

        Hide
        Hong Zhang added a comment -

        As the stack trace is from webservices code, I will let the webservices team do the evaluation on this one.

        Show
        Hong Zhang added a comment - As the stack trace is from webservices code, I will let the webservices team do the evaluation on this one.
        Hide
        xavierandre added a comment -

        Hi,

        I have same issue on same GF version, any idea of time for fix ?
        Thank you.

        Show
        xavierandre added a comment - Hi, I have same issue on same GF version, any idea of time for fix ? Thank you.
        Hide
        arjavdesai added a comment -

        Is this application a WS-AT client or service? Can you please post the application as well?

        If its a client, you need to apply the work-around as specified in release notes and part of http://java.net/jira/browse/WSIT-1500 i.e.

        "The WS-C and WS-AT endpoints necessary for WS-AT are deployed when the first web service is deployed. Therefore, it is necessary to have at least one web service deployed for WS-AT to function properly even in the case where only clients are used in the Metro instance."

        Show
        arjavdesai added a comment - Is this application a WS-AT client or service? Can you please post the application as well? If its a client, you need to apply the work-around as specified in release notes and part of http://java.net/jira/browse/WSIT-1500 i.e. "The WS-C and WS-AT endpoints necessary for WS-AT are deployed when the first web service is deployed. Therefore, it is necessary to have at least one web service deployed for WS-AT to function properly even in the case where only clients are used in the Metro instance."
        Hide
        Marcin_C added a comment -

        This is a client application. Unfortunately I cannot attach any source codes.

        Show
        Marcin_C added a comment - This is a client application. Unfortunately I cannot attach any source codes.
        Hide
        arjavdesai added a comment -

        As I mentioned in my first comment, if you have just a client application, you need to deploy a simple/any service application first as mentioned in the release notes.

        Show
        arjavdesai added a comment - As I mentioned in my first comment, if you have just a client application, you need to deploy a simple/any service application first as mentioned in the release notes.

          People

          • Assignee:
            arjavdesai
            Reporter:
            Marcin_C
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: