Problem on server side (Socket Programming)

Hi

I have a very weird problem. My application is a client server application and the server is running on a Unix machine ij the background using no-hup command. The problem is that after some days of running in this case it is like 15 days there is no response form the server. i can not find the problem so I am posting a certain section of my code here. if any one can find any technical flaw in the code plz do let me know. i would really appreciate that.


Here is the Code:




import java.io.*;
import java.net.*;
import java.sql.*;
import java.util.*;
import javax.swing.*;
import javax.swing.table.*;


public class Server
{
public static void main(String[] args)
{
ServerSocket s;

try
{
s = new ServerSocket(7000);
System.out.println("Server started");

while(true)
{
Socket incoming = s.accept( );
System.out.println("incoming " + incoming);
ThreadedDataObjectHandler t = new ThreadedDataObjectHandler(incoming);
t.start();
}
}
catch (Exception e)
{

}
}

static class ThreadedDataObjectHandler extends Thread
{
public ThreadedDataObjectHandler()
{

}

public ThreadedDataObjectHandler(Socket i)
{
incoming = i;
}

public void run()
{
try
{
//System.out.println("Server testing ");

//System.out.println("incoming " + incoming);

in = new ObjectInputStream(incoming.getInputStream());
out = new ObjectOutputStream(incoming.getOutputStream());

//System.out.println("in " + in);
//System.out.println("out " + out);

String strpassword = "";

ExtartingSurgeData extdata = null;

float []stationslevel = new float[6];

DataObject myobjecttowrite = new DataObject();

while(true)
{
// something //
}


Thanks

First of all please use code tags when you posting again. Unformated codes are harder to read. If you don't know how to do it, please check on my forum signature, you can find a relevant page.

Regarding your question, better to add some exception handling code in catch block. It's the easiest way to track what's really happening.

Alright I will post the thread again with proper tagged code:



Hi

I have a very weird problem. My application is a client server application and the server is running on a Unix machine ij the background using no-hup command. The problem is that after some days of running in this case it is like 15 days there is no response form the server. i can not find the problem so I am posting a certain section of my code here. if any one can find any technical flaw in the code plz do let me know. i would really appreciate that.


Here is the Code:




import java.io.*;
import java.net.*;
import java.sql.*;
import java.util.*;
import javax.swing.*;
import javax.swing.table.*;


public class Server
{
public static void main(String[] args)
{
ServerSocket s;

try
{
s = new ServerSocket(7000);
System.out.println("Server started");

while(true)
{
Socket incoming = s.accept( );
System.out.println("incoming " + incoming);
ThreadedDataObjectHandler t =
new ThreadedDataObjectHandler(incoming);
t.start();
}
}
catch (Exception e)
{

}
}

static class ThreadedDataObjectHandler extends Thread
{
public ThreadedDataObjectHandler()
{

}

public ThreadedDataObjectHandler(Socket i)
{
incoming = i;
}

public void run()
{
try
{
in = new ObjectInputStream(incoming.getInputStream());
out = new ObjectOutputStream(incoming.getOutputStream());

DataObject myobjecttowrite = new DataObject();

while(true)
{
// do something //
}
.................................................. ..................

Thanks

Thanks

The problem occurs only say after 15 days. So could this be coz the program goes into an infinite loop, coz there are 2 while loops

Still you didn't add code tags. Use open tag as [code] and class tag as [ /code]

Quote:

---

Originally Posted by ersachinjain

Thanks

The problem occurs only say after 15 days. So could this be coz the program goes into an infinite loop, coz there are 2 while loops

---

Could be something like this. For a long run, may be because of some hardware issues or anything related the socket can be not listening.

Oh so you mean there can be hardware issues because of which socket has problem in listening. Could this be because the server on which the code is running is really old like 10 years old.

That's not the exact issue lol. I just give you an example. Many issues could be cause for that, and what I want to point to you is that log more information on relevant catch blocks. Then it's easy to track the issues, if any.

Quote:

---

Originally Posted by ersachinjain

Could this be because the server on which the code is running is really old like 10 years old.

---

In an endless loop, if you are not handle the exceptions properly it can be executed even for millions of years. :)