Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46139EBEC for ; Mon, 25 Feb 2013 17:56:12 +0000 (UTC) Received: (qmail 44459 invoked by uid 500); 25 Feb 2013 17:56:11 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 44369 invoked by uid 500); 25 Feb 2013 17:56:10 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Delivered-To: moderator for user@commons.apache.org Received: (qmail 82480 invoked by uid 99); 25 Feb 2013 17:39:00 -0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of zenofuturista@gmail.com designates 74.125.82.51 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=6I5Jyf6JyQzJsGqJX82fkJ9wUcYPY2gVKknA43Yp1e0=; b=FxMp73t9mj3UJciAB7dg7u6XAyQ9N0in1qZB6y7LExjyiPzS2pCZtM86sYAhMBs3ag WbTbgiTIaJi6fpiQ8EZZLMY0siXBDg006VhvcoFOUyYff2Y4jXj8s8jghM5Chc+UWAs4 6R61FBxPVMwkEFg+Som/GHSV4Np1TnXqOwR4ryUlH/u0MKm8ukMujjLPhL+SS7ajgpRr Y2LuQg+O7Bl9WquBA9sSN3QqW+5F4PwQuSNp3xCKEOGh5SIcQe0SvwyBax3Sxaa/LKYF noME0GeUI+VNiNwm4Fwtk89p6FIRwh+TFNk+72rcIApCwgwLg3rLSVtNnndjcxqixFRX Lelw== X-Received: by 10.180.91.106 with SMTP id cd10mr13985012wib.6.1361813912493; Mon, 25 Feb 2013 09:38:32 -0800 (PST) MIME-Version: 1.0 Sender: zenofuturista@gmail.com From: =?UTF-8?B?SmFuIMWgw61sZW7DvQ==?= Date: Mon, 25 Feb 2013 18:38:12 +0100 X-Google-Sender-Auth: WVbp-VujZWJB4NhQG5z4mfNUvss Message-ID: Subject: commons daemon weird behaviour To: user@commons.apache.org Content-Type: multipart/alternative; boundary=f46d043be11a81371704d6900288 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043be11a81371704d6900288 Content-Type: text/plain; charset=ISO-8859-1 Dear mailing list, I have run into a strange behavior while using procrun to wrap my java application as a Windows service. This issue is linked to DatagramSocket, which is created and bound to local port inside the "service". So, what is going on: If I run the application as a service, the DatagramSocket stops receiving any datagrams after lets say five minutes of proper work. On the other hand, if I run my jar simply as a java application (via java -jar xxx.jar) everything works fine whole time without this issue. I have used tcpdump on the router which is source of these datagrams and the network traffic is correct, what more, I also used jpcap to see if these packets arrive on the local port and yes, they arrive. Next strange thing is, that if I send some datagram out trough this socket, it starts to work again, but only for lets say next five minutes, after this time, situation repeats and nothing else gets received from this time on, even though I see data arrived in the network dumps. There is probably everything fine in my code, I am trying to solve this for several days, so I have triple checked everything in my code. Important configurations of my service, machine and software versions are as follows: commons-daemon-1.0.13, OS Windows XP, firewall off. default JVM, which version is 1.7.0_13-b20 memory pools and thread stack size are not set up - left blank, startup and shutdown mode are set to jvm. Well, I dont know if I described my problem in a good way, so if you need some other info about my configuration or even some test case, let me know, I can probably prepare it. I hope it will be some simple problem. Have a nice day and thanks for your time, Jan --f46d043be11a81371704d6900288--