November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4110) EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used

by Dominik Pospisil (JIRA)

Dominik Pospisil created WFLY-4110: -------------------------------------- Summary: EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used Key: WFLY-4110 URL: https://issues.jboss.org/browse/WFLY-4110 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 9.0.0.Alpha1 Reporter: Dominik Pospisil Assignee: Dominik Pospisil -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1903) TCPPING: discovery dissemination for static discovery protocols

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1903?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1903. ---------------------------- Resolution: Done > TCPPING: discovery dissemination for static discovery protocols > --------------------------------------------------------------- > > Key: JGRP-1903 > URL: https://issues.jboss.org/browse/JGRP-1903 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.1 > > > For {{TCPPING}}, usually all members have to be listed in {{initial_hosts}}. If we don't know all of the members up front, we could have the coordinator disseminate the IP address and port information dynamically. > Say {{TCPPING.initial_hosts}} only lists A (the coord). When members B, C, D and E join (in that order), we have the following caches: > |A|B|C|D|E| > |ABCDE|AB|AC|AD|AE| > Every member has information about itself and A, but not about other members. So, for example, D won't be able to send a unicast to C, and vice versa. Or, when E sends a multicast, it would only be delivered to itself and A, but not to B, C and D. > h5. Solution > * When we have a static discovery layer, have the coordinator broadcast its cache information to the rest of the cluster > * This can be done when a new member join, or periodically, or upon request (JMX) > * Should be goverened by a property: if someone lists all members in {{initial_hosts}}, then he may want to turn this off -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3149) Windows service on 64 bit systems cannot be stopped

by Max Weidemann (JIRA)

[ https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin.... ] Max Weidemann edited comment on WFLY-3149 at 11/21/14 7:36 AM: --------------------------------------------------------------- Hi i had the same Problem and could fixt it by installing the service with the controller param with the value 127.0.0.1:10090. (complete command: service.bat install /user Admin /password **** /controller 127.0.0.1:10090) i had to do so because i added the following value to my JAVA_OPTS in the standalone.conf.bat file. set "JAVA_OPTS=%JAVA_OPTS% -Djboss.socket.binding.port-offset=100" I used Wildfly 8.1.0 with Java 7 on Windows Server 2012 64 bit. was (Author: max.weidemann): Hi i had the same Problem and could fixt it by installing the service with the controller param with the value 127.0.0.1:10090. (complete command: service.bat install /user Admin /password **** /controller 127.0.0.1:10090) i had to do so because i added the following value to my JAVA_OPTS in the standalone.conf.bat file. set "JAVA_OPTS=%JAVA_OPTS% -Djboss.socket.binding.port-offset=100" I used Wildfly 8.1.0 with Java 7. > Windows service on 64 bit systems cannot be stopped > --------------------------------------------------- > > Key: WFLY-3149 > URL: https://issues.jboss.org/browse/WFLY-3149 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Final > Environment: Windows 2008 Server, Windows 7 professional - both 64 bit systems using JDK 1.7.0_09 > Reporter: Mohan Potturi > Assignee: Mladen Turk > > The Windows service cannot be stopped. It says 'stopping' in the windows service user interface window. The only way to stop it is ti actually kill the java process. It works flawlessly on 32 bit systems though. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3149) Windows service on 64 bit systems cannot be stopped

by Max Weidemann (JIRA)

[ https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin.... ] Max Weidemann commented on WFLY-3149: ------------------------------------- Hi i had the same Problem and could fixt it by installing the service with the controller param with the value 127.0.0.1:10090. (complete command: service.bat install /user Admin /password **** /controller 127.0.0.1:10090) i had to do so because i added the following value to my JAVA_OPTS in the standalone.conf.bat file. set "JAVA_OPTS=%JAVA_OPTS% -Djboss.socket.binding.port-offset=100" I used Wildfly 8.1.0 with Java 7. > Windows service on 64 bit systems cannot be stopped > --------------------------------------------------- > > Key: WFLY-3149 > URL: https://issues.jboss.org/browse/WFLY-3149 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Final > Environment: Windows 2008 Server, Windows 7 professional - both 64 bit systems using JDK 1.7.0_09 > Reporter: Mohan Potturi > Assignee: Mladen Turk > > The Windows service cannot be stopped. It says 'stopping' in the windows service user interface window. The only way to stop it is ti actually kill the java process. It works flawlessly on 32 bit systems though. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4109) Remove outdated policy files from testsuite/integration/src/test/config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4109?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4109: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1166130|https://bugzilla.redhat.com/show_bug.cgi?id=1166130] from NEW to POST > Remove outdated policy files from testsuite/integration/src/test/config > ----------------------------------------------------------------------- > > Key: WFLY-4109 > URL: https://issues.jboss.org/browse/WFLY-4109 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Minor > > Policy files no-op.policy and permit_all_testsuite.policy are outdated. They should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 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 Anderson Parra de Paula (JIRA)

