"JSR 172 Web Service Timeout"

I have successfully used JSR172 and Sun's stub generator to access my web services and it works very nicely. The only hitch I see is that if for some reason ( not very likely but I'd like to handle it anyway ) the Blackberry client connects to the service by never receives a response, it appears to hang indefinitely.
Is there a way to set a time out, since it doesn't seem to fall through normal error trapping
I suppose I could kill the thread after a certain amount of time but that seems rude and would likely cause other problems
This is at the point where the JSR172 Invoke api is called.
thnx in advance...

Hi,
Check parameters *icm/server_port_<xx> *
In my CRM system, I have setup :
icm/server_port_0 = PROT=HTTP,PORT=80,TIMEOUT=90,PROCTIMEOUT=600
The PROCTIMEOUT is the one interesting for you.
I have set up it to 600 seconds to get the same timeout as with the sapgui.
Check also rdisp/plugin_auto_logout but it is more useful for the webui than for web services.
Regards,
Olivier

Similar Messages

  • A JSR 172 (Web services) tutorial

    Hi,
    Some mobile phones already include JSR 172 api. There are some tools that already allow the automatic generation of stubs. I have written an article on how to access the API without the use of this tools, maybe somebody will find it useful
    http://mobile.liveshere.net/articles/viewarticle.php?id=15

    I have written a dot net/ c# Web Services doesn't fully work with J2ME client - it too throws the same exception, with the exception text being "Missing SOAP Body or Envelope"
    a) c# web service works with c# WIndows Client (local & remote web service)
    b) c# web service works with J2ME client - when the Web Service is local
    c) c# web service FAILS with J2ME client - when the Web Service is remote
    error/exception:
    "Missing SOAP Body or Envelope" -- This occurs at the point of invoking the remote Web Service
    Speculation:
    a) dot net Web Services are "different" from Java Web services - yet it works fine in local mode
    b) error is a misnomer & there is some other problem, perhaps fixable thru Web.config changes remotely??
    - changed Web.Config authentication (from Windows to none), but this made no difference
    - changed back to default web service namespace of tempuri.org, but this made no difference

  • [JSR-172 Web Services] Error with some web services

    hello
    I m trying to use jsr172 with multiple services find at Xmethods.com
    - I choice only doc/litteral wsdl types ----> OK
    - use of the J2ME Wireless Toolkit Stubs Generator ---> OK
    - use the service stub generated to invoke the service -------> NOT OK
    Some services runs correctly, but lots of service methods throw a java.rmi.MarshalException: Missing SOAP Body or Envelope
    i.e: http://www.closerfar.com/dic2.asmx?WSDL
    --> this has a method which return a definition of a word by a complex type
    When I use the TryIt function in Xmethods.com, it's run!...
    .... but not in my midlet
    Can you help me
    thanks
    ludo

    I have written a dot net/ c# Web Services doesn't fully work with J2ME client - it too throws the same exception, with the exception text being "Missing SOAP Body or Envelope"
    a) c# web service works with c# WIndows Client (local & remote web service)
    b) c# web service works with J2ME client - when the Web Service is local
    c) c# web service FAILS with J2ME client - when the Web Service is remote
    error/exception:
    "Missing SOAP Body or Envelope" -- This occurs at the point of invoking the remote Web Service
    Speculation:
    a) dot net Web Services are "different" from Java Web services - yet it works fine in local mode
    b) error is a misnomer & there is some other problem, perhaps fixable thru Web.config changes remotely??
    - changed Web.Config authentication (from Windows to none), but this made no difference
    - changed back to default web service namespace of tempuri.org, but this made no difference

  • Windows Communcation Foundation - JSR 172 Web Stub - interoperability

    Hi! I am just playing with WCF -Windows Communication Foundation and JSR 172 Web Stub generation utility of WTK 2.5beta - is there a known problem with the import-expression i XML?
    WCF generates:
    ?wsdl -> web service descrption that has import- references to
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions name="EchoService" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:i0="http://schemas.microsoft.com/ws/2005/02/mex/bindings" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
      <wsdl:import namespace="http://schemas.microsoft.com/ws/2005/02/mex/bindings" location="http://localhost:8080/echo?wsdl=wsdl0" />
    - <wsdl:types>
    - <xsd:schema targetNamespace="http://tempuri.org/Imports">
      <xsd:import schemaLocation="http://localhost:8080/echo?xsd=xsd0" namespace="http://tempuri.org/" />
      <xsd:import schemaLocation="http://localhost:8080/echo?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
      </xsd:schema>
      </wsdl:types>
    + <wsdl:message name="IEchoService_Echo_InputMessage">
      <wsdl:part name="parameters" element="tns:Echo" />
      </wsdl:message>
    - <wsdl:message name="IEchoService_Echo_OutputMessage">
      <wsdl:part name="parameters" element="tns:EchoResponse" />
      </wsdl:message>
    - <wsdl:portType name="IEchoService">
    - <wsdl:operation name="Echo">
      <wsdl:input wsaw:Action="http://tempuri.org/IEchoService/Echo" message="tns:IEchoService_Echo_InputMessage" />
      <wsdl:output wsaw:Action="http://tempuri.org/IEchoService/EchoResponse" message="tns:IEchoService_Echo_OutputMessage" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:service name="EchoService">
    - <wsdl:port name="MetadataExchangeHttpBinding_IEchoService" binding="i0:MetadataExchangeHttpBinding_IEchoService">
      <soap12:address location="http://localhost:8080/echo" />
    - <wsa10:EndpointReference>
      <wsa10:Address>http://localhost:8080/echo</wsa10:Address>
      </wsa10:EndpointReference>
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>?wsdl=wsdl0
    ?xsd=xsd0
    ?xsd=xsd1Anyone experienced the same problem and knows a solution ?
    Henning

    I have gotten a step futher! The emulator had to be configured to run in the "secure" domain (as mentioned by some other people here), otherwise a http response "400 bad request (invalid header name)" was produced. J2ME web service is interoperable with WCF basichttpbinding (without debugging becuase it inserts unparseable soap-code into the http response)

  • Deployment of JSR-109 Web Services on Weblogic 11g (OAS migration)

    Hi.
    I'm being part of an ongoing migration effort from Oracle Application Server 10.1.3.5 to WebLogic 11g (10.3.6). Some of the OAS applications use old JSR-109 Web Services, where each service has the following components:
    - A SEI interface that extends java.rmi.Remote and declares the service methods, which throw java.rmi.RemoteException (e.g. ServiceSEI)
    - A service implementation POJO that implements the SEI interface (e.g. ServiceImpl)
    - A [Service]-config.xml file that declares the service and relates name, namespaces, packages, interface and implementation (e.g. Service-config.xml)
    - A declaration of the service implementation POJO as a servlet (with mapping) in web.xml (docs says it doesn't have to be technically a servlet)
    - A webservices.xml file that defines the service and references the mapping file.
    - A [Service]-mapping.xml file that defines the WS-Java mappings.
    All the artifacts look right according the old documentation:
    - Programming Web Services for WebLogic Server, Creating a J2EE Web Service Manually: http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html
    - Web Services for J2EE 1.0 Final Release Spec: http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    The Web Services work OK in OAS. When I try to deploy any of the application that contain one of that services to WebLogic, I get the following Exception:
    <BEA-101216> <Servlet: "WSServlet_Procesos" failed to preload on startup in Web application: "/webapp".
    java.lang.IllegalStateException: ClassNotFound co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:601)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:273)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:171)
    at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
    at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:705)
    at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201)
    at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54)
    at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:91)
    at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:372)
    at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:83)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    I obviously though the EAR package given to me was incomplete, lacking the ClassNotFound related class, but the package was OK, and is exactly the same that deploys without problems in OAS.
    The ClassNotFound related class is referenced in the <java-xml-type-mapping> element of the [Service]-mapping.xml file, e.g.:
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperationResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>result</java-variable-name>
    <xml-element-name>result</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I searched the OAs installation deployment dirs looking for the missing class and found it was present in a Jar called deployment-cache.jar. According OC4J related documentation, this Jar es auto-generated at deployment time.
    Weblogic 11g documentation says that kind of Web Services will continue to run, without any changes, on version 10.3.x of WebLogic Server because the associated Web services run time is still supported in this release, although it is deprecated and will be removed from the product in future releases (http://docs.oracle.com/cd/E21764_01/web.1111/e13760/upgrade.htm). I know the right estrategy is migrate the Web Services, but right now my client needs to deploy and use them as they are. I think WL recognizes my service since internally is calling a "Deploytime109MappingHelper" class.
    ¿Is there any way I can deploy that kind of services to Weblogic 11g? ¿I'm I missing some required step?
    As a workaround, I included the OAS generated deployment-cache.jar into the EAR to deploy in Weblogic 11g and the app deploys without errors, but I see this is not a nice solution.
    Any help would be much appreciated.
    Thanks,
    Esteban
    Edited by: salzo on Oct 30, 2012 9:54 AM
    Edited by: salzo on Oct 30, 2012 9:56 AM

    Hi. The [Service]-mapping.xml file is a standard "JAX-RPC mapping file" according the JSR-109 spec and WebLogic 9.2 doc ([1],[2]). That's the file that references the class. Here's a fragment:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Service/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Services/wsdl</namespaceURI>
    </package-mapping>
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperation</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>String_1</java-variable-name>
    <xml-element-name>String_1</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I'll take a look at the ant task.
    Thank you very much.
    [1]http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    [2]http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html

  • Netbeans 4.1: JSR-109 web services are only supported in j2ee 1.4 apps

    There is no way to create web services in NetBeans 4.1 with Tiger (jdk 1.5).
    Because when you try to create a web service in NB4.1, you will straight away get an message in the New Web Service window:
    JSR-109 web services are only supported in j2ee 1.4 applications.

    JSR-109 web services are only supported in j2ee 1.4
    applications.Do you have J2EE 1.4 SDK installed?

  • Web service timeout

    When i communicate with external system using web service call, i can transafer 3500 record. if i run it for more than 3500 records it gives error "SOAP:1,023 SRT: Processing error in Internet Communication".
    i tried to use SM59, HTTP connection to external server. current set up is ICM Default timeout..
    I want to change but rfc destination is generated and i dont have option to change it to "no timeout" or specify timeout.
    you help is appreciated. .

    Hello Vipul
    Enter the RZ10 and validates the TIMEOUT value of parameter "icm/server_port_<x>" for  PROT=HTTP and PROT=HTTPS.
    For example, the HTTP service is on port 0 and TIMEOUT=600 seconds
    icm/server_port_0 = PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
    in your case, increasing the TIMEOUT and validates the WS again
    regards
    Juan

  • EDQ Web Service Timeout setting

    Hi,
    We have integrated OEDQ with Siebel. Requests are flowing as expected. Just want to know, how long the connector will be waiting for web service response from OEDQ.
    Is there place where timeout is set by default?
    Best Regards
    Moorthy

    Hi,
    We have integrated OEDQ with Siebel. Requests are flowing as expected. Just want to know, how long the connector will be waiting for web service response from OEDQ.
    Is there place where timeout is set by default?
    Best Regards
    Moorthy

  • JSR 181 (Web Service Metadata) ambiguity clarification

    I have a question regarding the @WebService annotation.
    It can take a name and a serviceName attribute. The description of them in the JSR doesn't really clarify to me what the difference between them is.
    name--The name of the Web Service. Used as the
    name of the wsdl:portType when mapped to
    WSDL 1.1
    serviceName--The service name of the Web Service. Used as
    the name of the wsdl:service when mapped
    to WSDL 1.1.
    Not allowed on interfaces.
    Is the only difference their usages in the WSDL file?

    Can't you just use the SAAJ API that way you'll have controll as to how your SOAP message is constructed?
    gtata

  • Web service Timeouts

    Version                   :     Informatica 9.6.1 Hot Fix 1Installation Server    :   AIX server Informatica workflow reads records from an Oracle table and makes a web service calls. I am seeing the below error message in the session log. Time out defined in the connection object is 450s (7.5 min).  Need you inputs in understanding the timeouts i am seeing in the session log. The job runs in 4 partitions and i see few transactions getting dropped as well during this web service calls. Open Issues1. Where does this timeout enforced? In the application level the request completes before 7 mins.2. Why does Informatica drops requests while making web service calls (partition is pass through). Session Log ErrorTRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason: Operation timed out after 60014 milliseconds with 0 out of -1 bytes receivedTRANSF_1_2_4> CMN_1761 Timestamp Event: [Wed Jul 15 04:05:19 2015]TRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason:TRANSF_1_2_4> CMN_1761 Timestamp Event: [Wed Jul 15 04:06:19 2015]TRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason: Operation timed out after 60069 milliseconds with 0 out of -1 bytes received

    Hi all, Please help me with metadata query to extract each session RUN_DURTION, Start Time, end time for last 10 runs of each session at a workflow level. I know we can get information from REP_WFLOW_RUN table but i dont know table strucure and I dont have access to Repository database and we need an exact query to raise it to admin team. so please provide me an exact query.   Thanks

  • Where to increase Web Service timeout property

    Hello All,
    I have developed a stateless java web service that executes a sql query.
    Query exectung for more than 5 minutes by the time the web service is throughing an exception:
    ****************Exception Message**********************
    WARNING: Unable to connect to URL: http://testhost.appsassociates.com:7781/TimeOutTest/TimeOutTestSoapHttpPort due to java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
    java.rmi.RemoteException: ; nested exception is:
         HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
         at proxycallertimeout.proxy.runtime.TimeOutTestSoapHttp_Stub.testMethod(TimeOutTestSoapHttp_Stub.java:84)
         at proxycallertimeout.proxy.TimeOutTestSoapHttpPortClient.testMethod(TimeOutTestSoapHttpPortClient.java:43)
         at proxycallertimeout.proxy.TimeOutTestSoapHttpPortClient.main(TimeOutTestSoapHttpPortClient.java:30)
    Caused by: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
         at oracle.j2ee.ws.client.http.HttpClientTransport.invokeImpl(HttpClientTransport.java:174)
         at oracle.j2ee.ws.client.http.HttpClientTransport.invoke(HttpClientTransport.java:150)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:176)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:113)
         at proxycallertimeout.proxy.runtime.TimeOutTestSoapHttp_Stub.testMethod(TimeOutTestSoapHttp_Stub.java:77)
    If query tekes less time to finish everything is working fine.
    How to make the webservice wait for more time.
    Thanks
    Saikrishna

    Async process can be fire and forget, meaning you don't ever want to response from the client. You can also have a response that will return in any time in the future.
    A human task is an example of this. You create a work list for someone. The BPEL process waits for the person to either accept or reject.
    The beauty of calling a BPEL process is that this is managed out of the box. If you are doind some bespoke development then you may need to use correlation sets.
    cheers
    James

  • Web Service Timeout & connection errors

    Using jwsdp 2, i have developed a client that has a timeout property set. How are timeouts processed? Is an exception thrown by the port? or does the web method just return with a null return value?
    I also have noticed that in simulating a connection error (by stopping my app server) that an exception is thrown by the web method? but the exception is a javax.xml.ws.WebServiceException. How do I distinguish connection errors from other exceptions? what other exceptions are there?
    Basically, where is this info documented?

    Hello Vipul
    Enter the RZ10 and validates the TIMEOUT value of parameter "icm/server_port_<x>" for  PROT=HTTP and PROT=HTTPS.
    For example, the HTTP service is on port 0 and TIMEOUT=600 seconds
    icm/server_port_0 = PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
    in your case, increasing the TIMEOUT and validates the WS again
    regards
    Juan

  • Web Services Timeout

    I have a problem to specify the timeout of a service web. I have a client who accedes with Axis to a service web. I have the following code but it does not work:
    locator= new Locator();
    servicio= locator.getPort();
    ((org.apache.axis.client.Stub)(servicio)).setTimeout(Constantes.TIME_OUT);
    servicio.saluda("Juan");
    As I have the timeout of the Axis understood it is not of connection, but itcontrols the timeout when already these connected to the service web. There exists some way of specifying timeout of connection (socket)? Some suggestion?
    The problem that I have is that the application continues waiting for the connection for the service web until he(she) returns the following mistake:
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: java.net.ConnectException: Connection timed out
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace: java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:129)
    at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157)
    at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
    at org.apache.axis.client.Call.invoke(Call.java:2553)
    at org.apache.axis.client.Call.invoke(Call.java:2248)
    at org.apache.axis.client.Call.invoke(Call.java:2171)
    at org.apache.axis.client.Call.invoke(Call.java:1691)
    java.net.ConnectException: Connection timed out
    at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
    at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
    at org.apache.axis.client.Call.invoke(Call.java:2553)
    at org.apache.axis.client.Call.invoke(Call.java:2248)
    at org.apache.axis.client.Call.invoke(Call.java:2171)
    at org.apache.axis.client.Call.invoke(Call.java:1691)
    Caused by: java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:129)
    at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157)
    at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114)
    ... 13 more

    Hi
    I used axis to generate the stubs..
    In the stub "MySericeSoapStub extends org.apache.axis.client.Stub"
    i added the following line in the createCall() Routine
    protected org.apache.axis.client.Call createCall() throws java.rmi.RemoteException {
    try {
    org.apache.axis.client.Call call = super.createCall();
    System.out.println( "Calling :"+ super.cachedEndpoint) ;
    _call.setTimeout( new Integer(10000) ) ;
    System.out.println( "Setting the timeout 10 seconds ..." ) ;
    if (super.maintainSessionSet) {
    _call.setMaintainSession(super.maintainSession);
    .......................

  • How to use Web Serivce for not jsr 172 phone

    Hi:
    Is anyone know, how to use web service for phones that only have standard J2ME package installed (without jsr 172 web service packagenstalled)?
    thank you

    Hi,
    I think you need to write the code for this from scratch (built on top of existing HTTP functionality). There may be open-source J2ME code you could use. I've never tried this so I'm afraid I don't know any more. But maybe that is what you were asking... i.e. does anyone have code that does this already...
    Tx,
    Sam

  • 2 Java ME Web Service Errors of "Not Compliant with JSR-172"

    This happened when I use Microsoft's ASMX-based WSDL file on a Java ME WS client.
    Say I had a test.asmx WSDL. Then I use NetBeans, and I go to New > Java ME Web Service Client
    I tried to import from running web service, URL "http://www.testhost.com/wspackage/test.asmx?WSDL"
    and then the popup validation error told me "Reference in element is not supported by this version of stub compiler"
    also the X logo error told me "testasmx.wsdl is not compliant with Java ME Web Services specification (JSR-172)"
    I wondered what's going on? Is there any data types not supported by JSR-172? Which is it?
    When I "Validate XML" this ASMX file, it pops this:
    "Error: src-resolve: Cannot resolve the name 's:schema' to a(n) 'element declaration' component."
    The "types" section of my WSDL are like this:
    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/MMWebServices/Coverage"
    xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    targetNamespace="http://tempuri.org/MMWebServices/Coverage" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/MMWebServices/Coverage">
    <s:import namespace="http://www.w3.org/2001/XMLSchema" />
    <s:element name="ViewListDoctor">
    <s:complexType>
    <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="iUserId" type="s:int" />
    <s:element minOccurs="1" maxOccurs="1" name="iASchId" type="s:int" />
    <s:element minOccurs="0" maxOccurs="1" name="sSearchKeyword" type="s:string" />
    <s:element minOccurs="0" maxOccurs="1" name="dsView">
    <s:complexType>
    <s:sequence>
    <s:element ref="s:schema" /> // <<error occured on this line, and every time the ref="s:schema" shows up <<
    Anyone have experienced this?

    Yes, thx u. I didn't realized I was posting on the wrong section (Enterprise) so I posted again to the J2ME/MIDP section since it was all about mobility. Please delete the first post.

Maybe you are looking for