[JBoss JIRA] (DROOLS-3556) behavior of update is different from modify with dialect "mvel" + property reactive
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-3556:
------------------------------------
Summary: behavior of update is different from modify with dialect "mvel" + property reactive
Key: DROOLS-3556
URL: https://issues.jboss.org/browse/DROOLS-3556
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.14.0.Final
Environment: - Red Hat Decision Manager
- 7.2.0
Reporter: Hiroko Miura
Assignee: Mario Fusco
Attachments: updatePropertyReactive.zip
Behavior of 'update' is different from 'modify' when dialect "mvel" is sued with property reactive.
When using update() after fact modification, the same rule is continuously executed even though the condition no longer match.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ]
tao zhu commented on DROOLS-3492:
---------------------------------
[~kkufova][~danielezonca] Great, thanks!~
> Create UX proposal to show/edit Test Scenario (Preview) global setting
> ----------------------------------------------------------------------
>
> Key: DROOLS-3492
> URL: https://issues.jboss.org/browse/DROOLS-3492
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXD, UXTeam
> Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png, 屏幕快照 2019-01-22 下午4.44.04.png, 屏幕快照 2019-01-23 下午4.08.30.png, 屏幕快照 2019-01-23 下午4.08.30.png
>
>
> As user I want to be able to see/edit editor global settings.
> For instance DMN file linked to the scenario or the Session name of a Rule scenario
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3548) Thread used by LoadBalancer remains when connection to kie-server fails during instantinating of KieServicesClient
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-3548?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-3548:
---------------------------------
Summary: Thread used by LoadBalancer remains when connection to kie-server fails during instantinating of KieServicesClient (was: Thread used by loadbalancer remains when connection to kie-server fails a)
> Thread used by LoadBalancer remains when connection to kie-server fails during instantinating of KieServicesClient
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3548
> URL: https://issues.jboss.org/browse/DROOLS-3548
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.11.0.Final, 7.14.0.Final
> Environment: - Red Hat Decision Manager
> - 7
> - Red Hat Process Automation Manager
> - 7
> Reporter: Hiroko Miura
> Assignee: Maciej Swiderski
> Priority: Major
> Labels: support
> Attachments: rules-client.zip
>
>
> When KieServicesClient fails to connect to KieServer, LoadBalancer is invoked to check availability of server like the following.
> ~~~
> [2019/01/24 18:19:38.411] [pool-1-thread-1] [DEBUG] (LoadBalancer.java:149) - Starting to scan if any of the failed endpoints is back online
> org.kie.server.common.rest.NoEndpointFoundException: No available endpoints found
> at org.kie.server.client.balancer.impl.AbstractBalancerStrategy.checkEmpty(AbstractBalancerStrategy.java:27)
> at org.kie.server.client.balancer.impl.RoundRobinBalancerStrategy.next(RoundRobinBalancerStrategy.java:37)
> at org.kie.server.client.balancer.LoadBalancer.getUrl(LoadBalancer.java:52)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:809)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpGetRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:177)
> at org.kie.server.client.impl.KieServicesClientImpl.getServerInfo(KieServicesClientImpl.java:159)
> at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:132)
> at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:87)
> at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:74)
> at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
> at com.sample.rules.test.KieServerRestClientTest.connectionFailureTest(KieServerRestClientTest.java:55)
> ~~~
> But after that, the thread used by LoadBalancer remains until termination of client application as LoadBalancer.close() is not called.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3528) [DMN Designer] Data Types - Constraints - Shortcuts tooltip
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3528?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3528:
---------------------------------------
Sprint: 2019 Week 02-04 (was: 2019 Week 05-07)
> [DMN Designer] Data Types - Constraints - Shortcuts tooltip
> -----------------------------------------------------------
>
> Key: DROOLS-3528
> URL: https://issues.jboss.org/browse/DROOLS-3528
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-01-17 at 9.43.51 AM.png, tooltip.gif
>
>
> Show a tooltip like the following one for every Data Type shortcut :
> !tooltip.gif!
> List of shortcuts:
> Ctrl + E - Activate edit mode
> Ctrl + S - Save the Data Type
> Ctrl + B - Create a nested Data Type
> Ctrl + U - Create a Data Type above (up)
> Ctrl + D - Create a Data Type below (down)
> Ctrl + Backspace - Delete the Data Type
> Esc - Exit
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3528) [DMN Designer] Data Types - Constraints - Shortcuts tooltip
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3528?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3528:
---------------------------------------
Story Points: 2 (was: 5)
> [DMN Designer] Data Types - Constraints - Shortcuts tooltip
> -----------------------------------------------------------
>
> Key: DROOLS-3528
> URL: https://issues.jboss.org/browse/DROOLS-3528
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screen Shot 2019-01-17 at 9.43.51 AM.png, tooltip.gif
>
>
> Show a tooltip like the following one for every Data Type shortcut :
> !tooltip.gif!
> List of shortcuts:
> Ctrl + E - Activate edit mode
> Ctrl + S - Save the Data Type
> Ctrl + B - Create a nested Data Type
> Ctrl + U - Create a Data Type above (up)
> Ctrl + D - Create a Data Type below (down)
> Ctrl + Backspace - Delete the Data Type
> Esc - Exit
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11451) Classloading issues on IBM JDK 8 when JProfiler agent is enabled
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11451?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-11451:
--------------------------------------
Try using the append option and setting those arguments first. There is something, can't remember the exact details, in the IBM JVM that loads logging very early. In unit tests setting the arguments first and with the append option seemed to work.
{code}
JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/a:/home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.4.Final.jar $JAVA_OPTS"
{code}
> Classloading issues on IBM JDK 8 when JProfiler agent is enabled
> ----------------------------------------------------------------
>
> Key: WFLY-11451
> URL: https://issues.jboss.org/browse/WFLY-11451
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 14.0.1.Final
> Environment: IBM JDK 8:
> java version "1.8.0_191"
> Java(TM) SE Runtime Environment (build 8.0.5.25 - pxa6480sr5fp25-20181030_01(SR5 FP25))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20181029_400846 (JIT enabled, AOT enabled)
> OpenJ9 - c5c78da
> OMR - 3d5ac33
> IBM - 8c1bdc2)
> JCL - 20181022_01 based on Oracle jdk8u191-b26
> Reporter: Tomas Kyjovsky
> Assignee: James Perkins
> Priority: Major
>
> When I enable JProfiler agent for the server running on IBM JDK 8 the server doesn't start, throwing classloading exceptions.
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final
> JAVA: /home/tkyjovsk/software/java/ibm-java-80/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentpath:/home/tkyjovsk/software/tools/jprofiler9/bin/linux-x64/libjprofilerti.so=port=6766 -Xshareclasses:none
> =========================================================================
> JProfiler> Protocol version 55
> JProfiler> Using JVMTI
> JProfiler> Thread status info workaround enabled.
> JProfiler> Restricted JVMTI version 1.1 detected.
> JProfiler> 64-bit library
> JProfiler> Listening on port: 6766.
> JProfiler> Instrumenting native methods.
> JProfiler> Native library initialized
> JProfiler> VM initialized
> JProfiler> Waiting for a connection from the JProfiler GUI ...
> JProfiler> Using dynamic instrumentation
> JProfiler> Time measurement: elapsed time
> JProfiler> CPU profiling enabled
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Nov 30, 2018 1:48:31 PM org.jboss.msc.service.ServiceContainerImpl <clinit>
> INFO: JBoss MSC version 1.4.3.Final
> Nov 30, 2018 1:48:31 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.2.Final
> Nov 30, 2018 1:48:31 PM org.jboss.as.server.BootstrapImpl internalBootstrap
> WARN: WFLYSRV0071: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended
> Nov 30, 2018 1:48:31 PM org.jboss.as.server.ApplicationServerService start
> INFO: WFLYSRV0049: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) starting
> Nov 30, 2018 1:48:33 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.6.0.Final
> Nov 30, 2018 1:48:34 PM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:495)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:470)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:432)
> at org.jboss.as.server.ServerService.boot(ServerService.java:427)
> at org.jboss.as.server.ServerService.boot(ServerService.java:386)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372)
> at java.lang.Thread.run(Thread.java:812)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask.report(FutureTask.java:133)
> at java.util.concurrent.FutureTask.get(FutureTask.java:203)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107)
> ... 11 more
> Caused by: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:194)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:104)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
> at java.util.concurrent.FutureTask.run(FutureTask.java:277)
> 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:1378)
> at java.lang.Thread.run(Thread.java:812)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Nov 30, 2018 1:48:34 PM org.jboss.as.server.ServerService$4 logExit
> FATAL: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {noformat}
> I tried to work around this by adding "{{org.jboss.logmanager}}" to {{JBOSS_MODULES_SYSTEM_PKGS}} and adding "{{-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:...}}" in {{JAVA_OPTS}} but that just results in another class-loading error:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final
> JAVA: /home/tkyjovsk/software/java/ibm-java-80/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.awt.headless=true -agentpath:/home/tkyjovsk/software/tools/jprofiler9/bin/linux-x64/libjprofilerti.so=port=6766 -Xshareclasses:none -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/home/tkyjovsk/workspace/KEYCLOAK-8983/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.4.Final.jar
> =========================================================================
> JProfiler> Protocol version 55
> JProfiler> Using JVMTI
> JProfiler> Thread status info workaround enabled.
> JProfiler> Restricted JVMTI version 1.1 detected.
> JProfiler> 64-bit library
> JProfiler> Listening on port: 6766.
> JProfiler> Instrumenting native methods.
> JProfiler> Native library initialized
> JProfiler> VM initialized
> JProfiler> Waiting for a connection from the JProfiler GUI ...
> JProfiler> Using dynamic instrumentation
> JProfiler> Time measurement: elapsed time
> JProfiler> CPU profiling enabled
> java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
> at org.jboss.logmanager.ExtLogRecord.<init>(ExtLogRecord.java:87)
> at org.jboss.logmanager.Logger.log(Logger.java:796)
> at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:53)
> at org.jboss.logging.Logger.logf(Logger.java:2398)
> at org.jboss.msc.service.ServiceLogger_$logger.greeting(ServiceLogger_$logger.java:40)
> at org.jboss.msc.service.ServiceContainerImpl.<clinit>(ServiceContainerImpl.java:91)
> at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:250)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.register(BootstrapImpl.java:229)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.access$100(BootstrapImpl.java:219)
> at org.jboss.as.server.BootstrapImpl.<init>(BootstrapImpl.java:70)
> at org.jboss.as.server.Bootstrap$Factory.newInstance(Bootstrap.java:278)
> at org.jboss.as.server.Main.main(Main.java:106)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-9747) wildfly-arquillian-container-managed: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-9747?page=com.atlassian.jira.plugin.... ]
James Perkins resolved WFLY-9747.
---------------------------------
Resolution: Out of Date
This does seem out of date as I can't seem to reproduce it. One thing that struck me as odd is 2.1.0.Final was pulling in an older version of the jmx-protocol. If this still is an issue I'd be interesting in seeing a reproducer or at least the full pom really.
> wildfly-arquillian-container-managed: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9747
> URL: https://issues.jboss.org/browse/WFLY-9747
> Project: WildFly
> Issue Type: Bug
> Reporter: Geoffrey De Smet
> Assignee: James Perkins
> Priority: Major
>
> On a pretty vanilla war file with a bit JAX-RS and arquillian, I get this error when trying to run an arquillian test (that worked before we upgraded the wildfly version):
> {code}
> [INFO] Running org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest
> Jan 31, 2018 7:52:20 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> WARNING: Bundles path is deprecated and no longer used.
> Jan 31, 2018 7:52:20 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> INFO: Starting container with: [/usr/lib/jvm/java-openjdk/bin/java, -D[Standalone], -Djboss.socket.binding.port-offset=10000, -Xms512m, -Xmx1024m, -XX:MaxPermSize=512m, -ea, -Djboss.home.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final, -Dorg.jboss.boot.log.file=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/log/server.log, -Dlogging.configuration=file:/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/configuration/logging.properties, -jar, /home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/jboss-modules.jar, -mp, /home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final, -Djboss.server.base.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone, -Djboss.server.log.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/log, -Djboss.server.config.dir=/home/ge0ffrey/projects/jboss/optashift/optashift-employee-rostering/local/appserver/wildfly-10.1.0.Final/standalone/configuration]
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.449 s <<< FAILURE! - in org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest
> [ERROR] org.optaplanner.openshift.employeerostering.webapp.skill.SkillRestServiceTest Time elapsed: 0.448 s <<< ERROR!
> java.lang.NoClassDefFoundError: org/wildfly/security/permission/AbstractNameSetOnlyPermission
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> Caused by: java.lang.ClassNotFoundException: org.wildfly.security.permission.AbstractNameSetOnlyPermission
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> {code}
> With this parent pom:
> {code}
> <properties>
> <version.org.jboss.arquillian>1.2.1.Final</version.org.jboss.arquillian>
> <version.org.wildfly.arquillian>2.1.0.Final</version.org.wildfly.arquillian>
> <version.org.jboss.resteasy>3.1.4.Final</version.org.jboss.resteasy>
> </properties>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>${version.org.jboss.arquillian}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.arquillian</groupId>
> <artifactId>wildfly-arquillian-container-managed</artifactId>
> <version>${version.org.wildfly.arquillian}</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-client</artifactId>
> <version>${version.org.jboss.resteasy}</version>
> </dependency>
> ...
> {code}
> and this child pom:
> {code}
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.shrinkwrap.resolver</groupId>
> <artifactId>shrinkwrap-resolver-depchain</artifactId>
> <type>pom</type>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.arquillian</groupId>
> <artifactId>wildfly-arquillian-container-managed</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.resteasy</groupId>
> <artifactId>resteasy-client</artifactId>
> <scope>test</scope>
> </dependency>
> {code}
> I am probably not using a correct version combination of arquillian and wildfly, but for mere mortals such as myself it takes days to find a working versions combination of arquillian and wildfly - everytime I need to upgrade wildfly. (The arquillian guides and arquillian-showcase-jaxrs are all hopelessly outdated in this aspect, they still mention jboss-as (= wildfly 7)).
> Solution proposal A)
> wildfly-arquillian-managed should automatically detect that it's a wrong version combination and give an error message like "I am not build to work with version x, but it seems like you're combining me with version y."
> Solution proposal B)
> Use the same version numbers for wildfly-arquillian-container-managed (currently 2.1.0.Final) as for wildfly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-10937:
--------------------------------------
[~suganya_rajeswaran] I believe this is already done in WildFly 15. If you're using an earlier version just edit the {{appclient.conf.bat}} file and add something like {{set "JAVA_OPTS=%JAVA_OPTS% --add-modules=java.se"}} at the bottom of that file.
> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> -------------------------------------------------------------------------------
>
> Key: WFLY-10937
> URL: https://issues.jboss.org/browse/WFLY-10937
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: Richard Opalka
> Priority: Blocker
> Labels: Java11, blocker-WF14, jdk11
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> *Affected scripts*
> * appclient
> * jdr
> * wsconsume
> * wsprovide
> *Example of logs*
> {noformat}
> [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> [mkopecky@dhcp-10-40-4-197 bin]$
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3552) Error: "write size larger than buffer can fit" when opening object in workbench
by Petr Farmakovsky (Jira)
[ https://issues.jboss.org/browse/DROOLS-3552?page=com.atlassian.jira.plugi... ]
Petr Farmakovsky closed DROOLS-3552.
------------------------------------
Resolution: Migrated to another ITS
> Error: "write size larger than buffer can fit" when opening object in workbench
> -------------------------------------------------------------------------------
>
> Key: DROOLS-3552
> URL: https://issues.jboss.org/browse/DROOLS-3552
> Project: Drools
> Issue Type: Bug
> Components: DSLs Editor
> Affects Versions: 6.5.0.Final
> Environment: KIE Drools Workbench - Distribution Wars-Version: 6.5.0.Final
> Server version: Apache Tomcat/7.0.76
> Server number: 7.0.76.0
> OS Name: Linux
> OS Version: 3.10.0-957.1.3.el7.x86_64
> Architecture: amd64
> JVM Version: 1.7.0_161-b13
> JVM Vendor: Oracle Corporation
> H2 database
> Reporter: Petr Farmakovsky
> Assignee: Michael Anstis
> Priority: Major
> Attachments: Error.jpg, Error2.json
>
>
> To reproduce the error, I created a new repository, created a 300 Data Object in it. In each Data Object created 1000 fields of type Integer.
> After restarting the server when opening any object, Drools Workbeanch writes an error: *write size larger than buffer can fit*
> {noformat}
> java.lang.RuntimeException: failed to enqueue message for delivery
> at org.jboss.errai.bus.server.ServerMessageBusImpl.enqueueForDelivery(ServerMessageBusImpl.java:443)
> at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:391)
> at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:337)
> at org.jboss.errai.bus.server.service.MessageBusProxy.send(MessageBusProxy.java:87)
> at org.jboss.errai.bus.client.api.base.ConversationMessageWrapper.sendNowWith(ConversationMessageWrapper.java:238)
> at org.jboss.errai.bus.client.api.base.DefaultMessageBuilder$1.sendNowWith(DefaultMessageBuilder.java:84)
> at org.jboss.errai.bus.server.io.ValueReplyRPCEndpointCallback.callback(ValueReplyRPCEndpointCallback.java:22)
> at org.jboss.errai.bus.server.io.RemoteServiceCallback.callback(RemoteServiceCallback.java:54)
> at org.jboss.errai.cdi.server.CDIExtensionPoints$2.callback(CDIExtensionPoints.java:396)
> ..
> {noformat}
> The full text of the error is attached in the file.
> I know about the description https://developer.jboss.org/thread/220428 but I did not find the parameters under which you can open objects.
> I found an error in the TransmissionBuffer.java class, but I don’t know how to fix the problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months