[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ]
Kris Verlaenen commented on DROOLS-1511:
----------------------------------------
[~tomasdavidorg] I believe it was related to this fix:
https://github.com/kiegroup/droolsjbpm-tools/commit/381e7fc9bda075d0b086a...
> NullPointerException when running sample projects
> -------------------------------------------------
>
> Key: DROOLS-1511
> URL: https://issues.jboss.org/browse/DROOLS-1511
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: DevStudio 10 + IS 10.3.0.CR2
> Eclipse Neon + Drools plugin 7.0.0.CR3
> Drools Runtime 7.x
> Reporter: Tomas David
> Assignee: Kris Verlaenen
> Priority: Blocker
> Labels: reported-by-qe
> Fix For: 7.1.0.Final
>
>
> NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created.
> Eclipse log:
> !SESSION 2017-04-04 12:39:38.638 -----------------------------------------------
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737
> !MESSAGE Internal error in Drools Plugin:
> !STACK 1
> Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject']
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112)
> at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122)
> at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739
> !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3126) Cannot start EAP - MALLOC_ARENA_MAX=1: is not an identifier
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3126?page=com.atlassian.jira.plugi... ]
Tomaz Cerar moved JBEAP-12435 to WFCORE-3126:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3126 (was: JBEAP-12435)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Scripts
(was: Scripts)
Affects Version/s: 3.0.0.Beta30
(was: 7.1.0.ER3)
Affects Testing: (was: Regression,Blocks Testing)
> Cannot start EAP - MALLOC_ARENA_MAX=1: is not an identifier
> ------------------------------------------------------------
>
> Key: WFCORE-3126
> URL: https://issues.jboss.org/browse/WFCORE-3126
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.0.Beta30
> Environment: {noformat}
> $ uname -a
> SunOS 5.10 Generic_150400-51 sun4v sparc SUNW,SPARC-Enterprise-T1000
> {noformat}
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Priority: Blocker
>
> JBEAP-11565 add the following line into the EAP launching scripts:
> {noformat}
> export MALLOC_ARENA_MAX="${MALLOC_ARENA_MAX:-1}"
> {noformat}
> This is problematic on *Solaris 10 sparc*
> {noformat}
> $ ./standalone.sh
> ./standalone.sh: MALLOC_ARENA_MAX=1: is not an identifier
> $ ./domain.sh
> ./domain.sh: MALLOC_ARENA_MAX=1: is not an identifier
> {noformat}
> See https://issues.apache.org/jira/browse/MNG-5829 description:
> {noformat}
> The $(cmd) idiom is used extensively in bin/mvn from lines 199-220, but this is not supported by older incarnations of /bin/sh (used on the shebang line). The `cmd` idiom is slightly more portable, and looks like it can probably be directly substituted.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3042) It is not possible to add new Elytron policy after adding and removing it first
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3042?page=com.atlassian.jira.plugi... ]
Martin Stefanko reassigned WFCORE-3042:
---------------------------------------
Assignee: Martin Stefanko
> It is not possible to add new Elytron policy after adding and removing it first
> -------------------------------------------------------------------------------
>
> Key: WFCORE-3042
> URL: https://issues.jboss.org/browse/WFCORE-3042
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kašík
> Assignee: Martin Stefanko
>
> Adding new Elytron policy fails if it was previously added and then removed. Next adding fails [1] and with exception [2] in server.log.
> [1]
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/policy=jacc:add(jacc-policy=[{name => jacc}])
> {
> "outcome" => "failed",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> },
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.policy" => "Failed to start service
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection"}},
> "rolled-back" => true
> }
> {code}
> [2]
> {code}
> 2017-06-29 11:08:35,700 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.policy: org.jboss.msc.service.StartException in service org.wildfly.security.policy: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.start(PolicyDefinitions.java:177)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection
> at org.wildfly.security.authz.jacc.JaccDelegatingPolicy$1.add(JaccDelegatingPolicy.java:126)
> at java.security.Policy.addStaticPerms(Policy.java:686)
> at java.security.Policy.getPermissions(Policy.java:673)
> at org.jboss.security.jacc.DelegatingPolicy.getPermissions(DelegatingPolicy.java:125)
> at java.security.Policy.initPolicy(Policy.java:327)
> at java.security.Policy.setPolicy(Policy.java:270)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.lambda$setPolicyAction$0(PolicyDefinitions.java:201)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.setPolicy(PolicyDefinitions.java:195)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.start(PolicyDefinitions.java:173)
> ... 5 more
> 2017-06-29 11:08:35,701 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("policy" => "jacc")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.policy" => "Failed to start service
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection"}}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1186) Setting the planning variable nullable in nurserostering examples causes Drools NPE
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1186?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1186:
------------------------------------------
[~code4dc] If this was fixed after 6.5.0.Final community went out, then it's fixed only in a product release for the 6.x series. Of course, it's also fixed in community on master, so for 7.0.0.Final. If this was fixed before 6.5.0.Final community went out, it's probably fixed in there too.
See item "Backport bugfixes to maintenance branches" in the comparison here:
https://www.optaplanner.org/community/product.html
> Setting the planning variable nullable in nurserostering examples causes Drools NPE
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1186
> URL: https://issues.jboss.org/browse/DROOLS-1186
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Windows 7 x 64, JDK 8u66, IDE netbeans 8.0.1.
> Reporter: Julio Bellon Aguilera
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
> Attachments: PLANNER_488.patch
>
>
> If you set the planning variable to "nullable=true", firstable, causes a IllegalStateException.
> fixed that, causes the first NPE, and fixed that, causes other NPE unfixed:
> Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException:
> Caused by: java.lang.NullPointerException
> at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:778)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1186) Setting the planning variable nullable in nurserostering examples causes Drools NPE
by Eugene Shvartsman (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1186?page=com.atlassian.jira.plugi... ]
Eugene Shvartsman commented on DROOLS-1186:
-------------------------------------------
Any possible workaround for those on 6.3.0.Final?
> Setting the planning variable nullable in nurserostering examples causes Drools NPE
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1186
> URL: https://issues.jboss.org/browse/DROOLS-1186
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Windows 7 x 64, JDK 8u66, IDE netbeans 8.0.1.
> Reporter: Julio Bellon Aguilera
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
> Attachments: PLANNER_488.patch
>
>
> If you set the planning variable to "nullable=true", firstable, causes a IllegalStateException.
> fixed that, causes the first NPE, and fixed that, causes other NPE unfixed:
> Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException:
> Caused by: java.lang.NullPointerException
> at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:778)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-2968) Servers in a domain won't boot if local auth is disabled on the host controller
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2968?page=com.atlassian.jira.plugi... ]
Brian Stansberry reopened WFCORE-2968:
--------------------------------------
Reopening due to WFCORE-3125.
> Servers in a domain won't boot if local auth is disabled on the host controller
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2968
> URL: https://issues.jboss.org/browse/WFCORE-2968
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: James Perkins
> Assignee: Ken Wills
> Priority: Blocker
> Fix For: 3.0.0.Beta30
>
>
> If local authentication has been disabled on the host controller servers cannot communicate with the host controller and fail to start.
> {code}
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] ... 4 more
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:188)
> [Server:server-one] at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> [Server:server-one] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
> [Server:server-one] ... 3 more
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,243 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> [Server:server-one] 15:10:51,254 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 3.0.0.Beta27-SNAPSHOT "Kenny" stopped in 6ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Nuno Godinho de Matos edited comment on WFLY-8954 at 7/29/17 6:03 AM:
----------------------------------------------------------------------
Hi Scott, I still have not had the time to dedicate to this task.
I have been prioritizing some other work, since for the time being in relation to this bug, on the instances where the phenomena has taken place, we are doing a "dirty" entitymanager.referesh(myStaleEntity), as work-around. This work-around is useless if one is clueless as to what entity may have been changed in a business transaction, but out of luck, we do know the instances that we are getting served stale.
I hope to be able to dedicate some hours to this next week.
By the way, I must give you guys compliements on the JBOSS CLI.
The CLI is really fast.
We have written python/jython based create domain script for our business configuration (e.g. dynamically produce wildfly CLI based on desired configuration settings - datasources, jms, etc...) and I must say the speed with which a new standalone domain can get created and then finally configured via CLI is incredible. I was not expecting the CLI to be so fast configuring queues, factories, datasources. Incredible. So big compliments!
Kindest regards.
was (Author: nuno.godinhomatos):
Hi Scott, I still have not had the time to dedicate to this task.
I have been prioritizing some other work, since for the time being in relation to this bug, on the instances where the phenomena has taken place, we are doing a "dirty" entitymanager.referesh(myStaleEntity), as work-around. This work-around is useless if one is clueless as to what entity may have been changed in a business transaction, but out of luck, we do know the instances that we are getting served stale. The only problem I have with the current configuration architecture of Wildfly - is that it is not smooth for integration with Eclipse IDE.
Many configuration settings that I may wish to configure (e.g. -X system properties, etc..) I can tune them via dedicated start script for the domains, but there is no change that Eclipse will pick these up because unfortunately eclispe does not allow to tell it to start a domain via custom start script. and such syte properties, they are not effective if you put them in the standalone.xml system properties setting. So that means, manual work opening eclipse launch configuration that add such level of configuration by hand to start a widlfly domain. I think that should surely be improved... Eclipse plugin shuld assume less defaults, and swallow configurations from somewhere under the control of the person that configures the domain, in my oppinion. (I am quite off topic, sorry for that).
I hope to be able to dedicate some hours to this next week.
By the way, I must give you guys compliements on the JBOSS CLI.
The CLI is really fast.
We have written python/jython based create domain script for our business configuration (e.g. dynamically produce wildfly CLI based on desired configuration settings - datasources, jms, etc...) and I must say the speed with which a new standalone domain can get created and then finally configured via CLI is incredible. I was not expecting the CLI to be so fast configuring queues, factories, datasources. Incredible. So big compliments!
Kindest regards.
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
> Assignee: Scott Marlow
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months