[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:
---------------------------------------------
Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1185118|https://bugzilla.redhat.com/show_bug.cgi?id=1185118] from NEW to POST
> 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)
11 years, 3 months
[JBoss JIRA] (WFCORE-48) EOFException when address of a mgmt operation is of a bad data type
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-48?page=com.atlassian.jira.plugin.... ]
Emmanuel Hugonnet commented on WFCORE-48:
-----------------------------------------
Wondering in a ModelOperation must have an OP attribute defined.
[~brian.stansberry] may you take a look at https://github.com/ehsavoie/wildfly-core/tree/WFCORE-48 that 'validates' the operation checking the OP_ADDRESS and OP.
> EOFException when address of a mgmt operation is of a bad data type
> -------------------------------------------------------------------
>
> Key: WFCORE-48
> URL: https://issues.jboss.org/browse/WFCORE-48
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ladislav Thon
> Assignee: Emmanuel Hugonnet
>
> (Hopefully this belongs to WildFly Core. If not, please move to WildFly.)
> I'm doing a programmatic invocation of a simple mgmt operation on the root mgmt resource, say e.g. {{:whoami}}. I'm doing this against a freshly built WildFly from master branch (commit {{e2b9ecfb}}) and on the client side, I'm depending on {{org.wildfly.core:wildfly-controller-client:1.0.0.Alpha4}}.
> The code looks like this:
> {code:java}
> ModelControllerClient client = ModelControllerClient.Factory.create("localhost", 9990);
> try {
> ModelNode op = new ModelNode();
> op.get(ClientConstants.OP).set("whoami");
> op.get(ClientConstants.OP_ADDR).set("");
> ModelNode result = client.execute(op);
> System.out.println(result);
> } finally {
> client.close();
> }
> {code}
> This fails with an exception like this:
> {code}
> Exception in thread "main" java.io.IOException: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at cz.ladicek.wildfly.ErrorReproducer.main(ErrorReproducer.java:17)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: java.util.concurrent.ExecutionException: Operation failed
> at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 7 more
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readByte(DataInputStream.java:267)
> at org.jboss.as.protocol.mgmt.ProtocolUtils.expectHeader(ProtocolUtils.java:83)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient$1.handleRequest(AbstractModelControllerClient.java:167)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:270)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleRequest(AbstractMessageHandler.java:235)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:113)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:56)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:84)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:452)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> However, when I remove the line that sets {{address}} ({{op.get(ClientConstants.OP_ADDR).set("");}}), it works just fine.
> Fine, I made a mistake, but getting an {{EOFException}}? That's hardly an appropriate response. I should get a proper failure ({{"outcome" => "failed"}} etc.).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3711) Topology updates of EJBClient ClusterContexts not being processed correctly after failover
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-3711?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz resolved WFLY-3711.
---------------------------------------
Fix Version/s: 9.0.0.Alpha1
Resolution: Done
Change was merged.
> Topology updates of EJBClient ClusterContexts not being processed correctly after failover
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-3711
> URL: https://issues.jboss.org/browse/WFLY-3711
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.Alpha1
>
>
> ClusterContexts are used by EJBClient to keep track of the current set of nodes in a cluster, so that if an EJBClient invocation fails on one node, it may failover to another node in the same cluster. The ClusterContext is made up of ClusterNodeManagers which are responsible for setting up the connections between the EJBClient and the nodes in the cluster.
> Cluster topology updates are sent to registered EJBClients whenever the cluster topology changes (nodes join, nodes leave a cluster). Thse topology updates are processed on the client side by ClusterTopologyUpdateHandler and are used to update the current contents of the associated ClusterContext held on the client.
> The current implementation of the handling of topology updates does not correctly handle the addition/removal of ClusterNodeManagers from the cluster context - namely, rather than check whether or not a new ClusterNodeManager really needs to be added, ClusterNodeManagers are added for every node in the received topology update, leading to many unnecessary EJBReceivers and their channels being created.
> The logs show that up to 18 cluster node manager instances may be created, have their EJBReceivers registered and channels to the remote node created, when only one node has been added to the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on WFLY-4171 at 1/29/15 11:23 AM:
-------------------------------------------------------------
So now it looks pretty good overall. There are still a couple minor issues though, but they're the last ones.
- Unnecessary @suppresswarnings(unused) on the java ee webapp Resources.java
- none of the WEB-INF/templates/default.xhtml files are filtered. Leaving :
** in javaee7 webapp : {noformat}<title>${artifactId}</title>{noformat}
** in javaee7 ear webapp : {noformat}<title>${rootArtifactId}</title>{noformat}
was (Author: fbricon):
So now it looks pretty good overall. There are still a couple minor issues though, but they're the last ones.
- Unnecessary @suppresswarnings(unused) on the java ee webapp Resources.java
- none of the WEB-INF/templates/default.xhtml files are filtered. Leaving :
** {noformat}<title>${artifactId}</title>{noformat}
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on WFLY-4171:
-----------------------------------
So now it looks pretty good overall. There are still a couple minor issues though, but they're the last ones.
- Unnecessary @suppresswarnings(unused) on the java ee webapp Resources.java
- none of the WEB-INF/templates/default.xhtml files are filtered. Leaving :
** {noformat}<title>${artifactId}</title>{noformat}
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (SECURITY-772) SPNEGOLoginModule does not always respect removeRealmFromPrincipal
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SECURITY-772?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on SECURITY-772:
--------------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1039989|https://bugzilla.redhat.com/show_bug.cgi?id=1039989] from MODIFIED to ON_QA
> SPNEGOLoginModule does not always respect removeRealmFromPrincipal
> ------------------------------------------------------------------
>
> Key: SECURITY-772
> URL: https://issues.jboss.org/browse/SECURITY-772
> Project: PicketBox
> Issue Type: Bug
> Components: Negotiation
> Affects Versions: Negotiation_2_2_6
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
> Priority: Minor
> Fix For: Negotiation_2_2_7
>
>
> org.jboss.security.negotiation.spnego.SPNEGOLoginModule
> private class AcceptSecContext:
> if (gssContext.isEstablished())
> {
> log.warn("Authentication was performed despite already being authenticated!");
> // TODO - Refactor to only do this once.
> setIdentity(new KerberosPrincipal(gssContext.getSrcName().toString()));
> The last line should obey the "removeRealmFromPrincipal" flag similarly as a bit further down:
> setIdentity(createIdentity(gssContext.getSrcName().toString()));
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-701:
------------------------------------
No problem, it's far better to have a duplicated error report than a uncaught bug :)
Thanks a lor for your unvaluable help.
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Matteo Mortari commented on DROOLS-701:
---------------------------------------
Good news - sorry "suggestimate" looks like only to pull possible duplicate from JIRA, not RH's bugzilla ...but to be honest also this case would have been too different descriptions for me to notice =)
Sorry and thanks again.
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4298) DatabaseServerLoginModule doesn't support SHA-512 with Java 8
by Markus Eisele (JIRA)
Markus Eisele created WFLY-4298:
-----------------------------------
Summary: DatabaseServerLoginModule doesn't support SHA-512 with Java 8
Key: WFLY-4298
URL: https://issues.jboss.org/browse/WFLY-4298
Project: WildFly
Issue Type: Feature Request
Components: Security
Affects Versions: 8.2.0.Final
Environment: Win 7, x64
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Reporter: Markus Eisele
Assignee: Darran Lofthouse
I tried to use the following security domain configuration:
<security-domain name="secureDomain" cache-type="default">
<authentication>
<login-module code="Database" flag="required">
<module-option name="dsJndiName" value="java:jboss/datsources/MySQLTestDS"/>
<module-option name="principalsQuery" value="SELECT password FROM user WHERE email=?"/>
<module-option name="rolesQuery" value="select role, 'Roles' from role where email=?"/>
<module-option name="hashAlgorithm" value="SHA-512"/>
<module-option name="hashEncoding" value="base64"/>
</login-module>
</authentication>
</security-domain>
And never got a user successfully authenticated. Works with hashAlgorithm SHA-256
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months