[Red Hat JIRA] (WFLY-14311) javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-14311?page=com.atlassian.jira.plugi... ]
Lin Gao updated WFLY-14311:
---------------------------
Labels: downstream_dependency (was: )
> javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-14311
> URL: https://issues.redhat.com/browse/WFLY-14311
> Project: WildFly
> Issue Type: Bug
> Components: Naming
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Major
> Labels: downstream_dependency
>
> The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
> When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out.
> {code:java}
> 13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
> at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66)
> at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262)
> at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289)
> at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238)
> at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> 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)
> 13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
> at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108)
> at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301)
> at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309)
> at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236)
> at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> 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)
> {code}
> From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
> {quote}
> The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
> {quote}
> For more information and reproducer, please refer to WFLY-13459
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14311) javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-14311?page=com.atlassian.jira.plugi... ]
Lin Gao updated WFLY-14311:
---------------------------
Description:
The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out.
{code:java}
13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
{code}
From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
{quote}
The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
{quote}
For more information and reproducer, please refer to WFLY-13459
was:
The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out.
{code:java}
13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
{code}
From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
{quote}
The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
{quote}
> javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-14311
> URL: https://issues.redhat.com/browse/WFLY-14311
> Project: WildFly
> Issue Type: Bug
> Components: Naming
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Major
>
> The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
> When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out.
> {code:java}
> 13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
> at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66)
> at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262)
> at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289)
> at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238)
> at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> 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)
> 13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
> at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108)
> at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301)
> at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309)
> at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236)
> at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> 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)
> {code}
> From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
> {quote}
> The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
> {quote}
> For more information and reproducer, please refer to WFLY-13459
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14311) javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
by Lin Gao (Jira)
Lin Gao created WFLY-14311:
------------------------------
Summary: javax.naming.OperationNotSupportedException should be thrown when read-only remote naming operations failed
Key: WFLY-14311
URL: https://issues.redhat.com/browse/WFLY-14311
Project: WildFly
Issue Type: Bug
Components: Naming
Reporter: Lin Gao
Assignee: Lin Gao
The Remote Naming (JNDI) is Read-Only, remote clients cannot bind or rebind objects into it. Only applications running in the same JVM can bind values into JNDI.
When modifying methods like: bind/rebind/unbind/rename/createSubContext/destroySubContext are invoked from remote client, it expects *javax.naming.OperationNotSupportedException* thrown out, but *java.lang.UnsupportedOperationException* is thrown out.
{code:java}
13:20:22,804 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:66)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:262)
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:289)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:238)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:126)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
13:20:22,813 WARN [org.wildfly.naming] (default task-2) WFNAM00036: Unexpected internal error: java.lang.UnsupportedOperationException: WFLYNAM0043: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:160)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:108)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:301)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:309)
at org.wildfly.naming.client.remote.RemoteServerTransport.handleBind(RemoteServerTransport.java:236)
at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:129)
at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
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)
{code}
From EE Platform spec: EE.5.3.4 Java EE Product Provider's Responsibilities:
{quote}
The container must ensure that the application component instances have only read access to their naming context. The container must throw the *javax.naming.OperationNotSupportedException* from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.
{quote}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5230:
-------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 16-18 (from Apr 13))
> Managing a List of structures in Test Scenario editor produces an Exception
> ---------------------------------------------------------------------------
>
> Key: DROOLS-5230
> URL: https://issues.redhat.com/browse/DROOLS-5230
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Yeser Amer
> Priority: Critical
> Attachments: Error screen shot.png, test_scenario_list_exception.zip
>
>
> When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user.
> Log entry is:
> ```
> ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined
> ```
> From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined`
> (Screenshot is attached)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5230:
-------------------------------
Story Points: 3 (was: 5)
> Managing a List of structures in Test Scenario editor produces an Exception
> ---------------------------------------------------------------------------
>
> Key: DROOLS-5230
> URL: https://issues.redhat.com/browse/DROOLS-5230
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Yeser Amer
> Priority: Critical
> Attachments: Error screen shot.png, test_scenario_list_exception.zip
>
>
> When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user.
> Log entry is:
> ```
> ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined
> ```
> From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined`
> (Screenshot is attached)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5689) Test Scenario DMN included models decision support
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5689?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5689:
-------------------------------
Sprint: (was: 2021 Week 04-06 (from Jan 25))
> Test Scenario DMN included models decision support
> --------------------------------------------------
>
> Key: DROOLS-5689
> URL: https://issues.redhat.com/browse/DROOLS-5689
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.44.0.Final
> Reporter: Jan Stastny
> Assignee: Yeser Amer
> Priority: Major
> Attachments: reproducer.zip
>
>
> Test scenario does not currently fully support DMN models with included DMN model.
> Currently just Data types are correctly included, but issue is with Decisions. When running a test scenario where such imported decision is referenced in the decision being tested it results in SKIPPED evaluation of the decision and similar log entry:
> {code:java}
> 12:27:45,784 ERROR [org.kie.dmn.core.impl.DMNRuntimeImpl] (default task-20) Required dependency 'input-a' not found on node 'LessThanZero'
> 12:27:45,784 ERROR [org.kie.dmn.core.impl.DMNRuntimeImpl] (default task-20) Unable to evaluate decision 'NotLessThanZero' as it depends on decision 'a.LessThanZero'
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFCORE-4970) Changing the JVM settings at host level does not put the servers in restart-required
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug... ]
Parul Sharma reassigned WFCORE-4970:
------------------------------------
Assignee: Parul Sharma (was: Yeray Borges Santana)
> Changing the JVM settings at host level does not put the servers in restart-required
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4970
> URL: https://issues.redhat.com/browse/WFCORE-4970
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 12.0.0.Beta2
> Reporter: Yeray Borges Santana
> Assignee: Parul Sharma
> Priority: Major
>
> Operations like the following one should put the servers in restart required to indicate the user changes will be applied after restarting the servers:
> {noformat}
> [domain@localhost:9990 /] /host=master/jvm=default:write-attribute(name=heap-size, value=256m)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5230:
-------------------------------
Tester: Jan Stastny (was: Anna Dupliak)
> Managing a List of structures in Test Scenario editor produces an Exception
> ---------------------------------------------------------------------------
>
> Key: DROOLS-5230
> URL: https://issues.redhat.com/browse/DROOLS-5230
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Yeser Amer
> Priority: Critical
> Attachments: Error screen shot.png, test_scenario_list_exception.zip
>
>
> When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user.
> Log entry is:
> ```
> ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined
> ```
> From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined`
> (Screenshot is attached)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5956) Illegal reflective access
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5956?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5956:
--------------------------------
Sprint: 2020 Week 52-03 (from Dec 21)
> Illegal reflective access
> -------------------------
>
> Key: DROOLS-5956
> URL: https://issues.redhat.com/browse/DROOLS-5956
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.48.0.Final
> Reporter: Damon Horrell
> Assignee: Mario Fusco
> Priority: Minor
>
> Using Java 11, Drools MVEL is reporting an Illegal reflective access warning:
> {{WARNING: Illegal reflective access by org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer (file:/Users/damon/.m2/repository/org/drools/drools-mvel/7.48.0.Final/drools-mvel-7.48.0.Final.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.createDefineMethod(ClassGenerator.java:126)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.<clinit>(ClassGenerator.java:117)}}{{at org.drools.mvel.asm.ClassGenerator.generateClass(ClassGenerator.java:177)}}{{at org.drools.mvel.asm.ClassGenerator.newInstance(ClassGenerator.java:214)}}{{at org.drools.mvel.asm.ConsequenceGenerator.generate(ConsequenceGenerator.java:140)}}{{at defaultpkg.Rule_Expand_HealthCase181668088DefaultConsequenceInvoker.evaluate(Unknown Source)}}{{at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:434)}}{{at org.drools.core.phreak.RuleExecutor.fireActivation(RuleExecutor.java:382)}}{{at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:138)}}{{at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:90)}}{{at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:33)}}{{at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)}}{{at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1111)}}{{at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1058)}}{{at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1050)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1346)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1337)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1321)}}
>
> {{Is there a plan to update this code to avoid the warning (which will become an error in some future version of Java)?}}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months