January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding

by dfisher (JIRA)

dfisher created WFLY-2836: ----------------------------- Summary: http-listener requires 'https' socket-binding Key: WFLY-2836 URL: https://issues.jboss.org/browse/WFLY-2836 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 8.0.0.CR1, 8.0.0.Final Reporter: dfisher Assignee: Stuart Douglas Priority: Minor Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https". The following error is produced attempting to configure wildfly without https: {code} ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([ ("subsystem" => "undertow"), ("server" => "default-server"), ("http-listener" => "default") ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]} {code} I believe this constant is defined in ListenerResourceDefinition on line 80. If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2835) Session draining broken: requests counting broken on load-balancer

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-2835: ------------------------------------ Summary: Session draining broken: requests counting broken on load-balancer Key: WFLY-2835 URL: https://issues.jboss.org/browse/WFLY-2835 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.CR1 Reporter: Radoslav Husar Assignee: Radoslav Husar See all details at MODCLUSTER-383. Tracker bug, so that this gets into the realease notes as known issue if it doesn't get fixed for final. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2834) Remove 'org.jboss.as.domain.management.security.util.MSCTestRunner' class.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2834: -------------------------------------- Summary: Remove 'org.jboss.as.domain.management.security.util.MSCTestRunner' class. Key: WFLY-2834 URL: https://issues.jboss.org/browse/WFLY-2834 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Final The class 'org.jboss.as.domain.management.security.util.MSCTestRunner' was never actually used so should not have been committed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2490) Connecting using https-remoting times out and leaves thread within CLI spinning at 100%

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2490?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-2490. ------------------------------------ Resolution: Done With the most recent XNIO update this is no longer an issue. > Connecting using https-remoting times out and leaves thread within CLI spinning at 100% > --------------------------------------------------------------------------------------- > > Key: WFLY-2490 > URL: https://issues.jboss.org/browse/WFLY-2490 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > HTTP Upgrade is not fully working when SSL is enabled, other tasks will address that but this issue is about the CLI connecting to a server where HTTP Upgrade is not possible - a thread within the CLI is left running at 100% even after connecting has timed out. > {noformat} > [disconnected /] connect https-remoting://localhost:9993 > The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out > {noformat} > Connecting to the HTTP port where HTTP Upgrade is not available also results in a time out connecting rather than an early failure but does not result in the thread spinning at 100% > {noformat} > [disconnected /] connect http-remoting://localhost:9990 > The controller is not available at localhost:9990: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2289) deployed webapp before mod_cluster httpd discovery aren't see by httpd.

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/WFLY-2289?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere resolved WFLY-2289. --------------------------------------- Fix Version/s: 8.0.0.Final Resolution: Done It looks fixed now. > deployed webapp before mod_cluster httpd discovery aren't see by httpd. > ----------------------------------------------------------------------- > > Key: WFLY-2289 > URL: https://issues.jboss.org/browse/WFLY-2289 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 8.0.0.Final > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2778) CPU load at 99% with WildFly 8 CR1

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2778?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-2778. ------------------------------- Fix Version/s: 8.0.0.Final Resolution: Done Tnx Matthias for confirming that it works now. > CPU load at 99% with WildFly 8 CR1 > ---------------------------------- > > Key: WFLY-2778 > URL: https://issues.jboss.org/browse/WFLY-2778 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: $ java -version > java version "1.7.0_45" > Java(TM) SE Runtime Environment (build 1.7.0_45-b18) > Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) > WildFly 8.0.0.CR1 > XNIO version 3.2.0.Beta4 > Undertow 1.0.0.Beta30 > Reporter: Matthias Richter > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 8.0.0.Final > > Attachments: stacktrace-6156.out, stacktrace-6157.out, stacktrace-6158.out, stacktrace-new.out > > > After Undertow included https forwarding features when shipped with Wildfly CR1, we experienced high cpu load on our machines, reproduced on 5 different servers. Up to 3 threads are running wild, sometimes it's just one thread though. On the forum reference there are screenshots from jconsole including stacktraces of the threads. > https://community.jboss.org/message/853569#853569 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2778) CPU load at 99% with WildFly 8 CR1

