JAVA socket problem. need equivalent to a socket.shutdownOutput()

What do you mean by reference?

That stinks there isn't a special character you can send to say you are done sending.. Did you try socket.setSoLinger()?

>> PrintWriter wr = new PrintWriter(socket.getOutputStream(), true);

-->

OutputStream out = socket.getOutputStream();
PrintWriter wr = new PrintWriter(out, true);

......

out.close();

without the shutdownOutput() I meant..

I tried it to no avail...

Did you try the linger as well?

Ok,

I tried both suggestions and neither work... when closing the reference (out.close), it closes the socket and I have nothing to read.  I am attaching the modified source...  It will work by commenting the out.close and using the shutdownOutput() though...

import java.net.*;
import java.io.*;
import java.lang.*;

public class XXXX {
    public static void main (String[] args) throws Exception {
    try {
          
          char dq = (char)34;
          String data = "example";
        String hostname = "XX.XX.xx.xx";
        int port = 2000;
        InetAddress addr = InetAddress.getByName(hostname);
        Socket socket = new Socket(addr, port);    
       
        // Specify the timeout.
        socket.setSoTimeout(1000);

            // Send data to socket
       // PrintWriter wr = new PrintWriter(socket.getOutputStream(), true);
        OutputStream out = socket.getOutputStream();
            PrintWriter wr = new PrintWriter(out, true);
        //wr.println(data);
        wr.println(data);
        wr.flush();
       
        out.close();

         // socket.shutdownOutput();
      
          // Get response from the fed ex server!
            BufferedReader rd = new BufferedReader(new InputStreamReader(socket.getInputStream()));

             String line;
        while ((line = rd.readLine()) != null)
          {
                System.out.println(line);
              }
       
        wr.close();
        rd.close();
          socket.close();
          } catch (Exception e)
        {
              System.out.println(e);
          }         
  }
}

Yes, my first response was with the linger... I tried it right after I set the timeout and also after the flush...

ack.. I checked out the java source for the socket and of course it is a native method for shutdownOutput().  Did you write/control the socket server?  If so just code a special character for the "stop listening and give me some output" event.  If you don't control it (I think you said it is FedEx), have you asked them "how do I get it to stop listening?"

I guess in order for the server to see a FIN, it needs to see an EOF marker...  R there EOF markers embedded in files?  What I was thinking, is that I could somehow read an empty file with an EOF and append that to the data I am sending so the server would know that there was an end of file...

Just a brainstorm but I'm sure you could do something with the File class or the FileInputStream.. I would check out the source of those and see how they determine an EOF condition.. then replicate that to your outputstream..

I am waiting for a response to see if there is some sort of termination sequence that it is expecting... However, I didn't see that evidenced in the documentation they provide online...  Here is the "sample" source code from a C version of the program they include in the Appendix...

