October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2215) WorkManagerService does not start work manager

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-2215?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-2215: ----------------------------------- Every service in the container *must* be symmetrical. This means that if you stop and start the service again, when start completes, the service will be at exactly the same level of usability that it was before it was stopped. In other words, all work done in stop must undo the work done in start (nothing more, nothing less). Furthermore, your requirement "start() should invoke WorkManager.cancelShutdown()" is wrong. The stop() method should not complete until the work manager has completed shutdown. Use asynchronous stop for this if necessary. > WorkManagerService does not start work manager > ---------------------------------------------- > > Key: WFLY-2215 > URL: https://issues.jboss.org/browse/WFLY-2215 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Stefano Maestri > Fix For: 8.0.0.Beta1 > > > WorkManagerService does not start/restart WorkManager > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > WorkManager is set in constructor. In stop method, WorkManager.shutdown() is called. start() should invoke WorkManager.cancelShutdown(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2215) WorkManagerService does not start work manager

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-2215?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-2215: ----------------------------------- It is *always* wrong to perform service start tasks in the constructor of the service. > WorkManagerService does not start work manager > ---------------------------------------------- > > Key: WFLY-2215 > URL: https://issues.jboss.org/browse/WFLY-2215 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Stefano Maestri > Fix For: 8.0.0.Beta1 > > > WorkManagerService does not start/restart WorkManager > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > WorkManager is set in constructor. In stop method, WorkManager.shutdown() is called. start() should invoke WorkManager.cancelShutdown(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-209) Nested classes read from ClassMemberValue cannot be loaded

by Ben Romberg (JIRA)

