[JBoss JIRA] (WFLY-73) NPE in RootResourceIterator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-73?page=com.atlassian.jira.plugin.sy... ]
RH Bugzilla Integration commented on WFLY-73:
---------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1185118|https://bugzilla.redhat.com/show_bug.cgi?id=1185118] from POST to MODIFIED
> NPE in RootResourceIterator
> ---------------------------
>
> Key: WFLY-73
> URL: https://issues.jboss.org/browse/WFLY-73
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> Intermittent testsuite failures, e.g.
> http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
> Log shows this repeatedly:
> [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> RootResourceIterator.doIterate is reading the resource twice:
> {code}
> for (ResourceEntry entry : current.getChildren(type)) {
> final PathElement pathElement = entry.getPathElement();
> final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
> final PathAddress childAddress = address.append(pathElement);
> doIterate(child, childAddress);
> }
> {code}
> The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFCORE-523) wildfly-init-redhat.sh should touch /var/lock/subsys/wildfly for properly shutdown
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-523?page=com.atlassian.jira.plugin... ]
Kabir Khan closed WFCORE-523.
-----------------------------
Fix Version/s: 1.0.0.Alpha17
Resolution: Done
> wildfly-init-redhat.sh should touch /var/lock/subsys/wildfly for properly shutdown
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-523
> URL: https://issues.jboss.org/browse/WFCORE-523
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 1.0.0.Alpha16
> Environment: CentOS 6.6
> Reporter: Kohei Nozaki
> Assignee: Tomaz Cerar
> Fix For: 1.0.0.Alpha17
>
>
> When I shutdown CentOS, it doesn't wait for complete shutdown of WildFly. I see that server.log doesn't end with `JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 437ms` at shutdown of CentOS. also there's no message which indicates that processing of WildFly shutdown (e.g. Stopping wildfly...). it seems like that shutdown script was not invoked and CentOS killed the process of WildFly.
> It's not good for embedded database that requires shutdown properly. I have a embedded Derby within WildFly and it needs properly shutdown for every time to avoid data corruption.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (ELY-141) Add a Credential to Name Resolver SPI
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-141:
------------------------------------
Summary: Add a Credential to Name Resolver SPI
Key: ELY-141
URL: https://issues.jboss.org/browse/ELY-141
Project: WildFly Elytron
Issue Type: Feature Request
Components: API / SPI
Reporter: Darran Lofthouse
Fix For: 1.0.0.Alpha1
We are predominantly considering this in the context of the validation side of the API.
However should still not exclude the possibility that after obtaining a RealmIdentity the validation may still be performed in the mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFCORE-528) ServerService and ServerShutdownHandler are not embedded-friendly
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-528:
---------------------------------------
Summary: ServerService and ServerShutdownHandler are not embedded-friendly
Key: WFCORE-528
URL: https://issues.jboss.org/browse/WFCORE-528
Project: WildFly Core
Issue Type: Enhancement
Reporter: Brian Stansberry
Assignee: Brian Stansberry
ServerService and ServerShutdownHandler are both unfriendly to embedding as they call System.exit (in the case of ServerService only in the case of critical boot failures.)
Simplest fix is to use SystemExiter and have the embedded server code swap in an approproite Exiter. Only thing I don't like about that is SystemExiter is base on static fields and seems to have been written for testing.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFLY-3078) directory-grouping configuration is not getting persisted via CLI when no servers defined
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3078?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3078:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1073715|https://bugzilla.redhat.com/show_bug.cgi?id=1073715] from VERIFIED to CLOSED
> directory-grouping configuration is not getting persisted via CLI when no servers defined
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-3078
> URL: https://issues.jboss.org/browse/WFLY-3078
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Environment: All Operating System
> Reporter: Jay Kumar SenSharma
> Assignee: Emanuel Muckenhuber
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> - If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml
> {code}
> /host=master/:write-attribute(name=directory-grouping,value=by-type)
> {code}
> - The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (DROOLS-703) Add ability to see more text in a text field using a textarea or other multi-line wrapping capability
by Stephen Slaboda (JIRA)
Stephen Slaboda created DROOLS-703:
--------------------------------------
Summary: Add ability to see more text in a text field using a textarea or other multi-line wrapping capability
Key: DROOLS-703
URL: https://issues.jboss.org/browse/DROOLS-703
Project: Drools
Issue Type: Enhancement
Affects Versions: 6.1.0.Final
Environment: RedHat 6.3 Linux x86_64; Firefox 10.0.5
Reporter: Stephen Slaboda
Assignee: Mark Proctor
Currently, if we want to assemble a string in a formula text field using various bound variables, the full text being constructed does not display all at once. The size of the box forces you to scroll around or copy/paste to see all the text after you get to a few dozen characters. We like to be somewhat verbose in our naming of variables to offer more clarity, so in some cases the text field may do this even when using a single variable name. Perhaps there could be a way to wrap the text into a multi-line display so that it is easier to edit these fields?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match
by Davide Sottara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ]
Davide Sottara edited comment on DROOLS-702 at 2/1/15 12:42 PM:
----------------------------------------------------------------
Yacine,
"from" leads to this situation:
{code}
$p : Person( ... )
Person( ... ) from $p
{code}
This ensures that both patterns are applied to the same object.
In fact, the second will only be applied id an object passes the first.
unification is effectively an equality constraint:
{code}
$p Person( ... )
Person( this == $p, ... )
{code}
so it may even match two different objects that are equal to each other.
Pick the one that you prefer based on your actual use case
was (Author: dsotty):
Yacine,
"from" leads to this situation:
{code}
$p : Person( ... )
Person( ... ) from $p
{code}
This ensures that both patterns are applied to the same object.
In fact, the second will only be applied id an object passes the first.
unification is effectively an equality constraint:
{code}
$p Person()
Person( this == $p )
{code}
so it may even match two different objects that are equal to each other.
Pick the one that you prefer based on your actual use case
> Rule Inheritance fired the sub rule even the condition doen't match
> -------------------------------------------------------------------
>
> Key: DROOLS-702
> URL: https://issues.jboss.org/browse/DROOLS-702
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Environment: Windows, Java6.0.29
> Reporter: Yacine Jaber
> Assignee: Davide Sottara
> Priority: Critical
> Attachments: wod-drools-test.7z
>
>
> You can find the attached a simple maven project that shows this error.
> You can run ExampleDrools class as main java application.
> The sub rules are fired even if the condition is not matched.
> There are a work arround by using <from $fact> into a sub rule to avoid firing this one.
> This simple project shows the failed and work arround test.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month