[jira] Created: (DIRMINA-514) Session closing problem on Mac OS X

Session closing problem on Mac OS X
-----------------------------------

                 Key: DIRMINA-514
                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
             Project: MINA
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0.0-M1
         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
            Reporter: Matteo Merli


A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.

I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.

This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.

This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Merli updated DIRMINA-514:
---------------------------------

    Attachment: Echo1_1.java

Test case with Mina 1.1 (It works fine)

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>         Attachments: Echo1_1.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Merli updated DIRMINA-514:
---------------------------------

    Attachment: Echo2_0.java

Test case with Mina 2.0 (it shows up the problem on Mac OS X)

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559807#action_12559807 ]

Trustin Lee commented on DIRMINA-514:
-------------------------------------

As you pointed out, it works just fine for both in Linux.  The following is the TCPDUMP result.  I tested using loopback device and eth0 (connected via a switching hub).  Does anyone have access to MacOS X?  I don't have any Mac for me.  For now I just suspect JDK hmm...

trustin@eden:~/workspace/checkout/asf/mina/trunk/core$ sudo tcpdump -i lo port 9090
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 68 bytes
14:00:36.048017 IP localhost.34516 > localhost.9090: S 1140196216:1140196216(0) win 32792 <mss 16396,sackOK,timestamp 77224720[|tcp]>
14:00:36.059311 IP localhost.9090 > localhost.34516: S 1130214661:1130214661(0) ack 1140196217 win 32768 <mss 16396,sackOK,timestamp 77224720[|tcp]>
14:00:36.059353 IP localhost.34516 > localhost.9090: . ack 1 win 257 <nop,nop,timestamp 77224720 77224720>
14:00:36.199075 IP localhost.34516 > localhost.9090: P 1:3(2) ack 1 win 257 <nop,nop,timestamp 77224765 77224720>
14:00:36.199087 IP localhost.9090 > localhost.34516: . ack 3 win 256 <nop,nop,timestamp 77224765 77224765>
14:00:36.199628 IP localhost.9090 > localhost.34516: P 1:3(2) ack 3 win 256 <nop,nop,timestamp 77224765 77224765>
14:00:36.199643 IP localhost.34516 > localhost.9090: . ack 3 win 257 <nop,nop,timestamp 77224765 77224765>
14:00:36.199701 IP localhost.9090 > localhost.34516: F 3:3(0) ack 3 win 256 <nop,nop,timestamp 77224765 77224765>
14:00:36.211345 IP localhost.34516 > localhost.9090: F 3:3(0) ack 4 win 257 <nop,nop,timestamp 77224769 77224765>
14:00:36.211358 IP localhost.9090 > localhost.34516: . ack 4 win 256 <nop,nop,timestamp 77224769 77224769>

10 packets captured
20 packets received by filter
0 packets dropped by kernel
trustin@eden:~/workspace/checkout/asf/mina/trunk/core$ sudo tcpdump -i eth0 port 9090
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
14:01:03.247024 IP bonobono.60466 > eden.9090: S 918076750:918076750(0) win 5840 <mss 1460,sackOK,timestamp 29913736[|tcp]>
14:01:03.247334 IP eden.9090 > bonobono.60466: S 1159059088:1159059088(0) ack 918076751 win 5792 <mss 1460,sackOK,timestamp 77232880[|tcp]>
14:01:03.247222 IP bonobono.60466 > eden.9090: . ack 1 win 92 <nop,nop,timestamp 29913736 77232880>
14:01:03.751808 IP bonobono.60466 > eden.9090: P 1:3(2) ack 1 win 92 <nop,nop,timestamp 29913888 77232880>
14:01:03.751822 IP eden.9090 > bonobono.60466: . ack 3 win 46 <nop,nop,timestamp 77233031 29913888>
14:01:03.752581 IP eden.9090 > bonobono.60466: P 1:3(2) ack 3 win 46 <nop,nop,timestamp 77233032 29913888>
14:01:03.752666 IP eden.9090 > bonobono.60466: F 3:3(0) ack 3 win 46 <nop,nop,timestamp 77233032 29913888>
14:01:03.752841 IP bonobono.60466 > eden.9090: . ack 3 win 92 <nop,nop,timestamp 29913888 77233032>
14:01:03.753001 IP bonobono.60466 > eden.9090: F 3:3(0) ack 4 win 92 <nop,nop,timestamp 29913888 77233032>
14:01:03.753008 IP eden.9090 > bonobono.60466: . ack 4 win 46 <nop,nop,timestamp 77233032 29913888>

10 packets captured
10 packets received by filter
0 packets dropped by kernel
trustin@eden:~/workspace/checkout/asf/mina/trunk/core$

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573170#action_12573170 ]

Justin SB commented on DIRMINA-514:
-----------------------------------

I've got this happening in my application also, on Mac OS X Leopard 10.5.2.

I've verified that MINA seems to be doing the right thing, in that the destroy function of NioProcessor is called and seems to execute OK.  .close is called on the channel, no exception is thrown, and the channel moves into the closed state.  However, the socket does remain open (I've only tested loopback).

