2 Replies Latest reply on Apr 7, 2011 4:20 AM by danydyn

    Keep alive / status code 500

    danydyn

      Hi,

       

      I am running a jax-ws web service (using CFX). Whenever a service method throws a buisness exception, cxf (jaxws) sets a 500 HTTP status code, which triggers Jboss to insert a Connection: Close header into the HTTP response.

      This behaviour is undesirable, as I want to re-use the connection in the client.

       

      Any suggestions?

       

      Thanks

       

      Daniel

        • 1. Keep alive / status code 500
          jfclere

          CFX? you mean Apache CXF?

          It seems to me that your service connects to something remote.... I don't think that is a JBossWeb problem.

          • 2. Keep alive / status code 500
            danydyn

            Yes, CXF, appologies a typo.

            What do you mean by 'service connects to something remote..'? My web service, which runs on jboss-web throws a SOAP fault exception. JAX-WS sets status 500 in that case. Inspecting the HTTP header comming as a response from jboss-web, it is evident that a Connection: Close was set.

             

            Daniel