[ https://issues.jboss.org/browse/WFLY-3953?page=com.atlassian.jira.plugin.... ] Anderson Parra de Paula commented on WFLY-3953: ----------------------------------------------- I could not simulate this problem on development version: Please take a look at this code: @Singleton @Startup public class TimerTest { @Schedule(hour = "*", minute = "*", second="13") public void sayHello() { System.out.println("Hello"); } } Result: 11:53:13,005 INFO [stdout] (EJB default - 6) Hello 11:54:13,010 INFO [stdout] (EJB default - 7) Hello 11:55:13,007 INFO [stdout] (EJB default - 8) Hello 11:56:13,004 INFO [stdout] (EJB default - 9) Hello 11:57:13,040 INFO [stdout] (EJB default - 10) Hello > @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 > Components: EJB > Affects Versions: 8.1.0.Final > Reporter: Andrei Tchijov > Assignee: Stuart Douglas > > 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.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4109) Remove outdated policy files from testsuite/integration/src/test/config

by Josef Cacek (JIRA)

Josef Cacek created WFLY-4109: --------------------------------- Summary: Remove outdated policy files from testsuite/integration/src/test/config Key: WFLY-4109 URL: https://issues.jboss.org/browse/WFLY-4109 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Josef Cacek Assignee: Josef Cacek Priority: Minor Policy files no-op.policy and permit_all_testsuite.policy are outdated. They should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4109) Remove outdated policy files from testsuite/integration/src/test/config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4109?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4109: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166130 > Remove outdated policy files from testsuite/integration/src/test/config > ----------------------------------------------------------------------- > > Key: WFLY-4109 > URL: https://issues.jboss.org/browse/WFLY-4109 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Minor > > Policy files no-op.policy and permit_all_testsuite.policy are outdated. They should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3417) Accessing the EJB 3 container configuration of the web console fails

by Philippe Schaller (JIRA)

[ https://issues.jboss.org/browse/WFLY-3417?page=com.atlassian.jira.plugin.... ] Philippe Schaller closed WFLY-3417. ----------------------------------- Fix Version/s: 8.2.0.Final Resolution: Out of Date No longer an issue with 8.2.0.Final. > Accessing the EJB 3 container configuration of the web console fails > -------------------------------------------------------------------- > > Key: WFLY-3417 > URL: https://issues.jboss.org/browse/WFLY-3417 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.1.0.CR2 > Environment: HAL 2.2.6.Final & 2.2.7.Final > WildFly 8.1.0.CR2 & 8.1.0.CR5 > JDK 1.7.0_55 > Win 7 > Reporter: Philippe Schaller > Assignee: Heiko Braun > Fix For: 8.2.0.Final > > > Accessing the EJB 3 container configuration of the web console returns this message: > Unknown error > Unexpected HTTP response: 500 > Request > { > "address" => [("subsystem" => "threads")], > "child-type" => "thread-factory", > "operation" => "read-children-resources", > "recursive" => true > } > Response > Internal Server Error > { > "outcome" => "failed", > "failure-description" => "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"threads\")]", > "rolled-back" => true > } -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-270) Upgrade to JBoss SASL 1.0.5.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-270?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-270: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1164781|https://bugzilla.redhat.com/show_bug.cgi?id=1164781] from POST to MODIFIED > Upgrade to JBoss SASL 1.0.5.Final > --------------------------------- > > Key: WFCORE-270 > URL: https://issues.jboss.org/browse/WFCORE-270 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 10 months

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