Author |
Message
|
vijay.gopal |
Posted: Sun Sep 09, 2012 9:17 pm Post subject: MQ Upgrade to 7.0.1.7 in Domino Server on Linux s390x-64 |
|
|
Newbie
Joined: 09 Sep 2012 Posts: 5
|
Hi all,
The Lotus Notes application I support was on MQ version 6 before and on the server it has been upgraded to 7.0.1.6. in the test server. So I recompiled the application code with these Jar files
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
and commented some lines of code from the Java agent as explained below.
Removed line import com.ibm.gwa.mq.*;
Commented following lines:
// MQSecurityExit gwaPlugin = null;
// gwaPlugin = (MQSecurityExit) new SecurityExit();
// MQEnvironment.securityExit = gwaPlugin;
Included following packages into Archives and added them in the Java Build Path
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
This works well in the test server.
The same change is done one the production server as well.
Now the Production server is upgraded to the version 7.0.1.7 (different from the test server)and since then it is giving the following error in the Application Log.
--------------------
Start of Agent Logging
ClassPath=:/notes/d03dbs04/domino/java/NCSO.jar:/opt/domino/85030/lotus/notes/85030/zlinux/jvm/lib/ext/Notes.jar:/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.gwa.mq.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/connector.jar:/opt/mqm/java/l:.
class lotus.domino.NotesException null
End of Agent Logging
---------------------
The domino server is running on Linux s390x-64
JVM version: JRE 1.6.0 IBM J9 2.4
jvmxz6460sr7-20100219_54049 (JIT enabled, AOT enabled) J9VM
In the version 7.0.1.7, do I have to include any other Jar and recompile? Can anyone throw some light on this issue. The production environment is affected by this.
Any help will be much appreciated.
Regards.. |
|
Back to top |
|
 |
exerk |
Posted: Mon Sep 10, 2012 12:26 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Just as a general observation, it is not a good idea to package up WMQ jar files within your application, reference them correctly instead and ensure there is a full WMQ client installation (which is free) on the server where your application needs to run.
It's possible you are seeing changed behaviour of the jar files between FixPack levels, but that is speculation on my part. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
vijay.gopal |
Posted: Mon Sep 10, 2012 1:43 am Post subject: Thanks |
|
|
Newbie
Joined: 09 Sep 2012 Posts: 5
|
Thank you for your tip.
I am not the application developer so I do not have the proper privileges or knowledge to reference the Jar files instead of packaging it.
Not sure how to proceed. Development team also is of no help as I have already approached them. I was thinking, for the time being, to save my face, if anyone knows any other jar files that needs to be packaged for the MQ version 7.0.1.7?
Regards |
|
Back to top |
|
 |
exerk |
Posted: Mon Sep 10, 2012 1:49 am Post subject: Re: Thanks |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
vijay.gopal wrote: |
I am not the application developer so I do not have the proper privileges or knowledge to reference the Jar files instead of packaging it. |
I believe that classpath addresses the issue, and site standards should include the documentation of the install path for your WMQ installs - client and server.
vijay.gopal wrote: |
Not sure how to proceed. Development team also is of no help as I have already approached them. |
Don't allow them to just wash their hands of their responsibilities - if it's their application, they should provide support for you.
vijay.gopal wrote: |
I was thinking, for the time being, to save my face, if anyone knows any other jar files that needs to be packaged for the MQ version 7.0.1.7? |
You should not be saving face, you should be pointing out the application team that this is what can happen when jar files are copied into a package rather than being correctly referenced, and even if I did know what other jar files you may need, considering my antipathy towards inclusion rather than referencing, do you think I'd tell you?  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
vijay.gopal |
Posted: Mon Sep 10, 2012 2:06 am Post subject: |
|
|
Newbie
Joined: 09 Sep 2012 Posts: 5
|
The problem is that, I am facing the client, not the developers. They are taking their own sweet time to fix this.
I request, if you can provide me any solution you know.. It would be of great help..
Regards |
|
Back to top |
|
 |
exerk |
Posted: Mon Sep 10, 2012 2:10 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
vijay.gopal wrote: |
The problem is that, I am facing the client, not the developers. They are taking their own sweet time to fix this. |
Who is paying the developers, you, or the client?
vijay.gopal wrote: |
I request, if you can provide me any solution you know.. It would be of great help..  |
The only solution I can provide is that which I already have. You have a test infrastructure, so you could align that with the live infrastructure, i.e. apply the 7.0.1.7 FixPack and see if it breaks, or whether the issue is isolated to the live infrastructure. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
vijay.gopal |
Posted: Mon Sep 10, 2012 2:14 am Post subject: |
|
|
Newbie
Joined: 09 Sep 2012 Posts: 5
|
Its the client only.
Ok, will work that way then. Anyways thanks a lot for your help in this.
Regards |
|
Back to top |
|
 |
vijay.gopal |
Posted: Mon Sep 10, 2012 2:55 am Post subject: |
|
|
Newbie
Joined: 09 Sep 2012 Posts: 5
|
Just to add on to it,
This is the error i get on the server
> [18776:00002-63892016] 09/10/2012 04:51:47 JVM: Java Virtual Machine initialized.
[18776:00006-1375734096] 09/10/2012 04:51:47 AMgr: Start executing agent 'MQ Java Get messages' in 'c_dir/cdmsa/admprcla.nsf'
[18776:00009-1379182928] 09/10/2012 04:51:53 Agent Manager: Agent error: Exception in thread "AgentThread: GetMessageAgent"
[18776:00010-1379182928] 09/10/2012 04:51:53 Agent Manager: Agent error: java.lang.NullPointerException
[18776:00012-1379182928] 09/10/2012 04:51:53 Agent Manager: Agent error: at GetMessageAgent.NotesMain(Unknown Source)
[18776:00014-1379182928] 09/10/2012 04:51:53 Agent Manager: Agent error: at lotus.domino.AgentBase.runNotes(Unknown Source)
[18776:00016-1379182928] 09/10/2012 04:51:53 Agent Manager: Agent error: at lotus.domino.NotesThread.run(Unknown Source)
[18776:00006-1375734096] 09/10/2012 04:51:53 AMgr: Agent 'MQ Java Get messages' in 'c_dir/cdmsa/admprcla.nsf' completed execution |
|
Back to top |
|
 |
|