[JBoss JIRA] (AS7-3607) IPv6: Incorrect address binding - web subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/AS7-3607?page=com.atlassian.jira.plugin.s... ]
Jason Greene commented on AS7-3607:
-----------------------------------
I have confirmed this only happens with native/apr, which we have disabled in 7.1.0.Final
> IPv6: Incorrect address binding - web subsystem
> -----------------------------------------------
>
> Key: AS7-3607
> URL: https://issues.jboss.org/browse/AS7-3607
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Jean-Frederic Clere
> Priority: Critical
> Labels: eap6_prd_req
> Fix For: 7.1.1.Final
>
>
> There is another example of incorrect address binding in IPv6 environment.
> Steps how to reproduce:
> 1. Download, unpack DR12 build somewhere
> 2. Remove -Djava.net.preferIPv4Stack=true, or change it to -Djava.net.preferIPv4Stack=false parameter inside JAVA_OPT in file bin/standalone.conf
> 3. Set some usefull IPv6 address to network interface (in my case network interface is p2p1, so you can use command like "ip addr add 1:0:0:1::10 dev p2p1")
> 3a. Don't forget to configure this IPv6 address as hostname for box (let say, hostname is fedora15-vrt1, so at least /etc/hosts should contain "1:0:0:1::10 fedora15-vrt1")
> 4. Verify if you really have configured wanted eth. interface only aka:
> {code}
> [root@fedora15-vrt1 Documents]# ifconfig
> p2p1 Link encap:Ethernet HWaddr 00:00:00:00:00:01
> inet6 addr: 1:0:0:1::10/128 Scope:Global
> inet6 addr: fe80::200:ff:fe00:1/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:766 (766.0 b)
> [root@fedora15-vrt1 Documents]#
> {code}
> 5. Start EAP6 as usual bin/standalone.sh and wait until it says somethink similas as "[org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 16179ms - Started 158 of 228 services (68 services are passive or on-demand)"
> 6. Check addresses binding via "netstat -lnp|grep java"
> The result it this scenario should be something like mine:
> {code}
> [root@fedora15-vrt1 jboss-as]# netstat -lnp|grep java
> tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9990 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9999 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:4447 :::* LISTEN 4765/java
> [root@fedora15-vrt1 jboss-as]#
> {code}
> As you may see - poor binding is done to 127.0.0.1 IPv4 address, but anyway others are bound to IPv6 address ::ffff:127.0.0.1 although every log message refers to IPv4 address 127.0.0.1.
> The worst is that in case when you disable loopback interface at all (ip link set dev lo down) before starting EAP, the result is the same although IP address 127.0.0.1, nor ::ffff:127.0.0.1 doesn't exist (isn't active) in Linux system.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3607) IPv6: Incorrect address binding - web subsystem
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/AS7-3607?page=com.atlassian.jira.plugin.s... ]
Dimitris Andreadis reassigned AS7-3607:
---------------------------------------
Assignee: Jean-Frederic Clere (was: Remy Maucherat)
> IPv6: Incorrect address binding - web subsystem
> -----------------------------------------------
>
> Key: AS7-3607
> URL: https://issues.jboss.org/browse/AS7-3607
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Jean-Frederic Clere
> Priority: Critical
> Labels: eap6_prd_req
> Fix For: 7.1.1.Final
>
>
> There is another example of incorrect address binding in IPv6 environment.
> Steps how to reproduce:
> 1. Download, unpack DR12 build somewhere
> 2. Remove -Djava.net.preferIPv4Stack=true, or change it to -Djava.net.preferIPv4Stack=false parameter inside JAVA_OPT in file bin/standalone.conf
> 3. Set some usefull IPv6 address to network interface (in my case network interface is p2p1, so you can use command like "ip addr add 1:0:0:1::10 dev p2p1")
> 3a. Don't forget to configure this IPv6 address as hostname for box (let say, hostname is fedora15-vrt1, so at least /etc/hosts should contain "1:0:0:1::10 fedora15-vrt1")
> 4. Verify if you really have configured wanted eth. interface only aka:
> {code}
> [root@fedora15-vrt1 Documents]# ifconfig
> p2p1 Link encap:Ethernet HWaddr 00:00:00:00:00:01
> inet6 addr: 1:0:0:1::10/128 Scope:Global
> inet6 addr: fe80::200:ff:fe00:1/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:766 (766.0 b)
> [root@fedora15-vrt1 Documents]#
> {code}
> 5. Start EAP6 as usual bin/standalone.sh and wait until it says somethink similas as "[org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 16179ms - Started 158 of 228 services (68 services are passive or on-demand)"
> 6. Check addresses binding via "netstat -lnp|grep java"
> The result it this scenario should be something like mine:
> {code}
> [root@fedora15-vrt1 jboss-as]# netstat -lnp|grep java
> tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9990 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9999 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:4447 :::* LISTEN 4765/java
> [root@fedora15-vrt1 jboss-as]#
> {code}
> As you may see - poor binding is done to 127.0.0.1 IPv4 address, but anyway others are bound to IPv6 address ::ffff:127.0.0.1 although every log message refers to IPv4 address 127.0.0.1.
> The worst is that in case when you disable loopback interface at all (ip link set dev lo down) before starting EAP, the result is the same although IP address 127.0.0.1, nor ::ffff:127.0.0.1 doesn't exist (isn't active) in Linux system.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3607) IPv6: Incorrect address binding - web subsystem
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/AS7-3607?page=com.atlassian.jira.plugin.s... ]
Dimitris Andreadis commented on AS7-3607:
-----------------------------------------
Can someone from the JBoss Web team take look please?
> IPv6: Incorrect address binding - web subsystem
> -----------------------------------------------
>
> Key: AS7-3607
> URL: https://issues.jboss.org/browse/AS7-3607
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Remy Maucherat
> Priority: Critical
> Labels: eap6_prd_req
> Fix For: 7.1.1.Final
>
>
> There is another example of incorrect address binding in IPv6 environment.
> Steps how to reproduce:
> 1. Download, unpack DR12 build somewhere
> 2. Remove -Djava.net.preferIPv4Stack=true, or change it to -Djava.net.preferIPv4Stack=false parameter inside JAVA_OPT in file bin/standalone.conf
> 3. Set some usefull IPv6 address to network interface (in my case network interface is p2p1, so you can use command like "ip addr add 1:0:0:1::10 dev p2p1")
> 3a. Don't forget to configure this IPv6 address as hostname for box (let say, hostname is fedora15-vrt1, so at least /etc/hosts should contain "1:0:0:1::10 fedora15-vrt1")
> 4. Verify if you really have configured wanted eth. interface only aka:
> {code}
> [root@fedora15-vrt1 Documents]# ifconfig
> p2p1 Link encap:Ethernet HWaddr 00:00:00:00:00:01
> inet6 addr: 1:0:0:1::10/128 Scope:Global
> inet6 addr: fe80::200:ff:fe00:1/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:766 (766.0 b)
> [root@fedora15-vrt1 Documents]#
> {code}
> 5. Start EAP6 as usual bin/standalone.sh and wait until it says somethink similas as "[org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 16179ms - Started 158 of 228 services (68 services are passive or on-demand)"
> 6. Check addresses binding via "netstat -lnp|grep java"
> The result it this scenario should be something like mine:
> {code}
> [root@fedora15-vrt1 jboss-as]# netstat -lnp|grep java
> tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9990 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:9999 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 4765/java
> tcp 0 0 ::ffff:127.0.0.1:4447 :::* LISTEN 4765/java
> [root@fedora15-vrt1 jboss-as]#
> {code}
> As you may see - poor binding is done to 127.0.0.1 IPv4 address, but anyway others are bound to IPv6 address ::ffff:127.0.0.1 although every log message refers to IPv4 address 127.0.0.1.
> The worst is that in case when you disable loopback interface at all (ip link set dev lo down) before starting EAP, the result is the same although IP address 127.0.0.1, nor ::ffff:127.0.0.1 doesn't exist (isn't active) in Linux system.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3449) IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
by Rajesh Rajasekaran (JIRA)
[ https://issues.jboss.org/browse/AS7-3449?page=com.atlassian.jira.plugin.s... ]
Rajesh Rajasekaran reassigned AS7-3449:
---------------------------------------
Assignee: Pavel Janousek
Pavel, can you try Brian's comment?
> IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
> -----------------------------------------------------------------------------
>
> Key: AS7-3449
> URL: https://issues.jboss.org/browse/AS7-3449
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.CR1b
> Environment: Linux
> Reporter: Pavel Janousek
> Assignee: Pavel Janousek
> Priority: Blocker
>
> I unpacked DR5 build ZIP only, didn't touch configuration and try to run as usual:
> {code}
> cd <bin dir of EAP>
> ./standalone.sh
> {code}
> Got this result:
> {code}
> [root@fedora15-vrt1 bin]# ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/pjanouse/tmp/jboss-eap-6.0.0.Alpha2
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:55:46,040 INFO [org.jboss.modules] JBoss Modules version 1.0.3.GA
> 16:55:47,253 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
> 16:55:47,362 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) starting
> 16:55:48,163 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) stopped in 3ms
> 16:55:48,156 ERROR [org.jboss.as.controller.AbstractControllerService] Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:139) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:168) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:197) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:133) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 1 more
> Caused by: java.lang.RuntimeException: Unable to determine a default name based on the local host name
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:188) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:263) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:82) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 4 more
> Caused by: java.net.UnknownHostException: fedora15-vrt1: fedora15-vrt1
> at java.net.InetAddress.getLocalHost(InetAddress.java:1426) [:1.6.0_22]
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:186) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 10 more
> [root@fedora15-vrt1 bin]#
> {code}
> The root of this issue is that *fedora15-vrt1* can't be translated to IPv4 IP address, but only to IPv6 address:
> {code}
> [root@fedora15-vrt1 bin]# ping fedora15-vrt1
> ping: unknown host fedora15-vrt1
> [root@fedora15-vrt1 bin]# ping6 fedora15-vrt1
> PING fedora15-vrt1(vrt1-ip6) 56 data bytes
> 64 bytes from vrt1-ip6: icmp_seq=1 ttl=64 time=0.067 ms
> 64 bytes from vrt1-ip6: icmp_seq=2 ttl=64 time=0.105 ms
> ^C
> --- fedora15-vrt1 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.067/0.086/0.105/0.019 ms
> [root@fedora15-vrt1 bin]#
> {code}
> because I really config /etc/hosts like:
> {code}
> [root@fedora15-vrt1 bin]# cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> ::1 localhost6.localdomain6 localhost6
> 10.0.2.15 both
> ::ffff:10.0.2.15 both
> 1:0:0:1::10 vrt1-ip6 fedora15-vrt1
> 1:0:0:1::11 vrt2-ip6
> [root@fedora15-vrt1 bin]#
> {code}
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3700) jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-3700?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated AS7-3700:
-------------------------------
Component/s: Test Suite
> jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3700
> URL: https://issues.jboss.org/browse/AS7-3700
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Reporter: Geoffrey De Smet
> Priority: Trivial
>
> The xnio-api is probably the most dangerous one of these 3.
> It ships with xnio-api 3.0.0.Beta2, but some code requires 3.0.0.Beta3.
> {code}
> IncompatibleDependencyOverwrite error for org.jboss.logging:jboss-logging:3.0.0.GA paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.sasl:jboss-sasl:1.0.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-testenricher-msc:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.Beta5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-domain-http-api:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-deployment-repository:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-process-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.resolver:jbosgi-resolver-api:1.0.9
> +-org.jboss.osgi.resolver:jbosgi-resolver-metadata:1.0.9
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.xnio:xnio-api:3.0.0.Beta2 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.xnio:xnio-api:3.0.0.Beta2
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.xnio:xnio-nio:3.0.0.Beta3
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-remoting:7.0.2.Final
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.framework:jbosgi-framework-core:1.0.0.CR8
> +-org.jboss.osgi.vfs:jbosgi-vfs30:1.0.6
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> {code}
> Maybe JBoss modules makes this not as bad as it is with normal maven projects.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3700) jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-3700?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen moved ARQ-740 to AS7-3700:
----------------------------------------
Project: Application Server 7 (was: Arquillian)
Key: AS7-3700 (was: ARQ-740)
Security: (was: Public)
> jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3700
> URL: https://issues.jboss.org/browse/AS7-3700
> Project: Application Server 7
> Issue Type: Bug
> Reporter: Geoffrey De Smet
> Priority: Trivial
>
> The xnio-api is probably the most dangerous one of these 3.
> It ships with xnio-api 3.0.0.Beta2, but some code requires 3.0.0.Beta3.
> {code}
> IncompatibleDependencyOverwrite error for org.jboss.logging:jboss-logging:3.0.0.GA paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.sasl:jboss-sasl:1.0.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-testenricher-msc:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.Beta5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-domain-http-api:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-deployment-repository:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-process-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.resolver:jbosgi-resolver-api:1.0.9
> +-org.jboss.osgi.resolver:jbosgi-resolver-metadata:1.0.9
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.xnio:xnio-api:3.0.0.Beta2 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.xnio:xnio-api:3.0.0.Beta2
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.xnio:xnio-nio:3.0.0.Beta3
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-remoting:7.0.2.Final
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.framework:jbosgi-framework-core:1.0.0.CR8
> +-org.jboss.osgi.vfs:jbosgi-vfs30:1.0.6
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> {code}
> Maybe JBoss modules makes this not as bad as it is with normal maven projects.
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3337) AS7 does not work when it is installed in a path containing space character
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3337:
-------------------------------------
Summary: AS7 does not work when it is installed in a path containing space character
Key: AS7-3337
URL: https://issues.jboss.org/browse/AS7-3337
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
[dpospisi@simkin bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/dpospisi/run times/jboss-as-7.1.0.Final-SNAPSHOT
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
WARNING: No log manager service descriptor found in specified logmodule org.jboss.logmanager:main
WARNING: No mbeanserver service descriptor found in specified mbeanserverbuildermodule org.jboss.as.jmx:main
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:248)
at org.jboss.modules.Main.main(Main.java:313)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more
[dpospisi@simkin bin]$
--
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
14 years, 2 months
[JBoss JIRA] (AS7-2942) when EJB method called from application client with proper authorization call is wrongly denied
by Peter Skopek (Created) (JIRA)
when EJB method called from application client with proper authorization call is wrongly denied
-----------------------------------------------------------------------------------------------
Key: AS7-2942
URL: https://issues.jboss.org/browse/AS7-2942
Project: Application Server 7
Issue Type: Bug
Components: EJB, Security
Affects Versions: 7.1.0.CR1
Reporter: Peter Skopek
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
When calling EJB method from client with authenticated user holding proper authorization, method call is denied.
It is happening for stateless as well as stateful beans.
See server exception:
09:31:58,254 INFO [org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSFSBTestCase] (main) JNDI name=ejb:/singleMethodsAnnOnlySFSB//SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote?stateful
09:31:58,299 ERROR [org.jboss.ejb3.invocation] (pool-8-thread-5) JBAS014134: EJB Invocation failed on component SingleMethodsAnnOnlyCheckSFSB for method public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessOne(java.lang.String): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessOne(java.lang.String) of bean: SingleMethodsAnnOnlyCheckSFSB is not allowed
at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:99) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:57) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:259) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:56) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:177) [jboss-as-ejb3-7.1.0.CR1-SNAPSHOT.jar:]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_27]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_27]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]
--
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
14 years, 2 months