Socket proxy timeout

Hi,
I'm currently using:
mysock.connect(sockaddr, 2000);
to set socket connection timeout.
Everything works fine until i set a proxy:
System.setProperty("socksProxySet", "true");
System.setProperty("socksProxyHost", "proxy");
System.setProperty("socksProxyPort", "port");
Can i also set connection timeout for the proxy?

ejp wrote:
Oops I agree you are correct, it's there in 1.5 too. But does that propagate the 'closed' flag back to Socket?I think so, but I'm not sure. PlainSocketImpl extends SocketImpl. SocketImpl has a reference to the Socket, and close in PlainSocketImpl has this comment:
* We close the FileDescriptor in two-steps - first the
* "pre-close" which closes the socket but doesn't
* release the underlying file descriptor. This operation
* may be lengthy due to untransmitted data and a long
* linger interval. Once the pre-close is done we do the
* actual socket to release the fd.
*/It's hard to see if it call close on the Socket since socketPreClose and socketClose invokes native methods.

Similar Messages

Socket write timeout

How do you get a blocked write on a socket to timeout?
I've written a simple test program that has two threads, one is the server that accepts a connection form the other that is the client. Once the client has established a connection, the server thread starts writing to the output steam of the socket. The client doesn't attempt to read any of the incoming data. I have set the SO_TIMEOUT option on the socket to 5 seconds. The server quickly fills the output buffer and blocks on the write call. And that's where is sits even after the 5 second timout has elapsed. I've tried a similar test on the read operation and the timeout works just fine.
I'm using JDK 1.6.0_05.
Any thoughts... am I missing something? Does the timeout only apply to the read operation and not the write?
Thanks in advance.

There isn't one. SO_TIMEOUT is a read timeout.
Your only option is to use non-blocking NIO and a Selector and do the timing out yourself.
If your writes are blocking it means the other end is slow reading, as you described.

Socket で Proxy を介して Secure (HTTPS) な接続をするには?

Socket を使い、Proxyを介して "https://～" へ接続してレスポンスを取得するにはどうすればいいですか？
非SecureなURL(HTTP)へは、まずはProxyサーバーへ socket.connect() した後に、
目的のサーバーへの CONNECT リクエストを送ることによって実現できました。
しかし、SecureなURL(HTTPS)ではTLS/SSLを使用しないといけないのか、出来ませんでした。
Socket 接続を途中からTLS/SSLで暗号化することは出来るのでしょうか？
また、SecureSocket も使用してみましたが、Proxyサーバーへの接続が確立できません。
SecureSocket　を使って Proxy を介する方法はあるのでしょうか？
とても困っています。
どうかどうか、解決方法を教えてください。

Ok, here is the solution. The latest stable release of Apache ws-soap, v2.3.1, does not support soap vis proxy with auth. One has to use one of the nightlies. In my case it worked with the latest nightly from 2004-06-22. The classes SSLUtils and HTTPUtils have been improved a lot with this. If only this would have been easier to find...

Squid as socket proxy

hi,
can you help me to configure squid as socket proxy
I would like to use squid for all internet queries, for all services, for all ports
thank you
Last edited by sacarde (2007-09-23 10:01:47)

Ok Daniel! Thanks!
So, the one of the issues I'm facing is that there are no entries on cache logs during the requests. It looks like the eql rules are not being applied and the client requests aren't getting the cache.
The other thing is when I make a request from my browser to test, the content takes too long to be delivered, and all the files that match extensions listed in eql, are not being delivered...
The troubleshooting section from the document listed on my first post, tells that if the "sh summary" command doesn't show any hit on cache content rule, the problem is in the cache. But, if I go to the cache console, and fire up a browser, I can get the content perfectly, witch is to say that the cache can provide the content that is in the orgin server and while I'm doing that I can see entries on cache log (some MISS and HIT), indicating that the cache is doing its own work.
Do you know tell me where is the right place should I point the cache to get the content from origin server? Should I point it to the content rule from CSS or directly to origin server IP address that is in the same cache VLAN?
I'm sorry... I know the hole thing sounds confusing... But, that is the problem I'm facing.
Best regards,
Fabiano Martins

ABAP Proxy Timeout

Hi!
I have this scenario:
SAPR3 (A.Proxy) -> XI ->SOAP
SAP R3 sends Sync Messages to XI, through ABAP proxy, which starts a BPM, this BPM calls a WebService that sometimes takes more than one minute to give a response.
When the process reaches "Close S/A Bridge", it raises a Timeout Exception.
I have already increased HTTP_TIMEOUT in SXMB_ADM and icm/keep_alive_timeout in SMICM, in XI with no effect.
Do i need to change other parameter? Maybe in SAP R3?

