[jboss-jira] [JBoss JIRA] (WFLY-6611) undertow wrong log data emitted
Tomaz Cerar (JIRA)
issues at jboss.org
Mon May 16 08:17:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Cerar reassigned WFLY-6611:
---------------------------------
Assignee: Tomaz Cerar (was: Stuart Douglas)
> undertow wrong log data emitted
> -------------------------------
>
> Key: WFLY-6611
> URL: https://issues.jboss.org/browse/WFLY-6611
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final
> Environment: Windows JDK8
> Reporter: Darryl Miles
> Assignee: Tomaz Cerar
> Priority: Minor
>
> 20:05:49,621 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.3.15.Final starting
> 20:05:49,627 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.15.Final starting
> ...
> 20:05:50,075 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8122
> ...
> 20:06:10,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP listener default suspending
> 20:06:10,499 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 20:06:10,500 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.15.Final stopping
> This is running an arquallian managed instance.
> Notice on shutdown it emits port 8080 when there is nothing bound on that, it really is on port 8122 as shown in "netstat -p tcp -a -n | grep LISTEN" output.
> So I guess there is a bug somewhere in the data it is using.
> I am using -Djboss.socket.binding.port-offset=42 with a stock config for standalone-full.xml
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list