You're probably sending the right data (you could confirm this with a packet sniff of the Java and Perl sessions; but your error is probably in the reading back part: <$socket> will attempt to read a line of data from the socket; if the returned data isn't character based (which is probably isn't), then this is likely to hang waiting for a \n character. Instead, you need to look at the Java code that does the reading back, and determine what it is expecting, then read that number of bytes in.

For example the server might return 2 bytes indicating the length, followed by that many bytes of data. That could be read using 

my $buf;
read($socket, $buf,2);
my $len = unpack 'n', $buf;
read($socket, $buf, $len);

[download]

In reply to Re: Converting Java Sockets to Perl Sockets by dave_the_m
in thread Converting Java Sockets to Perl Sockets by Art_XIV

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.