10:11 p.m.
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722336#722336
--------------------------------------------------------------
Is Jboss 7.1.0 Final compatible with IPv 6 ?
I have followed the Admin guide
https://docs.jboss.org/author/display/AS71/Interfaces+and+ports
https://docs.jboss.org/author/display/AS71/Interfaces+and+ports to set up the IPv 6
support.
However I have encountered the following ERROR(s) while using the standalone.bat to start
the JBoss AS.
+11:33:10,511 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0000+
+1: Failed to start service jboss.serverManagement.controller.management.http: or+
+g.jboss.msc.service.StartException in service jboss.serverManagement.controller.+
+management.http: java.net.SocketException: Address family not supported by proto+
+col family: bind+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:199) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)+
+ at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav+
+a:54)+
+ at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ+
+er(DefaultHttpServerProvider.java:38)+
+ at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:14+
+7)+
+ at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen+
+tHttpServer.java:143)+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:164) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]+
+ ... 5 more+
+11:33:10,509 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC0000+
+1: Failed to start service jboss.remoting.server.management: org.jboss.msc.servi+
+ce.StartException in service jboss.remoting.server.management: JBAS017113: Faile+
+d to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:112)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ 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(AbstractStrea+
+mServerService.java:102)+
+ ... 5 more+
+11:33:10,509 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC0000+
+1: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.m+
+sc.service.StartException in service jboss.remoting.server.remoting-connector: J+
+BAS017113: Failed to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:112)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ 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(AbstractStrea+
+mServerService.java:102)+
+ ... 5 more+
I have enabled IPv 6 address with the JVM options under my *standalone.config.bat*
*set "JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=true"*
and I have changed the interfaces under my *standalone.xml* as
+<interfaces>+
+ <interface name="management"> +
+ <inet-address
value="${jboss.bind.address.management:[fe80::ed29:5b4b:37cc:d429]}"/>+
+ </interface>+
+ <interface name="public"> +
+ <inet-address
value="${jboss.bind.address:[fe80::ed29:5b4b:37cc:d429]}"/>+
+ </interface>+
+ </interfaces>+
+ <socket-binding-group name="standard-sockets"
default-interface="public"
port-offset="${jboss.socket.binding.port-offset:0}">+
+ <socket-binding name="http" port="8080"/>+
+ <socket-binding name="https" port="8443"/>+
+ <socket-binding name="management-native"
interface="management"
port="${jboss.management.native.port:9999}"/>+
+ <socket-binding name="management-http"
interface="management"
port="${jboss.management.http.port:9990}"/>+
+ <socket-binding name="management-https"
interface="management"
port="${jboss.management.https.port:9443}"/>+
+ <socket-binding name="osgi-http" interface="management"
port="8090"/>+
+ <socket-binding name="remoting" port="4447"/>+
+ <socket-binding name="txn-recovery-environment"
port="4712"/>+
+ <socket-binding name="txn-status-manager"
port="4713"/>+
+ <outbound-socket-binding name="mail-smtp">+
+ <remote-destination host="localhost" port="25"/>+
+ </outbound-socket-binding>+
+ </socket-binding-group>+
What other configuration I have to make changes to ? Your advice is very much
appreciated. Thanks in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722336#722336]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:48 p.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
Stuart Douglas [https://community.jboss.org/people/swd847] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722341#722341
--------------------------------------------------------------
You should not have the square brackets around the IP address, just the IPv6 address.
With that said there are some IPv6 related bugs in AS7.1 that have been fixed in the
upcoming 7.1.1 release.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722341#722341]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
11:52 p.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722353#722353
--------------------------------------------------------------
Hi Douglas:
Thanks for the advice. I try removing the square brackets, but the problem still
persists. Any idea when the related bugs will be fixed with the upcoming 7.1.1 release ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722353#722353]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:13 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722355#722355
--------------------------------------------------------------
You can try the latest nightly build (which contain these fixes) here
https://community.jboss.org/thread/167590 https://community.jboss.org/thread/167590.
By the way can you post the new config and the exception stacktrace?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722355#722355]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:38 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722369#722369
--------------------------------------------------------------
*standalone.conf.bat*
set "JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=true"
*standalone.xml*
<profile>
<subsystem xmlns="urn:jboss:domain:webservices:1.1">
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>${jboss.bind.address:fe80::ed29:5b4b:37cc:d429}</wsdl-host>
<endpoint-config name="Standard-Endpoint-Config"/>
<endpoint-config name="Recording-Endpoint-Config">
<pre-handler-chain name="recording-handlers"
protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP
##SOAP12_HTTP_MTOM">
<handler name="RecordingHandler"
class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
</pre-handler-chain>
</endpoint-config>
</subsystem>
</profile>
<interfaces>
<interface name="management">
<inet-address
value="${jboss.bind.address.management:fe80::ed29:5b4b:37cc:d429}"/>
</interface>
<interface name="public">
<inet-address
value="${jboss.bind.address.management:fe80::ed29:5b4b:37cc:d429}"/>
</interface>
</interfaces>
*Exception trace*
15:32:05,355 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC0000
1: Failed to start service jboss.serverManagement.controller.management.http: or
g.jboss.msc.service.StartException in service jboss.serverManagement.controller.
management.http: java.net.SocketException: Address family not supported by proto
col family: bind
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe
rvice.java:199) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886) [rt.jar:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) [rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
Caused by: java.net.SocketException: Address family not supported by protocol fa
mily: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
119) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.
jar:1.6.0_21]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav
a:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ
er(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:14
7)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen
tHttpServer.java:143)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe
rvice.java:164) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
... 5 more
15:32:05,402 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC0000
1: Failed to start service jboss.remoting.server.management: org.jboss.msc.servi
ce.StartException in service jboss.remoting.server.management: JBAS017113: Faile
d to start service
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea
mServerService.java:112)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886) [rt.jar:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) [rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
Caused by: java.net.SocketException: Address family not supported by protocol fa
mily: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
119) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.
jar:1.6.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.
jar:1.6.0_21]
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(AbstractStrea
mServerService.java:102)
... 5 more
15:32:05,412 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC0000
1: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.m
sc.service.StartException in service jboss.remoting.server.remoting-connector: J
BAS017113: Failed to start service
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea
mServerService.java:112)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886) [rt.jar:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) [rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
Caused by: java.net.SocketException: Address family not supported by protocol fa
mily: bind
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
119) [rt.jar:1.6.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.
jar:1.6.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.
jar:1.6.0_21]
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(AbstractStrea
mServerService.java:102)
... 5 more
*
*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722369#722369]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:44 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722371#722371
--------------------------------------------------------------
Please try the latest nightly build.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722371#722371]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:03 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722422#722422
--------------------------------------------------------------
I just tried the nightly build.
here is the exception trace, look similar to the 7.1.0 Final build
+18:58:03,219 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0000+
+1: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.m+
+sc.service.StartException in service jboss.remoting.server.remoting-connector: J+
+BAS017113: Failed to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:111)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ 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(AbstractStrea+
+mServerService.java:101)+
+ ... 5 more+
+18:58:03,222 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC0000+
+1: Failed to start service jboss.remoting.server.management: org.jboss.msc.servi+
+ce.StartException in service jboss.remoting.server.management: JBAS017113: Faile+
+d to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:111)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.+
+jar:1.6.0_21]+
+ 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(AbstractStrea+
+mServerService.java:101)+
+ ... 5 more+
+18:58:03,268 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC0000+
+1: Failed to start service jboss.serverManagement.controller.management.http: or+
+g.jboss.msc.service.StartException in service jboss.serverManagement.controller.+
+management.http: java.net.SocketException: Address family not supported by proto+
+col family: bind+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:212) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.java:886) [rt.jar:1.6.0_21]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor+
+.java:908) [rt.jar:1.6.0_21]+
+ at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]+
+Caused by: java.net.SocketException: Address family not supported by protocol fa+
+mily: bind+
+ at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:+
+119) [rt.jar:1.6.0_21]+
+ at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.+
+jar:1.6.0_21]+
+ at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)+
+ at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav+
+a:54)+
+ at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ+
+er(DefaultHttpServerProvider.java:38)+
+ at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:14+
+7)+
+ at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen+
+tHttpServer.java:145)+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:177) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]+
+ ... 5 more+
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722422#722422]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:01 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722438#722438
--------------------------------------------------------------
It looks like a JRE bug on Windows. Which exact version of Windows are you using? Looking
at your stactkrace the JRE version appears to be Sun Java 1.6.0_21. Can you try upgrading
to a latest update of Sun Java 1.6 (although I don't expect it to be fixed in the
latest versions if it isn't in the 21 update). But give it a try. The bug reference is
here http://bugs.sun.com/view_bug.do?bug_id=6230761
http://bugs.sun.com/view_bug.do?bug_id=6230761
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722438#722438]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:48 p.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722690#722690
--------------------------------------------------------------
I try with the latest JDK 1.6 and my Windows specification is Vista Business 32 bit. Are
you saying this JRE bug won't happen in Linux ?
I still hit the same errors:
+10:39:44,338 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC0000+
+1: Failed to start service jboss.remoting.server.management: org.jboss.msc.servi+
+ce.StartException in service jboss.remoting.server.management: JBAS017113: Faile+
+d to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:111)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.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: Address family not supported by protocol fa+
+mily: bind+
+ 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(AbstractStrea+
+mServerService.java:101)+
+ ... 5 more+
+10:39:44,337 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC0000+
+1: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.m+
+sc.service.StartException in service jboss.remoting.server.remoting-connector: J+
+BAS017113: Failed to start service+
+ at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStrea+
+mServerService.java:111)+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.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: Address family not supported by protocol fa+
+mily: bind+
+ 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(AbstractStrea+
+mServerService.java:101)+
+ ... 5 more+
+10:39:44,368 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC0000+
+1: Failed to start service jboss.serverManagement.controller.management.http: or+
+g.jboss.msc.service.StartException in service jboss.serverManagement.controller.+
+management.http: java.net.SocketException: Address family not supported by proto+
+col family: bind+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:212) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se+
+rviceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont+
+rollerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec+
+utor.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: Address family not supported by protocol fa+
+mily: bind+
+ 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 org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)+
+ at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.jav+
+a:54)+
+ at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServ+
+er(DefaultHttpServerProvider.java:38)+
+ at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:14+
+7)+
+ at org.jboss.as.domain.http.server.ManagementHttpServer.create(Managemen+
+tHttpServer.java:145)+
+ at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementSe+
+rvice.java:177) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]+
+ ... 5 more+
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722690#722690]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:15 p.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
Jason Greene [https://community.jboss.org/people/jason.greene] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/722691#722691
--------------------------------------------------------------
fan kam thong wrote:
I try with the latest JDK 1.6 and my Windows specification is Vista Business 32 bit. Are
you saying this JRE bug won't happen in Linux ?
That's correct. JBoss AS, and many other projects that use networking code rely on the
NIO API in the JDK. The problem is that the Sun/Oracle JDK 6 implementation of NIO does
not support IPv6 on Windows. They fixed this finally in JDK7 but have not backported it
since it was tied to NIO2. I recommend running AS7 on JDK 7 on Windows if you need IPv6.
Othwerise consider switching operating systems for your IPv6 applications.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722691#722691]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:24 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723084#723084
--------------------------------------------------------------
I try running JBoss AS 7.1 in Linux RedHat 6, the NIO issue does not happen in Linux
environment.
However, when I was running EJB client in Windows Vista , I encountered this problem:
+Mar 12, 2012 1:14:34 PM org.jboss.ejb.client.EJBClient <clinit>+
+INFO: JBoss EJB Client version 1.0.2.Final+
+Mar 12, 2012 1:14:35 PM org.xnio.Xnio <clinit>+
+INFO: XNIO Version 3.0.3.GA+
+Mar 12, 2012 1:14:35 PM org.xnio.nio.NioXnio <clinit>+
+INFO: XNIO NIO Implementation Version 3.0.3.GA+
+Mar 12, 2012 1:14:35 PM org.jboss.remoting3.EndpointImpl <clinit>+
+INFO: JBoss Remoting version 3.2.2.GA+
+Mar 12, 2012 1:14:35 PM org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector
setupEJBReceivers+
+WARN: Could not register a EJB receiver for connection to
remote://fe80::218:8bff:fe1e:c118:4447+
+java.lang.IllegalArgumentException: destination address may not be null+
+ at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)+
+ at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)+
+ at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)+
+ at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)+
+ at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)+
+ at
org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:113)+
+ at
org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.<init>(ConfigBasedEJBClientContextSelector.java:77)+
+ at
org.jboss.ejb.client.EJBClientContext.<clinit>(EJBClientContext.java:76)+
+ at
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:120)+
+ at
org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)+
+ at $Proxy0.getLogs(Unknown Source)+
+ at com.mytest.ejb.EJBClient.main(EJBClient.java:36)+
+java.lang.IllegalStateException: No EJB receiver available for handling
[appName:,modulename:test-web-service,distinctname:] combination+
+ at
org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:530)+
+ at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)+
+ at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)+
+ at
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)+
+ at
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)+
+ at
org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)+
+ at $Proxy0.getLogs(Unknown Source)+
+ at com.mytest.ejb.EJBClient.main(EJBClient.java:36)+
My *jboss-ejb-client.properties* is set as below:
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
#remote.connection.default.host=fe80--218-8bff-fe1e-c118.ipv6-literal.net
# tested working fine with IPv 4
#remote.connection.default.host=192.168.2.166
remote.connection.default.host=fe80::218:8bff:fe1e:c118
#remote.connection.default.host=[fe80::ed29:5b4b:37cc:d429]
remote.connection.default.port = 4447
My *pom.xml* is as below
+<!-- Import the transaction spec API, we use runtime scope because we aren't using
any direct+
+ reference to the spec API in our client code -->+
+ <dependency>+
+ <groupId>org.jboss.spec.javax.transaction</groupId>+
+ <artifactId>jboss-transaction-api_1.1_spec</artifactId>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <!-- Import the EJB 3.1 API, we use runtime scope because we aren't
using any direct+
+ reference to EJB spec API in our client code -->+
+ <dependency>+
+ <groupId>org.jboss.spec.javax.ejb</groupId>+
+ <artifactId>jboss-ejb-api_3.1_spec</artifactId>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <!-- JBoss EJB client API jar. We use runtime scope because the EJB client API+
+ isn't directly used in this example. We just need it in our runtime classpath
-->+
+ <dependency>+
+ <groupId>org.jboss</groupId>+
+ <artifactId>jboss-ejb-client</artifactId>+
+ <version>1.0.2.Final</version>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <!-- client communications with the server use XNIO -->+
+ <dependency>+
+ <groupId>org.jboss.xnio</groupId>+
+ <artifactId>xnio-api</artifactId>+
+ <version>3.0.3.GA</version>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <dependency>+
+ <groupId>org.jboss.xnio</groupId>+
+ <artifactId>xnio-nio</artifactId>+
+ <version>3.0.3.GA</version>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <!-- The client needs JBoss remoting to access the server -->+
+ <dependency>+
+ <groupId>org.jboss.remoting3</groupId>+
+ <artifactId>jboss-remoting</artifactId>+
+ <version>3.2.2.GA</version>+
+ <scope>runtime</scope>+
+ </dependency>+
+ <!-- Remote EJB accesses can be secured -->+
+ <dependency>+
+ <groupId>org.jboss.sasl</groupId>+
+ <artifactId>jboss-sasl</artifactId>+
+ <version>1.0.0.Final</version>+
+ </dependency>+
+ <!-- data serialization for invoking remote EJBs -->+
+ <dependency>+
+ <groupId>org.jboss.marshalling</groupId>+
+ <artifactId>jboss-marshalling-river</artifactId>+
+ <version>1.3.9.GA</version>+
+ <scope>runtime</scope>+
+ </dependency>+
Do I need the get the latest jboss-ejb-client jar ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723084#723084]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:37 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
Stuart Douglas [https://community.jboss.org/people/swd847] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723085#723085
--------------------------------------------------------------
The latest ejb-client jar should fix the issue
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723085#723085]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:44 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723086#723086
--------------------------------------------------------------
How to I figure out which is the latest ejb-client jar version ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723086#723086]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:17 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723093#723093
--------------------------------------------------------------
JBoss AS 7.1.1.Final has been released on Friday. Just use that and you should be good to
go. Point your client classpath to the JBOSS_HOME/bin/client/jboss-client.jar and it will
have the correct version of the library.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723093#723093]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:19 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723143#723143
--------------------------------------------------------------
I update the JDK version to 7 and replace the latest jboss client jar. Now I face the
following error. Please let me know if you need more info from me.
Mar 12, 2012 7:12:36 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.5.Final
Mar 12, 2012 7:12:36 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
Mar 12, 2012 7:12:36 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
Mar 12, 2012 7:12:36 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
Mar 12, 2012 7:12:41 PM org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector
setupEJBReceivers
WARN: Could not register a EJB receiver for connection to
remote://fe80::ed29:5b4b:37cc:d429:4447
java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)
at
org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:121)
at
org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.<init>(ConfigBasedEJBClientContextSelector.java:78)
at org.jboss.ejb.client.EJBClientContext.<clinit>(EJBClientContext.java:77)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:120)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.getLogs(Unknown Source)
at com.mytest.ejb.EJBClient.main(EJBClient.java:37)
java.lang.IllegalStateException: No EJB receiver available for handling
[appName:,modulename:test-web-service,distinctname:] combination for invocation context
org.jboss.ejb.client.EJBClientInvocationContext@a5ba31
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.getLogs(Unknown Source)
at com.mytest.ejb.EJBClient.main(EJBClient.java:37)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723143#723143]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:26 a.m.
New subject: [JBoss AS 7 Development] - Re: is Jboss 7.1.0 Final compatible with IPv 6 ?
fan kam thong [https://community.jboss.org/people/ktfan] created the discussion
"Re: is Jboss 7.1.0 Final compatible with IPv 6 ?"
To view the discussion, visit: https://community.jboss.org/message/723146#723146
--------------------------------------------------------------
I tried the same source & properties with IPv 4 on Windows Vista, it works fine but
not on IPv 6 on Windows Vista.
here is my jboss-ejb-client.properties
+remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false+
+remote.connections=default+
+remote.connection.default.host=fe80::ed29:5b4b:37cc:d429+
+#remote.connection.default.host=192.168.2.109+
+remote.connection.default.port =4447+
+remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false+
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/723146#723146]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4453
days inactive
4457
days old
jboss-dev-forums@lists.jboss.org
15 comments
4 participants
participants (4)
-
fan kam thong -
jaikiran pai
-
Jason Greene
-
Stuart Douglas