1. 홈
  2. 질의 응답
  3. DataPower 웹 서비스 프록시가 500 오류를 받고 있습니다.

DataPower 웹 서비스 프록시가 500 오류를 받고 있습니다.

2016-12-28 3 views
0

DataPower에 문제가 있습니다. 나는 ws proxy를 설정하려고 시도하지만 http 500을 계속 던지고있다. wsdl, java 코드를 아래에 제공 할 것이다.DataPower 웹 서비스 프록시가 500 오류를 받고 있습니다.

필자는 Remote Endpoint Host를 내 IP (로컬 호스트가 아님)로 설정했습니다 : 8080 - 이클립스 + Tomcat에서이 ws를 호스트하고 VM의 IP에 로컬 끝점 호스트를 사용합니다 - 사용하지 않는 포트가있는 DataPower Gateway Trial의 인스턴스 2911). wsdl 파일을 업로드하고 forc를 설정했습니다.

SOAP UI를 사용하여 POST 요청을 http://VMip/WebServiceProject/services/UsersCatalog에 getUserName 메서드 호출과 함께 보내고 테스트하려고하는데 오류 500이 발생합니다.하지만 모든 것을 시도했지만 아직 작동하지 않습니다. 도와주세요!

UsersCatalog.wsdl 

<wsdl:message name="setUserDataResponse"> 

     <wsdl:part element="impl:setUserDataResponse" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:message name="getUserDataRequest"> 

     <wsdl:part element="impl:getUserData" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:message name="setUserDataRequest"> 

     <wsdl:part element="impl:setUserData" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:message name="getUserNameResponse"> 

     <wsdl:part element="impl:getUserNameResponse" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:message name="getUserDataResponse"> 

     <wsdl:part element="impl:getUserDataResponse" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:message name="getUserNameRequest"> 

     <wsdl:part element="impl:getUserName" name="parameters"> 

     </wsdl:part> 

    </wsdl:message> 

    <wsdl:portType name="UsersCatalog"> 

     <wsdl:operation name="getUserData"> 

     <wsdl:input message="impl:getUserDataRequest" name="getUserDataRequest"> 

     </wsdl:input> 

     <wsdl:output message="impl:getUserDataResponse" name="getUserDataResponse"> 

     </wsdl:output> 

     </wsdl:operation> 

     <wsdl:operation name="setUserData"> 

     <wsdl:input message="impl:setUserDataRequest" name="setUserDataRequest"> 

     </wsdl:input> 

     <wsdl:output message="impl:setUserDataResponse" name="setUserDataResponse"> 

     </wsdl:output> 

     </wsdl:operation> 

     <wsdl:operation name="getUserName"> 

     <wsdl:input message="impl:getUserNameRequest" name="getUserNameRequest"> 

     </wsdl:input> 

     <wsdl:output message="impl:getUserNameResponse" name="getUserNameResponse"> 

     </wsdl:output> 

     </wsdl:operation> 

    </wsdl:portType> 

    <wsdl:binding name="UsersCatalogSoapBinding" type="impl:UsersCatalog"> 

     <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> 

     <wsdl:operation name="getUserData"> 

     <wsdlsoap:operation soapAction=""/> 

     <wsdl:input name="getUserDataRequest"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:input> 

     <wsdl:output name="getUserDataResponse"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:output> 

     </wsdl:operation> 

     <wsdl:operation name="setUserData"> 

     <wsdlsoap:operation soapAction=""/> 

     <wsdl:input name="setUserDataRequest"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:input> 

     <wsdl:output name="setUserDataResponse"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:output> 

     </wsdl:operation> 

     <wsdl:operation name="getUserName"> 

     <wsdlsoap:operation soapAction=""/> 

     <wsdl:input name="getUserNameRequest"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:input> 

     <wsdl:output name="getUserNameResponse"> 

      <wsdlsoap:body use="literal"/> 

     </wsdl:output> 

     </wsdl:operation> 

    </wsdl:binding> 

    <wsdl:service name="UsersCatalogService"> 

     <wsdl:port binding="impl:UsersCatalogSoapBinding" name="UsersCatalog"> 

     <wsdlsoap:address location="http://10.57.129.63:8080/WebServiceProject/services/UsersCatalog"/> 

     </wsdl:port> 

    </wsdl:service> 

