January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6414) Management Console - LDAP authentication fails

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6414?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6414: ---------------------------------- Complexity: (was: High) > Management Console - LDAP authentication fails > ---------------------------------------------- > > Key: AS7-6414 > URL: https://issues.jboss.org/browse/AS7-6414 > Project: Application Server 7 > Issue Type: Bug > Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml > Reporter: narayana b > Assignee: Darran Lofthouse > > 1) security realms >  > <security-realm name="my_Ldap_Realm"> > <authentication> > <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com"> > <username-filter attribute="sAMAccountName"/> >  > </ldap> > </authentication> > </security-realm> >  > 2) outbound connections >  > <outbound-connections> > <ldap name="my_Ldap_Connection" > url="ldap://localhost:10389/" > search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" /> > </outbound-connections> >  > 3) Management console info config >  > <native-interface security-realm="my_Ldap_Realm"> > <socket-binding native="management-native"/> > </native-interface> > <http-interface security-realm="my_Ldap_Realm"> > <socket-binding http="management-http"/> >  > > </http-interface> >  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6415) Access Log directory - XML Parse issue

by narayana b (JIRA)

narayana b created AS7-6415: ------------------------------- Summary: Access Log directory - XML Parse issue Key: AS7-6415 URL: https://issues.jboss.org/browse/AS7-6415 Project: Application Server 7 Issue Type: Bug Environment: Jboss 7.1.1 win xp 32 bit Reporter: narayana b step1)  <paths> <path path="E:/jboss/jboss-as-7.1.1.Final/standalone" name="access-log-dir" /> </paths> step2) created a "access-log" dir under E:/jboss/jboss-as-7.1.1.Final/standalone <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/> <acesss-log pattern="Time Taken: %T %h %l %u %t %r %s %b" resolve-hosts="false" extended="false" prefix="access_log." rotate="true"> <directory path ="access-log" relative-to="access-log-dir" /> </acesss-log> </virtual-server> Parse Error ----------- at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1 at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[351,5] Message: JBAS014789: Unexpected element '{urn:jboss:domain:web:1.1}acesss-log' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.WebSubsystemParser.parseHost(WebSubsystemParser.java:582) at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:329) at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:65) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Fi......... Please let me know is this fixed? ready to release?? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6408) Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned AS7-6408: -------------------------------- Assignee: Tomaz Cerar (was: Richard Achmatowicz) > Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT > --------------------------------------------------------------------------- > > Key: AS7-6408 > URL: https://issues.jboss.org/browse/AS7-6408 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.2.0.Alpha1 > Environment: Git checkout of JBossAS 7.2.0.ALPHA1 from today (28/Jan/2013) > Reporter: Bernd Koecke > Assignee: Tomaz Cerar > Attachments: standalone-ha-jgroups.cli, standalone-jgroups-fragment.xml > > > When I try to configure extension and subsystem JGroups with a CLI script, the attribute "protocols" of the stack=tcp- or stack=udp-node contains the list of configured protocols twice. The result is that the list of protocols is doubled in the standalone.xml. But having a protocol twice in one stack results in an error at next server startup. I will attach the CLI script and the resulting XML fragment. > When I shutdown the server, remove the doubled second part of each protocol list, the server comes up and all is working fine. But I can't configure it only with a CLI script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2293) JavaDoc of @javax.ejb.Local annotation is not correct

