[JBoss JIRA] (WFCORE-1718) Handlers within Audit Logger are not removed properly when Audit Logger is removed
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1718?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1718:
------------------------------------------
This can be fixed by having AuditLogLoggerRemoveHandler extend AbstractRemoveStepHandler.
However, as part of doing this we need to review the use of AuditLogLoggerResourceDefinition.createHostServerDefinition. The only use I see of that, the same auditLogger instance is passed to it as is passed to AuditLogLoggerResourceDefinition.createDefinition. So the same logger gets passed to two resources, in one case with 'executeRuntime=true' and another time with 'executeRuntime=false'. In both cases the add handler performs at least some sort of modification of the auditLogger, with executeRuntime controlling exactly what. And in both cases the remove handler is modifying the audit logger. This just seems a bit odd. Intuitively I'd think the AuditLogLoggerResourceDefinition.createHostServerDefinition would not involve any runtime modification at all as the resource is just storing config data on the HC for its use in configuring a server.
> Handlers within Audit Logger are not removed properly when Audit Logger is removed
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-1718
> URL: https://issues.jboss.org/browse/WFCORE-1718
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha5
> Reporter: Jan Tymel
> Assignee: Brian Stansberry
>
> If Audit Logger is removed, destination handlers (i.e. its child nodes) are not removed properly. They are not present in the config file. They seem to be not removed "internally" though. This leads to a couple of issues:
> 1. It is not possible to remove referenced File/Syslog handlers. If user tries to remove them the _NullPointerException_ is given as a result. Try following commands:
> {{/core-service=management/access=audit/file-handler=file:remove()}}
> {{/core-service=management/access=audit/syslog-handler=my-syslog-handler:remove()}}
> Their output is:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
> "rolled-back" => true
> }
> {code}
> 2. AuditLog continues to send auditable events to previously referenced File/Syslog handlers.
> * Create auditable event (e.g. {{/subsystem=logging/logger=com.arjuna:write-attribute(name=level,value=DEBUG)}})
> * See log in the file (WILDFLY_HOME/standalone/data/audit-log.log)
> * See log in the syslog (/var/log/messages)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1721) ConfigurationPersister problems in successfulBoot() should not be able to abort boot
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1721?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1721:
-------------------------------------
Summary: ConfigurationPersister problems in successfulBoot() should not be able to abort boot (was: ConfigurationPersister problems in successfulBoot() should be able to affect boot)
> ConfigurationPersister problems in successfulBoot() should not be able to abort boot
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1721
> URL: https://issues.jboss.org/browse/WFCORE-1721
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
>
> This error (reported in a testsuite run) should not have the effect:
> {code}
> 17:31:30,743 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0082: Failed to create backup copies of configuration file C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:514)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
> at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:455)
> at org.jboss.as.server.ServerService.boot(ServerService.java:366)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\standalone.boot.xml: The process cannot access the file because it is being used by another process.
> at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
> at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
> at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
> at java.nio.file.Files.copy(Files.java:1274)
> at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:78)
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:512)
> ... 5 more
> 17:31:30,744 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> WFCORE-1501 dealt with a similar problem.
> This needs a bit of caution, to ensure that we still fail boot on failures that are more substantial than problems creating the history folder stuff. Think about stuff like read-only-config cases where we need to make sure that a reload op will be able to function properly. That caveat probably should have been applied to my WFCORE-1501 work as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service
by Anton Yudin (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ]
Anton Yudin edited comment on WFCORE-1719 at 8/17/16 11:54 AM:
---------------------------------------------------------------
I just found out that the service starts successfully after the DESCRIPTION fix, but it is impossible to stop the service. One have to kill java process to stop the service.
Could you please look at it?
There is nothing in the server.log file after attempting to stop the service.
And this is what is in the service.log
[2016-08-17 11:47:25] [info] [ 6872] Commons Daemon procrun (1.0.15.0 64-bit) started
[2016-08-17 11:47:25] [info] [ 6872] Running 'Wildfly' Service...
[2016-08-17 11:47:25] [info] [ 9660] Starting service...
[2016-08-17 11:47:25] [info] [ 9660] Service started in 7 ms.
[2016-08-17 11:48:46] [info] [ 9636] Stopping service...
Windows reports the status of the service as "Stopping".
Thanks.
was (Author: antonyudin):
I just found out that the service starts successfully after the DESCRIPTION fix, but it is impossible to stop the service. One have to kill java process to stop the service.
Could you please look at it?
There is nothing in the server.log file.
And this is what is in the service.log
[2016-08-17 11:47:25] [info] [ 6872] Commons Daemon procrun (1.0.15.0 64-bit) started
[2016-08-17 11:47:25] [info] [ 6872] Running 'Wildfly' Service...
[2016-08-17 11:47:25] [info] [ 9660] Starting service...
[2016-08-17 11:47:25] [info] [ 9660] Service started in 7 ms.
[2016-08-17 11:48:46] [info] [ 9636] Stopping service...
Windows reports the status of the service as "Stopping".
Thanks.
> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
> Key: WFCORE-1719
> URL: https://issues.jboss.org/browse/WFCORE-1719
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.2.0.Final
> Environment: Windows 8/Windows Server 2012
> Oracle Java 8
> Reporter: Anton Yudin
> Assignee: Tomaz Cerar
> Fix For: 3.0.0.Alpha6
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error:
> Incorrect function.
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
> <EventID Qualifiers="49152">7024</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8080000000000000</Keywords>
> <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
> <EventRecordID>196500</EventRecordID>
> <Correlation/>
> <Execution ProcessID="668" ThreadID="10184"/>
> <Channel>System</Channel>
> <Computer>ITPC7.intra.rfgh.net</Computer>
> <Security/>
> </System>
> -
> <EventData>
> <Data Name="param1">Wildfly</Data>
> <Data Name="param2">%%1</Data>
> <Binary>570069006C00640066006C0079000000</Binary>
> </EventData>
> </Event>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service
by Anton Yudin (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ]
Anton Yudin commented on WFCORE-1719:
-------------------------------------
I just found out that the service starts successfully after the DESCRIPTION fix, but it is impossible to stop the service. One have to kill java process to stop the service.
Could you please look at it?
There is nothing in the server.log file.
And this is what is in the service.log
[2016-08-17 11:47:25] [info] [ 6872] Commons Daemon procrun (1.0.15.0 64-bit) started
[2016-08-17 11:47:25] [info] [ 6872] Running 'Wildfly' Service...
[2016-08-17 11:47:25] [info] [ 9660] Starting service...
[2016-08-17 11:47:25] [info] [ 9660] Service started in 7 ms.
[2016-08-17 11:48:46] [info] [ 9636] Stopping service...
Windows reports the status of the service as "Stopping".
Thanks.
> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
> Key: WFCORE-1719
> URL: https://issues.jboss.org/browse/WFCORE-1719
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.2.0.Final
> Environment: Windows 8/Windows Server 2012
> Oracle Java 8
> Reporter: Anton Yudin
> Assignee: Tomaz Cerar
> Fix For: 3.0.0.Alpha6
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error:
> Incorrect function.
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
> <EventID Qualifiers="49152">7024</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8080000000000000</Keywords>
> <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
> <EventRecordID>196500</EventRecordID>
> <Correlation/>
> <Execution ProcessID="668" ThreadID="10184"/>
> <Channel>System</Channel>
> <Computer>ITPC7.intra.rfgh.net</Computer>
> <Security/>
> </System>
> -
> <EventData>
> <Data Name="param1">Wildfly</Data>
> <Data Name="param2">%%1</Data>
> <Binary>570069006C00640066006C0079000000</Binary>
> </EventData>
> </Event>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1721) ConfigurationPersister problems in successfulBoot() should be able to affect boot
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1721:
----------------------------------------
Summary: ConfigurationPersister problems in successfulBoot() should be able to affect boot
Key: WFCORE-1721
URL: https://issues.jboss.org/browse/WFCORE-1721
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
This error (reported in a testsuite run) should not have the effect:
{code}
17:31:30,743 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0082: Failed to create backup copies of configuration file C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:514)
at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:455)
at org.jboss.as.server.ServerService.boot(ServerService.java:366)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\standalone.boot.xml: The process cannot access the file because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
at java.nio.file.Files.copy(Files.java:1274)
at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:78)
at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:512)
... 5 more
17:31:30,744 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{code}
WFCORE-1501 dealt with a similar problem.
This needs a bit of caution, to ensure that we still fail boot on failures that are more substantial than problems creating the history folder stuff. Think about stuff like read-only-config cases where we need to make sure that a reload op will be able to function properly. That caveat probably should have been applied to my WFCORE-1501 work as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1721) ConfigurationPersister problems in successfulBoot() should be able to affect boot
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1721?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1721:
----------------------------------------
Assignee: (was: Brian Stansberry)
> ConfigurationPersister problems in successfulBoot() should be able to affect boot
> ---------------------------------------------------------------------------------
>
> Key: WFCORE-1721
> URL: https://issues.jboss.org/browse/WFCORE-1721
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
>
> This error (reported in a testsuite run) should not have the effect:
> {code}
> 17:31:30,743 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0082: Failed to create backup copies of configuration file C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:514)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
> at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:455)
> at org.jboss.as.server.ServerService.boot(ServerService.java:366)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\standalone.boot.xml: The process cannot access the file because it is being used by another process.
> at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
> at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
> at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
> at java.nio.file.Files.copy(Files.java:1274)
> at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:78)
> at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:512)
> ... 5 more
> 17:31:30,744 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> WFCORE-1501 dealt with a similar problem.
> This needs a bit of caution, to ensure that we still fail boot on failures that are more substantial than problems creating the history folder stuff. Think about stuff like read-only-config cases where we need to make sure that a reload op will be able to function properly. That caveat probably should have been applied to my WFCORE-1501 work as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6968) https-listener does not support proxy-address-forwarding
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-6968:
---------------------------------
Summary: https-listener does not support proxy-address-forwarding
Key: WFLY-6968
URL: https://issues.jboss.org/browse/WFLY-6968
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Affects Versions: 9.0.2.Final, 10.0.0.Final
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
HttpsListenerService explicitly passes false to its superclass for proxyAddressForwarding and certificateForwarding, making it impossible to enable these features. For a security-sensitive application, we need a secure connection from our proxy to WildFly and we need WildFly to respect the headers sent by our proxy. It seems easy to support these options by reading them in HttpsListenerAdd and passing them to HttpsListenerService, which can simply pass them to the super constructor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1235) MBean naming rework
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1235?page=com.atlassian.jira.plugi... ]
Matteo Mortari edited comment on DROOLS-1235 at 8/17/16 9:24 AM:
-----------------------------------------------------------------
To recap:
h6. droolsjbpm-knowledge
* Perform necessary Public KIE API changes for allowing API users to
specify an optional, unique, container ID.
* KieContainer MBean public Kie API on already existing package dedicated for this purpose.
h6. drools
* give KieContainer an optional user defined name
* KieContainer MBean and various refactorings.
* jargon: containerId
* jargon: configuredReleaseId, resolvedReleaseId
* unit testing
* assuming the containerId can be "recycled" on dispose.
* introducing test for KieServices API with containerId.
* avoid using lock and leverage ConcurrentMap without java8
* fixing objectname conventions
* there are a few call to internal api / manual call to the implementation
constructor new KieContainerImpl from kie-wb-common, optaplanner, etc.
Original constructor marked with deprecation flag and javadoc notice on all constructors.
h6. droolsjbpm-integration
* KieServer cascade containerId while creating via KieServices
h6. kie-docs
* Including an entry for this on the release notes, as requested.
was (Author: tari_manga):
To recap:
h6. droolsjbpm-knowledge
* Perform necessary Public KIE API changes for allowing API users to
specify an optional, unique, container ID.
h6. drools
* give KieContainer an optional user defined name
* KieContainer MBean and various refactorings.
* jargon: containerId
* jargon: configuredReleaseId, resolvedReleaseId
* unit testing
* assuming the containerId can be "recycled" on dispose.
* introducing test for KieServices API with containerId.
* avoid using lock and leverage ConcurrentMap without java8
* fixing objectname conventions
* there are a few call to internal api / manual call to the implementation
constructor new KieContainerImpl from kie-wb-common, optaplanner, etc.
Original constructor marked with deprecation flag and javadoc notice on all constructors.
h6. droolsjbpm-integration
* KieServer cascade containerId while creating via KieServices
h6. kie-docs
* Including an entry for this on the release notes, as requested.
> MBean naming rework
> -------------------
>
> Key: DROOLS-1235
> URL: https://issues.jboss.org/browse/DROOLS-1235
> Project: Drools
> Issue Type: Sub-task
> Components: core engine, kie server
> Affects Versions: 6.4.0.Final
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Fix For: 6.5.0.Final, 7.0.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months