January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1267) Rever JBCACHE-1266 fix

by Brian Stansberry (JIRA)

Rever JBCACHE-1266 fix ---------------------- Key: JBCACHE-1267 URL: http://jira.jboss.com/jira/browse/JBCACHE-1267 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor The fix for JBCACHE-1266 is a workaround that should be reverted when JBCACHE-1265 is fixed. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1266) Startup errors due to replicated addChild calls

by Brian Stansberry (JIRA)

Startup errors due to replicated addChild calls ----------------------------------------------- Key: JBCACHE-1266 URL: http://jira.jboss.com/jira/browse/JBCACHE-1266 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Buddy Replication Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.1.0.CR3 JBCACHE-1265 is causing problems as a local-only node addition is getting replicated: First, in buddy group formation, 2008-01-14 16:59:35,104 DEBUG [org.jboss.cache.CacheImpl.DefaultPartition-SFSBCache.127_0_0_1:33296] Recieved exception'org.jboss.cache.CacheException: Cannot make a backup Fqn from a backup Fqn! Attempting to create a backup of /_BUDDY_BACKUP_/127.0.0.1_33296' from 192.168.1.145:33302 2008-01-14 16:59:35,104 ERROR [org.jboss.cache.buddyreplication.BuddyManager] Unable to communicate with Buddy for some reason org.jboss.cache.CacheException: Cannot make a backup Fqn from a backup Fqn! Attempting to create a backup of /_BUDDY_BACKUP_/127.0.0.1_33296 at org.jboss.cache.buddyreplication.BuddyManager.getBackupFqn(BuddyManager.java:627) at org.jboss.cache.buddyreplication.BuddyManager.getBackupFqn(BuddyManager.java:1042) at org.jboss.cache.buddyreplication.BuddyManager.handleArgs(BuddyManager.java:1029) at org.jboss.cache.buddyreplication.BuddyManager.transformFqns(BuddyManager.java:691) at org.jboss.cache.buddyreplication.BuddyManager.transformFqns(BuddyManager.java:683) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:104) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:80) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:75) at org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudMethod(ReplicationInterceptor.java:219) at org.jboss.cache.interceptors.ReplicationInterceptor.handlePutDataMethod(ReplicationInterceptor.java:119) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:62) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:452) at org.jboss.cache.interceptors.TxInterceptor.handlePutDataMethod(TxInterceptor.java:275) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.CacheMgmtInterceptor.handlePutData(CacheMgmtInterceptor.java:112) at org.jboss.cache.interceptors.CacheMgmtInterceptor.handlePutDataMethod(CacheMgmtInterceptor.java:99) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73) at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123) at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64) at org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:474) at org.jboss.cache.invocation.NodeInvocationDelegate.addChild(NodeInvocationDelegate.java:279) at org.jboss.cache.buddyreplication.BuddyManager.handleAssignToBuddyGroup(BuddyManager.java:541) at org.jboss.cache.invocation.RemoteCacheInvocationDelegate.assignToBuddyGroup(RemoteCacheInvocationDelegate.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330) at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:746) at org.jgroups.JChannel.up(JChannel.java:1151) ..... Next, in region activation: 2008-01-14 17:25:50,158 ERROR [org.jboss.cache.RegionManager] failed to activate /JSESSION/localhost/http-field-pass org.jboss.cache.CacheException: Cannot make a backup Fqn from a backup Fqn! Attempting to create a backup of /_BUDDY_BACKUP_/192.168.1.145_33313/JSESSION/localhost/http-field-pass at org.jboss.cache.buddyreplication.BuddyManager.getBackupFqn(BuddyManager.java:627) at org.jboss.cache.buddyreplication.BuddyManager.getBackupFqn(BuddyManager.java:1042) at org.jboss.cache.buddyreplication.BuddyManager.handleArgs(BuddyManager.java:1029) at org.jboss.cache.buddyreplication.BuddyManager.transformFqns(BuddyManager.java:691) at org.jboss.cache.buddyreplication.BuddyManager.transformFqns(BuddyManager.java:683) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:104) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:80) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:75) at org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudMethod(ReplicationInterceptor.java:213) at org.jboss.cache.interceptors.ReplicationInterceptor.handlePutDataMethod(ReplicationInterceptor.java:119) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:62) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:452) at org.jboss.cache.interceptors.TxInterceptor.handlePutDataMethod(TxInterceptor.java:275) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.CacheMgmtInterceptor.handlePutData(CacheMgmtInterceptor.java:112) at org.jboss.cache.interceptors.CacheMgmtInterceptor.handlePutDataMethod(CacheMgmtInterceptor.java:99) at org.jboss.cache.interceptors.MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:72) at org.jboss.cache.interceptors.Interceptor.nextInterceptor(Interceptor.java:111) at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73) at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123) at org.jboss.cache.invocation.AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64) at org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:474) at org.jboss.cache.invocation.NodeInvocationDelegate.addChild(NodeInvocationDelegate.java:279) at org.jboss.cache.RegionManager.activateRegion(RegionManager.java:436) at org.jboss.cache.RegionManager.activate(RegionManager.java:325) at org.jboss.cache.RegionManager.activate(RegionManager.java:288) at org.jboss.cache.RegionImpl.activate(RegionImpl.java:82) at org.jboss.web.tomcat.service.session.JBossCacheService.start(JBossCacheService.java:218) ...... I'm raising this as a separate issue to ensure we find workarounds if JBCACHE-1265 can't be solved for CR3. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-109) AddRole(Role) method in RoleGroup

