December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-665) Cannot extends rule from another one with the same package name

by Yacine Jaber (JIRA)

Yacine Jaber created DROOLS-665: ----------------------------------- Summary: Cannot extends rule from another one with the same package name Key: DROOLS-665 URL: https://issues.jboss.org/browse/DROOLS-665 Project: Drools Issue Type: Bug Affects Versions: 6.0.0.Final Reporter: Yacine Jaber Assignee: Mark Proctor When I extends a rule from another one with the same package, but into two differents .drl files. I got the following message : Unable to resolve parent rule, please check that both rules are in the same package. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4174) Xalan Linkage error : TransformerConfigurationException

by Stephen Kay (JIRA)

[ https://issues.jboss.org/browse/WFLY-4174?page=com.atlassian.jira.plugin.... ] Stephen Kay commented on WFLY-4174: ----------------------------------- Hope this help / our current 'workaround' consist in embeeding Xalan within our WAR : No bug encountered with that workaround : <dependency> <groupId>xalan</groupId> <artifactId>xalan</artifactId> <version>2.7.2</version> <exclusions> <exclusion> <groupId>xml-apis</groupId> <artifactId>xml-apis</artifactId> </exclusion> </exclusions> </dependency> > Xalan Linkage error : TransformerConfigurationException > ------------------------------------------------------- > > Key: WFLY-4174 > URL: https://issues.jboss.org/browse/WFLY-4174 > Project: WildFly > Issue Type: Bug > Environment: Wildfly 8.1 & 8.2-Final > JDK 1.7.0_45 & 1.7.0_71 > Windows & Linux > Reporter: Stephen Kay > Assignee: Jason Greene > Priority: Critical > > Please note that this bug wasn't present on JBoss 7.1 / same WAR artifact > This is full staktrace from our applicaion. > 11:13:32,130 SEVERE ch.mitsa.credoc.ui.views.messages.MessagesTable (default task-9) Error getting message payload: : javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance. > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) rt.jar:1.7.0_71 > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) rt.jar:1.7.0_71 > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) rt.jar:1.7.0_71 > at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:765) rt.jar:1.7.0_71 > at _redirected.TransformerFactory.newTransformer(_TransformerFactory.java:132) jboss-modules.jar:1.3.3.Final > at ch.mitsa.credoc.format.swift.impl.SwiftFormatter.getPrettyPrintedPayload(SwiftFormatter.java:196) > at ch.mitsa.credoc.engine.service.OutputService.getPrettyPrintedMessage(OutputService.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) rt.jar:1.7.0_71 > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) rt.jar:1.7.0_71 > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) rt.jar:1.7.0_71 > at java.lang.reflect.Method.invoke(Method.java:606) rt.jar:1.7.0_71 > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) wildfly-weld-8.2.0.Final.jar:8.2.0.Final > (...) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4174) Xalan Linkage error : TransformerConfigurationException

by Stephen Kay (JIRA)

Stephen Kay created WFLY-4174: --------------------------------- Summary: Xalan Linkage error : TransformerConfigurationException Key: WFLY-4174 URL: https://issues.jboss.org/browse/WFLY-4174 Project: WildFly Issue Type: Bug Environment: Wildfly 8.1 & 8.2-Final JDK 1.7.0_45 & 1.7.0_71 Windows & Linux Reporter: Stephen Kay Assignee: Jason Greene Priority: Critical Please note that this bug wasn't present on JBoss 7.1 / same WAR artifact This is full staktrace from our applicaion. 11:13:32,130 SEVERE ch.mitsa.credoc.ui.views.messages.MessagesTable (default task-9) Error getting message payload: : javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance. at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) rt.jar:1.7.0_71 at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) rt.jar:1.7.0_71 at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) rt.jar:1.7.0_71 at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:765) rt.jar:1.7.0_71 at _redirected.TransformerFactory.newTransformer(_TransformerFactory.java:132) jboss-modules.jar:1.3.3.Final at ch.mitsa.credoc.format.swift.impl.SwiftFormatter.getPrettyPrintedPayload(SwiftFormatter.java:196) at ch.mitsa.credoc.engine.service.OutputService.getPrettyPrintedMessage(OutputService.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) rt.jar:1.7.0_71 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) rt.jar:1.7.0_71 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) rt.jar:1.7.0_71 at java.lang.reflect.Method.invoke(Method.java:606) rt.jar:1.7.0_71 at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) wildfly-weld-8.2.0.Final.jar:8.2.0.Final (...) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4135) All-in-one Java EE 7 Quickstart

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4135?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-4135: ---------------------------------- Summary: All-in-one Java EE 7 Quickstart (was: EE Concurrency 1.0 Quickstarts) > All-in-one Java EE 7 Quickstart > ------------------------------- > > Key: WFLY-4135 > URL: https://issues.jboss.org/browse/WFLY-4135 > Project: WildFly > Issue Type: Sub-task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Update WildFly Quickstarts to demo usage of EE Concurrency 1.0, new technology introduced by Java EE 7. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4135) All-in-one Java EE 7 Quickstart

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4135?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-4135: ---------------------------------- Description: Introduce a WildFly Quickstart to demo usage of the new/updated technologies introduced by Java EE 7. (was: Update WildFly Quickstarts to demo usage of EE Concurrency 1.0, new technology introduced by Java EE 7. ) > All-in-one Java EE 7 Quickstart > ------------------------------- > > Key: WFLY-4135 > URL: https://issues.jboss.org/browse/WFLY-4135 > Project: WildFly > Issue Type: Sub-task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Introduce a WildFly Quickstart to demo usage of the new/updated technologies introduced by Java EE 7. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-400) Remove <any-ipv4-address/> and <any-ipv6-address>

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-400?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet commented on WFCORE-400: ------------------------------------------ Don't forget to update https://developer.jboss.org/wiki/IncompatibilitiesBetweenCurrentWildFlyAn... once this is merged. > Remove <any-ipv4-address/> and <any-ipv6-address> > ------------------------------------------------- > > Key: WFCORE-400 > URL: https://issues.jboss.org/browse/WFCORE-400 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Beta1 > > > These options have no reliable semantic (see, for example, WFLY-533) and should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-634) Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-634?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-634: ------------------------------------ I am pretty sure we have a problem there, but again it's impossible for me to figure out what's going wrong without a reproducer. Can somebody please send one? > Exception thrown from WorkingMemoryLogger randomly when simultaneous evaluation taking place by different threads > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-634 > URL: https://issues.jboss.org/browse/DROOLS-634 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR1 > Reporter: Anantjot Anand > Assignee: Mario Fusco > > Caused by: java.lang.NullPointerException > at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getDeclarationIds(RuleTerminalNodeLeftTuple.java:394) > at org.drools.core.audit.WorkingMemoryLogger.extractDeclarations(WorkingMemoryLogger.java:325) > at org.drools.core.audit.WorkingMemoryLogger.matchCreated(WorkingMemoryLogger.java:269) > at org.drools.core.event.AgendaEventSupport.fireActivationCreated(AgendaEventSupport.java:58) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftTupleInsert(PhreakRuleTerminalNode.java:95) > at org.drools.core.phreak.PhreakRuleTerminalNode.doLeftInserts(PhreakRuleTerminalNode.java:69) > at org.drools.core.phreak.PhreakRuleTerminalNode.doNode(PhreakRuleTerminalNode.java:42) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:316) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:225) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:98) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:988) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1274) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1254) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-444) JAVA_OPTS environment variable not used for domain mode on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-444: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1170051|https://bugzilla.redhat.com/show_bug.cgi?id=1170051] from ON_QA to VERIFIED > JAVA_OPTS environment variable not used for domain mode on Windows > ------------------------------------------------------------------ > > Key: WFCORE-444 > URL: https://issues.jboss.org/browse/WFCORE-444 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Josef Cacek > Assignee: Josef Cacek > > When I use JAVA_OPTS as an environment variable (i.e. configured before starting the AS) it's not propagated when used in domain mode on windows (domain.bat). > For standalone mode (standalone.bat) it works. > For Linux/Unix it works in both cases (standalone.sh, domain.sh). > Steps to reproduce: > {code} > SET "JAVA_OPTS=...MyOwnJavaOptsConfig..." > domain.bat > {code} > Actual result: > The configured JAVA_OPTS are not used. > Expected result: > Provided JAVA_OPTS are used for the process controller and host controller processes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4165) Invalidating another session removes the JSESSIONID cookie of the current session

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4165?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4165: -------------------------------------- Fixed in undertow upstream > Invalidating another session removes the JSESSIONID cookie of the current session > --------------------------------------------------------------------------------- > > Key: WFLY-4165 > URL: https://issues.jboss.org/browse/WFLY-4165 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: WildFly 8.1.0.Final and WildFly 8.2.0.Final on Windows 7 x64 > JDK 8u25 > Session storage set to Cookie > Reporter: Nicolas Grussenmeyer > Assignee: Stuart Douglas > > When calling {{invalidate()}} on a HttpSession object of another session than the current one, the server sends back a "cookie expired" header {{Set-Cookie: JSESSIONID=XXXXXXXX; path=/; HttpOnly; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:00 GMT}} where XXXXXXXX is the session id of the invalidated session. > This results in the current JSESSIONID cookie being discarded by the browser, and the current session being lost. > I was able to narrow the "problem" in {{[io.undertow.servlet.spec.HttpSessionImpl:193|https://github.com/undertow-io/undertow/blob/1.0.15.Final/servlet/src/main/java/io/undertow/servlet/spec/HttpSessionImpl.java#L193]}} (in Undertow 1.0.15.Final), where the ServletRequestContext is taken from the ThreadLocal storage, returning the current request context instead of null (as the target session is not associated to the current ServletRequestContext ) > A workaround is to call {{invalidate()}} in a new Thread, so the retrieved ServletRequestContext is null -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBREM-1330) Lease$LeaseTimerTask has a race condition

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1330?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1330: ---------------------------------- Lease$LeaseTimerTask synchronizes access to client leases. Change committed to https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x > Lease$LeaseTimerTask has a race condition > ----------------------------------------- > > Key: JBREM-1330 > URL: https://issues.jboss.org/browse/JBREM-1330 > Project: JBoss Remoting > Issue Type: Bug > Affects Versions: 2.5.4.SP5 > Reporter: Ron Sigal > Assignee: Ron Sigal > Fix For: 2.5.4.SP6 > > > org.jboss.remoting.Lease$LeasePinger and org.jboss.remoting.ServerInvoker both access the map of existing Leases. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014