January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3297) NumberFormatException during host-controller startup if the example of host.xml is used

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-3297: ------------------------------------- Summary: NumberFormatException during host-controller startup if the example of host.xml is used Key: AS7-3297 URL: https://issues.jboss.org/browse/AS7-3297 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Wolf-Dieter Fink Assignee: Brian Stansberry If a host-controller should be started and connected do a remote domain-controller the example did not work. <remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}"/> Nevertheless whether the properties are given or not the following exception occour: [Host Controller] Caused by: java.lang.NumberFormatException: For input string: "${jboss.domain.master.port:9999}" [Host Controller] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [:1.6.0_22] [Host Controller] at java.lang.Integer.parseInt(Integer.java:470) [:1.6.0_22] [Host Controller] at java.lang.Integer.valueOf(Integer.java:570) [:1.6.0_22] [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseRemoteDomainController(HostXml.java:756) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseDomainController(HostXml.java:716) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] The check of HostXml.parseRemoteDomainController checks hard whether the port is an Integer value -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] (AS7-3139) add-user.sh script error: ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found

by Hendy Irawan (Created) (JIRA)

add-user.sh script error: ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found -------------------------------------------------------------------------------------------------------- Key: AS7-3139 URL: https://issues.jboss.org/browse/AS7-3139 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1 Environment: Linux Mint 12 (Ubuntu Oneiric 11.10) 64-bit Linux annafi 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux java version "1.7.0_147-icedtea" OpenJDK Runtime Environment (IcedTea7 2.0) (7~b147-2.0-0ubuntu0.11.10.1) OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode) Reporter: Hendy Irawan Assignee: Alexey Loubyansky When I access localhost:9990 it says I need to create a user. But while doing so : ceefour@annafi:~/jboss-as-7.1.0.CR1/bin$ ./add-user.sh org.jboss.modules.ModuleNotFoundException: Module org.jboss.as.domain-add-user:main is not found at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:121) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:245) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:194) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:97) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:176) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:172) at org.jboss.modules.Main.main(Main.java:311) -- 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, 5 months

