[JBoss JIRA] (DROOLS-3844) DMN Editor not immediate how to relinquish space on the right
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3844?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3844:
-----------------------------------
Tester: Jozef Marko
> DMN Editor not immediate how to relinquish space on the right
> -------------------------------------------------------------
>
> Key: DROOLS-3844
> URL: https://issues.jboss.org/browse/DROOLS-3844
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Matteo Mortari
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: image-2019-04-03-10-41-41-987.png, image-2019-04-03-10-43-17-267.png
>
>
> In this example,
> !image-2019-04-03-10-41-41-987.png|thumbnail!
> One may notice the Description annotation column is "wasting" a lot of space. If I try to resize the Description column, I cannot:
> !image-2019-04-03-10-43-17-267.png|thumbnail!
> as the cursor does not change to horizonal resize cursor for the column.
> I later figured the only way is to act on the top-most parent.
> Can you consider if there can be a more easier/faster UX experience for this, please?
> Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3844) DMN Editor not immediate how to relinquish space on the right
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3844?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3844:
-----------------------------------
Labels: drools-tools (was: )
> DMN Editor not immediate how to relinquish space on the right
> -------------------------------------------------------------
>
> Key: DROOLS-3844
> URL: https://issues.jboss.org/browse/DROOLS-3844
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Matteo Mortari
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: image-2019-04-03-10-41-41-987.png, image-2019-04-03-10-43-17-267.png
>
>
> In this example,
> !image-2019-04-03-10-41-41-987.png|thumbnail!
> One may notice the Description annotation column is "wasting" a lot of space. If I try to resize the Description column, I cannot:
> !image-2019-04-03-10-43-17-267.png|thumbnail!
> as the cursor does not change to horizonal resize cursor for the column.
> I later figured the only way is to act on the top-most parent.
> Can you consider if there can be a more easier/faster UX experience for this, please?
> Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3844) DMN Editor not immediate how to relinquish space on the right
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3844:
--------------------------------------
Summary: DMN Editor not immediate how to relinquish space on the right
Key: DROOLS-3844
URL: https://issues.jboss.org/browse/DROOLS-3844
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Michael Anstis
Attachments: image-2019-04-03-10-41-41-987.png, image-2019-04-03-10-43-17-267.png
In this example,
!image-2019-04-03-10-41-41-987.png|thumbnail!
One may notice the Description annotation column is "wasting" a lot of space. If I try to resize the Description column, I cannot:
!image-2019-04-03-10-43-17-267.png|thumbnail!
as the cursor does not change to horizonal resize cursor for the column.
I later figured the only way is to act on the top-most parent.
Can you consider if there can be a more easier/faster UX experience for this, please?
Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3843) DMN Editor Decision Navigator differentiate icons for DRGElement
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3843:
--------------------------------------
Summary: DMN Editor Decision Navigator differentiate icons for DRGElement
Key: DROOLS-3843
URL: https://issues.jboss.org/browse/DROOLS-3843
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Michael Anstis
Attachments: image-2019-04-03-10-38-39-270.png
In this example:
!image-2019-04-03-10-38-39-270.png|thumbnail!
The 1st one is a Decision, the other are Input Data.
Experienced DMN practitioner may know that a decision logic can only happen to Decision or BKM node, hence one could distinguish potential Input data node by not having decision logic (context in the example). But also what about Decision or BKM for which you didn't write the decision logic yet?
PLease consider distinguished icon for DRG Elements.
For example
leave Input Data with the filled circle
Decision: filled square
BKM: filled trapezoid.
Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBREM-1340) Memory leak related to org.jboss.threads.JBossThreadFactory
by Adrián López (Jira)
[ https://issues.jboss.org/browse/JBREM-1340?page=com.atlassian.jira.plugin... ]
Adrián López commented on JBREM-1340:
-------------------------------------
Where can I find some doc to know how to configure the new client with the "old" remoting?
Kinda los with this protocol and its transports.
Thanks
> Memory leak related to org.jboss.threads.JBossThreadFactory
> -----------------------------------------------------------
>
> Key: JBREM-1340
> URL: https://issues.jboss.org/browse/JBREM-1340
> Project: JBoss Remoting
> Issue Type: Bug
> Components: jmx remoting
> Reporter: Adrián López
> Priority: Major
> Attachments: img-2019-04-01-130952.png, lep2jia1-heapdump-1554113927775_Leak_Suspects.zip
>
>
> We have a memory leak when using the jboss-cli-client JAR inside of Jolokia.
> Jolokia uses remoting to connect to the JMX of several JBoss servers. After running for some days, the Old Gen memory space reach 100%.
> A heap dump analyzed with Eclipse MAT returns:
> {code}
> One instance of "java.lang.ThreadGroup" loaded by "<system class loader>" occupies 377.517.248 (87,28%) bytes. The instance is referenced by org.jboss.threads.JBossThread @ 0xe0a81ef0 HTTP-11 , loaded by "org.jboss.modules.ModuleClassLoader @ 0xe04ffe20". The memory is accumulated in one instance of "java.lang.ThreadGroup[]" loaded by "<system class loader>".
> The stacktrace of this Thread is available. See stacktrace.
> Keywords
> java.lang.ThreadGroup[]
> org.jboss.modules.ModuleClassLoader @ 0xe04ffe20
> java.lang.ThreadGroup
> {code}
> Thread stack
> {code}
> HTTP-11
> at sun.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park(Ljava/lang/Object;)V (LockSupport.java:186)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await()V (AbstractQueuedSynchronizer.java:2043)
> at java.util.concurrent.LinkedBlockingQueue.take()Ljava/lang/Object; (LinkedBlockingQueue.java:442)
> at java.util.concurrent.ThreadPoolExecutor.getTask()Ljava/lang/Runnable; (ThreadPoolExecutor.java:1068)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (ThreadPoolExecutor.java:1130)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run()V (ThreadPoolExecutor.java:615)
> at java.lang.Thread.run()V (Thread.java:745)
> at org.jboss.threads.JBossThread.run()V (JBossThread.java:122)
> {code}
> I have created also another [issue|https://issues.jboss.org/browse/JBTHR-72] to jboss-threads, but looks the problem is not there.
> Same for [Jolokia|https://github.com/rhuss/jolokia/issues/401]
> Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11936) Unbound log messages at server startup
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-11936:
--------------------------------------
Summary: Unbound log messages at server startup
Key: WFLY-11936
URL: https://issues.jboss.org/browse/WFLY-11936
Project: WildFly
Issue Type: Bug
Components: Naming
Affects Versions: 16.0.0.Final
Reporter: Eduardo Martins
Assignee: Eduardo Martins
When server starts there are "Unbound ..." messages incorrectly logged, before related resources are bound. E.g. the following messages may be seen when starting the standalone-full.xml configuration:
{code}
07:14:07,656 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
07:14:07,674 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
07:14:07,855 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
07:14:08,604 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
07:14:11,858 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
07:14:11,862 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
07:14:12,131 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
07:14:12,131 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-9448) Unrecoverable "..DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state.." after " Unable to acquire lock after 15 seconds"
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-9448?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-9448.
------------------------------
Resolution: Out of Date
> Unrecoverable "..DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state.." after " Unable to acquire lock after 15 seconds"
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9448
> URL: https://issues.jboss.org/browse/WFLY-9448
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Environment: Centos
> Reporter: jamie smith
> Assignee: Paul Ferraro
> Priority: Major
>
> On our system, after some time we get this:
> javax.ejb.EJBTransactionRolledbackException: ISPN000299: Unable to acquire lock after 15 seconds for key UnknownSessionID [4957576549555554536866505268565165695766655070536957516655656852] and requestor GlobalTransaction:<node1>:682146:local. Lock is held by GlobalTransaction:<node1>:681890:local
> And then we start getting the following:
> ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-2) ISPN000136: Error executing command GetKeyValueCommand, writing keys []: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state to be invoking cache operations on.
> at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:395)
> ...
> ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /contextpath/someXYZResource: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state to be invoking cache operations on.
> continouously on most requests without being able to recover.
> After restarting, again if at some point the "Unable to acquire lock after 15 seconds" happens, we start getting errors about the DummyTransaction, which never stop.
> I believe "Unable to acquire lock after 15 seconds" should not lead to an unrecoverable state.
> NOTE: Each node runs with:
> `./standalone.sh -c=standalone-full-ha.xml -u=239.255.200.215 -b=$localIp -bmanagement=$localIp -bprivate=$localIp -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=200` .
> `jboss.node.name` and `$localIp` only changes between nodes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months