[jira] Commented: (QPID-1904) Timestamps are incorrect
[ https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795246#action_12795246 ] Julien Lavigne du Cadet commented on QPID-1904: --- Can someone comment on the status of this bug? Is it fixed for 0.6? > Timestamps are incorrect > > > Key: QPID-1904 > URL: https://issues.apache.org/jira/browse/QPID-1904 > Project: Qpid > Issue Type: Bug > Components: Qpid Managment Framework >Affects Versions: 0.5 > Environment: Windows XP > Reproduced both with the python API and the .Net API >Reporter: Julien Lavigne du Cadet > Attachments: qpid-dates.png > > > The timestamps for configuration and instrumentation messages are incorrect > both with the python and the .Net api. > According to the documentation "All timestamps are uint64 values representing > nanoseconds since the epoch (January 1, 1970)." However, the dates resulting > can be several years in the past or in the future. > To reproduce with the python api : > - in disp.py, line 178 add the following line : > print gmtime (nsec / 10) > - start qpid-tool and list the queues => the full dates will be displayed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2240) [.Net 0-10] When authentication fails on connect(), the api should raise an exception
[ https://issues.apache.org/jira/browse/QPID-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-2240: -- Attachment: missing files.patch The missing files from the first patch, sorry about that ! Let me know if there is any other problem > [.Net 0-10] When authentication fails on connect(), the api should raise an > exception > -- > > Key: QPID-2240 > URL: https://issues.apache.org/jira/browse/QPID-2240 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: missing files.patch, qpid-dotnet.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2240) [.Net 0-10] When authentication fails on connect(), the api should raise an exception
[ https://issues.apache.org/jira/browse/QPID-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787368#action_12787368 ] Julien Lavigne du Cadet commented on QPID-2240: --- Thanks for the feedback, I'll keep your remarks in mind for any new patch ! > [.Net 0-10] When authentication fails on connect(), the api should raise an > exception > -- > > Key: QPID-2240 > URL: https://issues.apache.org/jira/browse/QPID-2240 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: qpid-dotnet.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2240) [.Net 0-10] When authentication fails on connect(), the api should raise an exception
[ https://issues.apache.org/jira/browse/QPID-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-2240: -- Attachment: qpid-dotnet.patch This patch also fixes QPID-2239. As explained to Aidan, this stuff is probably a bit hacky as I'm not that familiar with the structure of the code... That's also why this patch covers 2 issues at once, as I'm not 100% which part applies to what (it's 6 months old... !) Anyway, all I'm saying is there's probably a better way to handle that and I won't mind at all if this stuff is rejected due to bad quality :-). > [.Net 0-10] When authentication fails on connect(), the api should raise an > exception > -- > > Key: QPID-2240 > URL: https://issues.apache.org/jira/browse/QPID-2240 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: qpid-dotnet.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2239) [.Net 0-10] Close() method is hanging indefinetely
[ https://issues.apache.org/jira/browse/QPID-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786024#action_12786024 ] Julien Lavigne du Cadet commented on QPID-2239: --- See QPID-2240 for patch > [.Net 0-10] Close() method is hanging indefinetely > -- > > Key: QPID-2239 > URL: https://issues.apache.org/jira/browse/QPID-2239 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > > Step to reproduce : > - open a connection to the broker > - close the connection > => wait till timeout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2240) [.Net 0-10] When authentication fails on connect(), the api should raise an exception
[.Net 0-10] When authentication fails on connect(), the api should raise an exception -- Key: QPID-2240 URL: https://issues.apache.org/jira/browse/QPID-2240 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2239) [.Net 0-10] Close() method is hanging indefinetely
[.Net 0-10] Close() method is hanging indefinetely -- Key: QPID-2239 URL: https://issues.apache.org/jira/browse/QPID-2239 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Step to reproduce : - open a connection to the broker - close the connection => wait till timeout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2238) [.Net 0-10] Recursive call to ToString method causes a stack overflow exception
[ https://issues.apache.org/jira/browse/QPID-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-2238: -- Attachment: Recursive ToString.patch > [.Net 0-10] Recursive call to ToString method causes a stack overflow > exception > --- > > Key: QPID-2238 > URL: https://issues.apache.org/jira/browse/QPID-2238 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: Recursive ToString.patch > > > See patch below -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2238) [.Net 0-10] Recursive call to ToString method causes a stack overflow exception
[.Net 0-10] Recursive call to ToString method causes a stack overflow exception --- Key: QPID-2238 URL: https://issues.apache.org/jira/browse/QPID-2238 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Attachments: Recursive ToString.patch See patch below -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2237) UUID are not decoded properly by the .Net 0-10 api
UUID are not decoded properly by the .Net 0-10 api -- Key: QPID-2237 URL: https://issues.apache.org/jira/browse/QPID-2237 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet Attachments: UUID decoding.patch See patch below -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2237) UUID are not decoded properly by the .Net 0-10 api
[ https://issues.apache.org/jira/browse/QPID-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-2237: -- Attachment: UUID decoding.patch > UUID are not decoded properly by the .Net 0-10 api > -- > > Key: QPID-2237 > URL: https://issues.apache.org/jira/browse/QPID-2237 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: UUID decoding.patch > > > See patch below -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1987: -- Attachment: qpid-dotnet - build.patch Slight modification to the previous patch > Patch for 0.10 C# API > - > > Key: QPID-1987 > URL: https://issues.apache.org/jira/browse/QPID-1987 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Reporter: Julien Lavigne du Cadet >Assignee: Ted Ross >Priority: Critical > Attachments: qpid-.net.patch, qpid-dotnet - build.patch > > > Please find attached a patch correcting the following issues : > - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) > - Fixes public API to match standard .NET conventions (QPID-500) > - Fixes code generation to match standard .NET conventions > - Fixes ToString() methods that don't override base classes > - Fixes blocking TearingDown in unit tests > - Use a .config file for tests/samples > - Adds interface to Invoker, Session and ClientSession to allow easy mocking > of the API > - Make the console solution compiling under Visual Studio 2008 > I'm more than happy to discuss any of this by email or through JIRA. Please > let me know if there's no plan (or nobody available) to evaluate this patch > for inclusion. If that is the case, I will consider forking the API to > continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1987: -- Attachment: (was: qpid-dotnet - build.patch) > Patch for 0.10 C# API > - > > Key: QPID-1987 > URL: https://issues.apache.org/jira/browse/QPID-1987 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Reporter: Julien Lavigne du Cadet >Assignee: Ted Ross >Priority: Critical > Attachments: qpid-.net.patch > > > Please find attached a patch correcting the following issues : > - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) > - Fixes public API to match standard .NET conventions (QPID-500) > - Fixes code generation to match standard .NET conventions > - Fixes ToString() methods that don't override base classes > - Fixes blocking TearingDown in unit tests > - Use a .config file for tests/samples > - Adds interface to Invoker, Session and ClientSession to allow easy mocking > of the API > - Make the console solution compiling under Visual Studio 2008 > I'm more than happy to discuss any of this by email or through JIRA. Please > let me know if there's no plan (or nobody available) to evaluate this patch > for inclusion. If that is the case, I will consider forking the API to > continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1987: -- Attachment: qpid-dotnet - build.patch Here is a patch to clarify the generation process. It contains an update to the build.xml to point to the correct path for jython and some new instructions to build the api. > Patch for 0.10 C# API > - > > Key: QPID-1987 > URL: https://issues.apache.org/jira/browse/QPID-1987 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Reporter: Julien Lavigne du Cadet >Assignee: Ted Ross >Priority: Critical > Attachments: qpid-.net.patch, qpid-dotnet - build.patch > > > Please find attached a patch correcting the following issues : > - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) > - Fixes public API to match standard .NET conventions (QPID-500) > - Fixes code generation to match standard .NET conventions > - Fixes ToString() methods that don't override base classes > - Fixes blocking TearingDown in unit tests > - Use a .config file for tests/samples > - Adds interface to Invoker, Session and ClientSession to allow easy mocking > of the API > - Make the console solution compiling under Visual Studio 2008 > I'm more than happy to discuss any of this by email or through JIRA. Please > let me know if there's no plan (or nobody available) to evaluate this patch > for inclusion. If that is the case, I will consider forking the API to > continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732377#action_12732377 ] Julien Lavigne du Cadet commented on QPID-1987: --- As long as no .Net 3/.Net 3.5 features are used it should be trivial to either compile under VS 2008 or VS 2005. Please note that you would have to recreate a solution file for VS 2005 as the one in the sources is for 2008 only (solutions files are not compatible between 2005 and 2008). However, I've been working on the API with VS 2008 and I never had any specific problems so far. What kind of errors are you seeing? It's probably a silly question bug have you regenerated the files from the client-010/gentool directory? This is a required step as I changed the the .py and .tpl files to accomodate the usual .Net convention regarding method naming (in pascal case and not in camel case) > Patch for 0.10 C# API > - > > Key: QPID-1987 > URL: https://issues.apache.org/jira/browse/QPID-1987 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Reporter: Julien Lavigne du Cadet >Assignee: Ted Ross >Priority: Critical > Attachments: qpid-.net.patch > > > Please find attached a patch correcting the following issues : > - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) > - Fixes public API to match standard .NET conventions (QPID-500) > - Fixes code generation to match standard .NET conventions > - Fixes ToString() methods that don't override base classes > - Fixes blocking TearingDown in unit tests > - Use a .config file for tests/samples > - Adds interface to Invoker, Session and ClientSession to allow easy mocking > of the API > - Make the console solution compiling under Visual Studio 2008 > I'm more than happy to discuss any of this by email or through JIRA. Please > let me know if there's no plan (or nobody available) to evaluate this patch > for inclusion. If that is the case, I will consider forking the API to > continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1972) UUID.randomUUID() is not thread-safe
[ https://issues.apache.org/jira/browse/QPID-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1972: -- Attachment: (was: qpid-dotnet.patch) > UUID.randomUUID() is not thread-safe > > > Key: QPID-1972 > URL: https://issues.apache.org/jira/browse/QPID-1972 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 > Environment: .net API >Reporter: Julien Lavigne du Cadet >Priority: Critical > > UUID.randomUUID is not thread-safe because it's using a static random object. > However, recreating a random object each time the method is called is not an > option because 2 successive calls might result in the same UUID. > Please find attached in the next comment a patch that fixes the issue by > introducing a UUIDGenerator class. Now, to get a random UUID, you first need > to instantiate a UUIDGenerator and request it through it. That way there's no > need to lock in the UUID class. > Please note that this patch is BREAKING COMPABILITY with previous versions of > the API ! > The patch is also fixing 2 others issues : > - test.config is not included in the unit test project which result in half > of the unit tests failing > - the management console is not compiling with vs 2008 and .Net 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1987) Patch for 0.10 C# API
[ https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1987: -- Attachment: qpid-.net.patch The patch > Patch for 0.10 C# API > - > > Key: QPID-1987 > URL: https://issues.apache.org/jira/browse/QPID-1987 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Reporter: Julien Lavigne du Cadet >Priority: Critical > Attachments: qpid-.net.patch > > > Please find attached a patch correcting the following issues : > - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) > - Fixes public API to match standard .NET conventions (QPID-500) > - Fixes code generation to match standard .NET conventions > - Fixes ToString() methods that don't override base classes > - Fixes blocking TearingDown in unit tests > - Use a .config file for tests/samples > - Adds interface to Invoker, Session and ClientSession to allow easy mocking > of the API > - Make the console solution compiling under Visual Studio 2008 > I'm more than happy to discuss any of this by email or through JIRA. Please > let me know if there's no plan (or nobody available) to evaluate this patch > for inclusion. If that is the case, I will consider forking the API to > continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1987) Patch for 0.10 C# API
Patch for 0.10 C# API - Key: QPID-1987 URL: https://issues.apache.org/jira/browse/QPID-1987 Project: Qpid Issue Type: Improvement Components: Dot Net Client Reporter: Julien Lavigne du Cadet Priority: Critical Please find attached a patch correcting the following issues : - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972) - Fixes public API to match standard .NET conventions (QPID-500) - Fixes code generation to match standard .NET conventions - Fixes ToString() methods that don't override base classes - Fixes blocking TearingDown in unit tests - Use a .config file for tests/samples - Adds interface to Invoker, Session and ClientSession to allow easy mocking of the API - Make the console solution compiling under Visual Studio 2008 I'm more than happy to discuss any of this by email or through JIRA. Please let me know if there's no plan (or nobody available) to evaluate this patch for inclusion. If that is the case, I will consider forking the API to continue fixing the API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1972) UUID.randomUUID() is not thread-safe
[ https://issues.apache.org/jira/browse/QPID-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730769#action_12730769 ] Julien Lavigne du Cadet commented on QPID-1972: --- Please do not consider this patch for now, there are issues with it. > UUID.randomUUID() is not thread-safe > > > Key: QPID-1972 > URL: https://issues.apache.org/jira/browse/QPID-1972 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 > Environment: .net API >Reporter: Julien Lavigne du Cadet >Priority: Critical > Attachments: qpid-dotnet.patch > > > UUID.randomUUID is not thread-safe because it's using a static random object. > However, recreating a random object each time the method is called is not an > option because 2 successive calls might result in the same UUID. > Please find attached in the next comment a patch that fixes the issue by > introducing a UUIDGenerator class. Now, to get a random UUID, you first need > to instantiate a UUIDGenerator and request it through it. That way there's no > need to lock in the UUID class. > Please note that this patch is BREAKING COMPABILITY with previous versions of > the API ! > The patch is also fixing 2 others issues : > - test.config is not included in the unit test project which result in half > of the unit tests failing > - the management console is not compiling with vs 2008 and .Net 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1904) Timestamps are incorrect
[ https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730263#action_12730263 ] Julien Lavigne du Cadet commented on QPID-1904: --- Please note that it only happens with brokers running on Windows. Timestamps are correct when the broker is running under linux. I also think that it's quite a significant issue and that it should be resolved asap ! > Timestamps are incorrect > > > Key: QPID-1904 > URL: https://issues.apache.org/jira/browse/QPID-1904 > Project: Qpid > Issue Type: Bug > Components: Qpid Managment Framework >Affects Versions: 0.5 > Environment: Windows XP > Reproduced both with the python API and the .Net API >Reporter: Julien Lavigne du Cadet > Attachments: qpid-dates.png > > > The timestamps for configuration and instrumentation messages are incorrect > both with the python and the .Net api. > According to the documentation "All timestamps are uint64 values representing > nanoseconds since the epoch (January 1, 1970)." However, the dates resulting > can be several years in the past or in the future. > To reproduce with the python api : > - in disp.py, line 178 add the following line : > print gmtime (nsec / 10) > - start qpid-tool and list the queues => the full dates will be displayed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1972) UUID.randomUUID() is not thread-safe
[ https://issues.apache.org/jira/browse/QPID-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1972: -- Attachment: qpid-dotnet.patch The patch > UUID.randomUUID() is not thread-safe > > > Key: QPID-1972 > URL: https://issues.apache.org/jira/browse/QPID-1972 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 > Environment: .net API >Reporter: Julien Lavigne du Cadet >Priority: Critical > Attachments: qpid-dotnet.patch > > > UUID.randomUUID is not thread-safe because it's using a static random object. > However, recreating a random object each time the method is called is not an > option because 2 successive calls might result in the same UUID. > Please find attached in the next comment a patch that fixes the issue by > introducing a UUIDGenerator class. Now, to get a random UUID, you first need > to instantiate a UUIDGenerator and request it through it. That way there's no > need to lock in the UUID class. > Please note that this patch is BREAKING COMPABILITY with previous versions of > the API ! > The patch is also fixing 2 others issues : > - test.config is not included in the unit test project which result in half > of the unit tests failing > - the management console is not compiling with vs 2008 and .Net 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1972) UUID.randomUUID() is not thread-safe
UUID.randomUUID() is not thread-safe Key: QPID-1972 URL: https://issues.apache.org/jira/browse/QPID-1972 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Environment: .net API Reporter: Julien Lavigne du Cadet Priority: Critical UUID.randomUUID is not thread-safe because it's using a static random object. However, recreating a random object each time the method is called is not an option because 2 successive calls might result in the same UUID. Please find attached in the next comment a patch that fixes the issue by introducing a UUIDGenerator class. Now, to get a random UUID, you first need to instantiate a UUIDGenerator and request it through it. That way there's no need to lock in the UUID class. Please note that this patch is BREAKING COMPABILITY with previous versions of the API ! The patch is also fixing 2 others issues : - test.config is not included in the unit test project which result in half of the unit tests failing - the management console is not compiling with vs 2008 and .Net 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1897) ToString() on UUID class should override and not hide Object.ToString()
[ https://issues.apache.org/jira/browse/QPID-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1897: -- Attachment: UUID.patch Third patch to fix an issue with randomUUID this time > ToString() on UUID class should override and not hide Object.ToString() > --- > > Key: QPID-1897 > URL: https://issues.apache.org/jira/browse/QPID-1897 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet >Assignee: Ted Ross > Attachments: UUID-equals.patch, UUID.patch, UUID.patch > > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > signature should be change from > public new String ToString() > to > public overrideString ToString() > Currently, if you to something like : > string queueName = _queuePrefix + _uuid > then queueName would look like "reply.org.apache.qpid.transport.util.UUID" > assuming that _queuePrefix == "Reply." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1906) C Sharp QMF Console (plus C# client fixes)
[ https://issues.apache.org/jira/browse/QPID-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725093#action_12725093 ] Julien Lavigne du Cadet commented on QPID-1906: --- The QMF C# Console doesn't compile on windows with VS 2008. Project file is somehow broken (references are missing and somehow it doesn't accept the auto-properties if you fix them) > C Sharp QMF Console (plus C# client fixes) > -- > > Key: QPID-1906 > URL: https://issues.apache.org/jira/browse/QPID-1906 > Project: Qpid > Issue Type: New Feature > Components: Dot Net Client, Qpid Managment Framework > Environment: mono on fedora 10 >Reporter: Bryan Kearney >Assignee: Ted Ross > Attachments: dotnetConsole.patch > > > Adds a C# Console to access QMF. Modeled after the python console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1904) Timestamps are incorrect
Timestamps are incorrect Key: QPID-1904 URL: https://issues.apache.org/jira/browse/QPID-1904 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.5 Environment: Windows XP Reproduced both with the python API and the .Net API Reporter: Julien Lavigne du Cadet Attachments: qpid-dates.png The timestamps for configuration and instrumentation messages are incorrect both with the python and the .Net api. According to the documentation "All timestamps are uint64 values representing nanoseconds since the epoch (January 1, 1970)." However, the dates resulting can be several years in the past or in the future. To reproduce with the python api : - in disp.py, line 178 add the following line : print gmtime (nsec / 10) - start qpid-tool and list the queues => the full dates will be displayed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1904) Timestamps are incorrect
[ https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1904: -- Attachment: qpid-dates.png See the screenshot for an example of an obviously wrong date > Timestamps are incorrect > > > Key: QPID-1904 > URL: https://issues.apache.org/jira/browse/QPID-1904 > Project: Qpid > Issue Type: Bug > Components: Qpid Managment Framework >Affects Versions: 0.5 > Environment: Windows XP > Reproduced both with the python API and the .Net API >Reporter: Julien Lavigne du Cadet > Attachments: qpid-dates.png > > > The timestamps for configuration and instrumentation messages are incorrect > both with the python and the .Net api. > According to the documentation "All timestamps are uint64 values representing > nanoseconds since the epoch (January 1, 1970)." However, the dates resulting > can be several years in the past or in the future. > To reproduce with the python api : > - in disp.py, line 178 add the following line : > print gmtime (nsec / 10) > - start qpid-tool and list the queues => the full dates will be displayed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1897) ToString() on UUID class should override and not hide Object.ToString()
[ https://issues.apache.org/jira/browse/QPID-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1897: -- Attachment: UUID-equals.patch Equality operators should also be overriden so that two instance of UUID with the same value are equals. See attached patch > ToString() on UUID class should override and not hide Object.ToString() > --- > > Key: QPID-1897 > URL: https://issues.apache.org/jira/browse/QPID-1897 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: UUID-equals.patch, UUID.patch > > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > signature should be change from > public new String ToString() > to > public overrideString ToString() > Currently, if you to something like : > string queueName = _queuePrefix + _uuid > then queueName would look like "reply.org.apache.qpid.transport.util.UUID" > assuming that _queuePrefix == "Reply." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1897) ToString() on UUID class should override and not hide Object.ToString()
[ https://issues.apache.org/jira/browse/QPID-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Lavigne du Cadet updated QPID-1897: -- Attachment: UUID.patch Patch file to fix the issue > ToString() on UUID class should override and not hide Object.ToString() > --- > > Key: QPID-1897 > URL: https://issues.apache.org/jira/browse/QPID-1897 > Project: Qpid > Issue Type: Bug > Components: Dot Net Client >Affects Versions: 0.5 >Reporter: Julien Lavigne du Cadet > Attachments: UUID.patch > > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > signature should be change from > public new String ToString() > to > public overrideString ToString() > Currently, if you to something like : > string queueName = _queuePrefix + _uuid > then queueName would look like "reply.org.apache.qpid.transport.util.UUID" > assuming that _queuePrefix == "Reply." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-1897) ToString() on UUID class should override and not hide Object.ToString()
ToString() on UUID class should override and not hide Object.ToString() --- Key: QPID-1897 URL: https://issues.apache.org/jira/browse/QPID-1897 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.5 Reporter: Julien Lavigne du Cadet signature should be change from public new String ToString() to public overrideString ToString() Currently, if you to something like : string queueName = _queuePrefix + _uuid then queueName would look like "reply.org.apache.qpid.transport.util.UUID" assuming that _queuePrefix == "Reply." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
