From: Andrew Haley <aph@redhat.com>
To: "Patrick Schäfer" <ps@ekse.de>
Cc: java@gcc.gnu.org
Subject: Re: Compiling project using apache mina fails
Date: Mon, 08 Jun 2009 10:05:00 -0000 [thread overview]
Message-ID: <4A2CE244.9030702@redhat.com> (raw)
In-Reply-To: <EE3F7261-A297-4778-A763-C799E3DDB182@ekse.de>
Patrick Schäfer wrote:
> hi andrew, thank you for looking into the stacktrace problem anyways!
>
> i have another problem running the code in gcj version 4.3.3 though.
>
> using jdk 1.5 the code runs just fine.
>
> using gcj I receive an exception when trying to access the local socket
> port, though the connection has been successfully established (which I
> can see on connected machine):
>
> java.lang.IllegalArgumentException: Bad port number: -1
> at java.net.InetSocketAddress.<init>(libgcj.9.dylib)
> at java.net.Socket.getLocalSocketAddress(libgcj.9.dylib)
> at
> org.apache.mina.transport.socket.nio.NioSocketSession.getLocalAddress(paa_mina)
>
> at
> org.apache.mina.transport.socket.nio.NioSocketSession.getLocalAddress(paa_mina)
>
> at paa.networklayer.paaClient.getSessionLocalAddress(paa_mina)
>
> is it possible that the local port number isn't stored in libgcj after
> connection establishment?
>
> would be great, if you had any idea what could be wrong.
If I had a way to look at what was happening I'd just have a look.
I don't know what class the Socket belongs to. At the call to
Socket.getLocalSocketAddress, do something like
println(socket)
println(socket.getClass())
Andrew.
next prev parent reply other threads:[~2009-06-08 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 14:38 Patrick Schäfer
2009-06-05 15:31 ` Andrew Haley
2009-06-07 18:32 ` Patrick Schäfer
2009-06-08 10:05 ` Andrew Haley [this message]
2009-06-08 19:26 ` Patrick Schäfer
2009-06-08 20:23 ` Andrew Haley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2CE244.9030702@redhat.com \
--to=aph@redhat.com \
--cc=java@gcc.gnu.org \
--cc=ps@ekse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).