[GLASSFISH-20251] Module "javax.enterprise.system.core" reports invalid hostname & invalid port format in the server log Created: 09/Apr/13  Updated: 20/Dec/16  Resolved: 22/May/13

Status: Closed
Project: glassfish
Component/s: grizzly-kernel
Affects Version/s: 4.0_dev
Fix Version/s: 4.1

Type: Bug Priority: Minor
Reporter: Mohamed Taman Assignee: Ryan Lubke
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 SP1 & Mac OS X 10.8.3
Glassfish 4 b83


Tags: fishcat, logging

 Description   

While starting up the server the javax.enterprise.system.core module reports invalid hostname as the following /0.0.0.0 alongside port number formated as currency 8,080

producing the following in the log:

[2013-04-10T01:03:19.356+0200] [glassfish 4.0] [INFO] [] [javax.enterprise.system.core] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1365548599356] [levelValue: 800] [[
  Grizzly Framework 2.3 started in: 1ms - bound to [/0.0.0.0:7,676]]]

[2013-04-10T01:05:43.014+0200] [glassfish 4.0] [INFO] [] [javax.enterprise.system.core] [tid: _ThreadID=106 _ThreadName=pool-23-thread-1] [timeMillis: 1365548743014] [levelValue: 800] [[
  Grizzly Framework 2.3 started in: 3ms - bound to [/0.0.0.0:8,080]]]

[2013-04-10T01:05:43.132+0200] [glassfish 4.0] [INFO] [] [javax.enterprise.system.core] [tid: _ThreadID=106 _ThreadName=pool-23-thread-1] [timeMillis: 1365548743132] [levelValue: 800] [[
  Grizzly Framework 2.3 started in: 2ms - bound to [/0.0.0.0:8,181]]]


 Comments   
Comment by shreedhar_ganapathy [ 16/Apr/13 ]

The port number appears in currency format.
This could be fixed in the next release.
Assigning to Tom for evaluation and tagging.

Comment by Tom Mueller [ 16/Apr/13 ]

The host name "0.0.0.0" is correct in that this port is being bound to all interfaces. Keeping this bug open for fixing the formatting of the port number.

This should be fixed in the next release.

Comment by Mohamed Taman [ 16/Apr/13 ]

Hi Tom,

Instead http-listener-2 on host/port 0.0.0.0:8181, I expect to show something like one of the following:

http-listener-2 on host/port 127.0.0.1:8181
http-listener-2 on host/port localhost:8181
http-listener-2 on host/port [current machine IP]:8181

As 0.0.0.0 is an invalid IP address for communication,

Computers normally show an address of 0.0.0.0 when they are not connected to a TCP/IP network. Having this address, a computer cannot be reached or communicate with any other devices over IP.

TCP/IP software applications also use 0.0.0.0 as a programming technique to monitor network traffic from any valid IP address. While connected computers do not use this address, messages carried over IP sometimes include 0.0.0.0 inside the header when the source of the message is unknown.

And as I understand this is the network address listener for communication to the server via HTTP, HTTPS and admin console ports.

Comment by Ryan Lubke [ 15/May/13 ]

Instead http-listener-2 on host/port 0.0.0.0:8181, I expect to show something like one of the following:

http-listener-2 on host/port 127.0.0.1:8181
http-listener-2 on host/port localhost:8181
http-listener-2 on host/port [current machine IP]:8181

But that's just it - it's not bound to that specific address unless it's explicitly configured to do so. If it's not explicitly configured (the address attribute on the network-listener element) to do so, then it binds to all addresses on the host.

I don't see the problem here.

Generated at Mon Apr 24 05:02:10 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.