January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2703) Undertow Broken pipe with JSFs f:ajax and h:inputText

by Andre Pankraz (JIRA)

Andre Pankraz created WFLY-2703: ----------------------------------- Summary: Undertow Broken pipe with JSFs f:ajax and h:inputText Key: WFLY-2703 URL: https://issues.jboss.org/browse/WFLY-2703 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andre Pankraz -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts

by Karim AMMOUS (JIRA)

[ https://issues.jboss.org/browse/JGRP-1765?page=com.atlassian.jira.plugin.... ] Karim AMMOUS commented on JGRP-1765: ------------------------------------ Disable the loopback ensures as much as possible that the sender handles the message at the same time as the other receivers. Otherwise, with loopback, there are more risks the sender processes the data much before the other members due to the network latency. > TP: enable loopback by default and discard own multicasts > --------------------------------------------------------- > > Key: JGRP-1765 > URL: https://issues.jboss.org/browse/JGRP-1765 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again. > When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization. > SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}} -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-490) Domain Management Role Based Access Control

by Gopi Chand Uppala (JIRA)

[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ] Gopi Chand Uppala commented on WFLY-490: ---------------------------------------- Okay. Thanks for the clarification! > Domain Management Role Based Access Control > ------------------------------------------- > > Key: WFLY-490 > URL: https://issues.jboss.org/browse/WFLY-490 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: Authorization > Fix For: 8.0.0.Final > > > Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute. > Also consider confidentiality in exchange e.g. Can read metrics over http but must use https to add new server. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-351) KIE FileSystem resource type overriding does not work as reported by documentation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-351?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-351: ------------------------------------------------ Tomas Schlosser <tschloss(a)redhat.com> changed the Status of [bug 1034250|https://bugzilla.redhat.com/show_bug.cgi?id=1034250] from ON_QA to VERIFIED > KIE FileSystem resource type overriding does not work as reported by documentation > ---------------------------------------------------------------------------------- > > Key: DROOLS-351 > URL: https://issues.jboss.org/browse/DROOLS-351 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > > When a resource is written into the KieFileSystem using the method write( path, Resource ), the resource type is ignored and it will be resolved from the file extension instead. > That is, Example 4.10 in the Drools Official Documentation is misleading and pointing to an unimplemented feature -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1548: ----------------------------------------------- Shaun Appleton <sappleto(a)redhat.com> changed the Status of [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311] from ASSIGNED to CLOSED > Add fallback querry to jconsole plugin > -------------------------------------- > > Key: WFLY-1548 > URL: https://issues.jboss.org/browse/WFLY-1548 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Darran Lofthouse > Labels: JConsole, JMX, Plugin > Fix For: 8.0.0.Beta1 > > > JConsolePlugin connecects to default port, despite chance to use proper info. > Problem: > Unless I miss somethingm JConsole has a bit tight isolation between components. There is no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no idea what is the content of URL being passed as remote. > AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If its not, it fallbacks to default: localhost:9990. > However we can check for socket bindings and try to connect to proper socket. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2702) CalendarBasedTimeoutTestCase failures at end/begin of the month

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-2702: ------------------------------------- Summary: CalendarBasedTimeoutTestCase failures at end/begin of the month Key: WFLY-2702 URL: https://issues.jboss.org/browse/WFLY-2702 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Reporter: Eduardo Martins Assignee: Eduardo Martins The referred test in the ejb module fails on end and begin of months, due to different timezones. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1765?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1765: -------------------------------- Why ? I want to reduce the number of properties, and removing loopback is on my list as we'd loop back messages by default. > TP: enable loopback by default and discard own multicasts > --------------------------------------------------------- > > Key: JGRP-1765 > URL: https://issues.jboss.org/browse/JGRP-1765 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again. > When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization. > SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}} -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-490) Domain Management Role Based Access Control

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on WFLY-490: --------------------------------------- This feature is already included in EAP 6.2 - this issue is only still open to act as a container for any subsequent tasks identified that need to go into WildFly 8. > Domain Management Role Based Access Control > ------------------------------------------- > > Key: WFLY-490 > URL: https://issues.jboss.org/browse/WFLY-490 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: Authorization > Fix For: 8.0.0.Final > > > Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute. > Also consider confidentiality in exchange e.g. Can read metrics over http but must use https to add new server. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2701) Deployed JMS resources are not manageable in the GUI console

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-2701: --------------------------------- Summary: Deployed JMS resources are not manageable in the GUI console Key: WFLY-2701 URL: https://issues.jboss.org/browse/WFLY-2701 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMS Affects Versions: 8.0.0.CR1 Reporter: Jeff Mesnil Assignee: Jeff Mesnil JMS resources that are part of a deployment are not manageable using the GUI console. They are manageable using the CLI console though under {noformat} /deployment=*/subsystem=messaging/hornetq-server=* {noformat} -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBPORTAL-2497) CR1 jdk 1.8 (b106) fresh install standalone.bat hangs on "Starting"

by Jared Nagle (JIRA)

Jared Nagle created JBPORTAL-2497: ------------------------------------- Summary: CR1 jdk 1.8 (b106) fresh install standalone.bat hangs on "Starting" Key: JBPORTAL-2497 URL: https://issues.jboss.org/browse/JBPORTAL-2497 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jared Nagle When calling the standalone.bat from a fresh install of CR1 with JAVA_HOME set to jdk 1.8.0 (b106, 20th Sep 2013) the server hangs (seems to be in an infinite loop of some sort).. WARNING: JBOSS_HOME may be pointing to a different installation - unpredictable results may occur. JBOSS_HOME: "C:\JavaLibs\jboss-as-7.1.1.Final" Calling "C:\JavaLibs\wildfly-8.0.0.CR1\bin\standalone.conf.bat" Setting JAVA property to "C:\Program Files\Java\jdk1.8.0\bin\java" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: "C:\JavaLibs\jboss-as-7.1.1.Final" JAVA: "C:\Program Files\Java\jdk1.8.0\bin\java" JAVA_OPTS: "-XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" =============================================================================== Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0 20:23:08,464 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 20:23:08,596 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 20:23:08,634 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting and then it hangs. -- 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

12 years

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