by Carlo de Wolf (JIRA)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6411) Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur."

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6411?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6411: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 > Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur." > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-6411 > URL: https://issues.jboss.org/browse/AS7-6411 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 7.1.3.Final (EAP) > Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686 > Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode > JBoss AS 7.1.3.Final > Reporter: Bernard Giroud > Assignee: Darran Lofthouse > Labels: as7, management > Fix For: 7.3.0.Alpha1 > > > First of all, the add-user.sh script has an invalid syntax on line 14 which reads: > {code} > cygwin = true; > {code} > It should read: > {code} > cygwin=true; > {code} > without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done. > Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME. > Finally, issuance of the following command : bin/add-user.sh u p > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107) > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Issuance of the following command : bin/add-user.sh > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Option --silent doesn't make a difference. > An obvious workaround exists though: use with a CMD windows > {noformat} > bin\add-user.bat u p > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1572) TP.sendToAllPhysicalAddresses does not handle singleton TP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1572?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1572: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=905387 > TP.sendToAllPhysicalAddresses does not handle singleton TP > ---------------------------------------------------------- > > Key: JGRP-1572 > URL: https://issues.jboss.org/browse/JGRP-1572 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.6 > Reporter: Radim Vansa > Assignee: Bela Ban > > Method {{TP.sendToAllPhysicalAddresses}} does not handle correctly TP being singleton, on line 1419 it calls directly up_prot.up(...) instead of up(...) which can handle multiple stacks based on this TP. > Result is NPE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1572) TP.sendToAllPhysicalAddresses does not handle singleton TP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1572?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1572: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> made a comment on [bug 905387|https://bugzilla.redhat.com/show_bug.cgi?id=905387] Method TP.sendToAllPhysicalAddresses does not handle correctly TP being singleton, on line 1419 it calls directly up_prot.up(...) instead of up(...) which can handle multiple stacks based on this TP. Result is NPE. Due to this error inserting record into __hotrodTopologyCache occasionally fails. > TP.sendToAllPhysicalAddresses does not handle singleton TP > ---------------------------------------------------------- > > Key: JGRP-1572 > URL: https://issues.jboss.org/browse/JGRP-1572 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.6 > Reporter: Radim Vansa > Assignee: Bela Ban > > Method {{TP.sendToAllPhysicalAddresses}} does not handle correctly TP being singleton, on line 1419 it calls directly up_prot.up(...) instead of up(...) which can handle multiple stacks based on this TP. > Result is NPE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1572) TP.sendToAllPhysicalAddresses does not handle singleton TP

by Radim Vansa (JIRA)

Radim Vansa created JGRP-1572: --------------------------------- Summary: TP.sendToAllPhysicalAddresses does not handle singleton TP Key: JGRP-1572 URL: https://issues.jboss.org/browse/JGRP-1572 Project: JGroups Issue Type: Bug Affects Versions: 3.2.6 Reporter: Radim Vansa Assignee: Bela Ban Method {{TP.sendToAllPhysicalAddresses}} does not handle correctly TP being singleton, on line 1419 it calls directly up_prot.up(...) instead of up(...) which can handle multiple stacks based on this TP. Result is NPE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6365) Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction

by Fredrik Lagerblad (JIRA)

[ https://issues.jboss.org/browse/AS7-6365?page=com.atlassian.jira.plugin.s... ] Fredrik Lagerblad updated AS7-6365: ----------------------------------- Issue Type: Bug (was: Feature Request) > Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction > -------------------------------------------------------------------------------------------------------------- > > Key: AS7-6365 > URL: https://issues.jboss.org/browse/AS7-6365 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.3.Final (EAP) > Reporter: Fredrik Lagerblad > Assignee: Scott Marlow > > The caches in the 'infinispan' subsystem configured with <transaction mode="NONE"/> get stuck in state= CLEARING when you perform a programmatic evict() on them to clear the caches. (Using e.g. em.getEntityManagerFactory().getCache().evictAll() ) > > The problem seem to lie within the class 'org.hibernate.cache.infinispan.impl.BaseRegion, where the 'checkValid' method fails to clear the cache (and set back the state to VALID). The reason it fails is due to that it calls: cacheAdapter.withinTx() , which in turn tries to get the TransactionManager from the cache (which seems to be null for these non-transactional caches), and then NPEs on the tm.begin(); The NPE is caught and logs out "Could not invalidate region: null", and never set the state in VALID. So from thereon the caches are in an Invalid state and is not used anymore by Infinispan, thus leading to much performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6414) Management Console - LDAP authentication fails

by narayana b (JIRA)

narayana b created AS7-6414: ------------------------------- Summary: Management Console - LDAP authentication fails Key: AS7-6414 URL: https://issues.jboss.org/browse/AS7-6414 Project: Application Server 7 Issue Type: Bug Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml Reporter: narayana b 1) security realms  <security-realm name="my_Ldap_Realm"> <authentication> <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com"> <username-filter attribute="sAMAccountName"/>  </ldap> </authentication> </security-realm>  2) outbound connections  <outbound-connections> <ldap name="my_Ldap_Connection" url="ldap://localhost:10389/" search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" /> </outbound-connections>  3) Management console info config  <native-interface security-realm="my_Ldap_Realm"> <socket-binding native="management-native"/> </native-interface> <http-interface security-realm="my_Ldap_Realm"> <socket-binding http="management-http"/>  </http-interface>  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2013