[JBoss JIRA] (WFCORE-3949) Cannot use server-file audit logger handler in JMX audit logging
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3949?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-3949:
---------------------------------
Steps to Reproduce:
# Start a domain mode
# enables the audit log at server level
{noformat}
/host=master/core-service=management/access=audit/server-logger=audit-log:write-attribute(name=enabled,value=true)
{noformat}
# Add the file-handler to the JMX audit loggin
{noformat}
/host=master/subsystem=jmx/configuration=audit-log:add()
/host=master/subsystem=jmx/configuration=audit-log/handler=server-file:add()
{noformat}
# reload the host master
{noformat}
/host=master:reload
{noformat}
was:
# Start a domain mode
# enables the audit log at server level
{noformat}
/host=master/core-service=management/access=audit/server-logger=audit-log:write-attribute(name=enabled,value=true)
{noformat}
# Add the file-handler to the JMX audit loggin
{noformat}
/host=master/subsystem=jmx/configuration=audit-log:add()
/host=master/subsystem=jmx/configuration=audit-log/handler=server-file:add()
{noformat}
# reload the host master
{noformat}
/host=mas:reload
{noformat}
> Cannot use server-file audit logger handler in JMX audit logging
> -----------------------------------------------------------------
>
> Key: WFCORE-3949
> URL: https://issues.jboss.org/browse/WFCORE-3949
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX, Logging
> Reporter: Yeray Borges
> Assignee: Yeray Borges
>
> When we are working in domain mode, we can register two kinds of audit logger handlers into JMX audit logging.
> Those predefined handlers are {{host-file}} handler, which has a log file relative to {{jboss.domain.data.dir}}, and {{server-file}} handler, which has a log file relative to {{jboss.server.data.dir}}.
> When we try to register {{server-file}} handler into JMX audit logging, its relative path cannot be resolved and when a log entry is written, we can see the following error log:
> {code:java}
> ERROR [org.jboss.as.controller.management-operation] (MSC service thread 1-1) WFLYCTL0037: Update of the management operation audit log failed in handler 'server-file': java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called 'jboss.server.data.dir'
> [Host Controller] at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110)
> [Host Controller] at org.jboss.as.controller.audit.AbstractFileAuditLogHandler.initialize(AbstractFileAuditLogHandler.java:62)
> [Host Controller] at org.jboss.as.controller.audit.AuditLogHandler.writeLogItem(AuditLogHandler.java:82)
> [Host Controller] at org.jboss.as.controller.audit.ManagedAuditLoggerImpl.writeLogItem(ManagedAuditLoggerImpl.java:266)
> [Host Controller] at org.jboss.as.controller.audit.ManagedAuditLoggerImpl.storeLogItem(ManagedAuditLoggerImpl.java:248)
> [Host Controller] at org.jboss.as.controller.audit.ManagedAuditLoggerImpl.logJmxMethodAccess(ManagedAuditLoggerImpl.java:122)
> [Host Controller] at org.jboss.as.jmx.PluggableMBeanServerImpl$LogAction.doLog(PluggableMBeanServerImpl.java:1281)
> [Host Controller] at org.jboss.as.jmx.PluggableMBeanServerImpl.log(PluggableMBeanServerImpl.java:1184)
> [Host Controller] at org.jboss.as.jmx.MBeanServerAuditLogRecordFormatter.log(MBeanServerAuditLogRecordFormatter.java:331)
> [Host Controller] at org.jboss.as.jmx.MBeanServerAuditLogRecordFormatter.registerMBean(MBeanServerAuditLogRecordFormatter.java:147)
> [Host Controller] at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:880)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$1.run(EnhancedQueueExecutor.java:385)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$1.run(EnhancedQueueExecutor.java:379)
> [Host Controller] at java.security.AccessController.doPrivileged(Native Method)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.<init>(EnhancedQueueExecutor.java:379)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$Builder.build(EnhancedQueueExecutor.java:671)
> [Host Controller] at org.jboss.as.controller.remote.AbstractModelControllerOperationHandlerFactoryService.start(AbstractModelControllerOperationHandlerFactoryService.java:112)
> [Host Controller] at org.jboss.as.host.controller.mgmt.MasterDomainControllerOperationHandlerService.start(MasterDomainControllerOperationHandlerService.java:90)
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> [Host Controller] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> [Host Controller] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> [Host Controller] at java.lang.Thread.run(Thread.java:748)
> {code}
> Registering a {{host-file}} does not throw any errors and work as expected. Althought there is a capability reference to jboss.server.data.dir in HostPathManagerService, when the handler is registered for JMX, jboss.server.data.dir cannot be resolved.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-2706:
------------------------------------------
[~ibek], what other assets besides rules will the scenario test then?
Regarding the name, I think the word "Test" needs to be there because users know what a "test" is intuitively, but "simulation" takes some thought and interpretation. A "simulation" and a "test" mean close to the same thing in this context, so we should opt for the clearer term, which imo is "test". And we should not say "simulation test" or "test simulator", which are redundant. As I understand it, this feature is a way to test that a scenario of conditions yields the expected results based on the rules user's have created. So because of that, *Rule Scenario Test* or just *Scenario Test* or frankly the existing name *Test Scenario* makes the most sense to me.
Is there any reason why we don't just leave this feature called *Test Scenario* as it is? Why do we need to change the name and why does everyone keep suggesting "simulation" as part of it? I assume I must be overlooking some aspect of this feature.
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10682) Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar
by Martin Styk (JIRA)
Martin Styk created WFLY-10682:
----------------------------------
Summary: Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar
Key: WFLY-10682
URL: https://issues.jboss.org/browse/WFLY-10682
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 13.0.0.Final
Reporter: Martin Styk
Assignee: Jeff Mesnil
Priority: Blocker
If standalone JMS client is using only jboss-client.jar on classpath then during look up of connection factory fails with:
{code}
java.lang.NoClassDefFoundError: javax/json/JsonValue
at org.apache.activemq.artemis.uri.schema.connector.TCPTransportConfigurationSchema.getTransportConfigurations(TCPTransportConfigurationSchema.java:68)
at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:44)
at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:33)
at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:86)
at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:30)
at org.apache.activemq.artemis.utils.uri.URIFactory.newObject(URIFactory.java:59)
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.newLocator(ServerLocatorImpl.java:411)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:209)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:202)
at org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory.<init>(ActiveMQJMSConnectionFactory.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.jboss.marshalling.reflect.SerializableClass.invokeConstructor(SerializableClass.java:340)
at org.jboss.marshalling.reflect.SerializableClass.callNoArgConstructor(SerializableClass.java:292)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1408)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at org.jboss.qa.artemis.test.client.ProducerJms11.sendMessages(ProducerJms11.java:27)
at org.jboss.qa.artemis.test.client.Producer.run(Producer.java:35)
at org.jboss.qa.artemis.test.client.Producer.sendAllSync(Producer.java:26)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2655:
-------------------------------------
[~manstis] [~tari_manga] I am checking the PR and has a question. Please follow my steps at first:
- Create a Decision node
- Then create InputData named *A*
- Then create InputData named *B*
- Then create connection B->Decision
- Then create connection A->Decision
- Then specify Decision node as a DecisionTable
And here is my question, should be the columns corresponding to InputData nodes sorted alphabetically? Currently the input columns will be sorted according to the order of connection creation. Long story short, currently input columns will be B, A. Wouldn't be better sort them alphabetically? I am not sure, so asking.
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
> h3. PR Manual Acceptance Test
> - Check Decision Table Decision node, with inputs (?)
> - Check Decision Table Decision node, without inputs
> - Check Non Decision Table Decision node, with inputs
> - Check Non Decision Table Decision node, without inputs
> - Check Decision Table BKM node, with inputs
> - Check Decision Table BKM node, without inputs
> - Check Non Decision Table BKM node, with inputs
> - Check Non Decision Table BKM node, without inputs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2655:
--------------------------------
Description:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
h3. PR Manual Acceptance Test
- Check Decision Table Decision node, with inputs (?)
- Check Decision Table Decision node, without inputs
- Check Non Decision Table Decision node, with inputs
- Check Non Decision Table Decision node, without inputs
- Check Decision Table BKM node, with inputs
- Check Decision Table BKM node, without inputs
- Check Non Decision Table BKM node, with inputs
- Check Non Decision Table BKM node, without inputs
was:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
h3. PR Manual Acceptance Test
- Check Decision Table Decision node, with inputs
- Check Decision Table Decision node, without inputs
- Check Non Decision Table Decision node, with inputs
- Check Non Decision Table Decision node, without inputs
- Check Decision Table BKM node, with inputs
- Check Decision Table BKM node, without inputs
- Check Non Decision Table BKM node, with inputs
- Check Non Decision Table BKM node, without inputs
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
> h3. PR Manual Acceptance Test
> - Check Decision Table Decision node, with inputs (?)
> - Check Decision Table Decision node, without inputs
> - Check Non Decision Table Decision node, with inputs
> - Check Non Decision Table Decision node, without inputs
> - Check Decision Table BKM node, with inputs
> - Check Decision Table BKM node, without inputs
> - Check Non Decision Table BKM node, with inputs
> - Check Non Decision Table BKM node, without inputs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2655:
--------------------------------
Description:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
h3. PR Manual Acceptance Test
- Check Decision Table Decision node, with inputs
- Check Decision Table Decision node, without inputs
- Check Non Decision Table Decision node, with inputs
- Check Non Decision Table Decision node, without inputs
- Check Decision Table BKM node, with inputs
- Check Decision Table BKM node, without inputs
- Check Non Decision Table BKM node, with inputs
- Check Non Decision Table BKM node, without inputs
was:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
> h3. PR Manual Acceptance Test
> - Check Decision Table Decision node, with inputs
> - Check Decision Table Decision node, without inputs
> - Check Non Decision Table Decision node, with inputs
> - Check Non Decision Table Decision node, without inputs
> - Check Decision Table BKM node, with inputs
> - Check Decision Table BKM node, without inputs
> - Check Non Decision Table BKM node, with inputs
> - Check Non Decision Table BKM node, without inputs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years