[JBoss JIRA] (AS7-3153) Failed to start NetworkInterfaceService: java.net.SocketException: Permission denied
by Carlo de Wolf (Created) (JIRA)
Failed to start NetworkInterfaceService: java.net.SocketException: Permission denied
------------------------------------------------------------------------------------
Key: AS7-3153
URL: https://issues.jboss.org/browse/AS7-3153
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.CR1b
Environment: Linux localhost 2.6.36.3 #1 SMP PREEMPT Fri Oct 28 16:35:28 CST 2011 armv7l armv7l armv7l GNU/Linux
java version "1.6.0_23"
OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre11-0ubuntu1.11.10)
JamVM (build 1.6.0-devel, inline-threaded interpreter with stack-caching)
Reporter: Carlo de Wolf
Assignee: Jason Greene
{noformat}
14:12:54,407 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: java.net.SocketException: Permission denied
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:94) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_23]
Caused by: java.net.SocketException: Permission denied
at java.net.NetworkInterface.getAll(Native Method) [:1.6.0_23]
at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:303) [:1.6.0_23]
at org.jboss.as.server.services.net.NetworkInterfaceService.resolveInterface(NetworkInterfaceService.java:135) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.as.server.services.net.NetworkInterfaceService.createBinding(NetworkInterfaceService.java:117) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:92) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
... 5 more
{noformat}
--
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
12 years, 11 months
[JBoss JIRA] (JGRP-1408) Rsp: suspecting a member marks the rsp as 'received'
by Bela Ban (Created) (JIRA)
Rsp: suspecting a member marks the rsp as 'received'
----------------------------------------------------
Key: JGRP-1408
URL: https://issues.jboss.org/browse/JGRP-1408
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.0.2, 3.1
When we broadcast a message to a number of members and wait for the responses, if P is suspected or P leaves the cluster, then we'll call Rsp.setValue(null). The setValue() method sets Rsp.received to true, which is unfortunate as we didn't really receive a response.
This was changed, the new semantics are:
- Every response is initially not received, not suspected, and the value is null
- On reception of a value or exception, we set received to true
- On a suspicion, we set received=false and suspected=true, but do *not* null the value (or exception)
--
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
12 years, 11 months