[JBoss JIRA] (JGRP-1500) ThreadLocal leak in FlowControl
by Elliot Lovy (JIRA)
Elliot Lovy created JGRP-1500:
---------------------------------
Summary: ThreadLocal leak in FlowControl
Key: JGRP-1500
URL: https://issues.jboss.org/browse/JGRP-1500
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.3
Environment: Tomcat
Reporter: Elliot Lovy
Assignee: Bela Ban
org.jgroups.protocols.FlowControl has a thread local leak.
Tomcat's memory management shows:
SEVERE: The web application [/app] created a ThreadLocal with key of type [null] (value [org.jgroups.protocols.FlowControl$1@79c1187f]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
The fix seems straightforward to me, just replace the two instances of:
ignore_thread.set(false);
with
ignore_thread.remove();
I have verified this does indeed prevent the leak.
Since false is the default value the thread local would get created with, then setting it to false is equivalent to removing it, with the added benefit of actually removing the ThreadLocal from the application server's thread.
So it only exists while it is set to true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5224) [JBoss 7.1.0.Final] High CPU usage for single-core CPU VMWare virtual machine running Redhat 6 OS
by Claudiu Muresan (JIRA)
Claudiu Muresan created AS7-5224:
------------------------------------
Summary: [JBoss 7.1.0.Final] High CPU usage for single-core CPU VMWare virtual machine running Redhat 6 OS
Key: AS7-5224
URL: https://issues.jboss.org/browse/AS7-5224
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Final
Environment: -bash-4.1$ cat /proc/version
Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)x86-008.build.bos.redhat.com) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Wed Jun 13 18:24:36 EDT 2012
-bash-4.1$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
stepping : 2
cpu MHz : 2666.761
cache size : 12288 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc up arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat epb dts
bogomips : 5333.52
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
-bash-4.1$ cat /proc/meminfo
MemTotal: 3925212 kB
MemFree: 328048 kB
Buffers: 21276 kB
Cached: 3268128 kB
SwapCached: 180 kB
Active: 1832808 kB
Inactive: 1475292 kB
Active(anon): 3104 kB
Inactive(anon): 16008 kB
Active(file): 1829704 kB
Inactive(file): 1459284 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 8388600 kB
SwapFree: 8387940 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 18624 kB
Mapped: 12656 kB
Shmem: 416 kB
Slab: 220480 kB
SReclaimable: 196296 kB
SUnreclaim: 24184 kB
KernelStack: 792 kB
PageTables: 6980 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 10351204 kB
Committed_AS: 102640 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 283176 kB
VmallocChunk: 34359452028 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 10240 kB
DirectMap2M: 4184064 kB
Reporter: Claudiu Muresan
Assignee: Jason Greene
When starting JBoss server in standalone configuration we have 100% CPU usage.
There are no deployments.
Please view attached items: thread dump, standalone.conf, standalone.xml.
The JVM version is -bash-4.1$ ./java -version
java version "1.6.0_27"
Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
.
Tried also with the latest JVM version (6u33) => high CPU usage.
Tried also with 7.1.1 Final and same configuration(standalone.conf/standalone.xml) => high CPU usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4859) CLONE - Default value of id-cache-size attribute is potencially dangerous when very small messages are used
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-4859?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil resolved AS7-4859.
------------------------------
Fix Version/s: 7.2.0.Alpha1
Resolution: Done
since HornetQ 2.2.19, default value for id-cache-size has been increased to 20000
> CLONE - Default value of id-cache-size attribute is potencially dangerous when very small messages are used
> -----------------------------------------------------------------------------------------------------------
>
> Key: AS7-4859
> URL: https://issues.jboss.org/browse/AS7-4859
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Hi,
> I hit an issue with HornetQ core bridges. I tried test scenario with 4 nodes where:
> 1) there are two clusters A and B (each contains two nodes)
> 2) there is hornetq core bridge configured from cluster A to cluster B (A1 -> B1, A2 -> B2)
> During sending messages (30KB ByteMessages) to A1 and reading them from B2, node A2 was killed and started a few times. In the end there were duplicated messages. Problem was in low value of id-cache-size attribute which is 2000 by default and confirmation-window-size which is for bridges (1024 * 1024) bytes.
> Can be default value of id-cache-size increased so we can avoid this situation? This is potentially dangerous and hard for admins to realize before the problem occurs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5360) CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5360?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry reassigned AS7-5360:
-------------------------------------
Assignee: Brian Stansberry
> CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5360
> URL: https://issues.jboss.org/browse/AS7-5360
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Pavel Janousek
> Assignee: Brian Stansberry
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
> {code}
> <server xmlns="urn:jboss:domain:1.3">
> {code}
> The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
> The very common Linux system has implemented and enabled dualstack in these days. If we instruct EAP instance to bind to +any+ IPv6 address via {code}<interface name="public">
> <any-ipv6-address />
> </interface>{code}
> The real result is mess messages to output log:{code}
> 08:17:55,779 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Error initializing endpoint: java.net.SocketException: Protocol family unavailable
> at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_30]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_30]
> at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:56) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:978) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> 08:17:55,828 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: LifecycleException: Protocol handler initialization failed: java.net.SocketException: Protocol family unavailable
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> 08:17:55,999 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
> 08:17:56,294 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.3.GA-redhat-1
> 08:17:56,294 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 08:17:56,904 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/users-tmp/pjanouse/jboss-eap-6.0/standalone/deployments
> 08:17:56,918 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
> 08:17:56,953 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:111)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: java.net.SocketException: Protocol family unavailable
> at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_30]
> at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
> at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
> at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
> ... 5 more
> 08:17:57,611 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> {code}
> The valid result message could be only - there isn't available any IPv6 address when IPv6 is disabled. Or there isn't a such IP address.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5360) CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5360?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-9690 to AS7-5360:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5360 (was: JBPAPP-9690)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0 ER 6_Beta2)
Component/s: Domain Management
(was: Server boot)
(was: IPv6 support)
Security: (was: JBoss Internal)
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5360
> URL: https://issues.jboss.org/browse/AS7-5360
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Pavel Janousek
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
> {code}
> <server xmlns="urn:jboss:domain:1.3">
> {code}
> The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
> The very common Linux system has implemented and enabled dualstack in these days. If we instruct EAP instance to bind to +any+ IPv6 address via {code}<interface name="public">
> <any-ipv6-address />
> </interface>{code}
> The real result is mess messages to output log:{code}
> 08:17:55,779 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Error initializing endpoint: java.net.SocketException: Protocol family unavailable
> at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_30]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_30]
> at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:56) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:978) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> 08:17:55,828 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: LifecycleException: Protocol handler initialization failed: java.net.SocketException: Protocol family unavailable
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> 08:17:55,999 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
> 08:17:56,294 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.3.GA-redhat-1
> 08:17:56,294 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 08:17:56,904 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/users-tmp/pjanouse/jboss-eap-6.0/standalone/deployments
> 08:17:56,918 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
> 08:17:56,953 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:111)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: java.net.SocketException: Protocol family unavailable
> at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_30]
> at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
> at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
> at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
> ... 5 more
> 08:17:57,611 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> {code}
> The valid result message could be only - there isn't available any IPv6 address when IPv6 is disabled. Or there isn't a such IP address.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5359) CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5359?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-5359:
----------------------------------
Fix Version/s: (was: 7.1.3.Final (EAP))
Description:
The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
{code}
<server xmlns="urn:jboss:domain:1.3">
{code}
The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
The very common Linux system has implemented and enabled dualstack in these days. If we instruct AS instance to bind to +any+ IPv4 address via {code}<interface name="public">
<any-ipv4-address />
</interface>{code}
The real result is to bind running AS instance to +any+ IP address, not only in IPv4 address space but in IPv6 too!
With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only.
was:
The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
{code}
<server xmlns="urn:jboss:domain:1.3">
{code}
The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
The very common Linux system has implemented and enabled dualstack in these days. If we instruct EAP instance to bind to +any+ IPv4 address via {code}<interface name="public">
<any-ipv4-address />
</interface>{code}
The real result is to bind running EAP6 instance to +any+ IP address, not only in IPv4 address space but in IPv6 too!
With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only.
Assignee: Brian Stansberry
> CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5359
> URL: https://issues.jboss.org/browse/AS7-5359
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Pavel Janousek
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
> {code}
> <server xmlns="urn:jboss:domain:1.3">
> {code}
> The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
> The very common Linux system has implemented and enabled dualstack in these days. If we instruct AS instance to bind to +any+ IPv4 address via {code}<interface name="public">
> <any-ipv4-address />
> </interface>{code}
> The real result is to bind running AS instance to +any+ IP address, not only in IPv4 address space but in IPv6 too!
> With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months