using TCP/IP protocol.
/*
* (c) Copyright FedEx 1998-2002
*
*
* Ship Manager Business Architecture Development
* Custom Integrated Solutions
* September 1998
*
*
*
* DESCRIPTION: Sample socket client to connect to the Ship Manager Plus Server.
* Inputs: <input file> <output file>
* Outputs: <output file>
*
* COMMENTS: change the #define PSPSERVER_HOSTNAME to match the PSPServer
* hostname as defined in your /etc/hosts file.
*
* COMPILE:
* SOLARIS 2.6 cc fxrssamp.c -o fxrssamp -lnsl -lsocket
* REDHAT LINUX 7.2 cc fxrssamp.c -o fxrssamp
* WINDOWS VISUAL STUDIO 6 Be sure to include WSOCK32.lib in link
* IBM AIX 3.4 /bin/xlc_r fxrssamp.c -o fxrssamp
* HPUX 11.0 /opt/aCC/bin/aCC +W829,749 +DA1.1 fxrssamp.c -o fxrssamp
*
*/
#ifdef WIN32
#include <winsock.h>
#include <io.h>
#define CLOSE_SOCKET closesocket
#else
#include <unistd.h> /* open(), close(), write(), read() */
#include <sys/types.h>
#include <sys/socket.h>
#include <netdb.h>
#include <netinet/in.h>
#include <errno.h>
#define CLOSE_SOCKET close
#endif
#include <stdio.h>
#include <string.h>
/***** SET YOUR TEST HOST HERE *****/
#define PSPSERVER_HOSTNAME "yourFedExServerName.yourcompany.com"
#define PSPSERVER_PORT 2000
int ConnectPSPServer(int *sd, char *hostNm, short portNbr);
void reportError (char *str);
int main(int argc, char **argv)
{
int sd, i=0;
FILE *inFile, *outFile;
char buffer[4096];
if(argc != 3)
{
printf("USAGE: %s <trans in file> <trans out file>\n", argv[0]);
return 1;
}
printf("Test Client of FedEx Ship Manager Plus Server started.\n");
printf("Attempting to connect to: %s:%d\n", PSPSERVER_HOSTNAME, PSPSERVER_PORT);
if(!ConnectPSPServer(&sd, PSPSERVER_HOSTNAME, PSPSERVER_PORT))
{
printf("Error: Cannot connect to %s\n", PSPSERVER_HOSTNAME);
return 2;
}
printf("Connected to %s:%d\n", PSPSERVER_HOSTNAME, PSPSERVER_PORT);
inFile = fopen(argv[1], "r");
/* error checking ignored for simplicity */
outFile = fopen(argv[2], "wa");
/* error checking ignored for simplicity */
printf("Reading request transactions from: %s\n", argv[1]);
printf("Writing reply transactions to: %s \n", argv[2]);
fgets(buffer, sizeof(buffer), inFile); /* read transaction request */
while(!feof(inFile))
{
int rc;
rc=send(sd, buffer, strlen(buffer),0); /* write request to server */
if (rc < 0)
reportError("Write to server failed");
memset (buffer, 0, sizeof buffer);
rc=recv(sd, buffer, sizeof buffer,0); /* read transaction reply */
if (rc <= 0)
{
if (rc == 0)
printf ("socket was closed by server\n");
else
reportError("Reading response failed");
}
fputs(buffer, outFile); /* write reply to file */
fputc('\n', outFile);
i++;/* increase reply count */
if(i % 10 == 0)
printf("%d", i);
else
printf(".");
fflush(stdout);/* stdout normally flushes with each \n character */
fgets(buffer, sizeof(buffer), inFile); /* read transaction request */
}
fclose(outFile);
fclose(inFile);
if(CLOSE_SOCKET(sd) == 0) /* Close connection */
printf("\nConnection to %s terminated.\n", PSPSERVER_HOSTNAME);
printf("%d transactions processed.\n", i);
return 0;
}
int ConnectPSPServer(int *sd, char *hostNm, short portNbr)
{
struct hostent *hp;
struct sockaddr_in sin;
#ifdef WIN32
WORD winsock_ver;
WSADATA winsock_data;
int rc;
winsock_ver = 0x0101;
rc = WSAStartup(winsock_ver, &winsock_data);
if (rc != 0)
return 0;
#endif
/* Set up the socket descriptor and the address */
memset(&sin, 0, sizeof(struct sockaddr_in));
*sd = socket(AF_INET, SOCK_STREAM, 0);
if (*sd < 0)
{
reportError("socket call failed");
return 0;
}
hp = gethostbyname(hostNm);
if (hp == NULL)
{
reportError("gethostbyname lookup failed");
return 0;
}
memcpy(&sin.sin_addr, hp->h_addr, hp->h_length);
sin.sin_port = htons(portNbr);
sin.sin_family = hp->h_addrtype;
/* Make the connection */
if(connect(*sd, (struct sockaddr *)&sin, sizeof(struct sockaddr_in)) == -1)
{
reportError("connect to host failed");
return 0;/*FALSE*/
}
return 1;/*TRUE*/
}
void reportError (char *str)
{
int errValue;
#ifdef WIN32
errValue = WSAGetLastError();
#else
errValue = errno;
#endif
printf ("ERROR: %s [err=%d]\n", str, errValue);
return;

I think you're right about the EOF as the terminator.. a quick test would be to read a file and write to the output stream and make sure that everything worked appropriately.

not to be flip.. but I'm sure it was stuff like this that caused the shutdownOutput() to be added.. what a pain.

Try

int buf = -1;
StringReader in = new StringReader(data);
while ((buf = in.read()) > -1) {
      out.write(buf);
}

that looks like a good call CEHJ..;-)

