October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-55) Implement Clean Digest MD5 Mech

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/ELY-55?page=com.atlassian.jira.plugin.sys... ] Peter Skopek reassigned ELY-55: ------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Implement Clean Digest MD5 Mech > ------------------------------- > > Key: ELY-55 > URL: https://issues.jboss.org/browse/ELY-55 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3953) @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"

by Andrei Tchijov (JIRA)

[ https://issues.jboss.org/browse/WFLY-3953?page=com.atlassian.jira.plugin.... ] Andrei Tchijov updated WFLY-3953: --------------------------------- Affects Version/s: 8.1.0.Final > @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method" > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-3953 > URL: https://issues.jboss.org/browse/WFLY-3953 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Andrei Tchijov > Assignee: Jason Greene > > Please take a look at this gist : https://gist.github.com/leapingbytes/01838d9534638cb04200 > In case of @Schedule second and all consecutive invocations produce this > {code} > 13:19:30,635 ERROR U( ) [org.jboss.as.ejb3] (EJB default - 8) JBAS014120: Error invoking timeout for timer: [id=ba9f1c67-5a91-42ff-8276-f715efaa3723 timedObjectId=ChumbaServer-2.0-SNAPSHOT.ChumbaServer-2.0-SNAPSHOT.SettingsManagerImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a898863 initialExpiration=Wed Oct 08 13:17:30 EEST 2014 intervalDuration(in milli sec)=60000 nextExpiration=Wed Oct 08 13:20:30 EEST 2014 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method null is not a timeout method > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3953) @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"

by Andrei Tchijov (JIRA)

Andrei Tchijov created WFLY-3953: ------------------------------------ Summary: @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method" Key: WFLY-3953 URL: https://issues.jboss.org/browse/WFLY-3953 Project: WildFly Issue Type: Bug Reporter: Andrei Tchijov Assignee: Jason Greene Please take a look at this gist : https://gist.github.com/leapingbytes/01838d9534638cb04200 In case of @Schedule second and all consecutive invocations produce this {code} 13:19:30,635 ERROR U( ) [org.jboss.as.ejb3] (EJB default - 8) JBAS014120: Error invoking timeout for timer: [id=ba9f1c67-5a91-42ff-8276-f715efaa3723 timedObjectId=ChumbaServer-2.0-SNAPSHOT.ChumbaServer-2.0-SNAPSHOT.SettingsManagerImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a898863 initialExpiration=Wed Oct 08 13:17:30 EEST 2014 intervalDuration(in milli sec)=60000 nextExpiration=Wed Oct 08 13:20:30 EEST 2014 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method null is not a timeout method at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3952) logging-profiles doesn't work with Apache Common Logging

by Anders Welen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3952?page=com.atlassian.jira.plugin.... ] Anders Welen updated WFLY-3952: ------------------------------- Attachment: 87905.tar > logging-profiles doesn't work with Apache Common Logging > -------------------------------------------------------- > > Key: WFLY-3952 > URL: https://issues.jboss.org/browse/WFLY-3952 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Reporter: Anders Welen > Assignee: James Perkins > Priority: Minor > Attachments: 87905.tar > > > The logging for one logging-profile ends up in another logging-profile from time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3952) logging-profiles doesn't work with Apache Common Logging

by Anders Welen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3952?page=com.atlassian.jira.plugin.... ] Anders Welen updated WFLY-3952: ------------------------------- Description: The logging for one logging-profile ends up in another logging-profile from time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong. (was: The logging for one logging-profile ends up in another logging-profile form time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong.) > logging-profiles doesn't work with Apache Common Logging > -------------------------------------------------------- > > Key: WFLY-3952 > URL: https://issues.jboss.org/browse/WFLY-3952 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Reporter: Anders Welen > Assignee: James Perkins > Priority: Minor > > The logging for one logging-profile ends up in another logging-profile from time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3952) logging-profiles doesn't work with Apache Common Logging

by Anders Welen (JIRA)

Anders Welen created WFLY-3952: ---------------------------------- Summary: logging-profiles doesn't work with Apache Common Logging Key: WFLY-3952 URL: https://issues.jboss.org/browse/WFLY-3952 Project: WildFly Issue Type: Bug Components: Logging Affects Versions: 9.0.0.Alpha1, 8.1.0.Final Reporter: Anders Welen Assignee: James Perkins Priority: Minor The logging for one logging-profile ends up in another logging-profile form time to time. It's not sporadic as all logging will end up in the wrong place when things go wrong. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3951) weld-spi module lacks dependency on transaction-api

by Jozef Hartinger (JIRA)

Jozef Hartinger created WFLY-3951: ------------------------------------- Summary: weld-spi module lacks dependency on transaction-api Key: WFLY-3951 URL: https://issues.jboss.org/browse/WFLY-3951 Project: WildFly Issue Type: Bug Components: CDI / Weld Affects Versions: 9.0.0.Alpha1, 8.1.0.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 8.2.0.CR1, 9.0.0.Beta1 This is a problem since [TransactionServices|https://github.com/weld/api/blob/master/weld-spi/src/...] depends on javax.transaction -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-628) DecisionTable incorrectly parsed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-628?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-628: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1150308|https://bugzilla.redhat.com/show_bug.cgi?id=1150308] from NEW to ASSIGNED > DecisionTable incorrectly parsed > --------------------------------- > > Key: DROOLS-628 > URL: https://issues.jboss.org/browse/DROOLS-628 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.CR1 > > > 5.2.0.CR1 creates incorrect drl from decision table. With 5.1.0.M1 the drl for the same decision table is correct. > Wrong DRL from 5.2.0.CR1: > rule "ProcessState" > salience 65522 > ruleflow-group "CompleteSubOrder" > activation-group "ProcessState" > when > $m:ModifiedMarker(processState==null, state ==null) > $s:SubOrder > then > $m.setIsModified(true); > $s.setProcessState(ProcessState.CREATED); > end > Correct DRL with 5.1.0.M1: > rule "ProcessState" > salience 65522 > ruleflow-group "CompleteSubOrder" > activation-group "ProcessState" > when > $m:ModifiedMarker() > $s:SubOrder(processState==null, state ==null) > then > $m.setIsModified(true); > $s.setProcessState(ProcessState.CREATED); > end > The difference is that the constraints are put to $m instead of putting them to $s. > The behaviour in 5.2.0.CR1 is the same for all decision tables in my project and prevents me from upgrading to newer drools versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3950) Remove @Ignore from SarTestCase

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-3950: ------------------------------------ Summary: Remove @Ignore from SarTestCase Key: WFLY-3950 URL: https://issues.jboss.org/browse/WFLY-3950 Project: WildFly Issue Type: Bug Components: JMX Reporter: Stuart Douglas Assignee: David Lloyd This test was ignored due to issues introduced by the security manager upgrade, as it now fails under the security manager due to checking being true by default. The MBean server does an explicit check on the ProtectionDomain of the class, which is what causes the issue. {noformat} Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("javax.management.MBeanTrustPermission" "register")" in code source "(vfs:/content/sar-example.sar <no signer certificates>)" of "null") {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-154) Patching does not process subdirectories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-154?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-154: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1134735, https://bugzilla.redhat.com/show_bug.cgi?id=1136365 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1134735) > Patching does not process subdirectories > ---------------------------------------- > > Key: WFCORE-154 > URL: https://issues.jboss.org/browse/WFCORE-154 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 1.0.0.Alpha9 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha10 > > > If patched resource is in subdirectory of moduleRoot, it is not included as part of patch, even though it is present in patch zip. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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 October 2014