by Matthias Richter (JIRA)

[ https://issues.jboss.org/browse/WFLY-2778?page=com.atlassian.jira.plugin.... ] Matthias Richter commented on WFLY-2778: ---------------------------------------- Well, up until now we cannot see the issue again, seems to be working! We'll keep the instance running and observe its behavior. Thanks for your work, guys. > CPU load at 99% with WildFly 8 CR1 > ---------------------------------- > > Key: WFLY-2778 > URL: https://issues.jboss.org/browse/WFLY-2778 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: $ java -version > java version "1.7.0_45" > Java(TM) SE Runtime Environment (build 1.7.0_45-b18) > Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) > WildFly 8.0.0.CR1 > XNIO version 3.2.0.Beta4 > Undertow 1.0.0.Beta30 > Reporter: Matthias Richter > Assignee: Stuart Douglas > Priority: Blocker > Attachments: stacktrace-6156.out, stacktrace-6157.out, stacktrace-6158.out, stacktrace-new.out > > > After Undertow included https forwarding features when shipped with Wildfly CR1, we experienced high cpu load on our machines, reproduced on 5 different servers. Up to 3 threads are running wild, sometimes it's just one thread though. On the forum reference there are screenshots from jconsole including stacktraces of the threads. > https://community.jboss.org/message/853569#853569 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-418) MVEL Unable to resolve method exception on fact update

by Nedo Nedic (JIRA)

[ https://issues.jboss.org/browse/DROOLS-418?page=com.atlassian.jira.plugin... ] Nedo Nedic commented on DROOLS-418: ----------------------------------- I tried it with 5.6.0 Final and it fails with same exception. > MVEL Unable to resolve method exception on fact update > ------------------------------------------------------ > > Key: DROOLS-418 > URL: https://issues.jboss.org/browse/DROOLS-418 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > Jboss 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Attachments: Classifier.xls > > > The following rule will fail with an exception after update is called on a fact: > rule "Classifier" > no-loop true > salience 65430 > when > $sn:Snort(sig_priority == "1", type == null) > then > $sn.setType("LOW"); > update($sn); > end > Snort fact type declaration: > declare Snort > @role( event ) > @timestamp( event_date ) > @expires( 1h ) > dport: String > data: String > sport: String > hostname: String > type: String > sig_priority: String > sensor: String > id: java.lang.Long > sig_class_name: String > ip_dst: String > sig_name: String > event_date: java.util.Date > ip_src: String > end > [Error: unable to resolve method: java.util.ArrayList.type() [arglength=0]] > [Near : {... type == "LOW" ....}] > ^ > [Line: 1, Column: 1] > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1071) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:980) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanProperty(ReflectiveAccessorOptimizer.java:670) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanPropertyAO(ReflectiveAccessorOptimizer.java:465) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:370) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140) > at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159) > at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) > at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:114) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:73) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:52) > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:218) > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:175) > at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:655) > at org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:594) > at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:364) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:371) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:327) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:950) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:894) > at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2833) data-source:enalbe and datasource:write-attribute(name=enabled, value=true) should have same result

by Stefano Maestri (JIRA)

Stefano Maestri created WFLY-2833: ------------------------------------- Summary: data-source:enalbe and datasource:write-attribute(name=enabled, value=true) should have same result Key: WFLY-2833 URL: https://issues.jboss.org/browse/WFLY-2833 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: JCA Affects Versions: 8.0.0.CR1 Reporter: Stefano Maestri Assignee: Stefano Maestri Currently enabled attribute always require a reload, while it should provide same functionalyity of :enable (and symmetric :disable operation) enabling/disabling datasource runtime. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2782) Testsuite leaks remoting endpoints by not closing JMXConnector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2782?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2782: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1055912|https://bugzilla.redhat.com/show_bug.cgi?id=1055912] from ON_QA to VERIFIED > Testsuite leaks remoting endpoints by not closing JMXConnector > -------------------------------------------------------------- > > Key: WFLY-2782 > URL: https://issues.jboss.org/browse/WFLY-2782 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Whereever JMXConnectorFactory.connect() is called, the resulting JMXConnector should be closed -- 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, 3 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 January 2014