Hi Jose,
go through tuning guide of XI (Once i find the link i update this thread ). The HTTP timeout property can be used for SOAP as well as the underlying transport protocol is http for SOAP messages too. That might help.
Also, the second thing you could do is that by default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
Regards
joel.

How to make a socket connection timeout infinity in Servlet doPost method.

I want to redirect my System.out to a file on a remote server (running Apache Web Server and Apache Tomcat). For which I have created a file upload servlet.
The connection is established only once with the servlet and the System.out is redirected to it. Everything goes fine if i keep sending data every 10 second.
But it is required that the data can be sent to the servlet even after 1 or 2 days. The connection should remain open. I am getting java.net.SocketTimeoutException: Read timed out Exception as the socket timeout occurs.
Can anyone guide me how to change the default timeout of the socket connection in my servlet class.
Following is the coding to establish a connection with the Servlet.
URL servletURL = new URL(mURL.getProtocol(), mURL.getHost(), port, getFileUploadServletName() );
URLConnection mCon = servletURL.openConnection();
mCon.setDoInput(true);
mCon.setDoOutput(true);
mCon.setUseCaches(false);
mCon.setRequestProperty("Content-Type", "multipart/form-data");
In the Servlet Code I am just trying to read the input from the in that is the input stream.
public void doPost(HttpServletRequest req, HttpServletResponse res)
throws ServletException, IOException
BufferedInputStream in = new BufferedInputStream(req.getInputStream());
byte [] content = new byte[1024];
do
read = in.read(content, 0, content.length);
if (read > 0)
out.write(content, 0, read);
I have redirected the System.out to the required position.
System.setOut(........);
Can anyone guide me how to change the default timeout of the socket connection in my servlet class.

I am aware of the setKeepAlive() method, but this can only used with the sockets. Here i am inside a servlet, have access to HTTPServletRequest and HTTPServletResponse and I don't know how to get access to the underlying sockets as the socket handling will be handled by the tomcat itself. If I am right there will be method in the apache tomcat 6.0.x to set this property. But till now I am not getting it.

Socket connection timeout

I have a simple threaded client application to connecting to the server
which is also threaded. I am using the following code to prevent(reduce)
connection timeouts, but it doesn't seem like timeout period elapses
before exception is thrown on the client side. Any ideas? Exception
occurs way before 10 seconds as specified in the code below.
InetAddress addr = InetAddress.getByName(this.serverName);
SocketAddress sockaddr = new InetSocketAddress(addr,this.port);
Socket socket = new Socket();
socket.connect(sockaddr,10000);
The exception I get on the client side is:
java.net.ConnectException: Connection refused: connect
Thanks

The timeout kicks in if the other end hasn't responded within the period. In this case the other end has refused the connect attempt, probably because nothing is listening on the requested port. This can happen well within the timeout period, as you have experienced.

ABAP Proxy timeout issue

Hi,
I have a scenario in where I provide a web service. I get called by this web service and then call a abap proxy (synch). The abap side takes time to gather the data. after 600 secs, the connection gets a timeout.
It says, "500 Connection timed out"
"Detail: Connection to partner timed out after 600s"
In smicm I increased the HTTP value to 9000. So, how do I get this error?
Parameters are like below in PI:
icm/server_port_0 = PROT=HTTP,PORT=50000,TIMEOUT=90,PROCTIMEOUT=9000
icm/keep_alive_timeout (sec.) = 50
icm/conn_timeout (msec.) = 5000
xiadapter.inbound.timeout.default = 5400000

Hi,
Check if you are getting some short dumps in ABAP side due to this timeout in ST22.
Probably the issue is the work process time out in the ABAP side as you mentioned it takes more time to gather data. the profile parameter is rdisp/max_wprun_time and it has default value of 600 seconds. if thats the case then you can increas it.
regards,
francis

SSL Sockets-Proxy Client && Server