6
5
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Dustin Kut Moy Cheung (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Dustin Kut Moy Cheung edited comment on AS7-3042 at 1/13/12 10:48 AM: ---------------------------------------------------------------------- Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error] [Tested in latest nightly build of JBoss-AS7] Thanks for your help! was (Author: dcheung): Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error] Thanks for your help! > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Heiko Braun > Priority: Blocker > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Dustin Kut Moy Cheung (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Dustin Kut Moy Cheung commented on AS7-3042: -------------------------------------------- Heiko: was it really fixed? I tried what Pavel described [connect to http://[::1]:8080, then click on Administration Console] and it still redirected me to http://[::1]:9990/console [and I got a "Unable To Connect" error] Thanks for your help! > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Heiko Braun > Priority: Blocker > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3251) Update console to reflect changes to ConfigAdmin

by Thomas Diesler (Created) (JIRA)

Update console to reflect changes to ConfigAdmin ------------------------------------------------ Key: AS7-3251 URL: https://issues.jboss.org/browse/AS7-3251 Project: Application Server 7 Issue Type: Task Components: Console, Domain Management, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.1.0.Final -- 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, 5 months

5
5
0 / 0

[JBoss JIRA] (AS7-3124) Upgrade Infinispan to 5.1.CR2

by Ove Ranheim (Created) (JIRA)

Upgrade Infinispan to 5.1.CR2 ----------------------------- Key: AS7-3124 URL: https://issues.jboss.org/browse/AS7-3124 Project: Application Server 7 Issue Type: Component Upgrade Components: Build System, Clustering Reporter: Ove Ranheim Assignee: Paul Gier Fix For: 7.1.0.CR1 Infinispan 5.1.CR2: http://planet.jboss.org/post/infinispan_5_1_0_cr2_is_out_in_time_for_xmas -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] (AS7-3290) second level cache is not working after upgrading to Hibernate 4.0.1 (NPE in org.hibernate.cache.infinispan.InfinispanRegionFactory.getCache)

by Scott Marlow (JIRA)

Scott Marlow created AS7-3290: --------------------------------- Summary: second level cache is not working after upgrading to Hibernate 4.0.1 (NPE in org.hibernate.cache.infinispan.InfinispanRegionFactory.getCache) Key: AS7-3290 URL: https://issues.jboss.org/browse/AS7-3290 Project: Application Server 7 Issue Type: Sub-task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow to recreate: cd as7/testsuite/integration/basic mvn clean install -Dtest=org.jboss.as.test.integration.jpa.hibernate.SecondLevelCacheTestCase http://pastie.org/3173509 occurs when running the above test case. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2227) @Startup @Singleton (via switchboard) should take into account transitive ENC dependencies before instantiating the bean

by jaikiran pai (JIRA)

@Startup @Singleton (via switchboard) should take into account transitive ENC dependencies before instantiating the bean ------------------------------------------------------------------------------------------------------------------------ Key: EJBTHREE-2227 URL: https://issues.jboss.org/browse/EJBTHREE-2227 Project: EJB 3.0 Issue Type: Bug Components: singleton Affects Versions: depchain-1.0.0-alpha-43 Environment: JBoss AS 6.0 Final Reporter: jaikiran pai Assignee: jaikiran pai Consider the following beans: @Startup @Singleton public class A { @EJB private B slsb1; @PostConstruct public void onConstruct() { slsb1.doSomething(); } } @Stateless public class B { @EJB private C slsb2; } @Stateless public class C { .... } Currently, the @Startup @Singleton is instantiated when the ENC of that bean is fully invokable. However, it only waits for a populated ENC of transitive dependent bean(s). This can lead random failures with lookup. Please see the referenced forum thread for the complete details. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

5
11
0 / 0

[JBoss JIRA] (AS7-3302) CLONE - Attribute local-bind-address in broadcast-groups configuration is ignored and 0.0.0.0 is always used

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3302: ----------------------------------- Summary: CLONE - Attribute local-bind-address in broadcast-groups configuration is ignored and 0.0.0.0 is always used Key: AS7-3302 URL: https://issues.jboss.org/browse/AS7-3302 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final When local-bind-address in broadcast-groups is set in messaging subsystem in stantalone-ha.xml: {code} <broadcast-groups> <broadcast-group name="bg-group-nodeA"> <local-bind-address>192.168.10.1</local-bind-address> <group-address>231.8.8.8</group-address> <group-port>9875</group-port> <broadcast-period>5000</broadcast-period> <connector-ref>netty</connector-ref> </broadcast-group> </broadcast-groups> {code} and server is started then "netstat -lnp | grep java" shows: {code} [jbossqa@station1 test-eap6]$ netstat -lnp | grep java (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 127.0.0.1:5455 0.0.0.0:* LISTEN 21181/java tcp 0 0 127.0.0.1:9999 0.0.0.0:* LISTEN 21181/java tcp 0 0 192.168.10.1:8080 0.0.0.0:* LISTEN 21181/java tcp 0 0 192.168.10.1:4447 0.0.0.0:* LISTEN 21181/java tcp 0 0 127.0.0.1:5445 0.0.0.0:* LISTEN 21181/java tcp 0 0 127.0.0.1:9990 0.0.0.0:* LISTEN 21181/java tcp 0 0 192.168.10.1:3528 0.0.0.0:* LISTEN 21181/java udp 0 0 0.0.0.0:9875 0.0.0.0:* 21181/java udp 0 0 0.0.0.0:40861 0.0.0.0:* 21181/java udp 0 0 224.0.1.105:23364 0.0.0.0:* 21181/java {code} >From this output it looks that hornetq is broadcasting on all interfaces. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-640) Jboss Negotiation fallback to login page if NTLM token is received or the user is not present in active directory.

by Hrishi Salvi (JIRA)

Hrishi Salvi created SECURITY-640: ------------------------------------- Summary: Jboss Negotiation fallback to login page if NTLM token is received or the user is not present in active directory. Key: SECURITY-640 URL: https://issues.jboss.org/browse/SECURITY-640 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Environment: Active Directory Winwos 2003, Client Machine windows XP, Jboss Server Machine Window XP and Jboss 6.1 Reporter: Hrishi Salvi Assignee: Darran Lofthouse We are trying to configure the single sign on using jboss negotiation. We are able to login successfully if the user is present in active directory. But in case if user is not present in active directory users, it throw 401 error page. Instead of 401 we want user to access login form and authenticate user using different login module. In our case we have login page we authenticate user on that page. If we receive user credentials we login the user without asking for password. Now if the user credentials are not received then we want user to open login form present on login page, but before that is throws 401 error. We have configure the login-config.xml, web.xml and jboss-web.xml as per the documentation. Also defined <web-resource-collection> <web-resource-name>Restricted</web-resource-name> <url-pattern>/Request</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> in web.xml Our application is access through Request servlet. -- 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, 5 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012