I will try your suggest CEHJ,  I also have another piece of info that may help you guys help me :)  (THANKS ALOT NO MATTER WHAT!)

Anyway, when I was cutting and pasting the C code, I noticed that they allocate 4096 bytes to the write... I decided to try to fill up the buffer... and tested > 4096 and <4096

        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        // total buffer size 4410 //
        System.out.println("*** 1 ***");

The end result was that if I run this code "no close or setoutputoff... It works, albeit strangely since I am sending mutliple requests...  Anyway, I think I may need to just fill up the buffer with  4096 - data.length() empty spaces or garbage character...

If one of you could help me with that code ( I AM TOTALLY NOT A JAVA PROGRAMMER) it would be awesome!


import java.net.*;
import java.io.*;
import java.lang.*;

public class XXXedex {
    public static void main (String[] args) throws Exception {
    try {
          
          char dq = (char)34;
          String data = "test";
        String hostname = "XXXXX5";
        int port = 2000;
        InetAddress addr = InetAddress.getByName(hostname);
        Socket socket = new Socket(addr, port);    
       
        // Specify the timeout.
        socket.setSoTimeout(1000);
       
       // Send data to socket
       // PrintWriter wr = new PrintWriter(socket.getOutputStream(), true);
        OutputStream out = socket.getOutputStream();
            PrintWriter wr = new PrintWriter(out, true);
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        wr.println(data); //441
        // total buffer size 4410 //
        System.out.println("*** 1 ***");
            
        wr.flush();
       
   
       // out.close();

         //socket.shutdownOutput();
      
          // Get response from the fed ex server!
            BufferedReader rd = new BufferedReader(new InputStreamReader(socket.getInputStream()));

             String line;
        while ((line = rd.readLine()) != null)
          {
                System.out.println(line);
              }
       
        wr.close();
        rd.close();
          socket.close();
          } catch (Exception e)
        {
              System.out.println(e);
          }
          
  }
}

I'm not sure that the size of the buffer is significant

Ok, I am trying your last suggestion CEHJ... Forgive my ignorance but where exactly should I include that... I am asuming that will handle the write to the server... but it looks like out.write(buf) will be numeric...

Forgive me in advance! :)

> Anyway, I think I may need to just fill up the buffer with  4096 - data.length() empty spaces or garbage character...

if you create a 4096 byte buffer it will be full of )'s by default.
You can use the Arrays.fill() method to fill it whatever you need.

Would look something like this (data is the string you want to pass):

byte[] bytes = data.getBytes();
byte[] buf = new byte[4096];
Arrays.fill(buf, 0);  // youcould also try spaces
System.arraycopy(bytes, 0, buf, 0, bytes.length);

Looks like filling the buffer should fix your problem.

There should be no need to be writing empty buffers redundantly to fix the problem.

It's conceivable that a null-termination is expected, so also try

int buf = -1;
StringReader in = new StringReader(data);
while ((buf = in.read()) > -1) {
     out.write(buf);
}
out.write(0);

CEHJ and others,

I am having trouble witht that last bit of code... when I print the output (buf) it is numeric data...  The data string is definately not...  I am going to take a look at this right now, any quick answers would be greatly appreciated.

