June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4271) failing org.jboss.test.pooled.test.SSLSocketsUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.pooled.test.SSLSocketsUnitTestCase --------------------------------------------------------- Key: JBAS-4271 URL: http://jira.jboss.com/jira/browse/JBAS-4271 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Anil Saldhana Priority: Critical Fix For: JBossAS-4.2.0.GA testClientCertSSLAccess Error SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Supplied Credential did not match existing credential for null java.rmi.AccessException: SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Supplied Credential did not match existing credential for null at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:637) at org.jboss.ejb.Container.invoke(Container.java:981) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.pooled.server.PooledInvoker$MBeanServerAction.invoke(PooledInvoker.java:896) at org.jboss.invocation.pooled.server.PooledInvoker.invoke(PooledInvoker.java:383) at org.jboss.invocation.pooled.server.ServerThread.processInvocation(ServerThread.java:233) at org.jboss.invocation.pooled.server.ServerThread.dorun(ServerThread.java:275) at org.jboss.invocation.pooled.server.ServerThread.run(ServerThread.java:156) Caused by: javax.security.auth.login.FailedLoginException: Supplied Credential did not match existing credential for null at org.jboss.security.auth.spi.BaseCertLoginModule.login(BaseCertLoginModule.java:218) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:579) at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601) at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344) at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:211) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:158) at org.jboss.ejb.plugins.SSLSessionInterceptor.invokeHome(SSLSessionInterceptor.java:53) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132) ... 16 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4462) mod() function not supported in SQL server 2005

by Alexey Loubyansky (JIRA)

mod() function not supported in SQL server 2005 ----------------------------------------------- Key: JBAS-4462 URL: http://jira.jboss.com/jira/browse/JBAS-4462 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.0.5.SP1 , JBossAS-4.2.1.CR1 Looks like the mod() function has been replaced by the % (Modulo) (SSIS) operator in MS SQL Server 2005. It should be possible to customize it with a template. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-522) Reduce some INFO log levels to DEBUG

by Bela Ban (JIRA)

