[JBoss JIRA] (DROOLS-2821) [DMN Designer] [IE11] Missing Edit Expression type icon
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2821?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2821:
--------------------------------
Description:
Icon for edit expression type is missing.
h2. Manual acceptance test
Check icon present and works on
- IE
- Firefox
- Chrome
was:Icon for edit expression type is missing.
> [DMN Designer] [IE11] Missing Edit Expression type icon
> -------------------------------------------------------
>
> Key: DROOLS-2821
> URL: https://issues.jboss.org/browse/DROOLS-2821
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-01 13-34-32.png
>
>
> Icon for edit expression type is missing.
> h2. Manual acceptance test
> Check icon present and works on
> - IE
> - Firefox
> - Chrome
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11023) DB2 sending larger message (1MB) crashes the whole server
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-11023:
-------------------------------------
Summary: DB2 sending larger message (1MB) crashes the whole server
Key: WFLY-11023
URL: https://issues.jboss.org/browse/WFLY-11023
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Environment: DB2 11 (Dballocator)
AMQP, Core sender
Reporter: Miroslav Novak
Assignee: Francesco Nigro
Priority: Critical
default broker.xml with JDBC for DB2 (and jdbc connector provided in libs dir)
{code:xml}
<store>
<database-store>
<jdbc-connection-url>jdbc:db2://db2-111.<hostname>.redhat.com:50000/dballo:user=<user>password=<pass>;</jdbc-connection-url>
<bindings-table-name>BINDINGS_TABLE</bindings-table-name>
<message-table-name>MESSAGE_TABLE</message-table-name>
<page-store-table-name>P_TABLE</page-store-table-name>
<large-message-table-name>LARGE_MESSAGES_TABLE</large-message-table-name>
<jdbc-driver-class-name>com.ibm.db2.jcc.DB2Driver</jdbc-driver-class-name>
</database-store>
</store>
{code}
{noformat}
$ ll -h /tmp/bigfile1mb
-rw-r--r--. 1 root root 1.1M Jun 19 17:44 /tmp/bigfile1m
{noformat}
Core sender
{noformat}
$ java -jar /var/dtests/node_data/clients/acce.jar sender --log-msgs dict --broker localhost:5672 --conn-username admin --conn-password admin --address "test_node_large_durable_msg_queue" --count 1 --msg-content-from-file /tmp/bigfile1mb --msg-durable True
02:59:52,796 ERROR Failed to create session factory
javax.jms.JMSException: Failed to create session factory
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:815)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:277)
at com.redhat.mqe.acc.AccConnectionManager.<init>(AccConnectionManager.java:73)
at com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:33)
at com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:27)
at com.redhat.mqe.lib.CoreClient.createConnection(CoreClient.java:94)
at com.redhat.mqe.acc.AccSenderClient.startClient(AccSenderClient.java:53)
at com.redhat.mqe.lib.Main.main(Main.java:46)
at com.redhat.mqe.acc.Main.main(Main.java:85)
at com.redhat.mqe.acc.Main.main(Main.java:89)
Caused by: ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119013: Timed out waiting to receive cluster topology. Group:null]
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:814)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:813)
... 9 more
Exception in thread "main" java.lang.NullPointerException
at com.redhat.mqe.lib.CoreClient.createSession(CoreClient.java:121)
at com.redhat.mqe.acc.AccSenderClient.startClient(AccSenderClient.java:70)
at com.redhat.mqe.lib.Main.main(Main.java:46)
at com.redhat.mqe.acc.Main.main(Main.java:85)
at com.redhat.mqe.acc.Main.main(Main.java:89)
{noformat}
AMQP sender
{noformat}
$ java -jar /var/dtests/node_data/clients/aac1.jar sender --log-msgs dict --broker localhost:5672 --conn-username admin --conn-password admin --address "test_node_large_durable_msg_queue" --count 1 --msg-content-from-file /tmp/bigfile1mb --msg-durable True
02:55:31,588 ERROR Error while sending a message!
javax.jms.JMSException: Received error from remote peer without description [condition = amqp:connection:forced]
at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:164)
at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
at org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:262)
at org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:971)
at org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:105)
at org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:854)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
Broker log
{noformat}
2018-06-22 02:59:22,766 DEBUG [io.netty.util.Recycler] -Dio.netty.recycler.ratio: 8
2018-06-22 02:59:22,779 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.n
etty.handler.codec.DecoderException: java.lang.NullPointerException
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:142) [artemis-server-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1359) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:935) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
Caused by: java.lang.NullPointerException
at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:201) [artemis-server-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
... 14 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11022) DB2 sending larger message (1MB) crashes the whole server
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-11022?page=com.atlassian.jira.plugin... ]
Miroslav Novak moved ENTMQBR-1983 to WFLY-11022:
------------------------------------------------
Project: WildFly (was: A-MQ Broker)
Key: WFLY-11022 (was: ENTMQBR-1983)
Workflow: GIT Pull Request workflow (was: AMQ Agile Workflow)
Component/s: JMS
(was: jdbc)
Target Release: (was: AMQ 7.2.1.GA)
Affects Version/s: 14.0.0.Final
(was: AMQ 7.2.0.GA)
> DB2 sending larger message (1MB) crashes the whole server
> ---------------------------------------------------------
>
> Key: WFLY-11022
> URL: https://issues.jboss.org/browse/WFLY-11022
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Environment: DB2 11 (Dballocator)
> AMQP, Core sender
> Reporter: Miroslav Novak
> Assignee: Francesco Nigro
> Priority: Critical
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> default broker.xml with JDBC for DB2 (and jdbc connector provided in libs dir)
> {code:xml}
> <store>
> <database-store>
> <jdbc-connection-url>jdbc:db2://db2-111.<hostname>.redhat.com:50000/dballo:user=<user>password=<pass>;</jdbc-connection-url>
> <bindings-table-name>BINDINGS_TABLE</bindings-table-name>
> <message-table-name>MESSAGE_TABLE</message-table-name>
> <page-store-table-name>P_TABLE</page-store-table-name>
> <large-message-table-name>LARGE_MESSAGES_TABLE</large-message-table-name>
> <jdbc-driver-class-name>com.ibm.db2.jcc.DB2Driver</jdbc-driver-class-name>
> </database-store>
> </store>
> {code}
> {noformat}
> $ ll -h /tmp/bigfile1mb
> -rw-r--r--. 1 root root 1.1M Jun 19 17:44 /tmp/bigfile1m
> {noformat}
> Core sender
> {noformat}
> $ java -jar /var/dtests/node_data/clients/acce.jar sender --log-msgs dict --broker localhost:5672 --conn-username admin --conn-password admin --address "test_node_large_durable_msg_queue" --count 1 --msg-content-from-file /tmp/bigfile1mb --msg-durable True
> 02:59:52,796 ERROR Failed to create session factory
> javax.jms.JMSException: Failed to create session factory
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:815)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:277)
> at com.redhat.mqe.acc.AccConnectionManager.<init>(AccConnectionManager.java:73)
> at com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:33)
> at com.redhat.mqe.acc.AccConnectionManagerFactory.make(AccConnectionManagerFactory.java:27)
> at com.redhat.mqe.lib.CoreClient.createConnection(CoreClient.java:94)
> at com.redhat.mqe.acc.AccSenderClient.startClient(AccSenderClient.java:53)
> at com.redhat.mqe.lib.Main.main(Main.java:46)
> at com.redhat.mqe.acc.Main.main(Main.java:85)
> at com.redhat.mqe.acc.Main.main(Main.java:89)
> Caused by: ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119013: Timed out waiting to receive cluster topology. Group:null]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:814)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:813)
> ... 9 more
> Exception in thread "main" java.lang.NullPointerException
> at com.redhat.mqe.lib.CoreClient.createSession(CoreClient.java:121)
> at com.redhat.mqe.acc.AccSenderClient.startClient(AccSenderClient.java:70)
> at com.redhat.mqe.lib.Main.main(Main.java:46)
> at com.redhat.mqe.acc.Main.main(Main.java:85)
> at com.redhat.mqe.acc.Main.main(Main.java:89)
> {noformat}
> AMQP sender
> {noformat}
> $ java -jar /var/dtests/node_data/clients/aac1.jar sender --log-msgs dict --broker localhost:5672 --conn-username admin --conn-password admin --address "test_node_large_durable_msg_queue" --count 1 --msg-content-from-file /tmp/bigfile1mb --msg-durable True
> 02:55:31,588 ERROR Error while sending a message!
> javax.jms.JMSException: Received error from remote peer without description [condition = amqp:connection:forced]
> at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:164)
> at org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)
> at org.apache.qpid.jms.provider.amqp.AmqpAbstractResource.processRemoteClose(AmqpAbstractResource.java:262)
> at org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:971)
> at org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:105)
> at org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:854)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Broker log
> {noformat}
> 2018-06-22 02:59:22,766 DEBUG [io.netty.util.Recycler] -Dio.netty.recycler.ratio: 8
> 2018-06-22 02:59:22,779 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.n
> etty.handler.codec.DecoderException: java.lang.NullPointerException
> at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:142) [artemis-server-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1359) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:935) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:404) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:304) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
> Caused by: java.lang.NullPointerException
> at org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:201) [artemis-server-2.6.1.amq-720004-redhat-1.jar:2.6.1.amq-720004-redhat-1]
> at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-all-4.1.19.Final-redhat-1.jar:4.1.19.Final-redhat-1]
> ... 14 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2818) [DMN Designer] [IE11] Rename throws an Error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2818?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2818:
--------------------------------
Description:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
h2. Manual Acceptance test
Rename via context dialog
- IE (/)
- Chrome (/)
- Firefox (/)
Rename via properties panel
- IE (/)
- Chrome (/)
- Firefox (/)
was:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
h2. Manual Acceptance test
Rename via context dialog
- IE (/)
- Chrome (/)
- Firefox (/)
Rename via properties panel
- IE
- Chrome
- Firefox
> [DMN Designer] [IE11] Rename throws an Error
> --------------------------------------------
>
> Key: DROOLS-2818
> URL: https://issues.jboss.org/browse/DROOLS-2818
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
> Renaming in properties panel works.
> h2. Manual Acceptance test
> Rename via context dialog
> - IE (/)
> - Chrome (/)
> - Firefox (/)
> Rename via properties panel
> - IE (/)
> - Chrome (/)
> - Firefox (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2818) [DMN Designer] [IE11] Rename throws an Error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2818?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2818:
--------------------------------
Description:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
h2. Manual Acceptance test
Rename via context dialog
- IE (/)
- Chrome (/)
- Firefox (/)
Rename via properties panel
- IE
- Chrome
- Firefox
was:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
h2. Manual Acceptance test
Rename via context dialog
- IE
- Chrome
- Firefox
Rename via properties panel
- IE
- Chrome
- Firefox
> [DMN Designer] [IE11] Rename throws an Error
> --------------------------------------------
>
> Key: DROOLS-2818
> URL: https://issues.jboss.org/browse/DROOLS-2818
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
> Renaming in properties panel works.
> h2. Manual Acceptance test
> Rename via context dialog
> - IE (/)
> - Chrome (/)
> - Firefox (/)
> Rename via properties panel
> - IE
> - Chrome
> - Firefox
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2818) [DMN Designer] [IE11] Rename throws an Error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2818?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2818:
--------------------------------
Description:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
h2. Manual Acceptance test
Rename via context dialog
- IE
- Chrome
- Firefox
Rename via properties panel
- IE
- Chrome
- Firefox
was:
Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
Renaming in properties panel works.
> [DMN Designer] [IE11] Rename throws an Error
> --------------------------------------------
>
> Key: DROOLS-2818
> URL: https://issues.jboss.org/browse/DROOLS-2818
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> Rename via context menu throws an error dialog: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*
> Renaming in properties panel works.
> h2. Manual Acceptance test
> Rename via context dialog
> - IE
> - Chrome
> - Firefox
> Rename via properties panel
> - IE
> - Chrome
> - Firefox
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFWIP-72) Critical IO Error ... when starting Artemis with HA JDBC store
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-72?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak closed WFWIP-72.
-------------------------------
Resolution: Done
This one is fixed in WF14. Closing.
> Critical IO Error ... when starting Artemis with HA JDBC store
> --------------------------------------------------------------
>
> Key: WFWIP-72
> URL: https://issues.jboss.org/browse/WFWIP-72
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: feature-branch-blocker
> Attachments: log-node-1.zip
>
>
> One of the servers in collocated HA topology with JDBC store can fail on critical IO exception and stop itself.
> This was hit on Artemis 1.5.5.012 and WF: https://github.com/jmesnil/wildfly - WFLY-9513_messaging_jdbc_HA_shared-store branch.
> Test scenario:
> * Start 2 WF/EAP servers in collocated topology with Artemis HA JDBC store
> * Start client which are sending and consuming messages to/from queue from 1st server
> Result:
> There is intermittent failure when client start to send/receive messages on 1st server. 1st fails on Critical IO Error with exception:
> {code}
> 10:19:27,965 WARN [org.apache.activemq.artemis.journal] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@7de7cbe3)) AMQ142021: Error on IO callback, null
> 10:19:27,965 WARN [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@7de7cbe3)) AMQ222010: Critical IO Error, shutting down the server. file=org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile@407c5d8f, message=Error writing to JDBC file.: java.lang.NullPointerException
> at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.internalWrite(JDBCSequentialFile.java:161) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.internalWrite(JDBCSequentialFile.java:186) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.lambda$scheduleWrite$1(JDBCSequentialFile.java:197) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> {code}
> NPE happens at {{JDBCSequentialFile.internalWrite}} line 161:
> {code}
> private synchronized int internalWrite(byte[] data, IOCallback callback) {
> try {
> open();
> 161 synchronized (writeLock) { <-- NPE is thrown here
> ...
> {code}
> .
> Attaching logs from the test.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFWIP-120) [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-120?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFWIP-120:
---------------------------------
Steps to Reproduce:
*Issue is intermittent:*
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/331/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=Lodh2TestCase#testLodh3kill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1534928425-SNAPSHOT -DfailIfNoTests=false -Deap=7x -Dprepare.param.DATABASE=oracle12cR2 -Dprepare.param.JDBC_STORE=true | tee log
{code}
was:
*Issue is intermittent:*
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/331/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest= -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1534928425-SNAPSHOT -DfailIfNoTests=false -Deap=7x -Dprepare.param.DATABASE=oracle12cR2 -Dprepare.param.JDBC_STORE=true | tee log
{code}
> [Artemis 2.x upgrade] Undelivered/Lost messages in remote JCA scenario with killing remote servers
> --------------------------------------------------------------------------------------------------
>
> Key: WFWIP-120
> URL: https://issues.jboss.org/browse/WFWIP-120
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
>
> There undelivered/lost messages in sceario where MDB is connected to remote Artemis cluster in which nodes are killed and restarted. Issue is intermittent.
> Test Scenario:
> * start cluster containing node 1 and 3 with deployed inQueue and outQueue
> ** JDBC store with Oracle 12c is used
> * start node 2 and 4
> * producer sends 5000 small and large messages to inQueue to node-1
> * wait for producer to finish
> * deploy MDBs to node-2 and node-4 which read messages from inQueue and sends them to outQueue in XA transactions
> * kill and start following nodes in this sequence: 1,3,1,3,1
> * wait until all messages are processed
> * start Consumer which consumes messages form outQueue
> * Check that number of messages sent to InQueue and received from OutQueue is the same
> Result:
> 7 messages were missing in OutQueue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months