September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3198) Comments (!) in certain places flagged as errors, dialect "mvel"

by Wolfgang Laun (JIRA)

Comments (!) in certain places flagged as errors, dialect "mvel" ---------------------------------------------------------------- Key: JBRULES-3198 URL: https://issues.jboss.org/browse/JBRULES-3198 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.0.Beta1 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.3.0.CR1 A bracketed comment (/* - */) is flagged as an error when it appears * in a cast after the type name (/*X*/) * immediately after a class name after new (/*Y*/) Rather wild error messages which don't help at all are emitted, see below. import java.util.HashMap; declare Student name : String @key gradeMap : HashMap end rule KickOff dialect "mvel" when then long l = (long /*X*/)0; Student s = new Student/*Y*/( "Joe" ); s.gradeMap = new HashMap/*Y*/(); insert( s ); end ########### Sample error message: Unable to Analyse Expression Student s = new Student/*Y*/( "Joe" ); s.gradeMap = new HashMap(); drools.insert( s );: [Error: Failed to compileShared: 1 compilation error(s): - (1,17) could not resolve class: Student/*Y*/] [Near : {... jectGradeMap().put( "CompSc", 0 ); ....}] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1359) TUNNEL:Destroy StubManager before creating a new one

by Vladimir Blagojevic (JIRA)

TUNNEL:Destroy StubManager before creating a new one ---------------------------------------------------- Key: JGRP-1359 URL: https://issues.jboss.org/browse/JGRP-1359 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1, 3.0 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.12.2, 3.0 In case of disconnect we only send disconnect GR command to GR but the socket(s) between TUNNEL and GR remain(s) open. In case of a new connect on the same channel we create a new RouterStubManager and thus a new socket from TUNNEL to GR *while* the old one remains open and connected. Not good! In TUNNEL#handleDownEvent right before a new TUNNELStubManager is created we should destroy previous TUNNELStubManager if it is non null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-171) ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable

by James Livingston (JIRA)

ClusteredSession.setAttribute() could report the attribute name and/or class FQN when not serializable ------------------------------------------------------------------------------------------------------ Key: JBWEB-171 URL: https://jira.jboss.org/browse/JBWEB-171 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cluster Affects Versions: JBossWeb-2.1.3.GA Reporter: James Livingston Assignee: Remy Maucherat Priority: Minor org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute() raises an exception with the clusteredSession.setAttribute.iae message if the attribute can't be replicated (i.e. isn't Serializable or a primitive). It would be nice if it mentioned the attribute name and/or the class FQN in the error message to aid in debugging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBJCA-669) JBoss Logging Generator 1.0.0.Beta8

by Jesper Pedersen (JIRA)

JBoss Logging Generator 1.0.0.Beta8 ----------------------------------- Key: JBJCA-669 URL: https://issues.jboss.org/browse/JBJCA-669 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-668) Track component updates

by Jesper Pedersen (JIRA)

Track component updates ----------------------- Key: JBJCA-668 URL: https://issues.jboss.org/browse/JBJCA-668 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-670) JBoss Logging Processor 1.0.0.Beta8

by Jesper Pedersen (JIRA)

JBoss Logging Processor 1.0.0.Beta8 ----------------------------------- Key: JBJCA-670 URL: https://issues.jboss.org/browse/JBJCA-670 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBLOGGING-58) Support setting the logging provider explicitly

by Dan Allen (JIRA)

Support setting the logging provider explicitly ----------------------------------------------- Key: JBLOGGING-58 URL: https://issues.jboss.org/browse/JBLOGGING-58 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Priority: Minor Fix For: 3.0.0.Beta5-jboss-logging Currently, JBoss Logging uses a classloading approach to look for a logging provider based on a hardcoded order of precedence. While this is sufficient for the default case, there should be a way to specify the logger explicitly, in the case that there is more than one concrete logging implementation on the classpath. The override should be part of the API, though a system property could also be supported. The API would take precedence. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-9447) 'logout' on custom authentication module never called

by Thomas Woelfle (JIRA)

'logout' on custom authentication module never called ----------------------------------------------------- Key: JBAS-9447 URL: https://issues.jboss.org/browse/JBAS-9447 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.1.0 Environment: JBoss 6.1.0, Java 1.6.0_26 Reporter: Thomas Woelfle Hi there, I have a custom authentication module that extends the JBoss DatabaseServerLoginModule (org.jboss.security.auth.spi.DatabaseServerLoginModule) that provides stuff like counting failed logins, disabling accounts, .... When loging in from a remote desktop client using LoginContext.login() the 'login' method of my custom authentication module is called. This works fine. But when loging out using LoginContext.logout() the 'logout' method of my authentication module is never called. This seems to be a bug, isn't it? Regards, Thomas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1750) Invocation batching not enabled errors when using DIST mode for web sessions

by Paul Ferraro (JIRA)

Invocation batching not enabled errors when using DIST mode for web sessions ---------------------------------------------------------------------------- Key: AS7-1750 URL: https://issues.jboss.org/browse/AS7-1750 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.2.Final, 7.1.0.Alpha1 This is a regression caused by a change to DefaultEmbeddedCacheManager, where calls to getCache(...) for a non-existent cache result in the cache being based on the CacheContainer.DEFAULT_CACHE, not the default-cache. 11:25:20,945 WARN [org.jboss.as.clustering.web.infinispan.DistributedCacheManager] (notification-thread-0) Invocation batching not enabled in current configuration! Please use the <invocationBatching /> element.: org.infinispan.config.ConfigurationException: Invocation batching not enabled in current configuration! Please use the <invocationBatching /> element. at org.infinispan.CacheImpl.startBatch(CacheImpl.java:433) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL] at org.infinispan.AbstractDelegatingCache.startBatch(AbstractDelegatingCache.java:66) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL] at org.jboss.as.clustering.web.infinispan.DistributedCacheManager$JvmRouteHandler.batch(DistributedCacheManager.java:618) at org.jboss.as.clustering.web.infinispan.DistributedCacheManager$JvmRouteHandler.viewChanged(DistributedCacheManager.java:666) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_23] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_23] at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:200) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23] at java.lang.Thread.run(Thread.java:679) [:1.6.0_23] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-808) Some instrumented classes have a null ProtectionDomain

by Flavia Rainone (JIRA)

Some instrumented classes have a null ProtectionDomain ------------------------------------------------------ Key: JBAOP-808 URL: https://issues.jboss.org/browse/JBAOP-808 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 1.5.7.GA, 2.1.6.CP04 Some instrumented classes have a null ProtectionDomain, while they should have the protection domain of the aspect or instrumented classes most closely associated with them. All instrumented class creation points in the code must be reviewed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
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 September 2011