Petals BC SOAP

0.0.0.0, the default host, crashes the component under some OS

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 4.0.3
  • Fix Version/s: 4.0.3
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    On some Linux OS (RHEL 5, CentOS, Fedora, Fuse,...), the default os '0.0.0.0' isn't allowed. So you've got a warning at the installation:

    [Petals.Container.Components.petals-bc-soap]-WARNING 2010-09-23 18:40:22,567 /0.0.0.0 is not a valid local address, using the wildcard one
    WARNING 2010-09-23 18:40:22,567 [Petals.Container.Components.petals-bc-soap]
    /0.0.0.0 is not a valid local address, using the wildcard one

    Further, at each connection, you will have a "Connection refused". Even you configure your network to accept a 'Broad Cast Binding', then the axis modules (rampart or wsaction for examples) chose only one IP to bind on (why?). So if you've got many IP's (like all the classic servers on production, with differents eth IP to invoke a service, to administrate or supervise), you've got some function not bind on some IP (a fun random way of life )

    Only 'localhost' is a good host, recognized by all the OS's, and with a great security approach (you work locally by default, and open only on your chosen IP on production).

    Show
    On some Linux OS (RHEL 5, CentOS, Fedora, Fuse,...), the default os '0.0.0.0' isn't allowed. So you've got a warning at the installation: [Petals.Container.Components.petals-bc-soap]-WARNING 2010-09-23 18:40:22,567 /0.0.0.0 is not a valid local address, using the wildcard one WARNING 2010-09-23 18:40:22,567 [Petals.Container.Components.petals-bc-soap] /0.0.0.0 is not a valid local address, using the wildcard one Further, at each connection, you will have a "Connection refused". Even you configure your network to accept a 'Broad Cast Binding', then the axis modules (rampart or wsaction for examples) chose only one IP to bind on (why?). So if you've got many IP's (like all the classic servers on production, with differents eth IP to invoke a service, to administrate or supervise), you've got some function not bind on some IP (a fun random way of life ) Only 'localhost' is a good host, recognized by all the OS's, and with a great security approach (you work locally by default, and open only on your chosen IP on production).
  • Environment:
    RHEL 5, jdk 1.6, platform 3.1.x

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
5d 22h 49m
1
noddoux
Wed, 29 Sep 2010 - 17:44:48 +0200
Open Open In Progress In Progress
1d 3m
1
noddoux
Thu, 30 Sep 2010 - 17:48:32 +0200
In Progress In Progress Resolved Resolved
9s
1
noddoux
Thu, 30 Sep 2010 - 17:48:41 +0200

People

Dates

  • Created:
    Thu, 23 Sep 2010 - 18:54:51 +0200
    Updated:
    Thu, 30 Sep 2010 - 17:48:41 +0200
    Resolved:
    Thu, 30 Sep 2010 - 17:48:41 +0200