openhub.net
Black Duck Software, Inc.
Open Hub
Follow @
OH
Sign In
Join Now
Projects
People
Organizations
Tools
Blog
BDSA
Projects
People
Projects
Organizations
Forums
S
Sandesha 2
Settings
|
Report Duplicate
10
I Use This!
×
Login Required
Log in to Open Hub
Remember Me
Inactive
Commits
: Listings
Analyzed
23 days
ago. based on code collected
23 days
ago.
Jan 29, 2024 — Jan 29, 2025
Showing page 17 of 35
Search / Filter on:
Commit Message
Contributor
Files Modified
Lines Added
Lines Removed
Code Location
Date
enable messages to override unreliable operations
Thomas McKiernan
More...
over 17 years ago
[no comment]
Thomas McKiernan
More...
over 17 years ago
some refactoring and potential NPE protection
Thomas McKiernan
More...
over 17 years ago
performance refactor
Thomas McKiernan
More...
over 17 years ago
When the same SandeshaStorageManager is used in an environment where there are multiple jvms, it is possible to insert multiple sequences with the same identifier. The changes here are for the ApplicationMsgProcessor to take note of the response returned when inserting the RMSBean and if a false is returned to reissue the getRMSBean request
Andrew Gatford
More...
over 17 years ago
https://issues.apache.org/jira/browse/SANDESHA2-127
Thomas McKiernan
More...
over 17 years ago
Removed copyright from source files and added the NOTICE.txt. See JIRA 124
Chamikara Madhusanka Jayalath
More...
over 17 years ago
https://issues.apache.org/jira/browse/SANDESHA2-126
Thomas McKiernan
More...
over 17 years ago
As described in SANDESHA2-108 this change avoids the Inorder thread switch if the message being received is the next message to be invoked. This change requires Axis2 revision 592132
Andrew Gatford
More...
over 17 years ago
Solve a NullPointerException when looking for the SandeshaPolicyBean when processing an AckRequest
Andrew Gatford
More...
over 17 years ago
Move the location for lookup for hasUserTransaction to before any updates are made to the storage manager to give the store a chance to setup any transactional information required.
Andrew Gatford
More...
over 17 years ago
Debug for potential complex deadlocks
Thomas McKiernan
More...
over 17 years ago
Do not predispatch in checkForSyncResponses
Thomas McKiernan
More...
over 17 years ago
If a SandeshaThread is stopped, we can't then restart it using Thread.start(). Also, change errors to debug and remove an unused method from SandeshaUtil
Andrew Gatford
More...
over 17 years ago
Ensure terminateSendingSide terminates properly
Thomas McKiernan
More...
over 17 years ago
Performance improvements
Thomas McKiernan
More...
over 17 years ago
Ensure checkSyncResponses copies properties correctly
Thomas McKiernan
More...
over 17 years ago
Close timing window when stopping SandeshaThreads and another thread requesting that it starts.
Andrew Gatford
More...
over 17 years ago
Debug rather than warn when catching exceptions in checkSyncResponses
Thomas McKiernan
More...
over 17 years ago
SenderBean changed to set sentCount in adjustRetransmission is not the same bean instance as the one updated in SenderBeanManager from inside the SenderWorker
Andrew Gatford
More...
over 17 years ago
Jira SANDESHA2-121: Optimize Sequence and SequenceAcknowldgement processing
Matthew Lovett
More...
over 17 years ago
Better trace in WorkerLock
Thomas McKiernan
More...
over 17 years ago
Ensure use the correct way to get RMSpecVer
Thomas McKiernan
More...
over 17 years ago
better logging of replyTo info in appMsgProcessor
Thomas McKiernan
More...
over 17 years ago
Add trace to bean mgrs
Thomas McKiernan
More...
over 17 years ago
Do not process createSequenceRefused if the sequence is established already
Thomas McKiernan
More...
over 17 years ago
no need to check that RM1.0 annon out-in has a sequence offer, since we actually force an offer in this case
Thomas McKiernan
More...
over 17 years ago
long backoff after several message retransmissions
Thomas McKiernan
More...
over 17 years ago
Undo changes made to SenderWorker as this breaks the Sandesha unit tests. The particular case broken is when a sync ack is sent on an Async request/response, the OpContext was being completed so no async response would ever be sent
Andrew Gatford
More...
over 17 years ago
In the client side if it gets ackReq after sequence is terminated , no need to send a fault to the server or need to throw exception
Deepal Jayasinghe
More...
over 17 years ago
←
1
2
…
13
14
15
16
17
18
19
20
21
…
34
35
→
This site uses cookies to give you the best possible experience. By using the site, you consent to our use of cookies. For more information, please see our
Privacy Policy
Agree