Reduce some INFO log levels to DEBUG ------------------------------------ Key: JGRP-522 URL: http://jira.jboss.com/jira/browse/JGRP-522 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 2007-06-06 11:22:22,849 INFO [org.jgroups.JChannel] JGroups version: 2.4.1 SP-3 -> Ok 2007-06-06 11:22:23,451 INFO [org.jgroups.protocols.FRAG2] frag_size=60000, overhead=200, new frag_size=59800 -> Move to DEBUG 2007-06-06 11:22:23,459 INFO [org.jgroups.protocols.FRAG2] received CONFIG event: {bind_addr=lo2/127.0.0.2} -> Move to DEBUG 2007-06-06 11:22:23,641 INFO [org.jgroups.protocols.UDP] sockets will use interface 127.0.0.2 2007-06-06 11:22:23,645 INFO [org.jgroups.protocols.UDP] socket information: local_addr=127.0.0.2:32826, mcast_addr=230.1.2.7:45577, bind_addr=lo2/127.0.0.2, ttl=2 sock: bound to 127.0.0.2:32826, receive buffer size=131071, send buffer size=131071 mcast_recv_sock: bound to 127.0.0.2:45577, send buffer size=131071, receive buffer size=131071 mcast_send_sock: bound to 127.0.0.2:32827, send buffer size=131071, receive buffer size=131071 -> For UDP, at INFO level we'd need: local address and port which is bound, multicast address and port and ttl, everything else is too verbose -> DEBUG or TRACE 2007-06-06 11:22:23,752 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.2:32826 ------------------------------------------------------- -> This should be removed. Previous info should indicate local address and port -> Same for the rest of channels... 2007-06-06 11:22:31,607 INFO [org.jgroups.JChannel] JGroups version: 2.4.1 SP-3 2007-06-06 11:22:31,612 INFO [org.jgroups.protocols.FRAG2] frag_size=60000, overhead=200, new frag_size=59800 2007-06-06 11:22:31,613 INFO [org.jgroups.protocols.FRAG2] received CONFIG event: {bind_addr=lo2/127.0.0.2} 2007-06-06 11:22:32,227 INFO [org.jgroups.protocols.UDP] sockets will use interface 127.0.0.2 2007-06-06 11:22:32,231 INFO [org.jgroups.protocols.UDP] socket information: local_addr=127.0.0.2:32829, mcast_addr=228.1.2.3:45566, bind_addr=lo2/127.0.0.2, ttl=2 sock: bound to 127.0.0.2:32829, receive buffer size=131071, send buffer size=131071 mcast_recv_sock: bound to 127.0.0.2:45566, send buffer size=131071, receive buffer size=131071 mcast_send_sock: bound to 127.0.0.2:32830, send buffer size=131071, receive buffer size=131071 2007-06-06 11:22:32,232 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.2:32829 ------------------------------------------------------- 2007-06-06 11:22:36,709 INFO [org.jgroups.JChannel] JGroups version: 2.4.1 SP-3 2007-06-06 11:22:36,880 INFO [org.jgroups.protocols.FRAG2] frag_size=60000, overhead=200, new frag_size=59800 2007-06-06 11:22:36,881 INFO [org.jgroups.protocols.FRAG2] received CONFIG event: {bind_addr=lo2/127.0.0.2} 2007-06-06 11:22:36,888 INFO [org.jgroups.protocols.UDP] sockets will use interface 127.0.0.2 2007-06-06 11:22:37,013 INFO [org.jgroups.protocols.UDP] socket information: local_addr=127.0.0.2:32831, mcast_addr=229.1.2.3:45551, bind_addr=lo2/127.0.0.2, ttl=2 sock: bound to 127.0.0.2:32831, receive buffer size=131071, send buffer size=131071 mcast_recv_sock: bound to 127.0.0.2:45551, send buffer size=131071, receive buffer size=131071 mcast_send_sock: bound to 127.0.0.2:32832, send buffer size=131071, receive buffer size=131071 2007-06-06 11:22:37,014 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.2:32831 ------------------------------------------------------- 2007-06-06 11:22:39,925 INFO [org.jgroups.JChannel] JGroups version: 2.4.1 SP-3 2007-06-06 11:22:39,931 INFO [org.jgroups.protocols.FRAG2] frag_size=60000, overhead=200, new frag_size=59800 2007-06-06 11:22:39,931 INFO [org.jgroups.protocols.FRAG2] received CONFIG event: {bind_addr=lo2/127.0.0.2} 2007-06-06 11:22:39,933 INFO [org.jgroups.protocols.UDP] sockets will use interface 127.0.0.2 2007-06-06 11:22:39,945 INFO [org.jgroups.protocols.UDP] socket information: local_addr=127.0.0.2:32833, mcast_addr=230.1.2.3:43333, bind_addr=lo2/127.0.0.2, ttl=2 sock: bound to 127.0.0.2:32833, receive buffer size=131071, send buffer size=131071 mcast_recv_sock: bound to 127.0.0.2:43333, send buffer size=131071, receive buffer size=131071 mcast_send_sock: bound to 127.0.0.2:32834, send buffer size=131071, receive buffer size=131071 2007-06-06 11:22:40,102 INFO [STDOUT] ------------------------------------------------------- GMS: address is 127.0.0.2:32833 ------------------------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-901) BRXML web editor and model to support new nested expressive goodness

by Michael Neale (JIRA)

BRXML web editor and model to support new nested expressive goodness -------------------------------------------------------------------- Key: JBRULES-901 URL: http://jira.jboss.com/jira/browse/JBRULES-901 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-714) Make sure 2.2.0 and 2.0.0 are compatible binary releases

by Tom Elrod (JIRA)

Make sure 2.2.0 and 2.0.0 are compatible binary releases -------------------------------------------------------- Key: JBREM-714 URL: http://jira.jboss.com/jira/browse/JBREM-714 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Critical Fix For: 2.2.0.Beta2 (Bluto) Can use the versioning tests within remoting build to check client and server binary compatibility between 2.2.0 and 2.0.0. For 2.2.0.Beta1 release, where issues with socket, multiplex, and rmi transports for both ways (client to server and server to client). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4466) JBossCacheService does too many cache operations to remove a session

