|
[PATCH 1.1] mama.c: Make sure that we load and unload bridges properly
These changes ensure that we hold the lock while opening and closing payload and
messaging brdiges. Additionally, we store the shared library handles so we can
close them when cleaning up.
These changes ensure that we hold the lock while opening and closing payload and
messaging brdiges. Additionally, we store the shared library handles so we can
close them when cleaning up.
|
By
John Gray <jgray@...>
·
#51
·
|
|
[PATCH 1.1] mama.c: Added Per-bridge Reference Count
Added a reference count to mamaBridgeImpl struct. mama_start() and mama_stop()
increment and decrement this reference count to determine when initialization is
required and when the bridges can be
Added a reference count to mamaBridgeImpl struct. mama_start() and mama_stop()
increment and decrement this reference count to determine when initialization is
required and when the bridges can be
|
By
John Gray <jgray@...>
·
#48
·
|
|
[PATCH 1.1] mama.c: Add mama_openWithPropertiesCount() and mama_closeCount()
These methods take an additonal unsigned int* parameter that upon return
contains the the reference count for mama_openXXX() and mama_closeXXX(). This
allows applications to performa one-time global
These methods take an additonal unsigned int* parameter that upon return
contains the the reference count for mama_openXXX() and mama_closeXXX(). This
allows applications to performa one-time global
|
By
John Gray <jgray@...>
·
#50
·
|
|
[PATCH 1.1] mama.c : Added locking around mama_open() and mama_close()
Improved the reference counting logic and added locking around mama_open() and
mama_close(). The change ensures that all initialization (one-time) and cleanup
only occurs once. It also ensures that
Improved the reference counting logic and added locking around mama_open() and
mama_close(). The change ensures that all initialization (one-time) and cleanup
only occurs once. It also ensures that
|
By
John Gray <jgray@...>
·
#47
·
|
|
[PATCH 1.1] mama.c: Reference counting prep
This is in preparation for adding improved reference counting and locking around
mama_open(), mama_start(), mama_stop(), and mama_close() to enable them to be
called safely from multi-threaded
This is in preparation for adding improved reference counting and locking around
mama_open(), mama_start(), mama_stop(), and mama_close() to enable them to be
called safely from multi-threaded
|
By
John Gray <jgray@...>
·
#49
·
|
|
[PATCH 1.1] transport: mamaTransportImpl_getAdvisoryCauseAndPlatformInfo new function
This method allows bridges to pass middleware specific details regarding errors
and events.
Index:
This method allows bridges to pass middleware specific details regarding errors
and events.
Index:
|
By
John Gray <jgray@...>
·
#46
·
|
|
[PATCH 1.1] Interlocked changes queue.c: Correct reference counting and destroy interlock
Index: queue.c
===================================================================
RCS file: /cvsroot/products/mama/c_cpp/src/c/queue.c,v
retrieving revision 1.35.4.5.2.1.4.11
diff -w -u
Index: queue.c
===================================================================
RCS file: /cvsroot/products/mama/c_cpp/src/c/queue.c,v
retrieving revision 1.35.4.5.2.1.4.11
diff -w -u
|
By
John Gray <jgray@...>
·
#45
·
|
|
[PATCH 1.1] Fault Tolerence Configuration: Use Transport Properties for FT Configuration
Currently, the FT setup code uses the hard-coded transport name, "ft", to read
properties from mama.properties despite the fact that the caller supplies a
mamaTransport reference. This change uses
Currently, the FT setup code uses the hard-coded transport name, "ft", to read
properties from mama.properties despite the fact that the caller supplies a
mamaTransport reference. This change uses
|
By
John Gray <jgray@...>
·
#44
·
|
|
[PATCH 1.1] mamasymbolist subscriber: Initialize Callbacks structs to 0 for mamasymbolist subscriber
This avoids a potential segmentation fault in the event that an uninitialized
callback gets invoked.
Index:
This avoids a potential segmentation fault in the event that an uninitialized
callback gets invoked.
Index:
|
By
John Gray <jgray@...>
·
#43
·
|
|
[PATCH 1.1] listenmsgcallback.c: Msg status possibly stale and unknown
Added new msg status of possibly stale and unknown
--- listenermsgcallback.c 2012-01-27 10:45:39.000000000 +0000
+++ listenermsgcallback.c 2012-01-27 11:10:30.000000000
Added new msg status of possibly stale and unknown
--- listenermsgcallback.c 2012-01-27 10:45:39.000000000 +0000
+++ listenermsgcallback.c 2012-01-27 11:10:30.000000000
|
By
John Gray <jgray@...>
·
#42
·
|
|
[PATCH 1.1] listenmsgcallback.c: invokeErrorCallback function renamed
Renamed listenerMsgCallbackImpl_invokeErrorCallback to
listenerMsgCallbackImpl_invokeErrorCallback because it is an internal method.
The method is also static and moved to the end of the file.
Renamed listenerMsgCallbackImpl_invokeErrorCallback to
listenerMsgCallbackImpl_invokeErrorCallback because it is an internal method.
The method is also static and moved to the end of the file.
|
By
John Gray <jgray@...>
·
#41
·
|
|
[PATCH 1.1] status.c: Added MAMA_STATUS_SUBSCRIPTION_GAP
Added MAMA_STATUS_SUBSCRIPTION_GAP
Middleware bridges pass this status to the mamaSubscription onError callback
when the middleware detects a gap:
Added MAMA_STATUS_SUBSCRIPTION_GAP
Middleware bridges pass this status to the mamaSubscription onError callback
when the middleware detects a gap:
|
By
John Gray <jgray@...>
·
#40
·
|
|
[PATCH 1.1] transport.c: Add mamaTransport_disableRefresh() Method
Add mamaTransport_disableRefresh() Method
Added method to disable refreshes for a transport. This method must be called
after mamaTransport_allocate() but before mamaTransport_create(). If
Add mamaTransport_disableRefresh() Method
Added method to disable refreshes for a transport. This method must be called
after mamaTransport_allocate() but before mamaTransport_create(). If
|
By
John Gray <jgray@...>
·
#39
·
|
|
[PATCH 1.1] Interlock declaration: Required for applying common_3 patch
This must be applied with the common_3 file as it contains the Interlocked_destroy function declaration.
Index:
This must be applied with the common_3 file as it contains the Interlocked_destroy function declaration.
Index:
|
By
John Gray <jgray@...>
·
#38
·
|
|
RabbitMQ bridge
DOT are considering producing an OpenMama bridge using RabbitMQ, which we would then donate to OpenMama. This would provide a solid, well supported and fully open source option to the current product
DOT are considering producing an OpenMama bridge using RabbitMQ, which we would then donate to OpenMama. This would provide a solid, well supported and fully open source option to the current product
|
By
Leslie Spiro <lspiro@...>
·
#37
·
|
|
[PATCH 1.1] Hash rename: Renamed hash functions to whash
This avoid potential namespace conflicts as the hash functions are now used
outside of common.
Index:
This avoid potential namespace conflicts as the hash functions are now used
outside of common.
Index:
|
By
John Gray <jgray@...>
·
#36
·
|
|
Recall: [PATCH 1.1] Hash rename: Renamed hash functions to whash
John Gray would like to recall the message, "[PATCH 1.1] Hash rename: Renamed hash functions to whash".
John Gray would like to recall the message, "[PATCH 1.1] Hash rename: Renamed hash functions to whash".
|
By
John Gray <jgray@...>
·
#35
·
|
|
[PATCH 1.1] Hash rename: Renamed hash functions to whash
This avoid potential namespace conflicts as the hash functions are now used
outside of common.
Index:
This avoid potential namespace conflicts as the hash functions are now used
outside of common.
Index:
|
By
John Gray <jgray@...>
·
#34
·
|
|
[PATCH 1.1] Windows Interlock: Function wInterlocked set to return 0
Function wInterlocked set to return 0 for windows. Not an operation (no-op) in Unix.
Index: queue.c
===================================================================
RCS file:
Function wInterlocked set to return 0 for windows. Not an operation (no-op) in Unix.
Index: queue.c
===================================================================
RCS file:
|
By
John Gray <jgray@...>
·
#33
·
|
|
Recall: [PATCH 1.1] Windows Interlock: Function wInterlocked set to return 0
John Gray would like to recall the message, "[PATCH 1.1] Windows Interlock: Function wInterlocked set to return 0".
John Gray would like to recall the message, "[PATCH 1.1] Windows Interlock: Function wInterlocked set to return 0".
|
By
John Gray <jgray@...>
·
#32
·
|