November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2305) add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2305: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1019264|https://bugzilla.redhat.com/show_bug.cgi?id=1019264] Add-user script now supports --silent=true argument. We should update help message for the script and documentation as well, I'll create a BZs for this. Verified on EAP 6.2.0.ER7. > add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file. > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-2305 > URL: https://issues.jboss.org/browse/WFLY-2305 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Environment: WildFly snapshot of master 15-oct-2013 > Reporter: Tom Fonteyne > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Running add-user.sh in silent mode and redirecting the output to a file results in an exception: > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: No java.io.Console available to interact with user. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2305) add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2305: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1019264|https://bugzilla.redhat.com/show_bug.cgi?id=1019264] from ON_QA to VERIFIED > add-user utility reports "No java.io.Console available to interact with user." when used silently with su and piped to a file. > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-2305 > URL: https://issues.jboss.org/browse/WFLY-2305 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Environment: WildFly snapshot of master 15-oct-2013 > Reporter: Tom Fonteyne > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Running add-user.sh in silent mode and redirecting the output to a file results in an exception: > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: No java.io.Console available to interact with user. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1533) UT015005: Error invoking method requestDestroyed on listener class

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-1533?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-1533: ------------------------------------ We cannot get rid of SessionHolder thread local because we need to work around an incompatibility problem with some Servlet containers - see also WFLY-175. We also can't reattach the session-related contexts because we're not able to reassociate the request with a new session - i.e. request.getSession(true) currently doesn't return a new/valid session (and the Servlet spec is quite vague in this area). So the only thing we can do is to try to make a proper cleanup as much as possible and possibly log some warning message (and the full stack in debug level). > UT015005: Error invoking method requestDestroyed on listener class > ------------------------------------------------------------------- > > Key: WFLY-1533 > URL: https://issues.jboss.org/browse/WFLY-1533 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Alpha2, 8.0.0.Alpha4 > Reporter: Juergen Zimmermann > Assignee: Martin Kouba > Attachments: mojarra-2.1.zip, testcase-WFLY-1533.zip, testcase-wildfly-1533.zip > > > I'm using a WildFly snapshot with Undertow 1.0.0.Alpha19 and Weld 2.0.1.Final. I'm getting the following stacktrace: > 16:55:04,534 ERROR [io.undertow.servlet.request] UT015005: Error invoking method requestDestroyed on listener class org.jboss.weld.servlet.WeldListener: java.lang.IllegalStateException: UT000010: Session not found MDEkG_Aum5OlXUsjh11kGkh9 > at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:221) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:106) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:25) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at org.jboss.weld.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:13) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at org.jboss.weld.context.AbstractConversationContext.dissociate(AbstractConversationContext.java:161) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at org.jboss.weld.servlet.ConversationContextActivator.disassociateConversationContext(ConversationContextActivator.java:162) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at org.jboss.weld.servlet.HttpContextLifecycle.requestDestroyed(HttpContextLifecycle.java:159) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:91) [weld-core-impl-2.0.1.Final.jar:2013-06-03 10:29] > at io.undertow.servlet.core.ApplicationListeners.requestDestroyed(ApplicationListeners.java:196) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:159) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:114) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:90) [undertow-servlet-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:607) [undertow-core-1.0.0.Alpha19.jar:1.0.0.Alpha19] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2445) Upgrade mod_cluster to 1.3.0.Alpha2

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-2445: ------------------------------------ Summary: Upgrade mod_cluster to 1.3.0.Alpha2 Key: WFLY-2445 URL: https://issues.jboss.org/browse/WFLY-2445 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.Beta1 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Blocker Fix For: 8.0.0.CR1 See MODCLUSTER-367 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2199) There is AS7 instead of Wildfly on Projects page

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2199?page=com.atlassian.jira.plugin.... ] David Hladky commented on WFLY-2199: ------------------------------------ ORG-1850 created. > There is AS7 instead of Wildfly on Projects page > ------------------------------------------------ > > Key: WFLY-2199 > URL: https://issues.jboss.org/browse/WFLY-2199 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Hladky > Assignee: Jason Greene > Attachments: project-site.zip > > > Hi, in order to fix ORG-1814 I need the Wildfly web pages author to fill project properties file and tell me his URL, so I can add it to the web page. > More information (including example) can be found here: https://www.jboss.org/help/awestructguide (the last chapter). > Make sure it is a property file and not a link to a property file, that is in i-frame. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2199) There is AS7 instead of Wildfly on Projects page

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2199?page=com.atlassian.jira.plugin.... ] David Hladky commented on WFLY-2199: ------------------------------------ The icon must be added to a special sprite picture. I will ask our designers to do that. Please, let me know, when you deploy the property file, so I can set it. > There is AS7 instead of Wildfly on Projects page > ------------------------------------------------ > > Key: WFLY-2199 > URL: https://issues.jboss.org/browse/WFLY-2199 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Hladky > Assignee: Jason Greene > Attachments: project-site.zip > > > Hi, in order to fix ORG-1814 I need the Wildfly web pages author to fill project properties file and tell me his URL, so I can add it to the web page. > More information (including example) can be found here: https://www.jboss.org/help/awestructguide (the last chapter). > Make sure it is a property file and not a link to a property file, that is in i-frame. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2203) Error deploying multiple *-ds.xml files

