September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2251) Fix JBoss Cache / AS integration issues

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2251?page=all ] Brian Stansberry updated JBAS-2251: ----------------------------------- Summary: Fix JBoss Cache / AS integration issues (was: Fix integration issues) Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta3) > Fix JBoss Cache / AS integration issues > --------------------------------------- > > Key: JBAS-2251 > URL: http://jira.jboss.com/jira/browse/JBAS-2251 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > > The JBossCache standalone build includes: > jboss-aop.jar (ok - should be standalone project) > jboss-common.jar (ok - should be standalone project(s)) > jboss-j2ee.jar (TransactionManager interfaces) > jboss-jmx.jar (only for JBossNotificationBroadcasterSupport leaking from jboss-system.jar?) > jboss-minimal.jar (for MarshalledValue, etc.) > jboss-system.jar (for ServiceMBeanSupport) > We are heading for a fall on this (not to mention the other thirdparty jars that could get out-of-sync) > Some of this will probably have to wait until we have the proper federated build. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4057) Port JBAS-3721 fix to trunk

by Brian Stansberry (JIRA)

Port JBAS-3721 fix to trunk --------------------------- Key: JBAS-4057 URL: http://jira.jboss.com/jira/browse/JBAS-4057 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3499) Use JBoss Cache for DistributedReplicantManager instead of HAPartition

by Brian Stansberry (JIRA)

Use JBoss Cache for DistributedReplicantManager instead of HAPartition ---------------------------------------------------------------------- Key: JBAS-3499 URL: http://jira.jboss.com/jira/browse/JBAS-3499 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Jerry Gauthier Fix For: JBossAS-5.0.0.Beta DRM remains as a service available via HAPartition, but it uses JBC for cluster-wide state management. This requires that the HAPartition and the JBC instance use the same underlying multiplexed JChannel. -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-4613) JBossCacheManager active session count should include backup sessions

by Brian Stansberry (JIRA)

JBossCacheManager active session count should include backup sessions --------------------------------------------------------------------- Key: JBAS-4613 URL: http://jira.jboss.com/jira/browse/JBAS-4613 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 Fix For: JBossAS-5.0.0.Beta3 The usage of the max active session configuration in JBossCacheManager currently only applies to sessions that are being used in the local node -- it ignores how many sessions are stored in the distributed cache. This makes little sense, since the primary purpose of controlling the session count is to control memory resources. A session in the distributed cache takes memory resources just as much as a locally used one does. With this change, when the Manager checks whether there are excess sessions, the maxActive property value will be compared against an "active" count derived as follows: visible sessions = count of locally accessed sessions + count of sessions in the local instance of the distributed cache that have not been locally accessed active sessions = visible sessions - sessions passivated locally The value of that calculation is what will be returned by the getActiveSessionCount() method. If the active session count >= maxActive, the session expiration/passivation method (processExpires()) will be executed before a new session is created. If after expiration/passivation the active session count still exceeds maxActive, the session creation request will be rejected with an IllegalStateException. (Rejecting the attempt to create excess sessions is not new; all that has changed is the calculation.) The same comparison is used within processExpires() to determine whether sessions that have reached their configured passivation-min-idle-time need to be passivated. Note that the value of "active sessions" will depend on whether the distributed cache is using buddy replication, as that will impact the number of sessions stored in the local instance of the distributed cache: 1) If buddy replication is disabled, a copy of all sessions used on any node in the cluster will be stored in the local instance of the distributed cache. 2) If buddy replication is enabled (the default in 5.x), only sessions hosted by cluster nodes for which the current node is serving as a buddy will be stored in the local instance of the distributed cache. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3735) Integrate JGroups 2.4 in JBossAS 5

by Brian Stansberry (JIRA)

Integrate JGroups 2.4 in JBossAS 5 ---------------------------------- Key: JBAS-3735 URL: http://jira.jboss.com/jira/browse/JBAS-3735 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta When 2.4 is released, need to integrate it into AS HEAD. I've been integrating various beta, snapshot and CR releases of 2.4 into AS HEAD for quite a while now, so most of the work for this task is done. -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3896) Expose JChannel and protocol mbeans via JMX

by Brian Stansberry (JIRA)

Expose JChannel and protocol mbeans via JMX ------------------------------------------- Key: JBAS-3896 URL: http://jira.jboss.com/jira/browse/JBAS-3896 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry JChannel and the protocols expose mbeans; when we create a channel we need to register those beans in JMX. API is via JmxConfigurator.reisterChannel(). Need to check how this works with a multiplexed channel. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4708) Move default clustering config info out of DeployerConfig to WebMetaData

by Brian Stansberry (JIRA)

Move default clustering config info out of DeployerConfig to WebMetaData ------------------------------------------------------------------------ Key: JBAS-4708 URL: http://jira.jboss.com/jira/browse/JBAS-4708 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.Beta3 This data isn't used by the deployer. See forum thread for details. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1179) Premature rule execution

by Markus Reitz (JIRA)

