[JBoss JIRA] (WFLY-6797) Is there a way to have more than one logging subystem belonging to one profile
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6797?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-6797:
-----------------------------------
Description:
I have "ha" profile in my domain.xml which has many subsystems.
Below is the structure I have:-
{color:#205081}<server-groups>
<server-group name="main-server-group" profile="ha">
<socket-binding-group ref="ha-sockets"/>
<deployments>
<deployment name="RC.war" runtime-name="RC.war"/>
</deployments>
</server-group>
<server-group name="other-server-group" profile="ha">
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="SL.war" runtime-name="SL.war"/>
</deployments>
</server-group>
</server-groups>{color}
There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
Example:-
RC.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>
{color}
while SL.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="ISEE">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="isee.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="FILE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="DB_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="MQ_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="JMS_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="HTTP_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VMWARE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VSOC_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="CLOUD_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>{color}
Thanks,
Preeta
was:
I have "ha" profile in my domain.xml which has many subsystems.
Below is the structure I have:-
<server-groups>
<server-group name="main-server-group" profile="ha">
<socket-binding-group ref="ha-sockets"/>
<deployments>
<deployment name="RC.war" runtime-name="RC.war"/>
</deployments>
</server-group>
<server-group name="other-server-group" profile="ha">
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="SL.war" runtime-name="SL.war"/>
</deployments>
</server-group>
</server-groups>
There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
Thanks,
Preeta
> Is there a way to have more than one logging subystem belonging to one profile
> ------------------------------------------------------------------------------
>
> Key: WFLY-6797
> URL: https://issues.jboss.org/browse/WFLY-6797
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Brian Stansberry
>
> I have "ha" profile in my domain.xml which has many subsystems.
> Below is the structure I have:-
> {color:#205081}<server-groups>
> <server-group name="main-server-group" profile="ha">
> <socket-binding-group ref="ha-sockets"/>
> <deployments>
> <deployment name="RC.war" runtime-name="RC.war"/>
> </deployments>
> </server-group>
> <server-group name="other-server-group" profile="ha">
> <socket-binding-group ref="standard-sockets"/>
> <deployments>
> <deployment name="SL.war" runtime-name="SL.war"/>
> </deployments>
> </server-group>
> </server-groups>{color}
> There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
>
> Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
> Example:-
> RC.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>
> {color}
> while SL.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <periodic-rotating-file-handler name="ISEE">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="isee.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="FILE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="DB_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="MQ_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="JMS_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="HTTP_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VMWARE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VSOC_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="CLOUD_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>{color}
> Thanks,
> Preeta
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6761) Wrong XAException return code when broker timeout is hit
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-6761?page=com.atlassian.jira.plugin.... ]
Dmitrii Tikhomirov reassigned WFLY-6761:
----------------------------------------
Assignee: Chen Maoqian (was: Dmitrii Tikhomirov)
> Wrong XAException return code when broker timeout is hit
> --------------------------------------------------------
>
> Key: WFLY-6761
> URL: https://issues.jboss.org/browse/WFLY-6761
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chen Maoqian
> Priority: Minor
>
> By creating testcases for checking behavior of transaction timeout I've hit an issue of wrong error code being returned when broker transaction timeout is hit before TM transaction timeout expires.
> It uses {{XAER_PROTO}} instead of {{RBTIMEOUT}}.
> This issue does not cause data inconsistency.
> Scenario:
> * ejb sends a message to a queue
> * processing inside of the ejb takes long time
> ** TM transaction timeout is set big enough to not hit the timeout
> ** jms broker internal transaction timeout is smaller than time needed for processing ejb method
> * jms broker txn timeout occurs - broker local txn is rolled back
> ** txn is removed from list of broker's local in-process transactions
> * TM calls XAResource.end
> ** the call returns {{XAException.XAER_PROTO}}
> That's current implementation returns {{XAER_PROTO}} in this scenario but {{RBTIMEOUT}} would be more appropriate.
> From discussion with Narayana developers, RM should return the most specific error return code as possible. In this scenario it's {{RBTIMEOUT}}.
> Other notes from TM dev point of view:
> {code}
> "[XA_RBTIMEOUT]
> The work represented by this transaction branch took too long."
> {code}
> _per XA spec page 39._
> The more complex question is, at what point can the resource manager forget about that branch (and therefore return NOTA to subsequent calls)?
> The XA spec says "After the transaction manager calls xa_end(), it should no longer consider the calling thread associated with that resource manager (although it must consider the resource manager part of the transaction branch when it prepares the branch.)"
> which implies the branch is still considered live at that point, a view corroborated by:
> {code}
> "[XA_RB∗]
> The resource manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of ∗xid."
> {code}
> Exception being thrown
> {code}
> WARN [com.arjuna.ats.jta] (Thread-0
> (ActiveMQ-client-global-threads-1468293951)) ARJUNA016056:
> TransactionImple.delistResource - caught exception during delist :
> XAException.XAER_PROTO: javax.transaction.xa.XAException
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:346)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1115)
> at
> org.apache.activemq.artemis.ra.ActiveMQRAXAResource.end(ActiveMQRAXAResource.java:112)
> at
> org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.end(ActiveMQXAResourceWrapperImpl.java:81)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:897)
> at
> org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$TransactionSynchronization.beforeCompletion(TxConnectionListener.java:1063)
> at
> org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.invokeBefore(TransactionSynchronizer.java:438)
> at
> org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.beforeCompletion(TransactionSynchronizer.java:376)
> at
> org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.beforeCompletion(JCAOrderedLastSynchronizationList.java:130)
> at
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76)
> at
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371)
> at
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at
> com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89)
> at
> org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
> at
> org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
> at
> org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
> at
> org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean$$$endpoint1.afterDelivery(Unknown
> Source)
> at
> org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:321)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:932)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1045)
> at
> org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBMX-20) QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
by john dboss (JIRA)
john dboss created JBMX-20:
------------------------------
Summary: QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
Key: JBMX-20
URL: https://issues.jboss.org/browse/JBMX-20
Project: JBossMX
Issue Type: Bug
Environment: QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
Reporter: john dboss
Intuit Quickbooks +++»--A- 1-844-414-4868 Quickbooks Support Phone Number 1-844-414-4868 Quickbooks technical phone number,
1-844-414-4868 Quickbooks technical number, 1-844-414-4868 Quickbooks technical support contact number,1-844-414-4868
Quickbooks contact number, 1-844-414-4868Quickbooks contact phone number, 1-844-414-4868 Quickbooks contact telephone
number, Quickbooks 24 hour contact number, Quickbooks customer support contact number, Quickbooks customer service contact
number, 1-844-414-4868Quickbooks official number, Quickbooks official contact number, Quickbooks 877 contact number,
Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number Quickbooks support
phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support number.Quickbooks
support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number, Quickbooks
customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone number,
Quickbooks support phone number. Help@Call 1-844-414-4868/.Quickbooks 24/7 support phone number,Quickbooks telephone number
for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks contact telephone
numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks official
number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone numberQuickbooks
support number,Quickbooks telephone number for support QB SUPPORT ON ((1-844-414-4868) Quickbooks PHONE NUMBER AND
Quickbooks SUPPORT PHONE NUMBER Online Support For Quickbooks support help intuit customer service number tech support for Quickbooks technical support for Quickbooks technical support for intuit Quickbooks help website Quickbooks support website Quickbooks .com/helpme Quickbooks customer support website intuit Quickbooks head office intuit Quickbooks call center intuit support number (any thing with intuit ) buy Quickbooks enhance buy intuit enhance customer support for Quickbooks customer support for intuit customer support for intuit Quickbooks www.Quickbooks .com/support (((1-844-414-4868)!!! Quickbooks ((Technical)) Support phone number Quickbooks HELP DESK phone number Online Support For
(((1-844-414-4868)!!! Quickbooks ((Technical)) Support phone number Quickbooks HELP DESK phone number Helpline TECH ))1-844-414-4868((Quickbooks technical support phone number Quickbooks phone number QB SUPPORT ON ((1-844-414-4868)) Quickbooks
PHONE NUMBER AND Quickbooks SUPPORT PHONE NUMBER Quickbooks Toll Free, Intuit@(1-844-414-4868)@ Quickbooks HELP DESK Phone
Number vides online solution for all USA/CANADA clients. For any help of query call 1-844-414-4868to get all Quickbooks
account solution. @@Call, 1-844-414-4868 for all type help by Quickbooks HELP DESK phone number, Intuit Quickbooks HELP
DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number, Quickbooks
technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer
Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline Number, Quickbooks
Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks Helpline Number;
Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks HELP DESK
Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone number,
Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular toll free
number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service
Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline
Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone number,
Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
Quickbooks customer support phone number 1-844-414-4868 Quickbooks technical help telephone number, Quickbooks technical
help contact number, Quickbooks technical support contact number, Quickbooks contact number, Quickbooks contact phone
number, Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
Quickbooks customer service contact number, Quickbooks official number, Quickbooks official contact number, Quickbooks 877
contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number
Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support
number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number,
Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone
number, Quickbooks support phone number. Help@Call 1-877-778-8714/.Quickbooks 24/7 support phone number,Quickbooks
telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks
contact telephone numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks
official number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone
numberQuickbooks support number,Quickbooks telephone number for support Quickbooks Toll Free, Intuit@(1-877-778-8714)@
Quickbooks HELP DESK Phone Number vides online solution for all USA/CANADA clients. For any help of query call 1 877 778
8714 to get all Quickbooks account solution. @@Call, 1-877-778-8714 for all type help by Quickbooks HELP DESK phone number,
Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
technical support phone number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline
Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks
Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks
Support Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support
contact number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks
HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular
toll free number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer
Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service
Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone
number, Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number,
Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support
phone number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
Quickbooks customer support phone number 1-844-414-4868 Quickbooks technical help telephone number, Quickbooks technical
help contact number, Quickbooks technical support contact number, Quickbooks contact number, Quickbooks contact phone
number, Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
Quickbooks customer service contact number, Quickbooks official number, Quickbooks official contact number, Quickbooks 877
contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number
Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support
number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number,
Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone
number, Quickbooks support phone number. Help@Call 1-877-778-8714/.Quickbooks 24/7 support phone number,Quickbooks
telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks
contact telephone numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks
official number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone
numberQuickbooks support number,Quickbooks telephone number for support Talk:TollFree,California ((1877 778 8714 USA))
Quickbooks technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone Number Call,Av..1
(877) 778.8714..(((( Quickbooks support phone number, Quickbooks customer service phone number 1-877-778-8714 FREE FREE
FREE FREE FREE for all type help by QuickBook?.s HELP DESK phone number, Intuit QuickBook?.s HELP DESK Phone Number,
QuickBook?.s Help Desk Phone Number, QuickBook?.s HELP DESK number, QuickBook?.s technical support phone number,@@@
QuickBook?.s phone number, QuickBook?.s technical support number, QuickBook?.s support phone number, QuickBook?.s technical
support, QuickBook?.s Customer Service Phone Number, QuickBook?.s Customer Service Number, QuickBook?.s Customer Support
Phone Number, QuickBook?.s Customer Support Number,@@@@ QuickBook?.s Customer Service Helpline Number, QuickBook?.s
Customer Care Number, QuickBook?.s support team phone number Talk:TollFree,California ((1877 778 8714 USA)) Quickbooks
technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone Number TollFree?,California
((1877 778 8714 USA)) Quickbooks technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone
Number QuickBook?.s help number-QuickBook?.s Helpline Number; QuickBook?.s help phone number-QuickBook?.s Helpline Number,
QuickBook?.s HELP DESK Toll free Number, QuickBook?.s Support Telephone Number, QuickBook?.s HELP DESK Telephone number,
QuickBook?.s HELP DESK contact number, QuickBook?.s support contact number, QuickBook?.s technical support contact number.
Call, QuickCallSend? SMSCall from mobileAdd to Skype You'll need Skype CreditFree? via Skype Helpline Number)).. 1 (877)
778.8714..(((( Quickbooks HELP DESK phone number, Quickbooks customer service phone number Call,QB customer..1 (877)
778.8714..(((( Quickbooks support phone number, Quickbooks customer service phone number Call,..1 (877) 778.8714((((
Quickbooks technical support phone number.Quickbooks phone number Quickbooks Toll Free, Intuit@(1-877-778-8714)@-:
Quickbooks HELP DESK Phone Number vides online solution for all USA/CANADA clients. For any help of query call 1 877 778
8714 to get all Quickbooks account solution. @@Call, 1-877-778-8714 for all type help by Quickbooks HELP DESK phone number,
Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
technical support phone number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline
Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks
Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks
Support Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support
contact number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks
HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular
toll free number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer
Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service
Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone
number, Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number,
Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support
phone number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
Quickbooks customer support phone number
Support helpline+++»--A- 1-844-414-4868 Quickbooks Support Phone Number US 1-844-414-4868 Quickbooks technical help
telephone number, 1-844-414-4868 Quickbooks technical help contact number, 1-844-414-4868 Quickbooks technical support
contact number,1-844-414-4868 Quickbooks contact number, 1-844-414-4868Quickbooks contact phone number, 1 877 778
8714Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
Quickbooks customer service contact number, 1-844-414-4868Quickbooks official number, Quickbooks official contact number,
Quickbooks 877 contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support
phone number Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks
technical support number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks
customer support number, Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks
customer service phone number, Quickbooks support phone number. Help@Call 1-844-414-4868/.Quickbooks 24/7 support phone
number,Quickbooks telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone
number
Support helpline+++»--A- 1-844-414-4868 Quickbooks Support Phone Number 1-844-414-4868 Quickbooks telephone number US 1-844-414-4868 Quickbooks technical help telephone number,1-844-414-4868 Quickbooks technical help contact number,1-844-414-4868
Quickbooks technical support contact number,1-844-414-4868 Quickbooks contact number,1-844-414-4868 Quickbooks contact phone
number,1-844-414-4868 Quickbooks contact telephone number,1-844-414-4868 Quickbooks 24 hour contact number,1-844-414-4868
Quickbooks customer support contact number,1-844-414-4868 Quickbooks customer service contact number,1-844-414-4868
Quickbooks official number, Quickbooks official contact number, Quickbooks 877 contact number, Quickbooks toll free number,
877 number for Quickbooks support, Quickbooks 24/7 support phone number
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1631) CLI to support attached file streams
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-1631:
----------------------------------
Summary: CLI to support attached file streams
Key: WFCORE-1631
URL: https://issues.jboss.org/browse/WFCORE-1631
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
This entry tracks the addition of a support for attached files in CLI operations,
Operation arguments of type INT and annotated with *attached-stream* and *filesystem-path* must be attached to the Operation.
Users will not deal directly with streams, but with file paths.
The CLI must discover such arguments and:
1) Propose completion by looking up the file system
2) Replace the path by a stream index
3) Send the File streams as attachements
This must be supported both in batch and non batch mode.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1614) Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1614?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-1614:
----------------------------------------------
Hi Petr, good catch. I have updated the PR. Thanks.
> Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-1614
> URL: https://issues.jboss.org/browse/WFCORE-1614
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Fix For: 3.0.0.Alpha4
>
> Attachments: test.cli
>
>
> We are proposing here to add a Cli option (command line option and an XML element) to make the CLI to echo the command and its options in non interactive mode. This will help to match a given command and its output.
> For example, the "ls -l" command output would be:
> [standalone@localhost:9990 /] ls -l
> ATTRIBUTE VALUE TYPE
> launch-type STANDALONE STRING
> management-major-version 5 INT
> management-micro-version 0 INT
> management-minor-version 0 INT
> ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6761) Wrong XAException return code when broker timeout is hit
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-6761?page=com.atlassian.jira.plugin.... ]
Dmitrii Tikhomirov reassigned WFLY-6761:
----------------------------------------
Assignee: Dmitrii Tikhomirov (was: Chen Maoqian)
> Wrong XAException return code when broker timeout is hit
> --------------------------------------------------------
>
> Key: WFLY-6761
> URL: https://issues.jboss.org/browse/WFLY-6761
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Dmitrii Tikhomirov
> Priority: Minor
>
> By creating testcases for checking behavior of transaction timeout I've hit an issue of wrong error code being returned when broker transaction timeout is hit before TM transaction timeout expires.
> It uses {{XAER_PROTO}} instead of {{RBTIMEOUT}}.
> This issue does not cause data inconsistency.
> Scenario:
> * ejb sends a message to a queue
> * processing inside of the ejb takes long time
> ** TM transaction timeout is set big enough to not hit the timeout
> ** jms broker internal transaction timeout is smaller than time needed for processing ejb method
> * jms broker txn timeout occurs - broker local txn is rolled back
> ** txn is removed from list of broker's local in-process transactions
> * TM calls XAResource.end
> ** the call returns {{XAException.XAER_PROTO}}
> That's current implementation returns {{XAER_PROTO}} in this scenario but {{RBTIMEOUT}} would be more appropriate.
> From discussion with Narayana developers, RM should return the most specific error return code as possible. In this scenario it's {{RBTIMEOUT}}.
> Other notes from TM dev point of view:
> {code}
> "[XA_RBTIMEOUT]
> The work represented by this transaction branch took too long."
> {code}
> _per XA spec page 39._
> The more complex question is, at what point can the resource manager forget about that branch (and therefore return NOTA to subsequent calls)?
> The XA spec says "After the transaction manager calls xa_end(), it should no longer consider the calling thread associated with that resource manager (although it must consider the resource manager part of the transaction branch when it prepares the branch.)"
> which implies the branch is still considered live at that point, a view corroborated by:
> {code}
> "[XA_RB∗]
> The resource manager has dissociated the transaction branch from the thread of control and has marked rollback-only the work performed on behalf of ∗xid."
> {code}
> Exception being thrown
> {code}
> WARN [com.arjuna.ats.jta] (Thread-0
> (ActiveMQ-client-global-threads-1468293951)) ARJUNA016056:
> TransactionImple.delistResource - caught exception during delist :
> XAException.XAER_PROTO: javax.transaction.xa.XAException
> at
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaEnd(ActiveMQSessionContext.java:346)
> at
> org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.end(ClientSessionImpl.java:1115)
> at
> org.apache.activemq.artemis.ra.ActiveMQRAXAResource.end(ActiveMQRAXAResource.java:112)
> at
> org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.end(ActiveMQXAResourceWrapperImpl.java:81)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:897)
> at
> org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$TransactionSynchronization.beforeCompletion(TxConnectionListener.java:1063)
> at
> org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.invokeBefore(TransactionSynchronizer.java:438)
> at
> org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.beforeCompletion(TransactionSynchronizer.java:376)
> at
> org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.beforeCompletion(JCAOrderedLastSynchronizationList.java:130)
> at
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76)
> at
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371)
> at
> com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200)
> at
> com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at
> com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89)
> at
> org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
> at
> org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
> at
> org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
> at
> org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean$$$endpoint1.afterDelivery(Unknown
> Source)
> at
> org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:321)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:932)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1045)
> at
> org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1628) Create module using 'module add' CLI command with absolute-path in resource-root element
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1628?page=com.atlassian.jira.plugi... ]
Martin Simka commented on WFCORE-1628:
--------------------------------------
I'll look into this one, I'll try to implement this with two params --resources and --absolute-resources as Brian suggests.
> Create module using 'module add' CLI command with absolute-path in resource-root element
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-1628
> URL: https://issues.jboss.org/browse/WFCORE-1628
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Martin Simka
> Assignee: Martin Simka
>
> MODULES-218, included in WildFly 10/WildFly Core 2.0.10, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
> {quote}
> resource-root's path previously only allowed resources within the module's directory, e.g.:
> <resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
> With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
> <resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
> {quote}
> {{module add}} command could have optional argument {{--copy-resources=(true|false)}} with default {{true}}, which would specify how new module will look like.
> * {{true}} copy files to the created module's directory = no change from how it works now.
> * {{false}} don't copy files and use absolute paths in {{resource-root}} instead.
> Another option could be to add optional argument without value, which would only specify to not copy files to the created module's directory and use absolute paths in {{resource-root}} instead. Name of this argument could be something like {{--use-absolute-paths-for-resources}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1628) Create module using 'module add' CLI command with absolute-path in resource-root element
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1628?page=com.atlassian.jira.plugi... ]
Martin Simka reassigned WFCORE-1628:
------------------------------------
Assignee: Martin Simka (was: Alexey Loubyansky)
> Create module using 'module add' CLI command with absolute-path in resource-root element
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-1628
> URL: https://issues.jboss.org/browse/WFCORE-1628
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Reporter: Martin Simka
> Assignee: Martin Simka
>
> MODULES-218, included in WildFly 10/WildFly Core 2.0.10, allows absolute paths to be used for resource-roots in module.xml. But there is no way to create module with absolute paths in resource-roots using CLI command {{module add}}.
> {quote}
> resource-root's path previously only allowed resources within the module's directory, e.g.:
> <resource-root path="wildfly-controller-2.2.0.CR2.jar"/>
> With MODULES-218 it allows resources to exist anywhere on the filesystem, in the form of an absolute path, e.g.:
> <resource-root path="/Users/whoever/mymodules/wildfly-controller-2.2.0.CR2.jar"/>
> {quote}
> {{module add}} command could have optional argument {{--copy-resources=(true|false)}} with default {{true}}, which would specify how new module will look like.
> * {{true}} copy files to the created module's directory = no change from how it works now.
> * {{false}} don't copy files and use absolute paths in {{resource-root}} instead.
> Another option could be to add optional argument without value, which would only specify to not copy files to the created module's directory and use absolute paths in {{resource-root}} instead. Name of this argument could be something like {{--use-absolute-paths-for-resources}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFLY-6781:
--------------------------------------
HornetQ cluster does not provide HA. For HA, replicated backup or shared store backup would have to be configured. HornetQ cluster just load balances messages across all active nodes. Every node in cluster has part of the messages for the given queue. Thus shutting down one node in cluster leads to "loss" of the messages. (of course of this node is started again and rejoins the HornetQ cluster then everything is ok again)
In your case there is no HornetQ cluster. All messages should be on node 1. I don't understand how SL.war could be disconnected if it's connected to node 1. Changing {{connection-ttl}} could at least show some warnings that something went wrong. Also could you double check sources of RC.war and SL.war that you do not ignore any exceptions?
> Wildfly cluster's failover functionality doesn't work as expected
> -----------------------------------------------------------------
>
> Key: WFLY-6781
> URL: https://issues.jboss.org/browse/WFLY-6781
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
>
>
> Following are the testing scenarios we did and the outcome:-
> 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
> 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
> 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
> 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
> Jgroups subsystem configuration in domain.xml we have is below:-
> <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE2"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months