by Isa Isa (JIRA)

[ https://issues.jboss.org/browse/WFLY-2203?page=com.atlassian.jira.plugin.... ] Isa Isa commented on WFLY-2203: ------------------------------- Hi I have added all my DS to the standalone.xml and it works fine. I will test multiple-ds after the next release > Error deploying multiple *-ds.xml files > --------------------------------------- > > Key: WFLY-2203 > URL: https://issues.jboss.org/browse/WFLY-2203 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Howes > Assignee: Stefano Maestri > Priority: Minor > Fix For: 8.0.0.Final > > > Our individual *-ds.xml datasources were all deploying fine in Alpha4 but in the Beta1 nightlies this error appears on startup: > {noformat} > 15:07:52,111 ERROR [org.jboss.msc.service] (MSC service thread 1-4) MSC000002: Invocation of listener "org.jboss.as.connector.subsystems.datasources.D > ataSourceStatisticsListener@7d18ac99" failed: java.lang.IllegalArgumentException: JBAS014742: A node is already registered at '(deployment => *)(subsy > stem => datasources)(data-source => *)(statistics => jdbc)' > at org.jboss.as.controller.registry.NodeSubregistry.register(NodeSubregistry.java:86) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1 > -SNAPSHOT] > at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:149) [wildfly-controller-8 > .0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.registry.AbstractResourceRegistration.registerSubModel(AbstractResourceRegistration.java:90) [wildfly-controller-8. > 0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.connector.subsystems.datasources.DataSourceStatisticsListener.transition(DataSourceStatisticsListener.java:72) [wildfly-connec > tor-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1533) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > {noformat} > Our datasource files look like this. I haven't tried putting all the datasource elements into one file. > {code} > <?xml version="1.0" encoding="UTF-8"?> > <datasources> > <datasource jndi-name="java:/AlphaDS" enabled="true" use-java-context="true" pool-name="AlphaDS"> > <connection-url>jdbc:oracle:thin://@db-host:1666/dev-db</connection-url> > <driver>oracle</driver> > <security> > <user-name>XXX</user-name> > <password>YYY</password> > </security> > <connection-property name="defaultNChar">true</connection-property> > </datasource> > </datasources> > {code} > {code} > <?xml version="1.0" encoding="UTF-8"?> > <datasources> > <datasource jndi-name="java:/BetaDS" enabled="true" use-java-context="true" pool-name="BetaDS"> > <connection-url>jdbc:oracle:thin://@db-host:1666/dev-db</connection-url> > <driver>oracle</driver> > <security> > <user-name>XXX</user-name> > <password>YYY</password> > </security> > <connection-property name="defaultNChar">true</connection-property> > </datasource> > </datasources> > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-322) Memory corruption using property reactivity in phreak

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-322: ---------------------------------- Summary: Memory corruption using property reactivity in phreak Key: DROOLS-322 URL: https://issues.jboss.org/browse/DROOLS-322 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mark Proctor This issue can be reproduced with the test case pasted below. Note that if you remove the @PropertyReactive annotation from the Hero class the test becomes green. More in detail the problem is caused by the fact that at some point, with property reactivity on, the method RuleNetworkEvaluator.doUpdatesReorderLeftMemory at line 802 tries to remove a leftTuple from an already empty memory causing the size to drop to -1 and then the memory corruption you found this morning. I believe that this is in turn caused by the fact that with property reactivity some updated staged left tuples are missing (because not propagated by the AlphaNode.modifyObject method at line 148) and this prevents the correct update of the memories. {code} @Test public void testWumpus() { String drl = "import org.drools.compiler.integrationtests.Misc2Test.Hero;\n" + "import org.drools.compiler.integrationtests.Misc2Test.StepForwardCommand;\n" + "import org.drools.compiler.integrationtests.Misc2Test.ChangeDirectionCommand;\n" + "\n" + "rule RotateLeft when\n" + " $h : Hero( goingRight == true )\n" + " $dc : ChangeDirectionCommand()\n" + "then\n" + " retract ( $dc ); \n" + " modify ( $h ) { setGoingRight( false ) };\n" + "end\n" + "\n" + "rule RotateRight when\n" + " $h : Hero( goingRight == false )\n" + " $dc : ChangeDirectionCommand()\n" + "then\n" + " retract ( $dc ); \n" + " modify ( $h ) { setGoingRight( true ) };\n" + "end\n" + "\n" + "rule StepLeft when\n" + " $h : Hero( goingRight == false )\n" + " $sc : StepForwardCommand()\n" + "then\n" + " retract ( $sc ); \n" + " modify ( $h ) { setPos( $h.getPos()-1 ) };\n" + "end\n" + "\n" + "rule StepRight when\n" + " $h : Hero( goingRight == true )\n" + " $sc : StepForwardCommand()\n" + "then\n" + " retract ( $sc );\n" + " modify ( $h ) { setPos( $h.getPos()+1 ) };\n" + "end\n"; KnowledgeBuilderConfiguration kbConf = KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(); KnowledgeBase kbase = loadKnowledgeBaseFromString( kbConf, drl ); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); Hero hero = new Hero(1); ksession.insert(hero); ksession.fireAllRules(); ksession.insert(new StepForwardCommand()); ksession.fireAllRules(); ksession.insert(new StepForwardCommand()); ksession.fireAllRules(); assertEquals(3, hero.getPos()); ksession.insert(new ChangeDirectionCommand()); ksession.fireAllRules(); ksession.insert(new StepForwardCommand()); ksession.fireAllRules(); assertEquals(2, hero.getPos()); } @PropertyReactive public static class Hero { private int pos = 1; private boolean goingRight = true; public Hero(int pos) { this.pos = pos; } public int getPos() { return pos; } public void setPos(int pos) { this.pos = pos; } public boolean isGoingRight() { return goingRight; } public void setGoingRight(boolean goingRight) { this.goingRight = goingRight; } } public static class ChangeDirectionCommand { } public static class StepForwardCommand { } {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-321) Unnecessary update using the TMS in EQUALITY mode

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-321: ---------------------------------- Summary: Unnecessary update using the TMS in EQUALITY mode Key: DROOLS-321 URL: https://issues.jboss.org/browse/DROOLS-321 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mark Proctor Having a class where some attributes are @key, but not all of them in EQUALITY mode it is possible to have a family of equivalent (by equality) facts which are not the same (by identity). The TMS will consider them equivalent, and use one of them as the "prime". When the justification for this prime fact goes away the second takes its place as prime. However if the SAME (by ID) fact was justified by two or more rules, there would be multiple entries in the list being the SAME by identity and the update would not be necessary. This is fixable in SimpleBeliefSystem by adding the condition: {code}&& node.getObject() != bfh.getObject(){code} at line 79 of the delete method. However other BeliefSystems need to be checked and fixed as well. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-319) "Unknown boolean operator" RuntimeException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-319?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-319: ------------------------------------ Could you please paste the stack trace of the Exception you got? > "Unknown boolean operator" RuntimeException > ------------------------------------------- > > Key: DROOLS-319 > URL: https://issues.jboss.org/browse/DROOLS-319 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Windows 8, java version "1.7.0_40" > Reporter: David Tombs > Assignee: Mark Proctor > > Steps to reproduce: > # Create a decision table with something like {{fooString != ""}} in the constraint and {{true}} in the rule cell. > # Execute the rule against a few objects. > Actual Result: > An internal Drools thread will crash with {{java.lang.RuntimeException: Unknown boolean operator}} when trying to compile {{fooString != "" == true}}. > Expected Result: > Even if an Exception is thrown, the currently-thrown exception is too low level and took me lots of investigation and debugging inside the drools code to figure out what I did wrong. -- 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, 6 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 November 2013