by Anil Saldhana (JIRA)

AddRole(Role) method in RoleGroup --------------------------------- Key: SECURITY-109 URL: http://jira.jboss.com/jira/browse/SECURITY-109 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Identity Affects Versions: 2.0.2-BETA3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Minor Fix For: 2.0.2-BETA4 Convenience method addRole(Role theRole) needs to be added to RoleGroup. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-110) DeploymentRoleMappingProvider is not mapping when there is no principal passed

by Anil Saldhana (JIRA)

DeploymentRoleMappingProvider is not mapping when there is no principal passed ------------------------------------------------------------------------------ Key: SECURITY-110 URL: http://jira.jboss.com/jira/browse/SECURITY-110 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA4 If an explicit principal is not passed in the context map, but a set of principals are passed from the subject, then the mapping provider should use the principals set. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-445) Change app server build to use the build directory for assembly instead of locating the build in the parent.

by Paul Gier (JIRA)

Change app server build to use the build directory for assembly instead of locating the build in the parent. ------------------------------------------------------------------------------------------------------------ Key: JBBUILD-445 URL: http://jira.jboss.com/jira/browse/JBBUILD-445 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - App Server I'd like to change the location of the parent pom in the app server build. So that the parent directory is both the aggregate project and the parent pom. The build subdirectory will then be the location for the combined distribution files. This is similar to the way that maven structures it's own build, and I think this might be a bit more intuitive. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4725) Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01)

by Dimitris Andreadis (JIRA)

Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01) ------------------------------------------------ Key: JBAS-4725 URL: http://jira.jboss.com/jira/browse/JBAS-4725 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Reporter: Dimitris Andreadis Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.CR1 An issue to track the hibernate upgrade needed by JBoss Cache. Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0 (JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and include it in the hibernate-int module. I'm currently working with Steve on a *much* improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have AS 5 use that." -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1387) Drools doesn't build with fresh maven2 installation and no repository

by Geoffrey De Smet (JIRA)

Drools doesn't build with fresh maven2 installation and no repository --------------------------------------------------------------------- Key: JBRULES-1387 URL: http://jira.jboss.com/jira/browse/JBRULES-1387 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.3 Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Fix For: 4.0.4 Some wierd exception is thrown and it's being caused when it's trying to get the pom of this: <extensions> <extension> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-webdav</artifactId> <version>1.0-beta-2</version> </extension> </extensions> -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JASSIST-34) Throw a more descriptive exception when a class file does not start with 0xCAFEBABE

by Josh Devins (JIRA)

Throw a more descriptive exception when a class file does not start with 0xCAFEBABE ----------------------------------------------------------------------------------- Key: JASSIST-34 URL: http://jira.jboss.com/jira/browse/JASSIST-34 Project: Javassist Issue Type: Bug Environment: Jboss 4.0.5 GA with EJB3 deployer and IBM DB2 JDBC driver v3.3.54 Reporter: Josh Devins Assigned To: Shigeru Chiba Attachments: server.snipped.log I have deployed an application that is using the IBM DB2 JDBC driver jar version 3.3.54. With the EJB3 deployer installed (since we have EJB3s), some class file in the DB2 jar apparently does not start with 0XCAFEBABE, or "the magic hex code". The EJB3 deployer is using Javassist to examine all of the class files in the jar, but when it hits one of these wonky IBM class files, Javaasisst is throwing an IOException with message "non class file". This is rather useless as the EJB3 deployer then rethrows this IOException as a RuntimeException. I get no info about what class failed, what jar file it was in, etc. Perhaps this is an EJB3 deployer issue, but I believe that Javassist should at least throw a more descriptive exception, and not even an IOException. Or better yet, the EJB3 deployer should not just die and rethrow the RuntimeException, just skip the file! Stepping through the JBoss and Javassist code with my debugger was the only way to figure this out. You can look at the attached stack trace from the server log for the exact files and line numbers. -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1284) ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer

by Justin Wick (JIRA)

ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-1284 URL: http://jira.jboss.com/jira/browse/JBRULES-1284 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Environment: Windows XP, Eclipse 3.2 Reporter: Justin Wick Assigned To: Mark Proctor If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint. See attached files for an example -- 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

16 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBAS-4254) Client read timeout setting wanted for HTTP Invoker

by Anders Welen (JIRA)

Client read timeout setting wanted for HTTP Invoker ---------------------------------------------------- Key: JBAS-4254 URL: http://jira.jboss.com/jira/browse/JBAS-4254 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.3 SP1 Reporter: Anders Welen Priority: Minor There is no read timeout setting to prevent client threads from hanging while using the HTTP Invoker. A quick fix (if you are using SUN JVM) is to use the parameter "-Dsun.net.client.defaultReadTimeout=60000". The problem with this solution is that it affects all connection, not just the HTTPInvoker. A solution that works (if Java 5 is used) is to add a call to the method "setReadTimeout(xxx)" on the "conn" variable in the method "invoke()" in "org.jboss.invocation.http.interfaces.Util". (The same problem exists with the standard JRMP Invoker aswell. It's just the Pooled Invoker that has a read timeout) -- 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

16 years, 11 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008