thanks!

You just need to substitute it for the code sending that 'data' String

>>when I print the output (buf) it is numeric data...

You needn't worry about that. If you want to print it, cast it to char

Ok, got it... Bad news is that this also works if you use the shutdownOutput statement. I tried it sans the out.write(0) as well...  Any other suggestions???

     // Send data to socket
       OutputStream out = socket.getOutputStream();
   
            int buf = -1;
            StringReader in = new StringReader(data);
            while ((buf = in.read()) > -1) {
                 out.write(buf);
                  }
          out.write(0);
        //out.close();

       //socket.shutdownOutput();

Try

out.write(0);
out.write("\r\n".getBytes());

Right so have you tried taking your data as a file and reading the file to that output? The socket server isn't getting the termination character that it wants.. I think that is what you should be striving to find.  Do you have a contact at fedex that you could ask about this?  

Nada...  Still works with the  shutdownOutput() thought :(

I have a contact that is researching...  I think they will probably come back with the suggestion to write it in C...  I will try the file idea right now and post.

tried to but the data in a file and pass... it doesn't work.. tried most comb/perms of file encoding  and term characters... also pc and dos.

>>I think they will probably come back with the suggestion to write it in C..

Don't let them palm you off with that ;-) It should be doable in Java

I just finished with fed-ex support...  I don't know if support is really the term that applies :)!  Anyway, they had no suggestion to help... The 99,"" is a termination sequence that is expected by the server... Using the shutdownOutput command, I receive a response and that can only happen if the transaction is complete which demonstrates that my test transaction is syntactically correct.

I am really at a loss...

>>The 99,"" is a termination sequence that is expected by the server

Don't quite understand this ...

Wait if you send the characters 99,"" fedex calls the transaction complete?  The "file" you are sending to them has a published spec right?  That file must have some type of "end" record.. which means that if you are sending the file in the right format the socket shouldn't have to be shutdown to start receiving a response.  Is there anyway you can ask them to give you a debugish environment. Can you confirm with them what they are actually receiving?  Maybe there is some stupid encoding problem?

The transaction I send has a specific format. The sequence 99,"" is a terminator for a transaction.  The fact that I am getting a valid response indicates that my transaction contains is valid as defined by fed-ex.

The support person i spoke to says that 99,"" is the terminator the server is looking for... I can conclusively show that my transaction contains the terminator and the failure to respond is not due to a malformed transaction...

This just takes us back to the fact that without the shutdownOutput method, I can't get the reply...

Okay so are you certain that fedex is receiving the 99,"" terminator?  If not, the shutdownOutput method could merely be doing something like a buffer flush (I know you have the flush in your code) at a lower level.  I would make sure that they are receiving what you think they are.  You could snoop the tcp packets and confirm you are sending what you think you are, if they can't help you.

Did you try the code I posted above?

>>The sequence 99,"" is a terminator for a transaction.

In that case, writing to the stream with \r\n is possibly 'undoing' the termination

You should not be using a PrintWriter at all in fact :)

I am changing the printwriter code when I get the chance... It works but it leaves a strange termination character I don't like.  Anyway, I split the points again because I found everyones help very usefull.  The solution was actually very simple and I am happy it is behind me.

The error turned out to be on the read of the response.  Using what I learned from CEHJ

int buf = -1;
StringReader in = new StringReader(data);
while ((buf = in.read()) > -1) {
     out.write(buf);
}
out.write(0);

I  modified this to see the effect of the multiple sends I did when I saw a resposne.  I realized by seeing the ascii stream coming back that the termination was not what I expected.  I then corrected it and it has been working great ever since!!!

You all rock!

You don't need to use a StringReader (that approach will be pretty slow), see the code I posted earlier :)

Glad to hear it..

that you solved the problem I mean.. It is usually challenging to find the real problem.. the solution is usually pretty easy once you find it.