[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 day, 11 hours
[JBoss JIRA] (JBADMCON-177) USA::@+!+!!!!!++I8~00.7.9.0~9186 @+*+ LEXMARK printer tech SUPPORT phone number LEXMARK tech support customer support phone number
by sont josef (JIRA)
sont josef created JBADMCON-177:
-----------------------------------
Summary: USA::@+!+!!!!!++I8~00.7.9.0~9186 @+*+ LEXMARK printer tech SUPPORT phone number LEXMARK tech support customer support phone number
Key: JBADMCON-177
URL: https://issues.jboss.org/browse/JBADMCON-177
Project: JBoss Admin Console
Issue Type: Task
Reporter: sont josef
USA::@+!+!!!!!++I8~00.7.9.0~9186 @+*+ LEXMARK printer tech SUPPORT phone number LEXMARK tech support customer support phone number
CANADA+++++-----GGGGGYDasbnd LEXMARK printer customer suppOrt number usaasdaa UCanaDa..@1-800-790-9186(USA), 0800-078-6054(UK), 1800-769-903(AUS)@LEXMARK telephone support@))))!@ $$@$$$ LEXMARK computer support number +@$$$@$$$@$@))))!@1-800-790-9186(USA), 0800-078-6054(UK), 1800-769-903(AUS)@USA CALL LEXMARK Printer Tech Support Phone Number, LEXMARK Printer Customer service number... +@$$$@$$$@$@))@1-800-790-9186@USA CALL LEXMARK Printer Tech Support Phone Number, LEXMARK Printer Customer service number.. ++@@@helpline@@USA_CALL_1-800-790-9186_LEXMARK_PRINTER_TECHNICAL_SUPPORT_PHONE_NUMBER,CUSTOMER_SERVICE_NUMBER_USA ? $CALL %%USA((1-800-790-9186))_!!LEXMARK Printer tech Support Number @1-800-790-9186@ LEXMARK Printer Tech Support Phone Number Call wireless 1-800-790-9186 1-800-790-9186 LEXMARK Tech Support Phone Number Canada LEXMARK printer customer service number1-800-790-9186 LEXMARK support number, LEXMARK support, LEXMARK printer support, LEXMARK tech support, LEXMARK technical support, LEXMARK customer service number, LEXMARK customer service, LEXMARK tech support number, ##LEXMARK support center##, LEXMARK printer support number, hewlett packard support, LEXMARK contact number, LEXMARK phone number, LEXMARK help and support, LEXMARK customer support, LEXMARK printer help, LEXMARK technical support number, LEXMARK support phone number, hewlett packard customer service, LEXMARK printers support, LEXMARK customer service phone number, LEXMARK number, LEXMARK customer care, LEXMARK contact, LEXMARK tech support phone number, LEXMARK support chat, LEXMARK customer support number, LEXMARK customer care number, contact LEXMARK support, LEXMARK help, LEXMARK phone, LEXMARK printer support phone number, LEXMARK customer support phone number, LEXMARK printer tech support, LEXMARK phone support, LEXMARK technical support phone number, LEXMARK laptop support number, hewlett packard printer support, LEXMARK helpline, LEXMARK telephone support, LEXMARK online support, LEXMARK support contact, LEXMARK chat support, hewlett packard phone number, LEXMARK printer customer service, LEXMARK printer tech support number, LEXMARK product support, hewlett packard customer service phone number, LEXMARK computer support number, LEXMARK support contact number, LEXMARK support printer, LEXMARK computer support, LEXMARK tech support chat, LEXMARK helpline number, LEXMARK laptop support, hewlett packard tech support, LEXMARK online chat, hewlett packard technical support, LEXMARK printer help line, phone number for LEXMARK support, hewlett packard support phone number, LEXMARK printer technical support, hewlett packard customer service number, LEXMARK service number, hewlett packard helpline, LEXMARK customer care no, LEXMARK printer customer service number, LEXMARK help number, LEXMARK printer customer service phone number, LEXMARK 1800 number, LEXMARK support phone, LEXMARK support line, hewlett packard contact number, LEXMARK printer tech support phone number, LEXMARK printer customer support phone number, LEXMARK printers help, call LEXMARK support, ##LEXMARK printer support## chat, hewlett packard support number, hewlett packard tech support number, LEXMARK support telephone number, hewlett packard tech support phone number, call LEXMARK, LEXMARK contact support, hewlett packard technical support phone number, LEXMARK support centre, hewlett packard customer support, LEXMARK desktop support, LEXMARK laptop customer service, contact LEXMARK printer support, LEXMARK pc support, LEXMARK laptop customer care number, LEXMARK support for printers, LEXMARK printer customer care, LEXMARK customer care phone number, hewlett packard help, phone number for LEXMARK, LEXMARK online help, LEXMARK laptop customer care, LEXMARK helpline phone number, LEXMARK printer customer support, LEXMARK technical support chat, LEXMARK computer help, LEXMARK support numbers, LEXMARK technical support contact number, LEXMARK telephone number, LEXMARK printer technical support phone number, LEXMARK printer helpline, LEXMARK support printers, LEXMARK support online, LEXMARK printer contact number, LEXMARK help phone number, LEXMARK printer customer care number, contact hewlett packard by phone, LEXMARK printer phone support, hewlett packard printers support, LEXMARK tech support phone, LEXMARK technical help, LEXMARK laptop tech support number, contact LEXMARK by phone, LEXMARK support call, LEXMARK computers support, hewlett packard customer service telephone number, phone number for hewlett packard, LEXMARK online support chat, LEXMARK laptop customer service number, LEXMARK online chat support, LEXMARK printers customer service, hewlett packard customer service phone, LEXMARK laptop tech support, LEXMARK service phone number, hewlett packard printer help, phone number for LEXMARK printers, LEXMARK troubleshooting phone number, LEXMARK 800 number, hewlett packard technical support number, contact LEXMARK support phone, phone number for LEXMARK printer support, LEXMARK customer support chat, LEXMARK help and support number, contact hewlett packard, LEXMARK laptop support phone number, LEXMARK printers customer service phone number, LEXMARK laptop customer service phone number, LEXMARK computer support phone number, LEXMARK pavilion support, LEXMARK computer customer service, LEXMARK customer services, hewlett packard telephone number, LEXMARK helpline no, LEXMARK help desk number, contact LEXMARK support phone number, hewlett packard contact, LEXMARK phone numbers, LEXMARK printers customer care number, LEXMARK printer help and support, contact LEXMARK technical support, LEXMARK contact numbers, contact LEXMARK support chat, call LEXMARK tech support, LEXMARK customer service phone, LEXMARK help support, LEXMARK computer tech support, LEXMARK assistance phone number, LEXMARK customer service telephone number, hewlett packard printer support phone number, LEXMARK contact support number, LEXMARK support center phone number, LEXMARK support phone numbers, tech support for LEXMARK, LEXMARK it support, LEXMARK laptop helpline, LEXMARK technical, LEXMARK laptop technical support number, LEXMARK printers tech support phone number, LEXMARK printers support phone number, hewlett packard help desk phone number, LEXMARK computer tech support phone number, LEXMARK customer service number for laptop, LEXMARK printer helpline number, contact LEXMARK support by phone, hewlett packard support center, LEXMARK laptop customer care no, LEXMARK printer support telephone number, LEXMARK support services, LEXMARK customer service number for printers, LEXMARK product support number, LEXMARK laptop tech support phone number, LEXMARK printer helpline phone number, contact LEXMARK customer support, hewlett packard customer support phone number, LEXMARK printers technical support, LEXMARK customer care center, support for LEXMARK printers, LEXMARK printer support center, phone number for LEXMARK tech support, LEXMARK desktop customer care number, LEXMARK laptops support, LEXMARK printer online support, LEXMARK printer phone number, hewlett packard printers support phone number, technical support for LEXMARK printers phone number, LEXMARK help center phone number, contact LEXMARK tech support, call LEXMARK printer support, LEXMARK printers customer support, LEXMARK computer customer service number, LEXMARK printers helpline, LEXMARK customer care contact number, LEXMARK laptop help, LEXMARK computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, LEXMARK printer help phone number, LEXMARK printers help phone number, LEXMARK printer phone number for customer service, LEXMARK computer technical support phone number, customer service LEXMARK, LEXMARK support technical support number, contact number for LEXMARK, LEXMARK computers support phone number, LEXMARK printers support number, LEXMARK printer technical support number, contact LEXMARK tech support by phone, LEXMARK computer customer care number, LEXMARK printer 800 number, call LEXMARK customer service, LEXMARK printer help center, LEXMARK computers customer service, LEXMARK printer help desk, hewlett packard computer support, LEXMARK printers technical support number, LEXMARK help desk phone number, LEXMARK printer support phone, LEXMARK contact help, contact LEXMARK laptop support, LEXMARK customer service contact number, support for LEXMARK printer, LEXMARK printer customer care no, LEXMARK computer phone number, LEXMARK tech help, LEXMARK pc support number, LEXMARK laptop customer support, LEXMARK desktop support number, support LEXMARK printer, LEXMARK support hours, number for LEXMARK support, LEXMARK support customer service number, LEXMARK contact phone number, customer service number for LEXMARK printers, LEXMARK computers help, LEXMARK tech support contact number, LEXMARK phone support number....
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-4697) EJBClient access to SFSBs does not play well with clean shutdown
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4697?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-4697:
---------------------------------
Summary: EJBClient access to SFSBs does not play well with clean shutdown (was: EJBCLient access to SFSBs does not play well with clean shutdown)
> EJBClient access to SFSBs does not play well with clean shutdown
> ----------------------------------------------------------------
>
> Key: WFLY-4697
> URL: https://issues.jboss.org/browse/WFLY-4697
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB, Remoting
> Affects Versions: 10.0.0.Alpha1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 10.0.0.Alpha4
>
>
> The clean shutdown mechanism allows EJB and web applications to make use of shutdown interceptors to allow the application server to refuse requests when a server is in the process of shutting down. These interceptors are tied to the processing of EJB invocations and web requests.
> In the case of EJBCLient invocations, they arrive at the remoting connector, and undergo some preliminary processing before being sent to the EJB interface in question. When a server is shutting down, EJBCLient invocations can arrive at the RemoteConnector and start processing, even when the EJB interface has been locked down, so to speak.
> I am seeing various types of exceptions arising from this preliminary processing (e.g. NPE on DeploymentRepository lookups) and these get returned to the client as exceptions on the SFSB invocation, before even reaching the SFSB interceptors.
> If the EJBCLient is running in a managed transaction context, these returned exceptions will case the SFSB to be discarded (as the SFSB invocation is considered failed with the exception returned) and the transaction will attempt to rollback. If the rollback processing fails (because the original node in the transaction is down the bean gets removed anyway. The SFSB session state is lost, even if there is another node in the cluster which can support the invocation.
> In short, it looks as though the clean shutdown mechanism needs to be used to also lock down the processing of EJBCLient invocations in some way.
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-6795) Introduce EJB "call stack" notion
by David Lloyd (JIRA)
David Lloyd created WFLY-6795:
---------------------------------
Summary: Introduce EJB "call stack" notion
Key: WFLY-6795
URL: https://issues.jboss.org/browse/WFLY-6795
Project: WildFly
Issue Type: Enhancement
Components: EJB
Reporter: David Lloyd
h1. Summary
It is sometimes useful for an EJB's interceptor to know if it was ultimately being called from the same EJB, or the same module, or the same application. It is also useful to know if an invocation which is blocked would permanently deadlock. To this end I propose that an EJB call stack mechanism is introduced.
h2. Implementation
On each EJB method entry, a thread local is updated with an object which holds an identifier for the current EJB along with a link to the value that was previously in the thread local, if any. On asynchronous dispatch, the thread local value is copied, and cleared after task completion.
h2. Deadlock detection
Once EJB locking is redesigned to use queues, it may be possible to introduce a deadlock detector using the call stack information. If a pair of EJBs (A and B) have concurrency control or another type of one-at-a-time restriction, and an invocation on A is blocked (directly or indirectly) due to an incomplete invocation on B, which in turn is blocked (directly or indirectly) due to A being incomplete, a deadlock exception can be raised to one or both of the participants, allowing the container to unwind and proceed. The detection could happen immediately upon entering the blocking queue, or after a time limit, depending on the expense of the algorithm.
h2. Diagnostics
A server with slow-moving or frozen EJB invocations could be examined to determine what the call stack is on the waiters. Invocations could be selectively cancellable via an admin interface.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFLY-6793) Batch subsystem cannot be removed with a remove operation
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-6793?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-6793:
--------------------------------
Description:
The {{batch-jberet}} subsystem fails when a {{remove}} operation is invoked.
{code}
[standalone@localhost:9990 /] /subsystem=batch-jberet:remove
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service org.wildfly.batch.thread.pool.batch was depended upon by service org.wildfly.batch.configuration",
"rolled-back" => true,
"response-headers" => undefined
}
{code}
-The batch configuration dependency needs to be removed before the its dependencies are removed.-
The thread-pool resource should also require a reload before removal. It's used in deployments and therefore shouldn't just be removed without a reload.
was:
The {{batch-jberet}} subsystem fails when a {{remove}} operation is invoked.
{code}
[standalone@localhost:9990 /] /subsystem=batch-jberet:remove
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service org.wildfly.batch.thread.pool.batch was depended upon by service org.wildfly.batch.configuration",
"rolled-back" => true,
"response-headers" => undefined
}
{code}
The batch configuration dependency needs to be removed before the its dependencies are removed.
> Batch subsystem cannot be removed with a remove operation
> ---------------------------------------------------------
>
> Key: WFLY-6793
> URL: https://issues.jboss.org/browse/WFLY-6793
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Reporter: James Perkins
> Assignee: James Perkins
>
> The {{batch-jberet}} subsystem fails when a {{remove}} operation is invoked.
> {code}
> [standalone@localhost:9990 /] /subsystem=batch-jberet:remove
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service org.wildfly.batch.thread.pool.batch was depended upon by service org.wildfly.batch.configuration",
> "rolled-back" => true,
> "response-headers" => undefined
> }
> {code}
> -The batch configuration dependency needs to be removed before the its dependencies are removed.-
> The thread-pool resource should also require a reload before removal. It's used in deployments and therefore shouldn't just be removed without a reload.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (WFCORE-1483) Recursive removal doesn't deal with reload-required cleanly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1483?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1483:
------------------------------------------
A possibility here is to use the OperationDefinition data associated with the handler for each remove to see if the op will require-reload. That is, the kernel doesn't wait for the remove OSH to call context.reloadRequired() in order to know that reload is required, as that call happens too late. Too late because the Stage.RUNTIME call (i.e. invocation of performRuntime(...)) for the parent resource will happen *after* the Stage.RUNTIME call for the children. What's needed is to have an expectation for the parent and all descendants before *any* of them get to their performRuntime() handling.
Still tricky though. The mechanism to communicate state between the relevant steps (but not to other steps) also doesn't exist.
> Recursive removal doesn't deal with reload-required cleanly
> -----------------------------------------------------------
>
> Key: WFCORE-1483
> URL: https://issues.jboss.org/browse/WFCORE-1483
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
>
> There's a flaw in the WFCORE-808 recursive removal feature when it comes to reload-required.
> The problem is some of the resources recursively removed can require a reload while others don't, with the result that you get a semi-random set of changes to the runtime. This is particularly an issue if the parent resource requires reload and children don't. So based on the parent resource description the user may be expecting no runtime changes but instead some services are removed.
> This is tricky because when the Stage.RUNTIME steps execute for the child resources, they don't know if their parents are going to require a reload. We can probably use a OperationContext attachment of some sort to communicate information between steps associated with a recursive reload, but even with that kind of thing in place, unless we change how AbstractRemoveStepHandler works (likely breaking subclasses) at the time the child decides whether or not to require reload it's not going to know what the parents will decide.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months