[JBoss JIRA] Created: (JBREM-726) BisocketServerInvoker control connection creation needs to be in loop
by Tim Fox (JIRA)
BisocketServerInvoker control connection creation needs to be in loop
---------------------------------------------------------------------
Key: JBREM-726
URL: http://jira.jboss.com/jira/browse/JBREM-726
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Tim Fox
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta2 (Bluto)
When using the bisocket transport the creation of non control tcp connections is done in a retry to loop to prevent failures which may happen when trying to create connections in Windows (known windowx bug).
However creation of the tcp connection to be used for the bisocket control connection does not appear to be protected in the same way. This can cause JBM intermittent test failures when running on Windows.
--
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
19 years, 1 month
[JBoss JIRA] Created: (JBRULES-737) Filter out <clinit> method when inspecting classes
by Edson Tirelli (JIRA)
Filter out <clinit> method when inspecting classes
--------------------------------------------------
Key: JBRULES-737
URL: http://jira.jboss.com/jira/browse/JBRULES-737
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 3.1-m1
Reporter: Edson Tirelli
Assigned To: Edson Tirelli
Fix For: 3.1-m2
FROM TERRY LAURENZO:
-------------------------------------------------
The attached diff (against 3.0.5 sources) adds a condition to the ClassFieldInspector to not analyze methods named <clinit>. For some reason, the Groovy compiler is outputing classes that were causing this check to choke and throw an IllegalArgumentException because of a <clinit> method with ACC_PUBLIC access code.
Applying this patch allows Drools to operate correctly with compiled Groovy Fact classes.
This seems like a pretty innocuous change that someone should apply to SVN. Unfortunately, it is rather difficult to create a test case for it.
Terry Laurenzo
--------------
Index: src/main/java/org/drools/util/asm/ClassFieldInspector.java
===================================================================
*** src/main/java/org/drools/util/asm/ClassFieldInspector.java Wed Mar 14 08:58:24 2007
--- src/main/java/org/drools/util/asm/ClassFieldInspector.java Mon Mar 12 11:21:23 2007
*************** public class ClassFieldInspector {
*** 241,247 ****
//only want public methods that start with 'get' or 'is'
//and have no args, and return a value
if ( (access & Opcodes.ACC_PUBLIC) > 0 ) {
! if ( desc.startsWith( "()" ) && !(name.equals( "<init>" )) ) {// && ( name.startsWith("get") || name.startsWith("is") ) ) {
try {
final Method method = this.clazz.getMethod( name,
(Class[]) null );
--- 241,247 ----
//only want public methods that start with 'get' or 'is'
//and have no args, and return a value
if ( (access & Opcodes.ACC_PUBLIC) > 0 ) {
! if ( desc.startsWith( "()" ) && !(name.equals( "<init>" )) && !(name.equals( "<clinit>" )) ) {// && ( name.startsWith("get") || name.startsWith("is") ) ) {
try {
final Method method = this.clazz.getMethod( name,
(Class[]) null );
--
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
19 years, 1 month
[JBoss JIRA] Created: (JBAS-4172) Document undocumented naming properties
by Brian Stansberry (JIRA)
Document undocumented naming properties
---------------------------------------
Key: JBAS-4172
URL: http://jira.jboss.com/jira/browse/JBAS-4172
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Brian Stansberry
Assigned To: Norman Richards
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.GA
The following properties accepted by org.jnp.interfaces.NamingContext are not covered in the documentation:
jnp.socketFactory -- The javax.net.SocketFactory impl to use for the bootstrap socket
jnp.localAddress -- The local (client-side) address to bind the connected bootstrap socket to
jnp.localPort -- The local (client-side) port to bind the connected bootstrap socket to
jnp.useRelativeName -- A flag indicating the style of names passed to javax.naming.spi.NamingManager methods. True for api expected relative names, false
for absolute names as used historically by the jboss naming implementation.
jnp.discoveryTTL -- The time-to-live for multicast discovery packets
The first four belong in the general discussion of org.jnp.interfaces.NamingContext (e.g. Section 2.3.2 of The JBoss 4 Application Server J2EE Reference), while the last belongs in the clustering discussion (Section 2.3.3 of the above as well as Section 1.2.2 of The JBoss 4 Application Server Clustering Guide).
--
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
19 years, 1 month
[JBoss JIRA] Created: (JBRULES-578) Running Jboss Rules in Weblogic
by Ruban Mahendran (JIRA)
Running Jboss Rules in Weblogic
-------------------------------
Key: JBRULES-578
URL: http://jira.jboss.com/jira/browse/JBRULES-578
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.5
Environment: Running JBoss Rules in Weblogic8.14 via a JSP deployed in a WAR.
Reporter: Ruban Mahendran
Assigned To: Mark Proctor
When attempting to create a package from a class called by a JSP ( see below) I get the following error:
CharScanner; panic: ClassNotFoundException: org.antlr.stringtemplate.language.ChunkToken
Stopping the Weblogic Workshop debugger...
Debugger Stopped.
The Weblogic server stops as well.
Here is the code snippet called by the jsp
PackageBuilderConfiguration pkgBuilderCfg = new PackageBuilderConfiguration();
pkgBuilderCfg.setCompiler(PackageBuilderConfiguration.JANINO);
PackageBuilder builder = new PackageBuilder(pkgBuilderCfg);
builder.addPackageFromDrl((new InputStreamReader(new FileInputStream("c:\\myruleresource.drl")) ) );
--
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
19 years, 1 month
[JBoss JIRA] Created: (JBRULES-736) Should be able to compare different numeric types
by Michael Neale (JIRA)
Should be able to compare different numeric types
-------------------------------------------------
Key: JBRULES-736
URL: http://jira.jboss.com/jira/browse/JBRULES-736
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 3.1-m1
Reporter: Michael Neale
Assigned To: Mark Proctor
Priority: Blocker
Fix For: 3.1-m3
rule High
when
RandomNumber(randomValue:value)
Guess(guess: value>randomValue)
game: GameHistory()
then
game.setBiggest(guess.intValue()-1);
end
will cause:
Caused by: java.lang.ClassCastException: java.lang.Long
at java.lang.Integer.compareTo(Integer.java:35)
at org.drools.base.evaluators.ObjectFactory$ObjectGreaterEvaluator.evaluateCachedRight(ObjectFactory.java:304)
at org.drools.rule.VariableRestriction.isAllowedCachedRight(VariableRestriction.java:74)
at org.drools.rule.VariableConstraint.isAllowedCachedRight(VariableConstraint.java:78)
at org.drools.common.SingleBetaConstraints.isAllowedCachedRight(SingleBetaConstraints.java:111)
This used to work in 3.0.5, so something is seriously broken in the evaluators.
--
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
19 years, 1 month