JAX-RPC request timeout

View: New views
4 Messages — Rating Filter:   Alert me  

JAX-RPC request timeout

by M.Kairys :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

   Hello,
JAX-RPC states itself as "Production Quality" service, but has no
possibility to specify http request timeouts in web service client side.
We have chosen this implementation as it has good performance, and is
supported by sun application server 8.2, but this lack of such important
feature is really show stopper.
If some external web service hangs or stops - our whole system also hangs
because no request timeout can occur and all threads hang trying to call
hanging web service.

I have looked at sources and found that this functionality is implemented
in JAX-WS class com.sun.xml.ws.transport.http.client.HttpClientTransport,
but is missing in JAX-RPC implementations class
com.sun.xml.rpc.client.http.HttpClientTransport.

Can we expect that this feature will be implemented some day?
If no, can we download JAX-RPC source code, add this functionality by
ourselves and use it internally for commercial use (we have sun jes
support license)?

P.S.
I have found several forum posts without an answer on the same topic:

http://markmail.org/message/ajwkgpgyna34v54k
http://forums.sun.com/thread.jspa?forumID=331&threadID=409549
http://forums.sun.com/thread.jspa?forumID=331&threadID=587997
http://markmail.org/message/fjklzmmuqnrvw5hh#query:jax-rpc%20timeout%20sun+page:1+mid:fjklzmmuqnrvw5hh+state:results
http://forums.java.net/jive/message.jspa?messageID=328098
http://www.nabble.com/Axis-stubs-vs-JAX-RPC-stubs-td8069451.html





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: JAX-RPC request timeout