For reference, the destroy function is below.

@Override
    protected void destroy(NioSession session) throws Exception {
        ByteChannel ch = session.getChannel();
        SelectionKey key = session.getSelectionKey();
        if (key != null) {
            key.cancel();
        }
        ch.close();
    }

ch is a java.nio.channels.SocketChannel.  After the close statement, toString() gives java.nio.channels.SocketChannel[closed]

I haven't found any references to this as a known bug.  I would think that if it were a bug in the Mac OS, that these problems would be visible in every application that uses NIO, but I can't think what could be different here.

Following the Tomcat example, I tried explicitly closing the socket:
protected void destroy(NioSession session) throws Exception {
        ByteChannel ch = session.getChannel();
        SelectionKey key = session.getSelectionKey();
        if (key != null) {
            key.cancel();
        }
        if (ch instanceof SocketChannel) {
                        SocketChannel sc = (SocketChannel) ch;
                        Socket socket = sc.socket();
                        socket.close();
                        System.out.println(socket.isClosed());
                }
        ch.close();
    }

But that doesn't improve matters: socket.isClosed() is true, but the socket remains open.

netstat shows the socket to be in state ESTABLISHED (on both legs, as this is localhost).

I think, but am not certain, that this only applies to channels where we are the server, if that provides a clue to anyone.

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Heath updated DIRMINA-514:
-------------------------------

    Fix Version/s: 2.0.0-M2

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574080#action_12574080 ]

Matthew Phillips commented on DIRMINA-514:
------------------------------------------

This looks like it might be related to DIRMINA-531

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576854#action_12576854 ]

Mark Webb commented on DIRMINA-514:
-----------------------------------

This is what I get on my iMac (OS X 10.5.2)

java -version
java version "1.6.0_04-dp"
Java(TM) SE Runtime Environment (build 1.6.0_04-dp-b06-110)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_04-b12-45-optimized, mixed mode)


23:38:27.969274 IP6 localhost.64788 > localhost.websm: S 3411499079:3411499079(0) win 65535 <mss 16324,nop,wscale 2,nop,nop,timestamp 33588472 0,sackOK,eol>
23:38:27.969313 IP6 localhost.websm > localhost.64788: S 1775328828:1775328828(0) ack 3411499080 win 65535 <mss 16324,nop,wscale 3,nop,nop,timestamp 33588472 33588472,sackOK,eol>
23:38:27.969322 IP6 localhost.64788 > localhost.websm: . ack 1 win 65535 <nop,nop,timestamp 33588472 33588472>
23:38:27.969331 IP6 localhost.websm > localhost.64788: . ack 1 win 65535 <nop,nop,timestamp 33588472 33588472>
23:38:29.805900 IP6 localhost.64788 > localhost.websm: P 1:8(7) ack 1 win 65535 <nop,nop,timestamp 33588491 33588472>
23:38:29.805926 IP6 localhost.websm > localhost.64788: . ack 8 win 65534 <nop,nop,timestamp 33588491 33588491>
23:38:29.806421 IP6 localhost.websm > localhost.64788: P 1:8(7) ack 8 win 65534 <nop,nop,timestamp 33588491 33588491>
23:38:29.806437 IP6 localhost.64788 > localhost.websm: . ack 8 win 65535 <nop,nop,timestamp 33588491 33588491>
23:38:29.806478 IP6 localhost.websm > localhost.64788: F 8:8(0) ack 8 win 65534 <nop,nop,timestamp 33588491 33588491>
23:38:29.806490 IP6 localhost.64788 > localhost.websm: . ack 9 win 65535 <nop,nop,timestamp 33588491 33588491>
23:38:29.806608 IP6 localhost.64788 > localhost.websm: F 8:8(0) ack 9 win 65535 <nop,nop,timestamp 33588491 33588491>
23:38:29.806623 IP6 localhost.websm > localhost.64788: . ack 9 win 65534 <nop,nop,timestamp 33588491 33588491>

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577129#action_12577129 ]

Justin SB commented on DIRMINA-514:
-----------------------------------

Mark - are you saying this works for you on your Mac?  Also, it looks like you're running Java 6, whereas the officially released Java on Leopard 10.5 is Java 5?

(Java is bundled with and tied into the Mac OS).

I'm wondering if this could be a Java 5 vs Java 6 issue.

I'll see if I can capture a trace of my own, Java 5 with 10.5.2.

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577133#action_12577133 ]

Mark Webb commented on DIRMINA-514:
-----------------------------------

I was just posting the output of tcpdump.  I did not analyze the results too well.  The JDK1.6 that I am using is a developer release from Apple.  I will look deeper into this tonight.

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577137#action_12577137 ]

Justin SB commented on DIRMINA-514:
-----------------------------------

Well that was easy - thanks Matteo for a good test case.  Again, Mac OS 10.5.2; Java 5.

Has anyone tried this with Java 5 on Linux / Windows?  Maybe the Mac OS isn't the factor here?


java -version
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)


