[JBoss JIRA] (WFLY-12083) Deployment failure if an explicit bean archive contain a Pojo with @NotNull annotation
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12083?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12083:
-----------------------------------------
[~guillaume.smet] Any thoughts on this one?
> Deployment failure if an explicit bean archive contain a Pojo with @NotNull annotation
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12083
> URL: https://issues.jboss.org/browse/WFLY-12083
> Project: WildFly
> Issue Type: Bug
> Components: Bean Validation
> Affects Versions: 17.0.0.Alpha1
> Reporter: Joerg Baesner
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: playground.zip
>
>
> If an exlicit bean archive ({{META-INF}} contains an empty {{beans.xml}}) contain a Pojo without any Bean defining annotations and it has {{@NotNull}} annotations, the deployment of that module fails with:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."playground-jar.jar".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."playground-jar.jar".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001436: Type org.jboss.playground.PlaygroundToStringUtil is not proxyable because it has a private constructor [EnhancedAnnotatedConstructorImpl] private org.jboss.playground.PlaygroundToStringUtil() - class org.jboss.playground.PlaygroundToStringUtil.
> at org.jboss.weld.injection.producer.InterceptionModelInitializer.init(InterceptionModelInitializer.java:117)
> at org.jboss.weld.injection.producer.BeanInjectionTarget.buildInterceptionModel(BeanInjectionTarget.java:94)
> at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeInterceptionModel(BeanInjectionTarget.java:89)
> at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeAfterBeanDiscovery(BeanInjectionTarget.java:99)
> at org.jboss.weld.injection.producer.InjectionTargetInitializationContext.initialize(InjectionTargetInitializationContext.java:42)
> at org.jboss.weld.injection.producer.InjectionTargetService.initialize(InjectionTargetService.java:63)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:481)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> ... 6 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12086) Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12086?page=com.atlassian.jira.plugin... ]
Scott Marlow updated WFLY-12086:
--------------------------------
Priority: Blocker (was: Major)
> Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12086
> URL: https://issues.jboss.org/browse/WFLY-12086
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 17.0.0.Beta1
>
>
> In org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(PersistenceUnitMetadata pu), enable second level cache if persistence unit has hibernate.cache.use_query_cache or hibernate.cache.use_second_level_cache is true, then the second level cache should be enabled unless shared cache mode is set to NONE.
> Workaround:
> {code}
> <shared-cache-mode>ALL</shared-cache-mode>
> {code}
> Or
> {code}
> <shared-cache-mode>ENABLE_SELECTIVE</shared-cache-mode>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12086) Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12086?page=com.atlassian.jira.plugin... ]
Scott Marlow updated WFLY-12086:
--------------------------------
Fix Version/s: 17.0.0.Beta1
> Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12086
> URL: https://issues.jboss.org/browse/WFLY-12086
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 17.0.0.Beta1
>
>
> In org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(PersistenceUnitMetadata pu), enable second level cache if persistence unit has hibernate.cache.use_query_cache or hibernate.cache.use_second_level_cache is true, then the second level cache should be enabled unless shared cache mode is set to NONE.
> Workaround:
> {code}
> <shared-cache-mode>ALL</shared-cache-mode>
> {code}
> Or
> {code}
> <shared-cache-mode>ENABLE_SELECTIVE</shared-cache-mode>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12086) Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
by Scott Marlow (Jira)
Scott Marlow created WFLY-12086:
-----------------------------------
Summary: Hibernate 2lc should be enabled if Hibernate cache properties are enabled and shared cache mode is not set to NONE
Key: WFLY-12086
URL: https://issues.jboss.org/browse/WFLY-12086
Project: WildFly
Issue Type: Enhancement
Components: JPA / Hibernate
Affects Versions: 14.0.0.Final
Reporter: Scott Marlow
Assignee: Scott Marlow
In org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(PersistenceUnitMetadata pu), enable second level cache if persistence unit has hibernate.cache.use_query_cache or hibernate.cache.use_second_level_cache is true, then the second level cache should be enabled unless shared cache mode is set to NONE.
Workaround:
{code}
<shared-cache-mode>ALL</shared-cache-mode>
{code}
Or
{code}
<shared-cache-mode>ENABLE_SELECTIVE</shared-cache-mode>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3674:
--------------------------------------
Attachment: Screen Shot 2019-05-16 at 3.09.26 PM.png
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, Screen Shot 2019-05-16 at 3.09.26 PM.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3674:
-------------------------------------------
[~manstis] Wiki media link was just to illustrate the pop-over behavior, sorry about that:
!Screen Shot 2019-05-16 at 3.09.26 PM.png|thumbnail!
:)
> UX proposal for error reporting after test run
> ----------------------------------------------
>
> Key: DROOLS-3674
> URL: https://issues.jboss.org/browse/DROOLS-3674
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UXTeam
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, Screen Shot 2019-05-16 at 3.09.26 PM.png
>
>
> As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
> For instance have the possibility to see the actual value that is different from the expected or the error message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-12085:
--------------------------------------
This unfortunately won't fix this warning from being logged. The {{ReloadManager}} will not be scheduled, but the {{new URL(System.getProperty("logging.proeprties")).toURL()}} will still be invoked. This is because it's registered as a callback to the reload manager.
{code:java}
if (System.getProperty("logging.configuration") != null) {
try {
reloadManager.addCallback(new URI(System.getProperty("logging.configuration")).toURL(), new LoggingConfigurationFileReloader());
} catch (Exception e) {
// a syntax error with the logging system property shouldn't prevent the server from starting
ActiveMQServerLogger.LOGGER.problemAddingConfigReloadCallback(System.getProperty("logging.configuration"), e);
}
}
{code}
I don't know enough about the reload manager, but we may want to set it to {{-1}} anyway if the configuration should be coming from WildFly itself anyway.
> java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-6892) Access logging for EJBs
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-6892:
--------------------------------
Fix Version/s: (was: 17.0.0.Beta1)
> Access logging for EJBs
> -----------------------
>
> Key: WFLY-6892
> URL: https://issues.jboss.org/browse/WFLY-6892
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Cheng Fang
> Priority: Major
> Labels: EAP-CD17, affects_elytron
>
> Access logging for EJB requests similar to Web access logging would be very useful.
> Possibly something like:
> {code}
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet commented on WFLY-12085:
------------------------------------------
The automatic logging configuration reload functionality in ActiveMQ Artemis is meant to be used when the broker is standalone. It will monitor whatever file is referenced by the -Dlogging.configuration system property and reload the configuration therein if necessary so that users/administrators can update the logging configuration while the broker is running. Obviously this behavior is not desirable in the EAP use-case. Therefore, the messaging subsystem can invoke setConfigurationFileRefreshPeriod(-1) on its instance of org.apache.activemq.artemis.core.config.Configuration to avoid any reload attempts. via [~jbertram]
> java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12085) [GSS](7.2.z) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet moved JBEAP-16917 to WFLY-12085:
--------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12085 (was: JBEAP-16917)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Affects Version/s: 17.0.0.Alpha1
(was: 7.2.1.CR2)
Fix Version/s: (was: 7.2.3.GA)
> [GSS](7.2.z) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months