July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-329) ClassFormatException when compile template with latest JDK8 (b114)

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-329?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-329: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > ClassFormatException when compile template with latest JDK8 (b114) > ------------------------------------------------------------------ > > Key: DROOLS-329 > URL: https://issues.jboss.org/browse/DROOLS-329 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR5 > Environment: Ubuntu linux, latest JDK1.8 (b114) downloaded from https://jdk8.java.net/download.html > Reporter: Marek Posolda > Assignee: Mark Proctor > Fix For: 5.5.1.Final, 6.2.0.Beta1 > > > When trying to run code for compile templates with latest JDK8 (For instance this example https://github.com/droolsjbpm/drools/blob/master/drools-examples/src/main... ) > it will throw an exception like this: > {code} > Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: wrong class format > at org.drools.template.parser.DefaultTemplateRuleBase.readRule(DefaultTemplateRuleBase.java:148) > at org.drools.template.parser.DefaultTemplateRuleBase.<init>(DefaultTemplateRuleBase.java:62) > at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:74) > at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:95) > at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:81) > at org.drools.examples.templates.SimpleRuleTemplateExample.buildKBase(SimpleRuleTemplateExample.java:84) > at org.drools.examples.templates.SimpleRuleTemplateExample.executeExample(SimpleRuleTemplateExample.java:49) > at org.drools.examples.templates.SimpleRuleTemplateExample.main(SimpleRuleTemplateExample.java:43) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) > Caused by: java.lang.RuntimeException: wrong class format > at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:263) > at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:203) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:102) > at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:49) > at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:122) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromTypeSignature(LookupEnvironment.java:1188) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromVariantTypeSignature(LookupEnvironment.java:1244) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeArgumentsFromSignature(LookupEnvironment.java:1031) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.getTypeFromTypeSignature(LookupEnvironment.java:1193) > at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethod(BinaryTypeBinding.java:495) > at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.createMethods(BinaryTypeBinding.java:577) > at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.cachePartsFrom(BinaryTypeBinding.java:327) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:640) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:619) > at org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:295) > at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:133) > at org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage(PackageBinding.java:183) > at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findImport(CompilationUnitScope.java:465) > at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findSingleImport(CompilationUnitScope.java:519) > at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInImports(CompilationUnitScope.java:368) > at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInTypes(CompilationUnitScope.java:444) > at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:752) > at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:464) > at org.drools.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJavaCompiler.java:389) > at org.drools.commons.jci.compilers.AbstractJavaCompiler.compile(AbstractJavaCompiler.java:49) > at org.drools.rule.builder.dialect.java.JavaDialect.compileAll(JavaDialect.java:371) > at org.drools.compiler.DialectCompiletimeRegistry.compileAll(DialectCompiletimeRegistry.java:46) > at org.drools.compiler.PackageRegistry.compileAll(PackageRegistry.java:102) > at org.drools.compiler.PackageBuilder.compileAll(PackageBuilder.java:1006) > at org.drools.compiler.PackageBuilder.compileAllRules(PackageBuilder.java:842) > at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:831) > at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:441) > at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:419) > at org.drools.template.parser.DefaultTemplateRuleBase.readRule(DefaultTemplateRuleBase.java:139) > ... 12 more > Caused by: org.eclipse.jdt.internal.compiler.classfmt.ClassFormatException > at org.eclipse.jdt.internal.compiler.classfmt.ClassFileReader.<init>(ClassFileReader.java:372) > at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.createNameEnvironmentAnswer(EclipseJavaCompiler.java:287) > at org.drools.commons.jci.compilers.EclipseJavaCompiler$2.findType(EclipseJavaCompiler.java:258) > ... 45 more > {code} > Workaround, which worked for me is to switch to Janino compiler (See Workaround description) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-470: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest)) > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-470 > URL: https://issues.jboss.org/browse/DROOLS-470 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Michael Anstis > Fix For: 6.2.0.Beta1 > > > This DT should work: > ||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))|| > |guestName == "$param"|guestName == "$param"|doSomething();| > It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed. > Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule: > ||CONDITION||CONDITION||CONDITION||ACTION| > |$guest : SeatDesignation()|$neighbor : SeatDesignation()||| > |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();| > Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-453) Allow KieSession globals configurable via kmodule.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-453?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-453: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > Allow KieSession globals configurable via kmodule.xml > ----------------------------------------------------- > > Key: DROOLS-453 > URL: https://issues.jboss.org/browse/DROOLS-453 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Anton Giertli > Assignee: Mark Proctor > Fix For: 6.2.0.Beta1 > > > Looking at the current xsd of kmodule.xml > https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/6.0.x/kie-api/src... > It is not possible to configure KieSession globals variables via kmodule.xml. > Given the fact it is already possible to configure almost every KieSession related features like listeners, handlers, loggers, globals, also session related, should be configurable through the kmodule.xml too. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-448) Traiting non-declared POJOS prevents the execution of WM actions from outside the WM

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-448?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-448: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > Traiting non-declared POJOS prevents the execution of WM actions from outside the WM > ------------------------------------------------------------------------------------ > > Key: DROOLS-448 > URL: https://issues.jboss.org/browse/DROOLS-448 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > Fix For: 6.2.0.Beta1 > > > When a trait is applied to non-declared bean, a transparent proxy is created and the handle is updated accordingly. However, this prevents the lookup of the handle using the original object as a key. > The proxy creation should be avoided. > See also PLANNER-229 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-546) FactType.get/set should throw specific exception (not NPE) for unknown fields

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-546?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-546: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > FactType.get/set should throw specific exception (not NPE) for unknown fields > ----------------------------------------------------------------------------- > > Key: DROOLS-546 > URL: https://issues.jboss.org/browse/DROOLS-546 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR1 > Reporter: Benoit Voisin > Assignee: Mario Fusco > Fix For: 6.2.0.Beta1 > > > factType.get(instance, "unknownField") is currently throwing an NPE. This gives improper information to the user/developper. > I propose that it throws a new UnknownFactFieldException giving improved information giving good hints for debugging or enabling specific exception management. > See pull request for test-case and proposed fix -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-542) Expose more Commands through the KieCommands API

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-542?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-542: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > Expose more Commands through the KieCommands API > ------------------------------------------------ > > Key: DROOLS-542 > URL: https://issues.jboss.org/browse/DROOLS-542 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 6.2.0.Beta1 > > > Not all Commands are exposed by the KieCommands API interface -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-494) Create an Execution Server for Drools

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-494?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-494: ------------------------------------------ Fix Version/s: 6.2.0.Beta1 (was: 6.1.0.Final) > Create an Execution Server for Drools > ------------------------------------- > > Key: DROOLS-494 > URL: https://issues.jboss.org/browse/DROOLS-494 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta1 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 6.2.0.Beta1 > > > Implement an Execution Server for KIE as defined by BPMSPL-35. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3448) Session ID change with sub-directories using "/" context (virtual host)

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-3448?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-3448: ---------------------------------- Can we get this in the 8.x branch as well? > Session ID change with sub-directories using "/" context (virtual host) > ----------------------------------------------------------------------- > > Key: WFLY-3448 > URL: https://issues.jboss.org/browse/WFLY-3448 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Wildfly 8.1.0 RC2 > Reporter: David Cabillic > Assignee: Stuart Douglas > Labels: sessionid, virtualhosts > Fix For: 9.0.0.Beta1 > > > I used a virtual host in Wildfly like this : > <host name="toto" alias="www.toto.com"> > <location name="/" handler="welcome-content"/> > </host> > When I try to access www.toto.com/sub/, a new cookie is created. It would be great with a "/sub" context but it is not for a "/" context. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3693) Module org.jboss.as.version contains 2 identical jar files

