geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-4548) A few modules don't bind on the proper hostname:port
Date Sun, 22 Feb 2009 02:08:01 GMT

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

Jarek Gawor resolved GERONIMO-4548.
-----------------------------------

    Resolution: Duplicate

This is duplicate of GERONIMO-4442 and will be fixed in 2.1.4.



> A few modules don't bind on the proper hostname:port 
> -----------------------------------------------------
>
>                 Key: GERONIMO-4548
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4548
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CORBA, naming, OpenEJB
>    Affects Versions: 2.1.3
>         Environment: Linux 2.6.18-92.1.22.el5 #1 SMP Tue Dec 16 11:57:43 EST 2008 x86_64
x86_64 x86_64 GNU/Linux
> JDK: jdk1.6.0_12
>            Reporter: Jean-Baptiste Laplace
>
> Geronimo doest not bind to the specified hostname:port values as specified in the config
> eventhough Geronimo states otherwise:
> I want ALL services to be bound on  a specific IP (174.132.7.6 in my case)
> Geronimo says it did so (output from geronimo.out) :
> Startup completed in 11.656s seconds
>   Listening on Ports:
>     1050 174.132.7.6 CORBA Naming Service
>     1099 174.132.7.6 RMI Naming
>     1527 174.132.7.6 Derby Connector
>     2001 174.132.7.6 OpenEJB ORB Adapter
>     4201 174.132.7.6 OpenEJB Daemon
>     6882 174.132.7.6 OpenEJB ORB Adapter
>     8080 174.132.7.6 Tomcat Connector HTTP BIO HTTP
>     8099 174.132.7.6 Tomcat Connector AJP AJP
>     8493 174.132.7.6 Tomcat Connector HTTPS BIO HTTPS
>     9999 174.132.7.6 JMX Remoting Connector
>    61613 174.132.7.6 ActiveMQ Transport Connector
>    61616 174.132.7.6 ActiveMQ Transport Connector
>   Started Application Modules:
> BUT a netstat shows otherwise:
> tcp        0      0 :::6882                     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:8099     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:4201     :::*                        LISTEN  
   13353/java
> tcp        0      0 :::1099                     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:8493     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:61613    :::*                        LISTEN  
   13353/java
> tcp        0      0 :::38351                    :::*                        LISTEN  
   13353/java
> tcp        0      0 :::9999                     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:8080     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:61616    :::*                        LISTEN  
   13353/java
> tcp        0      0 :::2001                     :::*                        LISTEN  
   13353/java
> tcp        0      0 ::ffff:174.132.7.6:1527     :::*                        LISTEN  
   13353/java
> tcp        0      0 :::1050                     :::*                        LISTEN  
   13353/java
> Some services are NOT bound to the proper IP, namely
> 6882 174.132.7.6 OpenEJB ORB Adapter
> 2001 174.132.7.6 OpenEJB ORB Adapter
> 1099 174.132.7.6 RMI Naming
> 9999 174.132.7.6 JMX Remoting Connector
> 1050 174.132.7.6 CORBA Naming Service
> and I have no clue as to what is bound on 0.0.0.0:38351 ?!

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


Mime
View raw message