sudo tcpdump -i lo0 port 9090
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes
12:30:59.691950 IP localhost.53249 > localhost.websm: S 2108918664:2108918664(0) win 65535 <mss 16344,nop,wscale 3,nop,nop,timestamp 148704767 0,sackOK,eol>
12:30:59.692004 IP localhost.websm > localhost.53249: S 879703052:879703052(0) ack 2108918665 win 65535 <mss 16344,nop,wscale 3,nop,nop,timestamp 148704767 148704767,sackOK,eol>
12:30:59.692017 IP localhost.53249 > localhost.websm: . ack 1 win 65535 <nop,nop,timestamp 148704767 148704767>
12:30:59.692033 IP localhost.websm > localhost.53249: . ack 1 win 65535 <nop,nop,timestamp 148704767 148704767>
12:31:00.774681 IP localhost.53249 > localhost.websm: P 1:3(2) ack 1 win 65535 <nop,nop,timestamp 148704778 148704767>
12:31:00.774726 IP localhost.websm > localhost.53249: . ack 3 win 65534 <nop,nop,timestamp 148704778 148704778>
12:31:00.775150 IP localhost.websm > localhost.53249: P 1:3(2) ack 3 win 65534 <nop,nop,timestamp 148704778 148704778>
12:31:00.775199 IP localhost.53249 > localhost.websm: . ack 3 win 65535 <nop,nop,timestamp 148704778 148704778>


Then nothing.  If I disconnect from the client, I then get this:

12:31:09.078705 IP localhost.53249 > localhost.websm: F 3:3(0) ack 3 win 65535 <nop,nop,timestamp 148704861 148704778>
12:31:09.078741 IP localhost.websm > localhost.53249: . ack 4 win 65534 <nop,nop,timestamp 148704861 148704861>

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577280#action_12577280 ]

Mark Webb commented on DIRMINA-514:
-----------------------------------

OK.  I run the Echo2_0 class.  In a terminal I do the following:

-------------------------------------------------
elihusmails$ telnet localhost 9090
Trying ::1...
Connected to localhost.
Escape character is '^]'.
hello
hello
Connection closed by foreign host.
-------------------------------------------------

As soon as I type in "hello", I get the "Connection closed by foreign host".  I get this with Java 6, but not in Java 5.  So I think this is a problem with Java 5.  

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577636#action_12577636 ]

Rich Dougherty commented on DIRMINA-514:
----------------------------------------

A "me too" for this bug.

I see this problem as a hang within NioFileRegionTest, at least since revision 630016. The connector's sessionClosed method never gets called, so we wait forever for the latch.

I'm running Mac OS 10.4.11. I see the problems with version 1.5.0_13 of Apple's JRE and version 1.6.0_03-p3 of the SoyLatte port (haven't tested the latest version yet).

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578127#action_12578127 ]

Trustin Lee commented on DIRMINA-514:
-------------------------------------

Someone donate me a MacBook! (Just kidding! :D)

> Session closing problem on Mac OS X
> -----------------------------------
>
>                 Key: DIRMINA-514
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-M1
>         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>            Reporter: Matteo Merli
>             Fix For: 2.0.0-M2
>
>         Attachments: Echo1_1.java, Echo2_0.java
>
>
> A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
> I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
> This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
> This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[elihusmails]

From the tests that I have run, I believe that the problem goes away
with the version of java that I am running.

java -version
java version "1.6.0_04-dp"
Java(TM) SE Runtime Environment (build 1.6.0_04-dp-b06-110)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_04-b12-45-optimized, mixed mode)

Its a developer release from Apple.

On Wed, Mar 12, 2008 at 11:15 PM, Trustin Lee (JIRA) <jira@...> wrote:

>
>     [ https://issues.apache.org/jira/browse/DIRMINA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578127#action_12578127 ]
>
>
>  Trustin Lee commented on DIRMINA-514:
>  -------------------------------------
>
>  Someone donate me a MacBook! (Just kidding! :D)
>
>
>
>  > Session closing problem on Mac OS X
>  > -----------------------------------
>  >
>  >                 Key: DIRMINA-514
>  >                 URL: https://issues.apache.org/jira/browse/DIRMINA-514
>  >             Project: MINA
>  >          Issue Type: Bug
>  >          Components: Core
>  >    Affects Versions: 2.0.0-M1
>  >         Environment: Mac OS X 10.4 with Java 1.5.0_07 -87
>  >            Reporter: Matteo Merli
>  >             Fix For: 2.0.0-M2
>  >
>  >         Attachments: Echo1_1.java, Echo2_0.java
>  >
>  >
>  > A call to session.close() does not send a FIN packet althought MINA will considers the session as closed.
>  > I've attached two test cases, one that works with MINA 1.1 (and works fine) and other with MINA 2.0 that doesn't close connections.
>  > This is a simple echo server that receives a message, writes it back to the client and (should) close the connection.
>  > This problem is *NOT* ocurring on Linux where the same test case works fine. It only shows up on Mac OS X.
>
>  --
>  This message is automatically generated by JIRA.
>  -
>  You can reply to this email to add a comment to the issue online.
>
>

--
--------------------------------
Talent hits a target no one else can hit; Genius hits a target no one
else can see.