[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-9955:
-------------------------------------
The documentation update should say why the restriction is necessary.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-9955:
-------------------------------------
Just a comment that if we set it to anything other than the value that the user requests we should log an error so they can fix their code and ensure it is in the documentation.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9982) Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9982?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9982:
---------------------------------
Attachment: node-1-thread-dump-when-killed-shutdown-sequence.txt
> Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
> ------------------------------------------------------------------------------
>
> Key: WFLY-9982
> URL: https://issues.jboss.org/browse/WFLY-9982
> Project: WildFly
> Issue Type: Bug
> Components: MSC, Server
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Attachments: node-1-thread-dump-when-killed-shutdown-sequence.txt
>
>
> There is intermittent failure where server does not stop and hangs during clean shutdown.
> Investigation:
> In attached thread dump there is shutdown of WF/EAP JVM thread waiting for finishing org.jboss.as.server.BootstrapImpl$ShutdownHook:
> {code}
> "Management Triggered Shutdown" #262 prio=5 os_prio=0 tid=0x00007f931c03b800 nid=0x3900 in Object.wait() [0x00007f9296423000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
> at java.lang.Thread.join(Thread.java:1252)
> - locked <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
> at java.lang.Thread.join(Thread.java:1326)
> at java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
> at java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
> at java.lang.Shutdown.sequence(Shutdown.java:167)
> at java.lang.Shutdown.exit(Shutdown.java:212)
> - locked <0x00000000cedfac08> (a java.lang.Class for java.lang.Shutdown)
> at java.lang.Runtime.exit(Runtime.java:109)
> at java.lang.System.exit(System.java:971)
> at org.jboss.as.server.SystemExiter$DefaultExiter.exit(SystemExiter.java:117)
> at org.jboss.as.server.SystemExiter.logAndExit(SystemExiter.java:98)
> at org.jboss.as.server.operations.ServerShutdownHandler$ShutdownAction$1.run(ServerShutdownHandler.java:184)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> which hangs in:
> {code}
> "Thread-3" #12 prio=5 os_prio=0 tid=0x00007f92d01dc800 nid=0x3902 waiting on condition [0x00007f9296221000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000fc2531d8> (a java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.shutdown(BootstrapImpl.java:276)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.run(BootstrapImpl.java:240)
> {code}
> where ShutdownHook.shutdown(BootstrapImpl.java:276) is waiting for latch to count down however this does not happen. It seems like that not all services shut down.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9982) Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9982?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9982:
---------------------------------
Component/s: MSC
> Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
> ------------------------------------------------------------------------------
>
> Key: WFLY-9982
> URL: https://issues.jboss.org/browse/WFLY-9982
> Project: WildFly
> Issue Type: Bug
> Components: MSC, Server
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
>
> There is intermittent failure where server does not stop and hangs during clean shutdown.
> Investigation:
> In attached thread dump there is shutdown of WF/EAP JVM thread waiting for finishing org.jboss.as.server.BootstrapImpl$ShutdownHook:
> {code}
> "Management Triggered Shutdown" #262 prio=5 os_prio=0 tid=0x00007f931c03b800 nid=0x3900 in Object.wait() [0x00007f9296423000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
> at java.lang.Thread.join(Thread.java:1252)
> - locked <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
> at java.lang.Thread.join(Thread.java:1326)
> at java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
> at java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
> at java.lang.Shutdown.sequence(Shutdown.java:167)
> at java.lang.Shutdown.exit(Shutdown.java:212)
> - locked <0x00000000cedfac08> (a java.lang.Class for java.lang.Shutdown)
> at java.lang.Runtime.exit(Runtime.java:109)
> at java.lang.System.exit(System.java:971)
> at org.jboss.as.server.SystemExiter$DefaultExiter.exit(SystemExiter.java:117)
> at org.jboss.as.server.SystemExiter.logAndExit(SystemExiter.java:98)
> at org.jboss.as.server.operations.ServerShutdownHandler$ShutdownAction$1.run(ServerShutdownHandler.java:184)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> which hangs in:
> {code}
> "Thread-3" #12 prio=5 os_prio=0 tid=0x00007f92d01dc800 nid=0x3902 waiting on condition [0x00007f9296221000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000000fc2531d8> (a java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.shutdown(BootstrapImpl.java:276)
> at org.jboss.as.server.BootstrapImpl$ShutdownHook.run(BootstrapImpl.java:240)
> {code}
> where ShutdownHook.shutdown(BootstrapImpl.java:276) is waiting for latch to count down however this does not happen. It seems like that not all services shut down.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9982) Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-9982:
------------------------------------
Summary: Sometimes BootstrapImpl$ShutdownHook does not finish and holds server shutdown
Key: WFLY-9982
URL: https://issues.jboss.org/browse/WFLY-9982
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 12.0.0.Final
Reporter: Miroslav Novak
Assignee: Jason Greene
There is intermittent failure where server does not stop and hangs during clean shutdown.
Investigation:
In attached thread dump there is shutdown of WF/EAP JVM thread waiting for finishing org.jboss.as.server.BootstrapImpl$ShutdownHook:
{code}
"Management Triggered Shutdown" #262 prio=5 os_prio=0 tid=0x00007f931c03b800 nid=0x3900 in Object.wait() [0x00007f9296423000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
at java.lang.Thread.join(Thread.java:1252)
- locked <0x00000000cf059e98> (a org.jboss.as.server.BootstrapImpl$ShutdownHook)
at java.lang.Thread.join(Thread.java:1326)
at java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:106)
at java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
at java.lang.Shutdown.runHooks(Shutdown.java:123)
at java.lang.Shutdown.sequence(Shutdown.java:167)
at java.lang.Shutdown.exit(Shutdown.java:212)
- locked <0x00000000cedfac08> (a java.lang.Class for java.lang.Shutdown)
at java.lang.Runtime.exit(Runtime.java:109)
at java.lang.System.exit(System.java:971)
at org.jboss.as.server.SystemExiter$DefaultExiter.exit(SystemExiter.java:117)
at org.jboss.as.server.SystemExiter.logAndExit(SystemExiter.java:98)
at org.jboss.as.server.operations.ServerShutdownHandler$ShutdownAction$1.run(ServerShutdownHandler.java:184)
at java.lang.Thread.run(Thread.java:748)
{code}
which hangs in:
{code}
"Thread-3" #12 prio=5 os_prio=0 tid=0x00007f92d01dc800 nid=0x3902 waiting on condition [0x00007f9296221000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000fc2531d8> (a java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at org.jboss.as.server.BootstrapImpl$ShutdownHook.shutdown(BootstrapImpl.java:276)
at org.jboss.as.server.BootstrapImpl$ShutdownHook.run(BootstrapImpl.java:240)
{code}
where ShutdownHook.shutdown(BootstrapImpl.java:276) is waiting for latch to count down however this does not happen. It seems like that not all services shut down.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-9955:
-----------------------------------
{quote}
if the value == 0;
TxControl.setDefaultTimeout(0); // the transaction will be never time out. So it is OK to set zero here
ContextTransactionManager.setGlobalDefaultTransactionTimeout(0); // this is wrong, so it has to be converted to the maximum timeout which might be Integer.MAX_VALUE
{quote}
Correct.
{quote}
[~dmlloyd], I do not understand the necessary to introduce a maximum timeout attribute. I suppose to change the above codes to
{code}
int timeoutValue = resolvedValue.asInt();
TxControl.setDefaultTimeout(timeoutValue);
if (timeoutValue == 0) {
timeoutValue = Integer.MAX_VALUE;
}
ContextTransactionManager.setGlobalDefaultTransactionTimeout(timeoutValue);
{code}
{quote}
My understanding from talking with Tom and [~ochaloup] is that some resources may fail with a timeout value of {{Integer.MAX_VALUE}} for various reasons, so a lower "maximum" (such as one year) might be better. The purpose of the _suggestion_ of the maximum timeout attribute would be to make this value configurable (also in the event where someone programmatically sets a timeout which might be problematic), but this is just an idea, not a requirement.
> Compatibility problem: allow a timeout value of "0" to be set
> -------------------------------------------------------------
>
> Key: WFLY-9955
> URL: https://issues.jboss.org/browse/WFLY-9955
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value.
> The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2373:
--------------------------------
Description:
Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
*Edited*
The problem is that in the piece of code below the expression {{column.getOperator()}} returns null.
{{BRLConditionVariableColumnConverter#convertColumn}}
{code:java}
if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
return newMultipleSelectEnumColumn(factType,
factField,
column,
access,
gridWidget);
} else {
return newSingleSelectionEnumColumn(factType,
factField,
dataType,
column,
access,
gridWidget);
}
{code}
was:
Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
*Edited*
The problem is that in the piece of code below the expressions {{column.getOperator()}} returns null.
{{BRLConditionVariableColumnConverter#convertColumn}}
{code:java}
if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
return newMultipleSelectEnumColumn(factType,
factField,
column,
access,
gridWidget);
} else {
return newSingleSelectionEnumColumn(factType,
factField,
dataType,
column,
access,
gridWidget);
}
{code}
> BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-2373
> URL: https://issues.jboss.org/browse/DROOLS-2373
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor, Guided Rule Editor
> Affects Versions: 7.6.0.Final
> Environment: Tomcat 8.5 / RHEL 7
> Reporter: Yannick Geerts
> Assignee: Michael Anstis
>
> Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
> *Edited*
> The problem is that in the piece of code below the expression {{column.getOperator()}} returns null.
> {{BRLConditionVariableColumnConverter#convertColumn}}
> {code:java}
> if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
> return newMultipleSelectEnumColumn(factType,
> factField,
> column,
> access,
> gridWidget);
> } else {
> return newSingleSelectionEnumColumn(factType,
> factField,
> dataType,
> column,
> access,
> gridWidget);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2373:
--------------------------------
Description:
Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
*Edited*
The problem is that in the piece of code below the expressions {{column.getOperator()}} returns null.
{{BRLConditionVariableColumnConverter#convertColumn}}
{code:java}
if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
return newMultipleSelectEnumColumn(factType,
factField,
column,
access,
gridWidget);
} else {
return newSingleSelectionEnumColumn(factType,
factField,
dataType,
column,
access,
gridWidget);
}
{code}
was:
Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
> BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-2373
> URL: https://issues.jboss.org/browse/DROOLS-2373
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor, Guided Rule Editor
> Affects Versions: 7.6.0.Final
> Environment: Tomcat 8.5 / RHEL 7
> Reporter: Yannick Geerts
> Assignee: Michael Anstis
>
> Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
> *Edited*
> The problem is that in the piece of code below the expressions {{column.getOperator()}} returns null.
> {{BRLConditionVariableColumnConverter#convertColumn}}
> {code:java}
> if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
> return newMultipleSelectEnumColumn(factType,
> factField,
> column,
> access,
> gridWidget);
> } else {
> return newSingleSelectionEnumColumn(factType,
> factField,
> dataType,
> column,
> access,
> gridWidget);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2375) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2375:
-----------------------------------
Summary: BRL "is contained in the (comma separated) list" does not produce multiselect dropdown
Key: DROOLS-2375
URL: https://issues.jboss.org/browse/DROOLS-2375
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor, Guided Rule Editor
Affects Versions: 7.6.0.Final
Environment: Tomcat 8.5 / RHEL 7
Reporter: Jozef Marko
Assignee: Michael Anstis
Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs
*Edited*
The problem is that in the piece of code below the expressions {{column.getOperator()}} returns null.
{{BRLConditionVariableColumnConverter#convertColumn}}
{code:java}
if (OperatorsOracle.operatorRequiresList(column.getOperator())) {
return newMultipleSelectEnumColumn(factType,
factField,
column,
access,
gridWidget);
} else {
return newSingleSelectionEnumColumn(factType,
factField,
dataType,
column,
access,
gridWidget);
}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months