1:45 a.m.
Hi,
I was playing with the plug computer today that Jason setup and noticed that he configured
it to only bind to one port, i.e.
<interface name="default">
<inet-address value="192.168.3.1"/>
</interface>
in an attempt to fix that quickly I tried to add an extra inet-address:
<interface name="default">
<inet-address value="192.168.3.1"/>
<inet-address value="192.168.2.10"/>
</interface>
When I booted as7 beta4-snapshot up it seem to work fine except it didn't ;)
I found the following IMO confusing message:
23:26:45,856 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service
jboss.network.default: org.jboss.msc.servic
e.StartException in service jboss.network.default: failed to resolve interface default
at
org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:106)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_18]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]
Didn't see any parsing errors/messages that would lead me to the apparent problem in
standalone.xml.
Is this the expected/wanted behavior ?
/max
http://about.me/maxandersen
4:27 a.m.
On 05/10/2011 08:45 AM, Max Rydahl Andersen wrote:
in an attempt to fix that quickly I tried to add an extra
inet-address:
<interface name="default">
<inet-address value="192.168.3.1"/>
<inet-address value="192.168.2.10"/>
</interface>
This is valid from an xml standpoint - however it tries to match all
criteria, however you can try something like this:
<interface name="default">
<any>
<inet-address value="192.168.3.1"/>
<inet-address value="192.168.2.10"/>
</any>
</interface>
4:54 a.m.
Note, I fixed it by just using the any-address.
But fixing the xml was not the question here.
My question was about the xml containing an error ( at least XSD validation is broken,
right?)
is it expected that no error about this is shown and its just failing
with a "cannot resolve network interface default" error ?
/max
On May 10, 2011, at 11:27, Emanuel Muckenhuber wrote:
On 05/10/2011 08:45 AM, Max Rydahl Andersen wrote:
> in an attempt to fix that quickly I tried to add an extra inet-address:
>
> <interface name="default">
> <inet-address value="192.168.3.1"/>
> <inet-address value="192.168.2.10"/>
> </interface>
This is valid from an xml standpoint - however it tries to match all
criteria, however you can try something like this:
<interface name="default">
<any>
<inet-address value="192.168.3.1"/>
<inet-address value="192.168.2.10"/>
</any>
</interface>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
6:23 a.m.
On 05/10/2011 11:54 AM, Max Rydahl Andersen wrote:
Note, I fixed it by just using the any-address.
But fixing the xml was not the question here.
My question was about the xml containing an error ( at least XSD validation is broken,
right?)
is it expected that no error about this is shown and its just failing
with a "cannot resolve network interface default" error ?
In general resolving a network interface can fail. But yeah, a clearer
error message and some additional checks while parsing won't hurt.
On May 10, 2011, at 11:27, Emanuel Muckenhuber wrote:
> On 05/10/2011 08:45 AM, Max Rydahl Andersen wrote:
>> in an attempt to fix that quickly I tried to add an extra inet-address:
>>
>> <interface name="default">
>> <inet-address value="192.168.3.1"/>
>> <inet-address value="192.168.2.10"/>
>> </interface>
>
> This is valid from an xml standpoint - however it tries to match all
> criteria, however you can try something like this:
>
> <interface name="default">
> <any>
> <inet-address value="192.168.3.1"/>
> <inet-address value="192.168.2.10"/>
> </any>
> </interface>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
5032
days inactive
5032
days old
3 comments
2 participants
participants (2)
-
Emanuel Muckenhuber -
Max Rydahl Andersen