Bhuvana Raj

Hi Renjan.

Thanks for your response.

We are using WLS version 10.3.

I would like to have an important piece of advice from ranchers on tuning our production WebLogic server - currently we are faced with the following scenario: We are performing load test on our server/application. Our application deployed on a managed server is not able to handle more than 650-700 sessions (cumulative count). Thereafter the server goes into 'Warning' state.

Exception thrown on the console is:
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

Reason: 'ThreadPool has stuck threads'

We understand that the error has got something to do with tuning the server. It would very nice if you could throw some light towards resolving this seemingly simple but severe problem we are faced with.

Originally posted by Joe Ess:
Is this problem specific to WinXP clients? Do you have other clients that can connect successfully?
Does your Windows 2003 server have a firewall (the answer to this question had better be "YES")? Is it properly configured?
Is your server in a DMZ or are there firewalls or proxies between your client and server?

Hi Joe,

The problem is solved. The network from which we tried to access the Server has firewall problem that blocks in creating the socket from one network to other.

We tried in stand alone XP systems and found to be working.

Kindly let me know if you have any questions.

Regards,
Bhuvana

Hi,
Thanks for your reply.

Client OS is Windows XP SP2.Server is Windows 2003 Server. For example, Server is running in the port 2000. Client tries to communicate to this port number but fails and throws: java.net.ConnectException: Connection timed out: connect.

It fail at this line: socketObject = new Socket(host,port); Before this line it prints the correct port number 2000 and the host name.

Please help me

Regards,
Bhuvana
[ November 03, 2007: Message edited by: Bhuvana Raj ]

Hi all,

It is a client server program using applet and socket. We are using applet in the client side & socket for communication to server.

In XP OS SP2 the socket object is not created and throws java.net.ConnectException: Connection timed out: connect.

Is it due to firewall that blocks port?

Thanks,
Bhuvana
[ November 02, 2007: Message edited by: Bhuvana Raj ]

Originally posted by Rogerio Kioshi:
allay -> array

actually

Originally posted by Milan Jagatiya:
Phycology

Geometry

Originally posted by manasi kulkarni:
risky

Kindly

Originally posted by manasi kulkarni:
tiny

nasty

Originally posted by Stan James:
lapidary

regularly
[ April 23, 2007: Message edited by: Bhuvana Raj ]

Originally posted by ankur rathi:


Lazy

Zoology

rally
[ April 20, 2007: Message edited by: Bhuvana Raj ]

Hello Ranchers,

I modified the code according to the link ActiveX Fix. It worked fine.

Regards,
Bhuvana

Ulf,

Thanks for your reply.
I tried that Patch in my local system. But they need not want the patch work to be applied on their OS. They are saying that this patch will work for certain months only. After that it will expire.They conclude that coding has to be modified.

Regards,
Bhuvana

Dear Ranchers,

Please help me to trace a solution to the above problem. When i applied the patch in XP OS using the microsoft link, the pop up didn't appear. It worked as in Windows 2000. But my client says that the patch is only a temporary solution because Microsoft lost their patent. They need the fix to be done in the code to get rid of the "Click to activate this control".

Thankyou for your help.

Regards,
Bhuvana