Premature rule execution ------------------------ Key: JBRULES-1179 URL: http://jira.jboss.com/jira/browse/JBRULES-1179 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1 Environment: JDK 1.5, Mac OS X 10.4 Reporter: Markus Reitz Assigned To: Mark Proctor Using the rules package test rule "A" when exists(x : String() and y : String(this!=x)) then System.out.println("x!=y exists."); end rule "B" when not(exists(x : String() and y : String(this!=x))) then System.out.println("x!=y does not exist."); end as input for the following program (java DroolsTest <name of rule file>) import org.drools.*; import org.drools.compiler.*; import org.drools.rule.Package; import java.io.*; public class DroolsTest { private RuleBase rules; private StatefulSession memory; public DroolsTest(File file) throws Exception { rules =RuleBaseFactory.newRuleBase(); memory=rules.newStatefulSession(); rules.addPackage(loadPackage(file)); } protected Package loadPackage(File file) throws IOException { FileInputStream stream=null; try { stream=new FileInputStream(file); return(loadPackage(stream)); } finally { if (stream!=null) stream.close(); } } protected Package loadPackage(InputStream stream) throws IOException { try { PackageBuilder builder=new PackageBuilder(); builder.addPackageFromDrl(new InputStreamReader(stream)); return(builder.getPackage()); } catch(Exception ex) { throw new IOException(); } } public StatefulSession getSession() { return(memory); } public static void main(String ... args) { try { DroolsTest test=new DroolsTest(new File(args[0])); System.out.println("Inserting ..."); test.getSession().insert(new String("42")); test.getSession().insert(new String("42")); test.getSession().insert(new String("1701")); test.getSession().insert(new String("0815")); test.getSession().insert(new String("4711")); System.out.println("Done."); System.out.println("Firing rules ..."); test.getSession().fireAllRules(); System.out.println("Done."); } catch (Exception ex) { ex.printStackTrace(); } } } creates the output x!=y does not exist. Inserting ... Done. Firing rules ... x!=y exists. Done. Premature firing of rules seems to occur ("x!=y does not exist" before fireAllRules is invoked), which is not the expected behaviour. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1100) BRMS Bug on view source in weblogic

by Fernando Meyer (JIRA)

BRMS Bug on view source in weblogic ----------------------------------- Key: JBRULES-1100 URL: http://jira.jboss.com/jira/browse/JBRULES-1100 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA, 4.0.0.MR3, 4.0.0.MR2 Environment: OS: Any Application Server: Weblogic > 9.2 Reporter: Fernando Meyer Assigned To: Fernando Meyer Fix For: 4.0.1 When trying to view source brms is using eclipse instead janino |####<Aug 18, 2007 1:59:34 AM BRT> <Error> <ServletContext-/drools-jbrms> <localhost.localdomain> <examplesServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1187413174144> <000000> <Exception while dispatching incoming RPC call org.drools.RuntimeDroolsException: Unable to load dialect ' org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java' at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:138) at org.drools.compiler.PackageBuilderConfiguration.init (PackageBuilderConfiguration.java:114) at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:87) at org.drools.brms.server.ServiceImplementation.buildAssetSource (ServiceImplementation.java:777) at org.drools.brms.server.ServiceImplementation$$FastClassByCGLIB$$8f2fab45.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57) at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke (RollbackInterceptor.java:34) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java :47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:37) at org.jboss.seam.intercept.SeamInvocationContext.proceed (SeamInvocationContext.java:69) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java :154) at org.jboss.seam.intercept.JavaBeanInterceptor.intercept(JavaBeanInterceptor.java:89) at org.drools.brms.server.ServiceImplementation$$EnhancerByCGLIB$$ea689016.buildAssetSource(<generated>) 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.jboss.seam.remoting.gwt.GWTToSeamAdapter.callWebRemoteMethod(GWTToSeamAdapter.java:70) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.processCall(GWTRemoteServiceServlet.java:300) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.doPost(GWTRemoteServiceServlet.java:181) at javax.servlet.http.HttpServlet.service (HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) java.lang.RuntimeException : The Eclipse JDT Core jar is not in the classpath at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98) at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init (JavaDialectConfiguration.java:56) at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134) at org.drools.compiler.PackageBuilderConfiguration.init (PackageBuilderConfiguration.java:114) at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:87) at org.drools.brms.server.ServiceImplementation.buildAssetSource (ServiceImplementation.java:777) at org.drools.brms.server.ServiceImplementation$$FastClassByCGLIB$$8f2fab45.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57) at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke (RollbackInterceptor.java:34) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java :47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:37) at org.jboss.seam.intercept.SeamInvocationContext.proceed (SeamInvocationContext.java:69) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java :154) at org.jboss.seam.intercept.JavaBeanInterceptor.intercept(JavaBeanInterceptor.java:89) at org.drools.brms.server.ServiceImplementation$$EnhancerByCGLIB$$ea689016.buildAssetSource(<generated>) 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.jboss.seam.remoting.gwt.GWTToSeamAdapter.callWebRemoteMethod(GWTToSeamAdapter.java:70) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.processCall(GWTRemoteServiceServlet.java:300) at org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.doPost(GWTRemoteServiceServlet.java:181) at javax.servlet.http.HttpServlet.service (HttpServlet.java:763) -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1187) Bug in guided editor when you add a boolean restriction field

by Fernando Meyer (JIRA)

Bug in guided editor when you add a boolean restriction field ------------------------------------------------------------- Key: JBRULES-1187 URL: http://jira.jboss.com/jira/browse/JBRULES-1187 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1, 4.0.0.GA, 4.0.0.MR3, 4.0.0.MR2 Reporter: Fernando Meyer Assigned To: Fernando Meyer Priority: Blocker Fix For: 4.0.2 got a bug in brms guided editor, when I insert a fact and try to add a restriction field for a boolean field the brms guided mess up everything -- 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, 10 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 September 2007