[ https://issues.jboss.org/browse/JASSIST-209?page=com.atlassian.jira.plugi... ] Ben Romberg updated JASSIST-209: -------------------------------- Affects Version/s: 3.18.1-GA > Nested classes read from ClassMemberValue cannot be loaded > ---------------------------------------------------------- > > Key: JASSIST-209 > URL: https://issues.jboss.org/browse/JASSIST-209 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA, 3.18.1-GA > Reporter: Ben Romberg > Assignee: Shigeru Chiba > > I'm trying to upgrade Javassist in my project from version 3.16.1 to 3.18.0. I'm using the ClassMemberValue to load the (String) class-name of an annotation value, in order to load the class with Javassist using ClassPool.get(...). > In 3.16.1, the returned class-name String for nested classes contained the $-sign, as in package.ParentClass$NestedClass, which didn't have any issues using the String with ClassPool.get(...). > In 3.18.0 however, the returned class-name String for nested classes changed to a pure dot-notation, as in package.ParentClass.NestedClass, which cannot be used with ClassPool.get(...) anymore, as Javassist tries to load the class-file from package/ParentClass/NestedClass.class instead of package/ParentClass$NestedClass.class. > I don't see any way to work around the issue without hacking into internal API, as the class-name String is the only way to get the annotation value. As this is a generic class (and not always a nested class), I also cannot simply replace the last dot with a $-sign. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2177) org.jboss.logmanager module needs dependency on javax.api for the SocketFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2177: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1013169|https://bugzilla.redhat.com/show_bug.cgi?id=1013169] Verified on EAP 6.2.0.ER4 > org.jboss.logmanager module needs dependency on javax.api for the SocketFactory > ------------------------------------------------------------------------------- > > Key: WFLY-2177 > URL: https://issues.jboss.org/browse/WFLY-2177 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Beta1 > > > The {{javax.net.SocketFactory}} is part of the {{javax.api}} module. Since the {{org.jboss.logmanager}} uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2177) org.jboss.logmanager module needs dependency on javax.api for the SocketFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2177: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1013169|https://bugzilla.redhat.com/show_bug.cgi?id=1013169] from ON_QA to VERIFIED > org.jboss.logmanager module needs dependency on javax.api for the SocketFactory > ------------------------------------------------------------------------------- > > Key: WFLY-2177 > URL: https://issues.jboss.org/browse/WFLY-2177 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Beta1 > > > The {{javax.net.SocketFactory}} is part of the {{javax.api}} module. Since the {{org.jboss.logmanager}} uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1709) Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1709?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1709 at 10/4/13 8:28 AM: --------------------------------------------------------- The following classes below still need to be converted, excluding - classes that are not officially supported (STOMP, PRIO) - classes that are not used anymore (e.g. NAKACK, NakReceiverWindow, Retransmitter, DefaultRetransmitter, RangeBasedRetransmitter etc) - test code (StateTransferTest) - demos (Whiteboard, GraphPanel, Draw, QuoteServer) {panel} -src/org/jgroups/stack/Configurator.java- -src/org/jgroups/conf/XmlConfigurator.java- -src/org/jgroups/conf/PropertyHelper.java- -src/org/jgroups/conf/ProtocolConfiguration.java- -src/org/jgroups/conf/ClassConfigurator.java- src/org/jgroups/protocols/FILE_PING.java src/org/jgroups/protocols/FD_SOCK.java src/org/jgroups/protocols/RSVP.java src/org/jgroups/protocols/UDP.java src/org/jgroups/protocols/FD_PING.java src/org/jgroups/protocols/COMPRESS.java src/org/jgroups/protocols/VERIFY_SUSPECT.java src/org/jgroups/protocols/MFC.java src/org/jgroups/protocols/MERGE3.java src/org/jgroups/protocols/FRAG2.java src/org/jgroups/protocols/FlowControl.java src/org/jgroups/protocols/ENCRYPT.java src/org/jgroups/protocols/FORWARD_TO_COORD.java src/org/jgroups/protocols/S3_PING.java src/org/jgroups/protocols/FD.java src/org/jgroups/protocols/UNICAST2.java src/org/jgroups/protocols/Discovery.java src/org/jgroups/protocols/JDBC_PING.java src/org/jgroups/protocols/TCP.java src/org/jgroups/protocols/UFC.java src/org/jgroups/protocols/SEQUENCER.java src/org/jgroups/protocols/AUTH.java src/org/jgroups/protocols/TP.java src/org/jgroups/protocols/TCPGOSSIP.java src/org/jgroups/protocols/MPING.java src/org/jgroups/protocols/pbcast/GMS.java src/org/jgroups/protocols/pbcast/GmsImpl.java src/org/jgroups/protocols/pbcast/STATE_TRANSFER.java src/org/jgroups/protocols/pbcast/ClientGmsImpl.java src/org/jgroups/protocols/pbcast/StreamingStateTransfer.java src/org/jgroups/protocols/pbcast/Merger.java src/org/jgroups/protocols/pbcast/CoordGmsImpl.java src/org/jgroups/protocols/pbcast/STABLE.java src/org/jgroups/protocols/pbcast/FLUSH.java src/org/jgroups/protocols/pbcast/STATE_SOCK.java -src/org/jgroups/protocols/pbcast/NAKACK2.java- src/org/jgroups/protocols/relay/RELAY2.java src/org/jgroups/protocols/relay/Relayer.java src/org/jgroups/protocols/tom/TOA.java src/org/jgroups/util/TimeScheduler2.java src/org/jgroups/util/Util.java src/org/jgroups/util/ForwardQueue.java src/org/jgroups/util/Queue.java src/org/jgroups/jmx/ResourceDMBean.java src/org/jgroups/jmx/JmxConfigurator.java src/org/jgroups/blocks/RequestCorrelator.java src/org/jgroups/blocks/GroupRequest.java src/org/jgroups/blocks/TCPConnectionMap.java src/org/jgroups/blocks/Request.java src/org/jgroups/blocks/RpcDispatcher.java src/org/jgroups/blocks/MethodCall.java src/org/jgroups/blocks/MessageDispatcher.java src/org/jgroups/auth/MD5Token.java src/org/jgroups/auth/FixedMembershipToken.java src/org/jgroups/auth/SimpleToken.java src/org/jgroups/auth/X509Token.java {panel} was (Author: belaban): The following classes below still need to be converted, excluding - classes that are not officially supported (STOMP, PRIO) - classes that are not used anymore (e.g. NAKACK, NakReceiverWindow, Retransmitter, DefaultRetransmitter, RangeBasedRetransmitter etc) - test code (StateTransferTest) - demos (Whiteboard, GraphPanel, Draw, QuoteServer) {panel} -src/org/jgroups/stack/Configurator.java- -src/org/jgroups/conf/XmlConfigurator.java- -src/org/jgroups/conf/PropertyHelper.java- -src/org/jgroups/conf/ProtocolConfiguration.java- -src/org/jgroups/conf/ClassConfigurator.java- src/org/jgroups/protocols/FILE_PING.java src/org/jgroups/protocols/FD_SOCK.java src/org/jgroups/protocols/RSVP.java src/org/jgroups/protocols/UDP.java src/org/jgroups/protocols/FD_PING.java src/org/jgroups/protocols/COMPRESS.java src/org/jgroups/protocols/VERIFY_SUSPECT.java src/org/jgroups/protocols/MFC.java src/org/jgroups/protocols/MERGE3.java src/org/jgroups/protocols/FRAG2.java src/org/jgroups/protocols/FlowControl.java src/org/jgroups/protocols/ENCRYPT.java src/org/jgroups/protocols/FORWARD_TO_COORD.java src/org/jgroups/protocols/S3_PING.java src/org/jgroups/protocols/FD.java src/org/jgroups/protocols/UNICAST2.java src/org/jgroups/protocols/Discovery.java src/org/jgroups/protocols/JDBC_PING.java src/org/jgroups/protocols/TCP.java src/org/jgroups/protocols/UFC.java src/org/jgroups/protocols/SEQUENCER.java src/org/jgroups/protocols/AUTH.java src/org/jgroups/protocols/TP.java src/org/jgroups/protocols/TCPGOSSIP.java src/org/jgroups/protocols/MPING.java src/org/jgroups/protocols/pbcast/GMS.java src/org/jgroups/protocols/pbcast/GmsImpl.java src/org/jgroups/protocols/pbcast/STATE_TRANSFER.java src/org/jgroups/protocols/pbcast/ClientGmsImpl.java src/org/jgroups/protocols/pbcast/StreamingStateTransfer.java src/org/jgroups/protocols/pbcast/Merger.java src/org/jgroups/protocols/pbcast/CoordGmsImpl.java src/org/jgroups/protocols/pbcast/STABLE.java src/org/jgroups/protocols/pbcast/FLUSH.java src/org/jgroups/protocols/pbcast/STATE_SOCK.java src/org/jgroups/protocols/pbcast/NAKACK2.java src/org/jgroups/protocols/relay/RELAY2.java src/org/jgroups/protocols/relay/Relayer.java src/org/jgroups/protocols/tom/TOA.java src/org/jgroups/util/TimeScheduler2.java src/org/jgroups/util/Util.java src/org/jgroups/util/ForwardQueue.java src/org/jgroups/util/Queue.java src/org/jgroups/jmx/ResourceDMBean.java src/org/jgroups/jmx/JmxConfigurator.java src/org/jgroups/blocks/RequestCorrelator.java src/org/jgroups/blocks/GroupRequest.java src/org/jgroups/blocks/TCPConnectionMap.java src/org/jgroups/blocks/Request.java src/org/jgroups/blocks/RpcDispatcher.java src/org/jgroups/blocks/MethodCall.java src/org/jgroups/blocks/MessageDispatcher.java src/org/jgroups/auth/MD5Token.java src/org/jgroups/auth/FixedMembershipToken.java src/org/jgroups/auth/SimpleToken.java src/org/jgroups/auth/X509Token.java {panel} > Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles > ------------------------------------------------------------------------------------------- > > Key: JGRP-1709 > URL: https://issues.jboss.org/browse/JGRP-1709 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4 > > > Convert WARN and ERROR messages that might be seen by users to use a resource bundle (conf/jg-messages*.properties) and assign unique IDs the those messages. > Link in BZ: https://bugzilla.redhat.com/show_bug.cgi?id=999671 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2217) Enable reload tests

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2217?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-2217: ---------------------------------------- Assignee: Bartosz Baranowski (was: Ondrej Zizka) > Enable reload tests > ------------------- > > Key: WFLY-2217 > URL: https://issues.jboss.org/browse/WFLY-2217 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > > Tests need not stay ignored any longer! > Some tests which :reload are still ignored, even though :reload has been fixed ( well, it seems there is more to it due to other code changes ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2217) Enable reload tests

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-2217: ---------------------------------------- Summary: Enable reload tests Key: WFLY-2217 URL: https://issues.jboss.org/browse/WFLY-2217 Project: WildFly Issue Type: Enhancement Components: Test Suite Affects Versions: 8.0.0.Beta1 Reporter: Bartosz Baranowski Assignee: Ondrej Zizka Tests need not stay ignored any longer! Some tests which :reload are still ignored, even though :reload has been fixed ( well, it seems there is more to it due to other code changes ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Headers: data in some headers might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1714. ---------------------------- Resolution: Done > Headers: data in some headers might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.4 > > > Similar to JGRP-1710 and JGRP-1713, investigate headers which might become too big, and move their contents into the message body. Check all headers which contain > * a view > * a digest > * a list of members > Candidates: > * {{PingHeader}}. > Probable solution: move {{PingHeader.PingData}} from the header to the message body -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2216) include-all role mappings don't work in domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2216?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2216: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1015493 > include-all role mappings don't work in domain > ---------------------------------------------- > > Key: WFLY-2216 > URL: https://issues.jboss.org/browse/WFLY-2216 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Ladislav Thon > Assignee: Darran Lofthouse > Labels: rbac-filed-by-qa > > If I understand correctly, roles that have {{include-all=true}} in their role mappings should be added to all authenticated users. In my tests, though, this only works in standalone mode. > In domain mode, if I set a role mapping to {{include-all}}, this setting is not reflected (at least not immediately; maybe it would work after restart, but that's wrong anyway). It doesn't matter which role is set to be {{include-all}} -- in my tests, I use both standard roles and scoped roles and it consistently doesn't work. There's probably some wrong caching going on. > The failing test case is in my pull request https://github.com/wildfly/wildfly/pull/5166 (it's the _RBAC tests for include-all role mappings in domain_ commit). If it's more convenient, the pull request is the same as my _rbac_ branch (https://github.com/Ladicek/wildfly/commits/rbac). > Darran, I'm not sure if you are the right assignee -- please reassign if needed. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 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 October 2013