October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-150) Undefining suffix on size-rotating-file-handler sets invalid value on suffix

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-150?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-150: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1148842|https://bugzilla.redhat.com/show_bug.cgi?id=1148842] from POST to MODIFIED > Undefining suffix on size-rotating-file-handler sets invalid value on suffix > ---------------------------------------------------------------------------- > > Key: WFCORE-150 > URL: https://issues.jboss.org/browse/WFCORE-150 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When the suffix is undefined ({{undefine-attribute(name=suffix)}}) on a {{size-rotating-file-handler}} the value {{undefined}} gets written to the suffix which is invalid. The value needs to be set to null if undefined. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-90) DigestMD is missing permission check to use authorisation id

by Peter Skopek (JIRA)

Peter Skopek created ELY-90: ------------------------------- Summary: DigestMD is missing permission check to use authorisation id Key: ELY-90 URL: https://issues.jboss.org/browse/ELY-90 Project: WildFly Elytron Issue Type: Bug Reporter: Peter Skopek Assignee: Peter Skopek DigestMD is missing permission check to use authorisation id. See CompatibilityServerTest:ignored test testUnauthorizedAuthorizationId. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-68) Password type: DIGEST-MD5 pre-digested

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/ELY-68?page=com.atlassian.jira.plugin.sys... ] Peter Skopek reassigned ELY-68: ------------------------------- Assignee: Peter Skopek > Password type: DIGEST-MD5 pre-digested > -------------------------------------- > > Key: ELY-68 > URL: https://issues.jboss.org/browse/ELY-68 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: David Lloyd > Assignee: Peter Skopek > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-89) Add integrity and confidentiality suport to DigestMD5 mechanism

by Peter Skopek (JIRA)

Peter Skopek created ELY-89: ------------------------------- Summary: Add integrity and confidentiality suport to DigestMD5 mechanism Key: ELY-89 URL: https://issues.jboss.org/browse/ELY-89 Project: WildFly Elytron Issue Type: Task Components: SASL Reporter: Peter Skopek Assignee: Peter Skopek Integrity and confidentiality suport of DigestMD5 mechanism is missing. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[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)

10 years

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)

10 years

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)

10 years

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)

10 years

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)

10 years

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)

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