Hi,
I used to connect a static ip server from client behind proxy.I used ssl and achieved.When i gave proxy server ip and port manually my code works.If i try to find those by program ,socket is not created.I posted by code below.Please help
* SSLClient.java
* Created on August 14, 2007, 11:47 AM
* To change this template, choose Tools | Template Manager
* and open the template in the editor.
* @author Administrator
import java.net.*;
import java.io.*;
import javax.net.ssl.*;
import java.util.*;
public class SSLClient {
private SSLSocketFactory dfactory;
private String tunnelHost;
private int tunnelPort;
HashMap rec=new HashMap();
SSLSocket result ;
Socket tunnel;
static InetSocketAddress addr;
/** Creates a new instance of SSLClient */
public SSLClient(String proxyhost, String proxyport) {
System.out.println("Test");
tunnelHost = proxyhost;
tunnelPort = Integer.parseInt(proxyport);
System.setProperty("https.proxyHost",tunnelHost);
System.setProperty("https.proxyPort",""+tunnelPort);
tunnelHost= System.getProperty("https.proxyHost");
tunnelPort=Integer.parseInt( System.getProperty("https.proxyPort"));
System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
System.out.println("Connected --1"+tunnelHost+" "+tunnelPort);
System.out.println("Testing"+tunnelHost+tunnelPort);
try {
dfactory = (SSLSocketFactory)SSLSocketFactory.getDefault();
System.out.println("1 "+dfactory.toString());
Socket ss=createSocket("59.144.49.75",2500);
System.out.println("2");
} catch (Exception e) {
System.out.println("Exception"+e);
public Socket createSocket(String host, int port) throws IOException, UnknownHostException {
return createSocket(null,host,port,true);
public Socket createSocket(Socket s, String host, int port,
boolean autoClose)
throws IOException,UnknownHostException {
try {
System.out.println("Connected --");
tunnel = new Socket(tunnelHost,tunnelPort);
System.out.println("Connected"+tunnel);
doTunnelHandshake(tunnel,host,port);
result = (SSLSocket)dfactory.createSocket(tunnel,host,port,autoClose);
System.out.println("result"+result);
} catch (Exception e) {
System.out.println("Exc123"+e);
result.addHandshakeCompletedListener(
new HandshakeCompletedListener() {
public void handshakeCompleted(HandshakeCompletedEvent event) {
System.out.println("Handshake finished!");
System.out.println(
"\t CipherSuite:" + event.getCipherSuite());
System.out.println(
"\t SessionId " + event.getSession());
System.out.println(
"\t PeerHost " + event.getSession().getPeerHost());
System.out.println("result1.startHandshake "+result);
HashMap Hm=new HashMap();
Hm.put("Nithya","Success");
ObjectOutputStream output=new ObjectOutputStream(tunnel.getOutputStream());
output.writeObject(Hm);
try {
while(true){
ObjectInputStream inn=new ObjectInputStream(tunnel.getInputStream());
rec=(HashMap)inn.readObject();
if(rec.containsKey("Vidya")){
System.out.println("Values"+rec.get("Vidya"));
if(rec.containsKey("ramya")){
System.out.println("Value2"+rec.get("ramya"));
if(rec.containsKey("raja")){
System.out.println("Value3"+rec.get("raja"));
} catch (Exception e) {
System.out.println("EXCEPTION"+e);
result.startHandshake();
System.out.println("result.startHandshake "+result);
return result;
private void doTunnelHandshake(Socket tunnel, String host, int port)
throws IOException {
System.out.println("Inside handshake");
OutputStream out = tunnel.getOutputStream();
String msg = "CONNECT " + host + ":" + port + " HTTP/1.0\n"
+ "User-Agent: "
+ sun.net.www.protocol.http.HttpURLConnection.userAgent
+ "\r\n\r\n";
System.out.println("Message "+msg);
byte b[];
try {
* We really do want ASCII7 -- the http protocol doesn't change
* with locale.
b = msg.getBytes("ASCII7");
} catch (UnsupportedEncodingException ignored) {
* If ASCII7 isn't there, something serious is wrong, but
* Paranoia Is Good (tm)
b = msg.getBytes();
out.write(b);
out.flush();
* We need to store the reply so we can create a detailed
* error message to the user.
byte          reply[] = new byte[200];
int          replyLen = 0;
int          newlinesSeen = 0;
boolean          headerDone = false;     /* Done on first newline */
InputStream     in = tunnel.getInputStream();
boolean          error = false;
while (newlinesSeen < 2) {
int i = in.read();
if (i < 0) {
throw new IOException("Unexpected EOF from proxy");
if (i == '\n') {
headerDone = true;
++newlinesSeen;
} else if (i != '\r') {
newlinesSeen = 0;
if (!headerDone && replyLen < reply.length) {
reply[replyLen++] = (byte) i;
* Converting the byte array to a string is slightly wasteful
* in the case where the connection was successful, but it's
* insignificant compared to the network overhead.
String replyStr;
try {
replyStr = new String(reply, 0, replyLen, "ASCII7");
} catch (UnsupportedEncodingException ignored) {
replyStr = new String(reply, 0, replyLen);
/* Look for 200 connection established */
if(replyStr.toLowerCase().indexOf("200 connection established") == -1){
throw new IOException("Unable to tunnel through "
+ tunnelHost + ":" + tunnelPort
+ ". Proxy returns \"" + replyStr + "\"");
/* tunneling Handshake was successful! */
public String[] getDefaultCipherSuites(){
return dfactory.getDefaultCipherSuites();
public String[] getSupportedCipherSuites(){
return dfactory.getSupportedCipherSuites();
public static String getaddress(){
String address="";
try {
System.setProperty("java.net.useSystemProxies","true");
List l = ProxySelector.getDefault().select(
new URI("http://www.google.com/"));
for (Iterator iter = l.iterator(); iter.hasNext(); ) {
Proxy proxy = (Proxy) iter.next();
System.out.println("proxy type : " + proxy.type());
addr = (InetSocketAddress)
proxy.address();
if(addr == null) {
System.out.println("No Proxy");
} else {
System.out.println("proxy hostname : " +addr.getHostName());
address=addr.getHostName();
System.out.println("proxy port : " +addr.getPort());
} catch (Exception e) {
e.printStackTrace();
System.out.println("Valaddress"+addr.getHostName());
System.out.println("Valport"+addr.getPort());
return address;
public static String getPort(){
String port="";
try {
System.setProperty("java.net.useSystemProxies","true");
List l = ProxySelector.getDefault().select(
new URI("http://www.google.com/"));
for (Iterator iter = l.iterator(); iter.hasNext(); ) {
Proxy proxy = (Proxy) iter.next();
System.out.println("proxy type : " + proxy.type());
addr = (InetSocketAddress)
proxy.address();
if(addr == null) {
System.out.println("No Proxy");
} else {
System.out.println("proxy hostname : " +
addr.getHostName());
System.out.println("proxy port : " +
addr.getPort());
port=String.valueOf(addr.getPort());
} catch (Exception e) {
e.printStackTrace();
System.out.println("Valaddress1"+addr.getHostName());
System.out.println("Valport1"+addr.getPort());
return port;
public static void main(String[] args) {
String address1=getaddress();
String port1=getPort();
System.out.println("add:port"+address1+port1);
// System.setProperty("http.proxySet","true") ;
// System.setProperty("http.proxyHost","90.0.0.1");
// System.setProperty("http.proxyPort","80");
new SSLClient(address1,port1);
I got the error while running the program is
xc123java.net.SocketException: Malformed reply from SOCKS server
Exceptionjava.lang.NullPointerException
Please help

Thanks ejb for yopur help.Actually the control gave exception at createSocket it self.It is not going to doTunnelHandShake method.If i make change like this ,my program runs.
public static void main(String[] args) {
//String address1=getaddress();
//String port1=getPort();
//System.out.println("add:port"+address1+port1);
// System.setProperty("http.proxySet","true") ;
// System.setProperty("http.proxyHost","90.0.0.1");
// System.setProperty("http.proxyPort","80");
new SSLClient("90.0.0.1","80");
I suspect the getaddress and getport makes some changes in proxy settings.I cant able to find it.Please help.

ABAP Client Proxy Timeout

Dear all,
A ABAP Client proxy has been generated to connect non-SAP web service. It runs successfully except it may time out when the web service method is running too long (over 1 minute).
We know timeout/keepalive value can be set at the ICM timeout parameter by using Tcode RZ11. However, can we set it at ABAP code? It is more convenient to override server settings.
Thanks!
Regards,
Thomas

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

OSB socket proxy

Hi All
I have a requirement of reading from a socket. I built the socket adapter from samples and successfully deployed on the server.
After that i created a proxy on socket protocol specified a port. Now when i try to write to the socket using a java client i get the following error.
<Error> <Sample.SocketTransport> <BEA-000000> <[Sample.SocketTransport:800034]SocketTransport receiver is failed.
java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:150)
     at java.net.SocketInputStream.read(SocketInputStream.java:121)
     at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
     at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
     Truncated. see log file for complete stacktrace
But when i test this using a business service, i.e. business service writes to the socket. It works.
I need to make it work using a class.
thnx

Hi All
I have a requirement of reading from a socket. I built the socket adapter from samples and successfully deployed on the server.
After that i created a proxy on socket protocol specified a port. Now when i try to write to the socket using a java client i get the following error.
<Error> <Sample.SocketTransport> <BEA-000000> <[Sample.SocketTransport:800034]SocketTransport receiver is failed.
java.net.SocketTimeoutException: Read timed out
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:150)
     at java.net.SocketInputStream.read(SocketInputStream.java:121)
     at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
     at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
     Truncated. see log file for complete stacktrace
But when i test this using a business service, i.e. business service writes to the socket. It works.
I need to make it work using a class.
thnx

Sync inbound java proxy timeout

Hi all
my scenario abap proxy to java proxy sync.
but i had timeout error with some bulk data, but not too big...
does anyone know how to increase time for inbound java proxy?
regards;
dennis

Dear Ogawa,
Please if you have step by step document please send me .
i am getting this error in my scenario:
I am working on Java server proxy, In my scenario i am picking a file from sender File Adapter and in Receiver side i am using java proxy (Inbound). But in SXMB_MONI , it give me the Error and Error no is :110
See the Detailed Error in Call Adapter.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please help me .
Regards
Lateef

ASA auth-proxy timeout

Hi, everyone
I have a puzzle with ASA auth-proxy authentication timeout. I want to achieve the inactivity timeout, that is, when there are some traffic btw client and host through ASA after user authenticated, cache timeout timer don't work. When traffic is end, cache timeout timer work again.
but when I configurate the ASA 7.0, I found if I have configurate the ASA timeout timer as absolute with the following command:
timeout uauth 0:05:00 absolute
I cannot change the timer to inactivity,
but can changed to as below
timeout uauth 0:05:00 absolute uauth 0:05:00 inactivity
what is its meaning?
and can user authentication timer change to inactivity?
very thanks

Use the timeout uauth absolute & inactivity values locally.
Try the bug CSCsg52108
http://www.cisco.com/en/US/docs/security/asa/asa71/command/reference/t_711.html#wp1318629

Unexpected socket read timeout

Hi everybody.
I am having problems with socket communication. I have a client application which connects to a server, sends a request over a socket and waits for a response. This procedure actually works unless the server doesn?t reply fast enough. I found out that the maximum time for the server to reply is exactly 4 minutes. The weird part is that I do not set any timeouts.
I was able to isolate the problem and it turned out that the unexpected 4 minute timeout only occurs if I use the socket?s shutdownOutput method prior to reading from the input stream.
Does anyone know of this problem and how one can solve it? Or is this a (known) bug in the JDK?
Regards,
Kai

This is a simple server that listens for a one-line message ("HI") which will receive no response, and will then close the connection.
// don't forget to import
import java.io.*;
import java.net.*;
public class Server {
ServerSocket server;
Socket socket;
BufferedReader in;
PrintWriter out;
public Server() {
try {
// Note: No timeouts or linger options were set on THIS machine.
server = new ServerSocket(110); // We will use port 110 for our example
socket = server.accept();
in = new BufferedReader(new InputStreamReader(socket.getInputStream()));
out = new PrintWriter(socket.getOutputStream());
String request = in.readLine(); // this method blocks (unless Java 1.4 is used and the Non-blocking option is set)
System.out.println(request);
in.close();
out.close();
socket.close();
server.close();
} catch(Exception e) {
e.printStackTrace(); // show the error
// add this is you want this to run as a stand-alone application
public static void main(String[] args) {
new Server();
The server starts, listens for connections, prints the 'request' to the console, and then closes the connection and the server is shutdown. There will be no problems since I DO NOT USE socket.shutdownInput()
Use my model code here to by-pass the issue you are having.

STUMPER - wl-proxy timeout default approx 220 seconds??

using iplanet4.1sp9 -- WL6.1sp1 -- Solaris 2.6
when the wl-proxy plugin tries to transfer a request to the WL server and the
server is down, it retries from #0 to #2 times (total of 3) before timing out.
Each retry takes about 220 seconds to timeout and only after all tries is the
errorPage info displayed. I have tried all timeout settings available to the
plugin and none affect this. Where is this value set!!!?magnus.conf ? obj.conf
? help ... thanks in advance.
-geoff.

Hi -
Was there any resolution to this? We have the same problem currently. While
the timeout was due to our long transaction and we'll optimise on that, but we
don't want the plugin to retry. We tried setting IDEMPOTENT OFF and it didn't
work either.
Any help appreciated. Thx.
[email protected]
"Geoff" <[email protected]> wrote:
>
using iplanet4.1sp9 -- WL6.1sp1 -- Solaris 2.6
when the wl-proxy plugin tries to transfer a request to the WL server
and the
server is down, it retries from #0 to #2 times (total of 3) before timing
out.
Each retry takes about 220 seconds to timeout and only after all tries
is the
errorPage info displayed. I have tried all timeout settings available
to the
plugin and none affect this. Where is this value set!!!?magnus.conf
? obj.conf
? help ... thanks in advance.
-geoff.

Socket proxy timeout

Similar Messages

Maybe you are looking for