From dev-return-25177-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Feb 10 22:05:26 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 7423 invoked from network); 10 Feb 2006 22:05:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Feb 2006 22:05:25 -0000 Received: (qmail 29509 invoked by uid 500); 10 Feb 2006 22:05:21 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 29468 invoked by uid 500); 10 Feb 2006 22:05:21 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 29457 invoked by uid 99); 10 Feb 2006 22:05:21 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 14:05:20 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 6B63CDC for ; Fri, 10 Feb 2006 23:04:59 +0100 (CET) Message-ID: <1678965389.1139609099400.JavaMail.jira@ajax.apache.org> Date: Fri, 10 Feb 2006 23:04:59 +0100 (CET) From: "Aaron Mulder (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-1349) Missing Ports in Startup Port List In-Reply-To: <489337089.1134500385132.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GERONIMO-1349?page=comments#action_12365990 ] Aaron Mulder commented on GERONIMO-1349: ---------------------------------------- With the previous patch committed and an adjustment to OpenEJB to show the ORB TSS listen port, there is only one port left, which is the CORBA root POA. The last line of our code that executes is the OpenEJBPOA constructor -- it calls super and super listens on a random port. It would be nice to figure out a way to pass a port into that. However, that would still leave the problem that one GBean (the CORBABean) effectively wraps both the ORB and POA, and our port list currently can't handle a single GBean listening on multiple ports. It would be nice if OpenEJBORB and OpenEJBPOA were GBeans such that they could each provide a manageable port number. Perhaps the TSS configuration should be a GBean, as it's what has the actual SSL listen port configured on it. Also, if a secondary TSS is defined to listen on a different port and then associated with a live EJB, that probably would not be caught at present. > Missing Ports in Startup Port List > ---------------------------------- > > Key: GERONIMO-1349 > URL: http://issues.apache.org/jira/browse/GERONIMO-1349 > Project: Geronimo > Type: Bug > Components: CORBA, startup/shutdown > Versions: 1.0-M5, 1.0 > Reporter: Aaron Mulder > Assignee: Aaron Mulder > Fix For: 1.1, 1.0.1 > Attachments: GERONIMO-1349_JMXConnector.patch > > The port list for Geronimo is: > Listening on Ports: > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 4201 0.0.0.0 ActiveIO Connector EJB > 4242 0.0.0.0 Remote Login Listener > 8019 127.0.0.1 Jetty Connector AJP13 > 8080 0.0.0.0 Jetty Connector HTTP > 8443 0.0.0.0 Jetty Connector HTTPS > 61616 0.0.0.0 ActiveMQ Message Broker Connector > The port list from netstat is: > tcp 0 0 :::1099 :::* LISTEN 8447/java > tcp 0 0 :::1389 :::* LISTEN 8447/java > tcp 0 0 :::1527 :::* LISTEN 8447/java > tcp 0 0 :::4201 :::* LISTEN 8447/java > tcp 0 0 :::4242 :::* LISTEN 8447/java > tcp 0 0 127.0.0.1:8019 :::* LISTEN 8447/java > tcp 0 0 :::8080 :::* LISTEN 8447/java > tcp 0 0 :::8443 :::* LISTEN 8447/java > tcp 0 0 :::16321 :::* LISTEN 8447/java > tcp 0 0 :::61616 :::* LISTEN 8447/java > The differences are: > 1389 -- Directory > variable -- 16321 (16333 on next run) -- what is this?? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira