| Author |
Message
|
| brianleetl |
 Posted: Tue Apr 10, 2007 6:21 pm Post subject: (Solved) Timestamp issue with MQWF Java API |
 |
|
Newbie
Joined: 10 Apr 2007
Posts: 3
|
Hi
I am currently having and issue with the Timestamp when using
MQWF Java API to queryWorkItems based on 'RECEIVED_TIME BETWEEN ? AND ?' filter.
Understand that MQWF store timestamp in UTC(GMT):
Question: Why is it that i can query workitems when using local time in a standalone application, but i was unable to query workitems when the same code is running under WebSphere Application Server v5.1 in the same server? It seems like
the java API no longer convert my local time to UTC time in WAS v5.1
Is there any setting or configuration problem?
Thanks
Last edited by brianleetl on Wed Apr 11, 2007 6:51 pm; edited 1 time in total |
|
| Back to top |
|
 |
| hos |
| Posted: Wed Apr 11, 2007 1:25 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
there are several possible reasons for the problems you describe.
You should try to achieve the same results in both, your 'Fat Client' and your Web Client. Therefore you should make sure to use the same triggering environment:
- use the same MQWF and operating system UserID
- make sure that the same TZ settings are in effect
- make sure that you use the same version of the Java API:
if you are using MQWF 3.6 or 3.5 you should use the native Jave API
facjapi.jar otherwise the 'classic' Java API fmcojagt.jar.
( make sure that you do not have erronously a Java API version on your
AppServer's CLASSPASTH )
- make sure that you use the same JDK. Recently there was an update on the
JDK's with respect to changes in daylight savings time.
Once you see the same results, you can verify whether the result is what you expect. If this is not the case and you are using the native Java API, you should obtain the latest version. afak the were fixes in the native Java API wrt timezone handling. |
|
| Back to top |
|
|
| brianleetl |
| Posted: Wed Apr 11, 2007 2:14 am Post subject: |
|
|
Newbie
Joined: 10 Apr 2007
Posts: 3
|
Hi Hos
-make sure that the same TZ settings are in effect
Had check the TZ setting on my AIX server, since both the standalone app and WAS server are running on the same server, should be using
the same TZ??
- make sure that you use the same version of the Java API:
Had use Agent.versionInfo().version and Agent.versionInfo().release
to check on the version for and they are the same (v3.6).
- make sure that you use the same JDK. Recently there was an update on the JDK's with respect to changes in daylight savings time.
Both are using the same JRE->J2RE 1.4.2.
-use the same MQWF and operating system UserID
Both are using the same userID to login to the MQWF.
Thanks of ya reply
Brian |
|
| Back to top |
|
|
| hos |
| Posted: Wed Apr 11, 2007 6:26 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
| Quote: |
| - make sure that you use the same version of the Java API: |
Sorry for not being clear enough.
I meant the identical API implementation.
You cannot be sure about the maintenance level from reading version and release information. Please use the identical fmcjapi.jar file.
As I mentioned there was at least one fix in the fmcjapi.jar in this area. |
|
| Back to top |
|
|
| brianleetl |
| Posted: Wed Apr 11, 2007 6:49 pm Post subject: |
|
|
Newbie
Joined: 10 Apr 2007
Posts: 3
|
Hi Hos
Thanks for your clarification. I double check the version level and discovered that the maintainance level are indeed different.
One is using IBM WebSphere MQ Workflow V3.6.0.3 Native Java API
while another is using IBM WebSphere MQ Workflow V3.6.0.0 Native Java API.
So i fix up my classpath again using the lastest version and it work!
Guess i am fixed up my API version initially hence causing this problem.
Thanks for ya help! |
|
| Back to top |
|
|
|
|
