[JBoss JIRA] (DROOLS-968) Random Nullpointer
by Michal Letynski (JIRA)
Michal Letynski created DROOLS-968:
--------------------------------------
Summary: Random Nullpointer
Key: DROOLS-968
URL: https://issues.jboss.org/browse/DROOLS-968
Project: Drools
Issue Type: Bug
Affects Versions: 5.6.0.Final
Environment: Windows, Jetty
Reporter: Michal Letynski
Assignee: Mark Proctor
>From time to time i.m getting weird Nullpointer exception. I didn't reproduce the problem when the app is deployed on Glassfish. Only on jetty and only on windows system (with MAC OS everything is ok)
Stacktrace:
java.lang.NullPointerException
at org.drools.base.evaluators.EvaluatorRegistry.addEvaluatorDefinition(EvaluatorRegistry.java:155)
at org.drools.base.evaluators.EvaluatorRegistry.<init>(EvaluatorRegistry.java:77)
at org.drools.compiler.PackageBuilderConfiguration.buildEvaluatorRegistry(PackageBuilderConfiguration.java:544)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:196)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:308)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:236)
And my code is a simple object creation:
PackageBuilder packageBuilder = new PackageBuilder();
Any hint why this might occur ? Or should i just ignore it because on production we have Glassfish server ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5596) MessageDrivenComponent startDelivery/stopDelivery is not thread safe
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/WFLY-5596?page=com.atlassian.jira.plugin.... ]
James Livingston commented on WFLY-5596:
----------------------------------------
In addition, stop() calls deactivate() even when deliveryActive is false, which means activate() may never have been called.
> MessageDrivenComponent startDelivery/stopDelivery is not thread safe
> --------------------------------------------------------------------
>
> Key: WFLY-5596
> URL: https://issues.jboss.org/browse/WFLY-5596
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMS
> Affects Versions: 10.0.0.CR4
> Reporter: James Livingston
> Assignee: Jeff Mesnil
>
> WFLY-4470 made a change to prevent MDBs being activated or deactivated multiple times, but it is not thread safe. A volatile boolean is used for the flag, but there is no protection against multiple threads invoking the methods simultaneously.
> Possible effects include:
> * activating the endpoint twice, with (probably) only one deactivation later, leading to not de-registering XA resources from the recovery manager properly
> * activate() and deactivate() running in the wrong order if done by separate threads
> Several simple solutions probably will not work correctly. Using an AtomicBoolean would stop multiple activations/deactivations from concurrent calls, but would mean that startDelivery() could return before the activation was one. Using a synchronized block or other exclusive lock would work, however since it involves invoking non-container code (the resource adapter), there could potentially be a deadlock risk if that invoked some related container functionality.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5602) Jsp Trim spaces doesn't work
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5602?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5602.
----------------------------------
Resolution: Rejected
This is only supposed to trim spaces between directives and actions, it will not trip all whitespace from a page.
> Jsp Trim spaces doesn't work
> ----------------------------
>
> Key: WFLY-5602
> URL: https://issues.jboss.org/browse/WFLY-5602
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.1.Final
> Reporter: Giuseppe Morreale
> Assignee: Stuart Douglas
> Priority: Minor
>
> I add it in my standalone-full.xml
> {{<servlet-container name="default" default-encoding="utf-8">
> * <jsp-config trim-spaces="true"/>**
> <persistent-sessions path="session" relative-to="jboss.server.temp.dir"/>
> <websockets/>
> </servlet-container>}}
>
> but with this test.jsp:
> {{<html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
> <title>JSP Page</title>
> </head>
> <body>
> <h1> Hello World!</h1>
> <div> test</div>
> </body>
> </html>}}
>
> the spaces are not trimmed..
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JASSIST-252) Javaassist problem with Test class having inheritance when used with PoweMock
by Srinivas Pasupulate (JIRA)
[ https://issues.jboss.org/browse/JASSIST-252?page=com.atlassian.jira.plugi... ]
Srinivas Pasupulate commented on JASSIST-252:
---------------------------------------------
Hi ,
Im facing the same issue with Java 8 and the latest versions of power mock and mockito.
*Issue:*
Getting the error: "Failed to transform class with name com.gs.ops.domain.StaticClass Reason: java.io.IOException: invalid constant type: 18"
*Solutions Tried:*
Googled threads for issue on with powermock - mockito & java-8
Excluded java assist from powermock and added java assist 3.19.0-GA
Tried different versions of powermock (1.5.4, 1.6.2...)
Below is the exception stack trace:
java.lang.IllegalStateException: Failed to transform class with name com.StaticClass. Reason: java.io.IOException: invalid constant type: 18
at org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:266)
at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:180)
at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:68)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:340)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:145)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:40)
at org.powermock.tests.utils.impl.AbstractTestSuiteChunkerImpl.createTestDelegators(AbstractTestSuiteChunkerImpl.java:244)
at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.<init>(JUnit4TestSuiteChunkerImpl.java:61)
at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.<init>(AbstractCommonPowerMockRunner.java:32)
at org.powermock.modules.junit4.PowerMockRunner.<init>(PowerMockRunner.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
Caused by: java.lang.RuntimeException: java.io.IOException: invalid constant type: 18
at javassist.CtClassType.getClassFile2(CtClassType.java:203)
at javassist.compiler.MemberResolver.lookupMethod(MemberResolver.java:110)
at javassist.compiler.MemberResolver.lookupMethod(MemberResolver.java:96)
at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:704)
at javassist.expr.NewExpr$ProceedForNew.setReturnType(NewExpr.java:243)
at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:146)
at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
at javassist.compiler.TypeChecker.atVariableAssign(TypeChecker.java:248)
at javassist.compiler.TypeChecker.atAssignExpr(TypeChecker.java:217)
at javassist.compiler.ast.AssignExpr.accept(AssignExpr.java:38)
at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
Please fix this asap.
Thanks in advance.
> Javaassist problem with Test class having inheritance when used with PoweMock
> -----------------------------------------------------------------------------
>
> Key: JASSIST-252
> URL: https://issues.jboss.org/browse/JASSIST-252
> Project: Javassist
> Issue Type: Bug
> Environment: Java Version 7 with below JARs
> cglib-nodep-2.2.2.jar
> javassist-3.20.0-GA.jar
> junit-4.12.jar
> mockito-all-1.10.19.jar
> objenesis-2.1.jar
> powermock-mockito-1.6.3-full.jar
> Reporter: Shailendra Yadav
> Assignee: Shigeru Chiba
>
> https://github.com/jayway/powermock/issues/583
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months