by Frank Langelage (JIRA)

Frank Langelage created WFLY-3693: ------------------------------------- Summary: Module org.jboss.as.version contains 2 identical jar files Key: WFLY-3693 URL: https://issues.jboss.org/browse/WFLY-3693 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System, Server Affects Versions: 9.0.0.Beta1 Environment: WildFly 9.0 build from current github-sources as of today. Solaris SPARC 10, Oracle JDK 1.7.0_65 Reporter: Frank Langelage Assignee: Paul Gier Priority: Minor Module org.jboss.as.version contains 2 identical jar files -rw-r--r-- 1 jboss informix 14111 Jul 30 13:21 jboss-as-version-9.0.0.Alpha1-SNAPSHOT.jar -rw-r--r-- 1 jboss informix 14111 Jul 30 13:21 wildfly-version-1.0.0.Alpha3.jar As only wildfly-version-1.0.0.Alpha3.jar is referenced in module.xml the jboss-as-version-9.0.0.Alpha1-SNAPSHOT.jar seems to be a relict from the past. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1864) UDP unable to bind to ephemeral port: port out of range:65536

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/JGRP-1864?page=com.atlassian.jira.plugin.... ] Ion Savin commented on JGRP-1864: --------------------------------- The version used is 3.5.0.Beta9. > UDP unable to bind to ephemeral port: port out of range:65536 > ------------------------------------------------------------- > > Key: JGRP-1864 > URL: https://issues.jboss.org/browse/JGRP-1864 > Project: JGroups > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.4.4 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4.5, 3.5 > > > It looks like {{UDP.createEphemeralDatagramSocket()}} swallows any errors it gets while creating the socket, and throws this exception after trying to bind to all ports in the 0 - 65535 range: > {noformat} > java.lang.IllegalArgumentException: port out of range:65536 > at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143) > at java.net.InetSocketAddress.<init>(InetSocketAddress.java:185) > at java.net.DatagramSocket.<init>(DatagramSocket.java:284) > at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62) > at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:429) > at org.jgroups.protocols.UDP.createSockets(UDP.java:311) > at org.jgroups.protocols.UDP.start(UDP.java:216) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966) > at org.jgroups.JChannel.startStack(JChannel.java:889) > at org.jgroups.JChannel._preConnect(JChannel.java:547) > at org.jgroups.JChannel.connect(JChannel.java:282) > at org.jgroups.JChannel.connect(JChannel.java:273) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:200) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014