January 2012 - jboss-jira - Jboss List Archives

[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

14 years, 3 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

14 years, 3 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

14 years, 3 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

14 years, 3 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

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] (AS7-3226) ListEditor requires confirmation dialogue

by Heiko Braun (Created) (JIRA)

ListEditor requires confirmation dialogue ----------------------------------------- Key: AS7-3226 URL: https://issues.jboss.org/browse/AS7-3226 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final ListEditor doesn't request confirmation before removing items (See "Root Logger>Handler>Remove -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3052) ComboBox is flaky

by Heiko Braun (Created) (JIRA)

ComboBox is flaky ----------------- Key: AS7-3052 URL: https://issues.jboss.org/browse/AS7-3052 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final the previously selected value retains when a new value is set. it should be cleared instead -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3053) NumberBox is flaky

by Heiko Braun (Created) (JIRA)

NumberBox is flaky ------------------ Key: AS7-3053 URL: https://issues.jboss.org/browse/AS7-3053 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final for some reason the modification flag has been changed even if the value is not updated. edit datasources to see an example -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3252) Error configuring a resource adapter through the console

by Heiko Braun (Created) (JIRA)

Error configuring a resource adapter through the console --------------------------------------------------------- Key: AS7-3252 URL: https://issues.jboss.org/browse/AS7-3252 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final Attachments: DeploymentError.png Deployment was successful and I am able to use it. Problem I reported was about configuring the adapter through Admin UI which was working with "Tesla" (though edits didn't work there either) and stopped working when we upgraded to "Flux Capacitor". There are UI changes in the Flux Capacitor and I suspect there are bugs. I have attached the screen shot of the error I am encountering when I try to add a resource adapter using admin UI. -- 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, 3 months

4
3
0 / 0

[JBoss JIRA] (AS7-3205) Integrate the remoting-jmx project with the JMX subsystem

by Darran Lofthouse (Created) (JIRA)

Integrate the remoting-jmx project with the JMX subsystem --------------------------------------------------------- Key: AS7-3205 URL: https://issues.jboss.org/browse/AS7-3205 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Stuart Douglas Priority: Blocker Fix For: 7.1.0.Final Integrate the remoting-jmx project with the JMX subsystem so that JMX is accessible Remotely using Remoting through the management connection. -- 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, 3 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012