by Brian Stansberry (JIRA)

JBossCacheService does too many cache operations to remove a session -------------------------------------------------------------------- Key: JBAS-4466 URL: http://jira.jboss.com/jira/browse/JBAS-4466 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Does this (intevening comments removed): cacheWrapper_.remove(fqn, realId); cacheWrapper_.remove(fqn); This is silly as the second step makes the first unnecessary. Adds overhead plus we found it caused issues with ClusteredCacheLoader, which wants to do a cluster-wide get call for remove(Fqn, Object) so it can return the old value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-363) Create an assembly for the combined microcontainer distribution.

by Paul Gier (JIRA)

Create an assembly for the combined microcontainer distribution. ---------------------------------------------------------------- Key: JBBUILD-363 URL: http://jira.jboss.com/jira/browse/JBBUILD-363 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Fix For: MavenBuild 2.0 An assembly in zip and tar.gz formats should be available for microcontainer. The initial version of this can be based on the old 1.0.2 microcontainer zip distributions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-329) replacement of java.util. classes create invalid classes

by St?le Pedersen (JIRA)

replacement of java.util. classes create invalid classes -------------------------------------------------------- Key: JBBUILD-329 URL: http://jira.jboss.com/jira/browse/JBBUILD-329 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Affects Versions: JBossRetro-1.0.4.GA Environment: GNU/Linux, 2.6.15. Jdk5.0, Jdk1.4 Reporter: St?le Pedersen This problem was discovered when a test in jbossaop failed when using retro to run the tests in jdk1.4. The case: public class SuperPOJO<T extends java.util.AbstractList> { private T fooObject; public void setFoo(T arg) { fooObject = arg;} public T getFoo() {return fooObject;} } public class SubPOJO extends SuperPOJO<java.util.ArrayList> { private java.util.ArrayList bar; public void setFoo(java.util.ArrayList a) { bar = a;} public java.util.ArrayList getFoo(){ return bar;} } you can find the test under bridgemethods in jbossaop. SubPOJO will after compilation have a method like: public volatile AbstractList getFoo() { return getFoo() }; - note that volatile is what the decompiler names it. more specifically its a bridge method created by the compiler. SubPOJO will have the method: public ArrayList getFoo() { return bar; } after jbossretro have changed java.util.AbstractList to edu.emory...AbstractList, the class will fail when its called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1472) Logging levels should never be set programatically, that's why we have log4j.xml!!!

by Galder Zamarreno (JIRA)

Logging levels should never be set programatically, that's why we have log4j.xml!!! ----------------------------------------------------------------------------------- Key: JBPORTAL-1472 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1472 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.CR2, 2.4.1 SP1, 2.4.1 Final, 2.4 Final Reporter: Galder Zamarreno Assigned To: Julien Viet Priority: Blocker I have spent two days with 3 support customers explaining them how to set TRACE level logs for org.jboss.cache without success. They could never get it to work. Eventually, I have found the culprit: org.jboss.portal.cms.impl.jcr.JCRCMS //set the proper logging level for JBossCache and JGroups Logger cacheLogger = Logger.getLogger("org.jboss.cache"); cacheLogger.setLevel(Level.ERROR); Logger groupsLogger = Logger.getLogger("org.jgroups"); groupsLogger.setLevel(Level.ERROR); This code should be removed immediately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-908) Clean up DRL.g accoding to ANTLR consultancy recommendations

by Edson Tirelli (JIRA)

Clean up DRL.g accoding to ANTLR consultancy recommendations ------------------------------------------------------------ Key: JBRULES-908 URL: http://jira.jboss.com/jira/browse/JBRULES-908 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.MR2 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.0.MR3 Fix DRL.g grammar as per ANTLR consultancy recommendations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
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 June 2007