</wsdl:definitions>

UsersCatalog (userImpl 단지 2 개 필드 클래스 - 사용자 이름과 userAddress + 게터와 세터) 앤더스 요청

package wtp; 

import javax.jws.WebMethod; 
import javax.jws.WebService; 

@WebService 
public class UsersCatalog implements User{ 
    public static final User userImpl = new UserImpl(); 

    @WebMethod 
    public String getUserName() { 
     return userImpl.getUserName(); 
    } 

    @WebMethod 
    public String getUserData() { 
     return userImpl.getUserData(); 
    } 

    @WebMethod 
    public void setUserData(String userName, String userAddress) { 
     userImpl.setUserData(userName, userAddress); 
    } 
}

로그로 :

11:54:45 network   debug  16945 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:45 multistep  debug  3044 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:45 multistep  debug  3044 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:41 memory-report debug  33491    10.57.129.63 0x80e00690 wsgw (User.wsp): Response Finished: memory used 0 
11:54:41 ws-proxy  information 33491 error  10.57.129.63 0x80e000b6 wsgw (User.wsp): No match from processing policy 'User.wsp' for code '0x01130006' 
11:54:41 ws-proxy  warning  33491    10.57.129.63 0x80c0007b wsm-stylepolicy (User.wsp): No error rule is matched. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x810000d6 wsgw (User.wsp): Match: Received value [http://www.datapower.com/fragment-id#dp.all()] matches WSDL component type 'fragmentid' 'getUserData'. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x810000d6 wsgw (User.wsp): Match: Received value [http://www.datapower.com/fragment-id#dp.all()] matches WSDL component type 'fragmentid' 'getUserData'. 
11:54:41 ws-proxy  error  33491 error  10.57.129.63 0x01130006 wsgw (User.wsp): Failed to establish a backside connection 
11:54:41 ws-proxy  error  33491    10.57.129.63 0x80e00126 wsgw (User.wsp): Valid backside connection could not be established: Failed to establish a backside connection, url: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  error  33491    10.57.129.63 0x80e00627 wsgw (User.wsp): Error occurred (port error) when connecting to URL 'http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog' 
11:54:41 network   error  33491        0x80e00049 xmlmgr (default): Host connection failed to establish: 10.57.129.63 : tcp port 2911 
11:54:41 network   error  33491        0x00b30009 xmlmgr (default): Host connection could not be established 
11:54:41 network   debug  3471        0x80e006bd A hangup error occurred on socket (119). Error details (111: Connection refused). Local(10.57.129.109:25227) - Remote(n/a) 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00536 wsgw (User.wsp): HTTP Header-Retention:Compression Policy: Off, URL: /WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00536 wsgw (User.wsp): HTTP Header-Retention:Header-Retention Policy:MQMD = OFF. MQMD Header = (NULL), URL: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00536 wsgw (User.wsp): HTTP Header-Retention:Header-Retention Policy: Range = OFF. Range Header = (NULL), URL: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00536 wsgw (User.wsp): HTTP Header-Retention:Header-Retention Policy: Accept-Encoding = OFF. Accept-Encoding Header = gzip,deflate, URL: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00536 wsgw (User.wsp): HTTP Header-Retention:Header-Retention Policy: TE = OFF. TE Header = (NULL), URL: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 network   debug  33491    10.57.129.63 0x80e003ca xmlmgr (default): Attempting TCP connect to 10.57.129.63 
11:54:41 multistep  information 33491 request  10.57.129.63 0x80c00002 wsgw (User.wsp): rule (User.wsp_default_request-rule): #2 results: Generated from INPUT. Results stored in OUTPUT. completed OK. 
11:54:41 memory-report debug  33491 request  10.57.129.63 0x80e0068d wsgw (User.wsp): Processing [Rule (User.wsp_default_request-rule), Action ('User.wsp_default_request-rule_defaultaction_result', results()), Input(INPUT), Output(OUTPUT)] finished: memory used 342160 
11:54:41 multistep  information 33491 request  10.57.129.63 0x80c00002 wsgw (User.wsp): rule (User.wsp_default_request-rule): #1 slm: 'INPUT User.wsp' completed OK. 
11:54:41 memory-report debug  33491 request  10.57.129.63 0x80e0068d wsgw (User.wsp): Processing [Rule (User.wsp_default_request-rule), Action ('User.wsp_default_request-rule_defaultaction_slm', slm(User.wsp)), Input(INPUT), Output(NULL)] finished: memory used 0 
11:54:41 xmlfilter  information 33491 request  10.57.129.63 0x80c00036 wsgw (User.wsp): Accept set. 
11:54:41 xslt   debug  33491    10.57.129.63 0x80a002ac xmlmgr (default): xslt Compilation Request: Found in cache store:///dp/slmpolicy.xsl. 
11:54:41 xslt   debug  33491    10.57.129.63 0x80a002aa xmlmgr (default): xslt Compilation Request: Checking cache for URL 'store:///dp/slmpolicy.xsl'. 
11:54:41 multistep  debug  33491 request  10.57.129.63 0x80c0004e wsgw (User.wsp): Stylesheet URL to compile is 'store:///dp/slmpolicy.xsl' 
11:54:41 ws-proxy  information 33491    10.57.129.63 0x80a002a4 xmlmgr (default): wsdl Compilation Request: Compilation complete of URL 'local:///UsersCatalog.wsdl'. Memory used 1349568 bytes. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80a002a3 xmlmgr (default): wsdl Compilation Request: Beginning compilation of URL 'local:///UsersCatalog.wsdl'. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80a002af xmlmgr (default): wsdl Compilation Request: Not in cache. Compiling 'local:///UsersCatalog.wsdl'. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80a002aa xmlmgr (default): wsdl Compilation Request: Checking cache for URL 'local:///UsersCatalog.wsdl'. 
11:54:41 xmlparse  debug  33491 request  10.57.129.63 0x80e003ab wsgw (User.wsp): Finished parsing: http://10.57.129.110:2912/WebServiceProject/services/UsersCatalog 
11:54:41 xmlparse  debug  33491 request  10.57.129.63 0x80e003a6 wsgw (User.wsp): Parsing document: 'http://10.57.129.110:2912/WebServiceProject/services/UsersCatalog' 
11:54:41 multistep  warning  33491 request  10.57.129.63 0x00340027 wsgw (User.wsp): Multistep Probe enabled 
11:54:41 memory-report debug  33491    10.57.129.63 0x80e0068c wsgw (User.wsp): Request Started: memory used 0 
11:54:41 ws-proxy  information 33491 request  10.57.129.63 0x80e000b4 wsm-stylepolicy (User.wsp): rule (User.wsp_default_request-rule): selected via match 'User.wsp_match_all' from processing policy 'User.wsp' 
11:54:41 http   debug  33491    10.57.129.63 0x81000171 Matching (User.wsp_match_all): Match: Received URL [/WebServiceProject/services/UsersCatalog] matches rule '*' 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x810000d6 wsgw (User.wsp): Match: Received value [http://www.datapower.com/fragment-id#dp.all()] matches WSDL component type 'fragmentid' 'getUserData'. 
11:54:41 ws-proxy  information 33491    10.57.129.63 0x80e00383 source-http (handler): WS-Proxy selected: 'User.wsp'. Operation 'getUserData' matches all criteria. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00384 source-http (handler): WS-Proxy User.wsp operation getUserName does not match SOAP operation as required by WS-I BP1.0/1.1 R2744 or R2745: received (getUserData) required (getUserName). Received protocol 'http://schemas.xmlsoap.org/wsdl/soap/', required protocol 'http://schemas.xmlsoap.org/wsdl/soap12/'. Received SOAPAction ((null)) required SOAPAction(). SOAPAction policy is lax. 
11:54:41 ws-proxy  warning  33491    10.57.129.63 0x80e004b8 source-http (handler): Unrecognized content type so SOAP Action header '' will be ignored 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00384 source-http (handler): WS-Proxy User.wsp operation setUserData does not match SOAP operation as required by WS-I BP1.0/1.1 R2744 or R2745: received (getUserData) required (setUserData). Received protocol 'http://schemas.xmlsoap.org/wsdl/soap/', required protocol 'http://schemas.xmlsoap.org/wsdl/soap12/'. Received SOAPAction ((null)) required SOAPAction(). SOAPAction policy is lax. 
11:54:41 ws-proxy  warning  33491    10.57.129.63 0x80e004b8 source-http (handler): Unrecognized content type so SOAP Action header '' will be ignored 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00384 source-http (handler): WS-Proxy User.wsp operation getUserData does not match SOAP operation as required by WS-I BP1.0/1.1 R2744 or R2745: received (getUserData) required (getUserData). Received protocol 'http://schemas.xmlsoap.org/wsdl/soap/', required protocol 'http://schemas.xmlsoap.org/wsdl/soap12/'. Received SOAPAction ((null)) required SOAPAction(). SOAPAction policy is lax. 
11:54:41 ws-proxy  warning  33491    10.57.129.63 0x80e004b8 source-http (handler): Unrecognized content type so SOAP Action header '' will be ignored 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00384 source-http (handler): WS-Proxy User.wsp operation getUserName does not match SOAP operation as required by WS-I BP1.0/1.1 R2744 or R2745: received (getUserData) required (getUserName). Received protocol 'http://schemas.xmlsoap.org/wsdl/soap/', required protocol 'http://schemas.xmlsoap.org/wsdl/soap/'. Received SOAPAction() required SOAPAction(). SOAPAction policy is lax. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e00384 source-http (handler): WS-Proxy User.wsp operation setUserData does not match SOAP operation as required by WS-I BP1.0/1.1 R2744 or R2745: received (getUserData) required (setUserData). Received protocol 'http://schemas.xmlsoap.org/wsdl/soap/', required protocol 'http://schemas.xmlsoap.org/wsdl/soap/'. Received SOAPAction() required SOAPAction(). SOAPAction policy is lax. 
11:54:41 xmlparse  debug  33491 request  10.57.129.63 0x80e003a9 xmlmgr (default): Parsing http://10.57.129.110:2912/WebServiceProject/services/UsersCatalog stopped on XPath match 
11:54:41 xmlparse  debug  33491 request  10.57.129.63 0x80e003a6 xmlmgr (default): Parsing document: 'http://10.57.129.110:2912/WebServiceProject/services/UsersCatalog' 
11:54:41 xslt   debug  33491    10.57.129.63 0x80a002ac xmlmgr (default): patterns Compilation Request: Found in cache expr:////*[local-name()='Envelope']/*[local-name()='Body']/*. 
11:54:41 xslt   debug  33491    10.57.129.63 0x80a002aa xmlmgr (default): patterns Compilation Request: Checking cache for URL 'expr:////*[local-name()='Envelope']/*[local-name()='Body']/*'. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation setUserData matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation getUserName matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation getUserData matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation setUserData matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation getUserName matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 ws-proxy  debug  33491    10.57.129.63 0x80e0037d source-http (handler): WS-Proxy User.wsp operation getUserData matches address (10.57.129.110:2912) url (/WebServiceProject/services/UsersCatalog). SOAP operation and Action will be evaluated. 
11:54:41 mpgw   debug  33491    10.57.129.63 0x80e00140 source-http (handler): Generating chunked response stream to front 
11:54:41 mpgw   debug  33491    10.57.129.63 0x80e0013f source-http (handler): Found content length 207 HTTP input 
11:54:41 mpgw   debug  33491    10.57.129.63 0x80e0013b source-http (handler): HTTP Transaction # 1 on this TCP connection 
11:54:41 mpgw   information 33491    10.57.129.63 0x80e0013a source-http (handler): Received HTTP/1.1 POST for /WebServiceProject/services/UsersCatalog from 10.57.129.63 
11:54:34 network   debug  16865 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:34 network   debug  16865 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:34 multistep  debug  2996 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 multistep  debug  2996 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:34 multistep  debug  20309 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 multistep  debug  20309 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:34 multistep  debug  20293 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 multistep  debug  20293 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:34 network   debug  3968 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:34 multistep  debug  20277 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 multistep  debug  20277 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 network   debug  3952 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:34 network   debug  3952 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:34 multistep  debug  2964 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:34 multistep  debug  2964 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:33 network   debug  16817 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/ 
11:54:33 network   debug  16817 response 10.57.129.63 0x80e0039e xmlfirewall (web-mgmt): url-open: response code 200 
11:54:33 multistep  debug  20245 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:33 multistep  debug  20245 request      0x80c00004 xmlfirewall (map): Protocol layer did not supply content-type 
11:54:33 network   debug  16817 response 10.57.129.63 0x80e0039f xmlfirewall (web-mgmt): url-open: Finished parsing response from: http://127.0.0.1:63503/

이 부분은 내가 생각하는 가장 중요한 : 나는 내 관리자에게 물었다

11:54:41 ws-proxy  error  33491 error  10.57.129.63 0x01130006 wsgw (User.wsp): Failed to establish a backside connection 
11:54:41 ws-proxy  error  33491    10.57.129.63 0x80e00126 wsgw (User.wsp): Valid backside connection could not be established: Failed to establish a backside connection, url: http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog 
11:54:41 ws-proxy  error  33491    10.57.129.63 0x80e00627 wsgw (User.wsp): Error occurred (port error) when connecting to URL 'http://10.57.129.63:2911/WebServiceProject/services/UsersCatalog' 
11:54:41 network   error  33491        0x80e00049 xmlmgr (default): Host connection failed to establish: 10.57.129.63 : tcp port 2911 
11:54:41 network   error  33491        0x00b30009 xmlmgr (default): Host connection could not be established

우리의 방화벽이 들어오는 트래픽을 차단하지 않은 경우 만 허용합니다.

DataPower가 요청을 받아들이지 만 호스트 (Tomcat)를 만드는 데 실패했음을 발견했습니다.

VM 네트워크 설정에 문제가 있다고 생각했지만 브리지 및 호스트 전용 모두 동일한 오류가 발생합니다.

출처

2016-12-28 voidmat

+0

로깅을 디버그하고 로그를 공유하도록 설정할 수 있습니까? – Anders

+0

로그와 추가 정보가 추가되었습니다. 당신이 대답한다면 기꺼이 것입니다 :) – voidmat

답변

0

연결을 거부 했으므로 대부분 방화벽에 부딪쳤을 가능성이 높습니다. DataPower의 문제 해결 도구를 사용하여 연결해야하는 포트와 IP에 대한 연결 테스트를 수행하고 연결을 확인하십시오. 그렇다면 Java 서비스에 몇 가지 문제가 있습니다. 그렇지 않으면 DataPower와 대상 서버 사이에 방화벽과 라우트를 점검하십시오.

두 개 이상의 IP/NIC를 사용하는 경우 NIC가 DataPower에 올바르게 설정되어 있는지 확인하십시오. 하나의 NIC에만 기본 게이트웨이가 있어야하며 나머지 정적 경로가 있어야합니다.

출처

2016-12-29 13:26:24 Anders

+0

나는 포트 2911에서 거부했다. 포트 80에 바람둥이를 설정했습니다 이것을 피하기 위해. 지금 내가 어떤 구문 분석 오류 (wtf?) : wsgw (user1.wsp) : 규칙 (user1.wsp_default_response-rule) : 암시 적 작업 입력을 SOAP로 구문 분석하고 파이프 라인을 시도합니다. 실패 : 10.57.129.103:80/WebServiceProject/services/UsersCatalog 의 오프셋 0에서 잘못된 문자 '4'와 다른 하나 : wsgw (user1.wsp) : http : //10.57의 오프셋 0에서 잘못된 문자 '4' .129.103 : 80/WebServiceProject/services/UsersCatalog 이 응답에 대한 정보를 얻을 수 있습니까? 신이여, 그것은 정말로 성가시기 시작합니다. – voidmat

+0

나는 패킷 캡쳐 (packet capture)로 그것을 들여다 볼 방법이 있다는 것을 깨달았습니다. 그러나 그것은 나를 더욱 혼란에 이르게했다. 흐름 : soapUI는 xml과 함께 메소드를 호출합니다 -> datapower는 같은 xml 메소드 호출로 포스트에 응답합니다 -> 내 localhost는 404를 dp (왜?)로 보냅니다 -> dp post 500 to soapUI – voidmat

+0

WSP에서 프로브를 활성화하기 만하면됩니다. 당신은 아마도 유효한 XML/SOAP을 반환하지 않을 것입니다. – Anders

 관련 문제

  • 관련 문제 없음^_^