by T. Anbu Balakumaran :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This is a  valid enhancement request.  Please submit an issue in the
issue tracker (https://jax-rpc.dev.java.net/issues), and we will work on
provide this enhancement in the next jax-rpc patch release.  Thanks.
bala

M.Kairys@... wrote:

>    Hello,
> JAX-RPC states itself as "Production Quality" service, but has no
> possibility to specify http request timeouts in web service client side.
> We have chosen this implementation as it has good performance, and is
> supported by sun application server 8.2, but this lack of such important
> feature is really show stopper.
> If some external web service hangs or stops - our whole system also hangs
> because no request timeout can occur and all threads hang trying to call
> hanging web service.
>
> I have looked at sources and found that this functionality is implemented
> in JAX-WS class com.sun.xml.ws.transport.http.client.HttpClientTransport,
> but is missing in JAX-RPC implementations class
> com.sun.xml.rpc.client.http.HttpClientTransport.
>
> Can we expect that this feature will be implemented some day?
> If no, can we download JAX-RPC source code, add this functionality by
> ourselves and use it internally for commercial use (we have sun jes
> support license)?
>
> P.S.
> I have found several forum posts without an answer on the same topic:
>
> http://markmail.org/message/ajwkgpgyna34v54k
> http://forums.sun.com/thread.jspa?forumID=331&threadID=409549
> http://forums.sun.com/thread.jspa?forumID=331&threadID=587997
> http://markmail.org/message/fjklzmmuqnrvw5hh#query:jax-rpc%20timeout%20sun+page:1+mid:fjklzmmuqnrvw5hh+state:results
> http://forums.java.net/jive/message.jspa?messageID=328098
> http://www.nabble.com/Axis-stubs-vs-JAX-RPC-stubs-td8069451.html
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: JAX-RPC request timeout

by M.Kairys :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thank you very much, i have submitted an issue
https://jax-rpc.dev.java.net/issues/show_bug.cgi?id=41 .

Mindaugas Kairys




"T. Anbu Balakumaran" <Bala.Balakumaran@...>
Sent by: Bala.Balakumaran@...
2009.03.17 20:35
Please respond to
users@...
Saugumo zyma:

To
users@...
cc

Subject
Re: JAX-RPC request timeout






This is a  valid enhancement request.  Please submit an issue in the
issue tracker (https://jax-rpc.dev.java.net/issues), and we will work on
provide this enhancement in the next jax-rpc patch release.  Thanks.
bala

M.Kairys@... wrote:
>    Hello,
> JAX-RPC states itself as "Production Quality" service, but has no
> possibility to specify http request timeouts in web service client side.

> We have chosen this implementation as it has good performance, and is
> supported by sun application server 8.2, but this lack of such important

> feature is really show stopper.
> If some external web service hangs or stops - our whole system also
hangs
> because no request timeout can occur and all threads hang trying to call

> hanging web service.
>
> I have looked at sources and found that this functionality is
implemented
> in JAX-WS class
com.sun.xml.ws.transport.http.client.HttpClientTransport,

> but is missing in JAX-RPC implementations class
> com.sun.xml.rpc.client.http.HttpClientTransport.
>
> Can we expect that this feature will be implemented some day?
> If no, can we download JAX-RPC source code, add this functionality by
> ourselves and use it internally for commercial use (we have sun jes
> support license)?
>
> P.S.
> I have found several forum posts without an answer on the same topic:
>
> http://markmail.org/message/ajwkgpgyna34v54k
> http://forums.sun.com/thread.jspa?forumID=331&threadID=409549
> http://forums.sun.com/thread.jspa?forumID=331&threadID=587997
>
http://markmail.org/message/fjklzmmuqnrvw5hh#query:jax-rpc%20timeout%20sun+page:1+mid:fjklzmmuqnrvw5hh+state:results

> http://forums.java.net/jive/message.jspa?messageID=328098
> http://www.nabble.com/Axis-stubs-vs-JAX-RPC-stubs-td8069451.html
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...








---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Dynamic Proxy, DII problems with rpc/encoded returned arrays of Bean objects

by emiddio :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

my initial goal was to learn about wscompile static stub clients, Dynamic
Proxy clients, and DII

Dynamic Invocation Interface clients -- and jax-rpc custom serialization.

i was studying the Oreilly JavaWebServices Nutshell 2002-2003 book.

i then encountered some problems -- are they jax-rpc bugs or something else?

i am running netbeans 6.5.1 with glassfishv2ur2.

after lots of experiments i have reduced the problem to the following
example/experiments.

i have created 2 different jax-rpc web services.

each contains 3 operations/methods.

they are identical -- except 1 is rpc/encoded, the other is rpc/literal.

there is 1 Java Bean object/class with getter, setter methods named
BookInfo.java, which is the

same in both clients and was generated by wscompile -- using netbeans 6.5;


the rpc/literal client wscompile also generated a BookInfoArray.java java
bean -- and is

referenced in the below rpc/literal SEI.

both services have the SEI
public interface wsTestSEI extends java.rmi.Remote {

    String rString(String s1) throws RemoteException;

    BookInfo r1BookInfo() throws RemoteException;

    BookInfo[] rBookInfos(String i1) throws RemoteException;

}

the rpc/encoded client generates the following SEI
public interface WsTestSEI extends java.rmi.Remote {
    public websvc1.BookInfo r1BookInfo() throws
         java.rmi.RemoteException;

// uses and array return type
    public websvc1.BookInfo[] rBookInfos(java.lang.String string_1) throws
         java.rmi.RemoteException;

    public java.lang.String rString(java.lang.String string_1) throws
         java.rmi.RemoteException;
}

the rpc/literal client generates the following SEI
public interface WsTestSEI extends java.rmi.Remote {
    public websvc3.BookInfo r1BookInfo() throws
         java.rmi.RemoteException;

// uses a java bean return type
    public websvc3.BookInfoArray rBookInfos(java.lang.String string_1)
throws
         java.rmi.RemoteException;

    public java.lang.String rString(java.lang.String string_1) throws
         java.rmi.RemoteException;
}

------------------------------------------------------------

all 3 methods work without problems for the rpc/literal client -- using all
3 invocation models

-- wscompile static stub, Dynamic Proxy, and DII Dynamic Invocation
Interface.


for the rpc/encoded clients -- only the wscompiled static stub client works
without any

problems.

the only method that fails to work of the 3 is the rBookInfos() operation --  
which expects and
array of BookInfo objects to be returned.

i got the DII rpc/encoded client to work by adding a custom serializer to
the type mapping

registry -- for the rBookInfos method/operation.

for the rpc/encoded Dynamic Proxy client -- i was unable to discover a way
to make the

rBookInfos() method/operation work at all -- i experimented with adding
cutom serializers but

never got it to work.

====================================================

is this a jax-rpc bug?

if not what am i doing wrong?

i could provide info from the stack trace, and the tcpmon monitored SOAP
messages if wanted.

thanks


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...