[JBoss JIRA] (WFLY-4384) ContextService (JSR236): transactional context always suspended
by Maxim Frolov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4384?page=com.atlassian.jira.plugin.... ]
Maxim Frolov closed WFLY-4384.
------------------------------
Resolution: Rejected
It works as defined by the specification.
See also:
https://java.net/projects/concurrency-ee-spec/lists/users/archive/2015-03...
> ContextService (JSR236): transactional context always suspended
> ---------------------------------------------------------------
>
> Key: WFLY-4384
> URL: https://issues.jboss.org/browse/WFLY-4384
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 8.2.0.Final, 9.0.0.Alpha1
> Reporter: Maxim Frolov
> Assignee: Eduardo Martins
> Priority: Critical
>
> According to §3.3.5 of JSR-236 specification:
> ??By using an execution property when creating the contextual proxy object, application components can choose to not suspend the transactional context on the thread ...??
> Given the following EJB and Task:
> {code:java}
> @WebService(serviceName = "Jsr236WebService")
> @Stateless
> public class Jsr236WebService {
> @Inject Jsr236ManagedTask jsr236ManagedTask;
> @Resource ManagedExecutorService executor;
> @Resource ContextService contextService;
>
> @WebMethod(operationName = "hello")
> public String hello(@WebParam(name = "name") String txt) {
> Map<String, String> execProps = new HashMap<>();
> execProps.put(ManagedTask.TRANSACTION, ManagedTask.USE_TRANSACTION_OF_EXECUTION_THREAD);
> Future<String> future = executor.submit(
> contextService.createContextualProxy(jsr236ManagedTask, execProps, Callable.class));
> try {
> return future.get();
> } catch (InterruptedException | ExecutionException e) {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> {code:java}
> @Dependent
> @Transactional(Transactional.TxType.MANDATORY)
> public class Jsr236ManagedTask implements Callable<String>, ManagedTask {
> @Override
> public String call() {
> return "called";
> }
> @Override
> public Map<String, String> getExecutionProperties() {
> Map<String, String> execProps = new HashMap<>();
> execProps.put(ManagedTask.TRANSACTION, ManagedTask.USE_TRANSACTION_OF_EXECUTION_THREAD);
> return execProps;
> }
> }
> {code}
> When the {{call()}} Method of the task is called the following exception occurs:
> {noformat}
> javax.transaction.TransactionalException: ARJUNA016110: Transaction is required for invocation
> {noformat}
> See maven test project [https://github.com/wrungel/bugs/tree/master/jsr236-test] on GitHub.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (REMJMX-95) RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around
by Sergiy Barlabanov (JIRA)
[ https://issues.jboss.org/browse/REMJMX-95?page=com.atlassian.jira.plugin.... ]
Sergiy Barlabanov updated REMJMX-95:
------------------------------------
Summary: RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around (was: RemotingConnector violates JMXConnector#connect contract and leads to thread explosion)
> RemotingConnector violates JMXConnector#connect contract and leads to threads hanging around
> --------------------------------------------------------------------------------------------
>
> Key: REMJMX-95
> URL: https://issues.jboss.org/browse/REMJMX-95
> Project: Remoting JMX
> Issue Type: Feature Request
> Components: Connection
> Affects Versions: 2.0.0.Final
> Environment: Wildfly 8.2.0
> Reporter: Sergiy Barlabanov
> Assignee: Darran Lofthouse
>
> The javadoc of javax.management.remote.JMXConnector#connect says that "If connect has already been called successfully on this object, calling it again has no effect.".
> But this does not work with org.jboss.remotingjmx.RemotingConnector. Every connect result in a creation of a remoting endpoint with the corresponding io/worker threads, which are not closed when close() method is called. Only the threads from the first connect() invocation are closed, all threads created from the subsequent connect() invocations are not closed and stay alive until the VM shutdown.
> Our application currently crashes after 10 minutes running - it pulls some JMX data periodically and after some time, the VM refuses to create new threads.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (REMJMX-95) RemotingConnector violates JMXConnector#connect contract and leads to thread explosion
by Sergiy Barlabanov (JIRA)
Sergiy Barlabanov created REMJMX-95:
---------------------------------------
Summary: RemotingConnector violates JMXConnector#connect contract and leads to thread explosion
Key: REMJMX-95
URL: https://issues.jboss.org/browse/REMJMX-95
Project: Remoting JMX
Issue Type: Feature Request
Components: Connection
Affects Versions: 2.0.0.Final
Environment: Wildfly 8.2.0
Reporter: Sergiy Barlabanov
Assignee: Darran Lofthouse
The javadoc of javax.management.remote.JMXConnector#connect says that "If connect has already been called successfully on this object, calling it again has no effect.".
But this does not work with org.jboss.remotingjmx.RemotingConnector. Every connect result in a creation of a remoting endpoint with the corresponding io/worker threads, which are not closed when close() method is called. Only the threads from the first connect() invocation are closed, all threads created from the subsequent connect() invocations are not closed and stay alive until the VM shutdown.
Our application currently crashes after 10 minutes running - it pulls some JMX data periodically and after some time, the VM refuses to create new threads.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-740) NoSuchMethodError at runtime while evaluating String and Long
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-740?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-740:
------------------------------------------------
Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug 1202365|https://bugzilla.redhat.com/show_bug.cgi?id=1202365] from MODIFIED to ASSIGNED
> NoSuchMethodError at runtime while evaluating String and Long
> -------------------------------------------------------------
>
> Key: DROOLS-740
> URL: https://issues.jboss.org/browse/DROOLS-740
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 6.3.0.Beta1
>
>
> When you write a LHS like this,
> {noformat}
> Person( name == "Elizabeth" + new Long(2L) )
> {noformat}
> you will face NoSuchMethodError after 20 times evaluation.
> {noformat}
> testJittedConstraintStringAndLong(org.drools.compiler.integrationtests.Misc2Test) Time elapsed: 1.216 sec <<< ERROR!
> java.lang.NoSuchMethodError: java.lang.StringBuilder.append(Ljava/lang/Long;)Ljava/lang/StringBuilder;
> at ConditionEvaluator80a8832efb1646d488df2cde72963f02.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:294)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:255)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:277)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:237)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1495)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1450)
> at org.drools.compiler.integrationtests.Misc2Test.testJittedConstraintStringAndLong(Misc2Test.java:7253)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4164) New JTS record types are not showing up in the CLI
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4164?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-4164:
-------------------------------------
Fixed in Narayana 5.0.5-SNAPSHOT (master) - needs release and version upgrade
> New JTS record types are not showing up in the CLI
> --------------------------------------------------
>
> Key: WFLY-4164
> URL: https://issues.jboss.org/browse/WFLY-4164
> Project: WildFly
> Issue Type: Enhancement
> Components: CLI, Transactions
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
>
> We need to expose the new JTS record types in the tooling:
> {code}
> AssumedCompleteHeuristicTransaction
> AssumedCompleteHeuristicServerTransaction
> AssumedCompleteTransaction
> AssumedCompleteServerTransaction
> {code}
> We need these because if a transaction ends up in a heuristic state we can't actually view this using the CLI even though the records are in the object store. This has the consequence that a transaction can remain in the object store indefinitely.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-740) NoSuchMethodError at runtime while evaluating String and Long
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-740?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-740:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1202365|https://bugzilla.redhat.com/show_bug.cgi?id=1202365] from ASSIGNED to MODIFIED
> NoSuchMethodError at runtime while evaluating String and Long
> -------------------------------------------------------------
>
> Key: DROOLS-740
> URL: https://issues.jboss.org/browse/DROOLS-740
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 6.3.0.Beta1
>
>
> When you write a LHS like this,
> {noformat}
> Person( name == "Elizabeth" + new Long(2L) )
> {noformat}
> you will face NoSuchMethodError after 20 times evaluation.
> {noformat}
> testJittedConstraintStringAndLong(org.drools.compiler.integrationtests.Misc2Test) Time elapsed: 1.216 sec <<< ERROR!
> java.lang.NoSuchMethodError: java.lang.StringBuilder.append(Ljava/lang/Long;)Ljava/lang/StringBuilder;
> at ConditionEvaluator80a8832efb1646d488df2cde72963f02.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:294)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:255)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:277)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:237)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1495)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1450)
> at org.drools.compiler.integrationtests.Misc2Test.testJittedConstraintStringAndLong(Misc2Test.java:7253)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-740) NoSuchMethodError at runtime while evaluating String and Long
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-740?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-740:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1202365|https://bugzilla.redhat.com/show_bug.cgi?id=1202365] from NEW to ASSIGNED
> NoSuchMethodError at runtime while evaluating String and Long
> -------------------------------------------------------------
>
> Key: DROOLS-740
> URL: https://issues.jboss.org/browse/DROOLS-740
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 6.3.0.Beta1
>
>
> When you write a LHS like this,
> {noformat}
> Person( name == "Elizabeth" + new Long(2L) )
> {noformat}
> you will face NoSuchMethodError after 20 times evaluation.
> {noformat}
> testJittedConstraintStringAndLong(org.drools.compiler.integrationtests.Misc2Test) Time elapsed: 1.216 sec <<< ERROR!
> java.lang.NoSuchMethodError: java.lang.StringBuilder.append(Ljava/lang/Long;)Ljava/lang/StringBuilder;
> at ConditionEvaluator80a8832efb1646d488df2cde72963f02.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:294)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:255)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:277)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:237)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1495)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1450)
> at org.drools.compiler.integrationtests.Misc2Test.testJittedConstraintStringAndLong(Misc2Test.java:7253)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-740) NoSuchMethodError at runtime while evaluating String and Long
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-740?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated DROOLS-740:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1202365
> NoSuchMethodError at runtime while evaluating String and Long
> -------------------------------------------------------------
>
> Key: DROOLS-740
> URL: https://issues.jboss.org/browse/DROOLS-740
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Fix For: 6.3.0.Beta1
>
>
> When you write a LHS like this,
> {noformat}
> Person( name == "Elizabeth" + new Long(2L) )
> {noformat}
> you will face NoSuchMethodError after 20 times evaluation.
> {noformat}
> testJittedConstraintStringAndLong(org.drools.compiler.integrationtests.Misc2Test) Time elapsed: 1.216 sec <<< ERROR!
> java.lang.NoSuchMethodError: java.lang.StringBuilder.append(Ljava/lang/Long;)Ljava/lang/StringBuilder;
> at ConditionEvaluator80a8832efb1646d488df2cde72963f02.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:294)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:255)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:277)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:237)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1495)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1450)
> at org.drools.compiler.integrationtests.Misc2Test.testJittedConstraintStringAndLong(Misc2Test.java:7253)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4424) NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/WFLY-4424?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on WFLY-4424:
---------------------------------------
Unfortunately it failed: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2351/1/artifact/XTS/localj...
> NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig
> --------------------------------------------------------------------------
>
> Key: WFLY-4424
> URL: https://issues.jboss.org/browse/WFLY-4424
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Gytis Trikleris
> Assignee: Alessio Soldano
>
> Lately we started to get following exception in our XTS tests:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xtstest.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xtstest.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "xtstest.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NullPointerException
> at org.jboss.ws.common.configuration.AbstractCommonConfigResolver.resolveEndpointConfig(AbstractCommonConfigResolver.java:129)
> at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:95)
> at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:74)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> {code}
> It is intermittent and seems to be caused by some sort of race condition.
> It started to happen once this commit was introduced: https://github.com/wildfly/wildfly/commit/c0c1e82d8472e1b29c679380d5e0aea...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months