ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Very strange issue with CURRENT_TIMESTAMP

Post new topic  Reply to topic Goto page Previous  1, 2
 Very strange issue with CURRENT_TIMESTAMP « View previous topic :: View next topic » 
Author Message
mgk
PostPosted: Sun Sep 23, 2012 1:29 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
even just a modification to the ESQL log statement to allow it to write to User Trace, in the way that the .NET APIs can write to User Trace would likely be sufficient for most purposes.


But the LOG statement CAN write to user trace, what am I missing?

King regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Sun Sep 23, 2012 5:56 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mgk wrote:
Quote:
even just a modification to the ESQL log statement to allow it to write to User Trace, in the way that the .NET APIs can write to User Trace would likely be sufficient for most purposes.


But the LOG statement CAN write to user trace, what am I missing?

King regards,


Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Sep 24, 2012 4:48 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

rekarm01 wrote:
request for enhancement.



. . . . . . : r f e :
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
dwmllr
PostPosted: Fri Jul 26, 2013 7:39 am    Post subject: Reply with quote

Newbie

Joined: 31 Jul 2012
Posts: 5

For anybody who comes across the same crap behavior which the original poster complained about...

I got the same when I set the local machine (a VM) time back a couple of hours. Every time the flow executed CURRENT_TIMESTAMP would return THE EXACT SAME VALUE 15:36, every time!!. Even after a broker restart. 15:36 ...

Set the time back to current time and it started working again.

Ridiculous ....
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Very strange issue with CURRENT_TIMESTAMP
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.