| Author |
Message
|
| sasmita10 |
 Posted: Tue Feb 13, 2007 8:18 pm Post subject: DST Patch |
 |
|
Novice
Joined: 23 Feb 2005
Posts: 24
Location: Danbury, CT
|
We have one server with IBM MQSeries 5.2 for Solaris. Is there any DST patch for it ? What will happen if we don't apply the patch ?
We have other servers with 5.3 in Solaris, Linux, AS400, and Windows. We are using Circular logging for all MQ servers. Do I have to apply DST patch for all these servers ?
We have WMQI 2.1 broker. Is ther any patch for it ?
We are applying patch for 6.0 and broker 6.0.
What is the work around solution if we don't apply DST patch for all these 5.2 and 5.3 version ?
_________________
WMQ and WMQI specialist
(IBM Certified Web Sphere MQSeries 6.0 System Administrator )
(IBM Certified Web Sphere Message Broker 6.1 System Administrator ) |
|
| Back to top |
|
 |
| lex_talionis |
| Posted: Sun Mar 11, 2007 8:29 am Post subject: |
|
|
Novice
Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX
|
my 6 environment is running an hour behind...i thought the refresh pack 2 covered us...we installed refresh pack 2 almost 2 months ago.
anyone have this issue right now? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 11, 2007 5:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| lex_talionis wrote: |
my 6 environment is running an hour behind...i thought the refresh pack 2 covered us...we installed refresh pack 2 almost 2 months ago.
anyone have this issue right now? |
You did not specify which OS.
Remember that the OS too needs to be patched for DST.
And if dealing with AIX make sure the OS is brought up to the right patch level before applying the DST or you're going to be good to reimage the server....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lex_talionis |
| Posted: Mon Mar 12, 2007 5:37 am Post subject: |
|
|
Novice
Joined: 23 Aug 2006
Posts: 23
Location: Austin, TX
|
Sorry, it's W2K3...just to clarify this thread:
Our servers had the MS DST patches applied and the server OS time was correct; however, Eclipse was still showing times one hour behind. I contacted IBM and it's the Eclipse JRE that needed to be updated. Here's there email support message to me:
| Code: |
Here are the instructions I mentioned in my voicemail..
The JVM that is installed with the Eclipse GUI needs to be updated using the JAVA Time Zone Utility (JTZU) tool...
Send me an email if you have any questions.. (websphere_support@mainz.ibm.com)..
Hello L2,
Customers need to ensure that the JRE being used by eclipse (which can be customized be customers) is up to date by running the JTZU against
the specified version that they are using. The actions that need to be
taken are as follows ....
- identify the JDK in use by eclipse
This is achieved by launching the WebSphere MQ explorer, and then
following the menu tree ...
Window ->Preferences -> Java -> Installed JREs
.
A list of one or more installed JREs are displayed in the panel.
One of these JREs will be 'checked' indicating that it is the one
that eclipse will use to run java code (MQ Explorer in this case)
against. Make a note of this location for example C:\JDK\J150
- Download and extract the appropriate JTZU from ...
.
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html
.
- use the command and change directories to the extract location.
- alter the runjtzuenv.bat file to set the location of a JVM that the
tool will be launched under. for example...
rem set JAVA_HOME to the a Java installation directory
set JAVA_HOME=c:\jdk\j142\jre
rem set NOGUI
set NOGUI=false
rem set DISCOVERONLY
set DISCOVERONLY=true
rem set SILENTPATCH
set SILENTPATCH=false
This would instruct the tool to run against a JRE (in this case 1.4.2) at a location c:\jdk\j142\jre
- launch the tool using runjtzu.bat
- select 'Interactive mode' and click start button
- ensure customer make a note of the warning message regarding applying
maintenance
- enter the location of the java runtime being used by eclipse,
for example c:\jdk\J150\jre (please note that '\jre' is needed here)
- click update to begin the update process.
.
.
Customer should then re-test the MQExplorer and determine if the problem
persists.
|
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Mar 12, 2007 6:22 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| rb462627 |
| Posted: Tue Mar 20, 2007 9:53 am Post subject: DST Eclipse Patch |
|
|
Novice
Joined: 23 Apr 2004
Posts: 23
Location: Hartford, CT
|
WE too are 1 hour off on our WMBT. When I attemp IBM ZTZU, it tells me the JAVA JRE I extracted from WMQ Toolkit is up to date.
Anyone else experiencing this? If so how do you resolve the time issue without applying FP9 to WMBT?
TNKS
Ralph
_________________
Ralph Beckers
IBM Certified Specialist - MQSeries
IBM Global Services - The Hartford Account
Office #: 860.547.4745
ralph.beckers@thehartford.com
rbeckers@us.ibm.com
"No! Try Not. Do. Or Do Not... There Is No Try!" Master Yoda |
|
| Back to top |
|
|
| sasmita10 |
| Posted: Tue Mar 20, 2007 11:40 am Post subject: MQ Problem after applying DST patch |
|
|
Novice
Joined: 23 Feb 2005
Posts: 24
Location: Danbury, CT
|
Hi
We have typical problem for Java/JMS/JBoss application. We have applied DST patch in MQSeries 5.3 Unix Soalris. Initially it had MQ 5.2 in UNIX Solaris system.
After applying the patch application running in Java, Dotnet are working fine. But only one JBoss application is giving error MQJE001: Completion Code 2, Reason 2019 for few transaction.
It is resolved in production when we hooked it to another fail over queue manager which is running Windows ( MQ 5.3 without DST patch in Windows)
We are facing problem in QA when we connect to either Unix or Windows.
When I checked the log I found that connection is breaking with the server connection channel.
03/19/2007 04:06:21
AMQ9604: Channel 'JAVA.CHANNEL.xxx' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'JAVA.CHANNEL.xxx' is no longer
running. The check process system call returned 545284357 for process 4092.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated.
I appreciate if anyone can help me to resolve this issue.
_________________
WMQ and WMQI specialist
(IBM Certified Web Sphere MQSeries 6.0 System Administrator )
(IBM Certified Web Sphere Message Broker 6.1 System Administrator ) |
|
| Back to top |
|
|
|
|
