Author |
Message
|
scottm |
Posted: Thu Aug 06, 2009 12:35 pm Post subject: 32 bit execution groups on a 64 bit broker? |
|
|
Apprentice
Joined: 13 May 2004 Posts: 44 Location: SE Tennessee
|
Hopefully this is just a simple configuration issue that I’m having, but I’m having a problem creating a 32 bit execution group in my 64 bit broker. I need to access a 32 bit user database, so my understanding is that I need to do that in a 32 bit execution group. I have no issues creating 64 bit EG and I can connect to all of my 64 DB’s. I’m on AIX v5.3, MQ v6.0.2.4 and Broker v6.1.04, Broker databases UDB v9.1, user databases v9.1 and v8.1.
According to a chart about "Enabling ODBC connections to the databases" from the manual
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/ae03440_.htm
I can run MQ and MB as 64 bit and connect to both 64 and 32 bit databases.
I have the odbc64.ini file working with all my 64 bit databases and my broker databases just fine. But now I need to get my odbc32.ini file working. From what I read, I need to put in access to my broker databases in this file along with the access to my other 32 bit user databases.
For the broker database I have this in my odbc64.ini
[MQD9004D]
DRIVER=libdb2Wrapper64.so
Description=MQD9004D DB2 ODBC Database
Database=MQD9004D
In my odbc32.ini file I have this for the same broker database:
[MQD9004D]
Driver=/udbhome/wfinst2/sqllib/lib/libdb2.a
Description=DB2V8DB DB2 ODBC Database
Database=MQD9004D
The driver is pointing to a 32 bit driver. I also have the following variables set:
ODBCINI=/var/mqsi/odbc/odbc64.ini
ODBCINI32=/var/mqsi/odbc/odbc32.ini
MQSI_LIBPATH32=/usr/opt/mqsi/jre15/bin:/usr/opt/mqsi/jre15/bin/classic:/usr/mqm/java/lib:/usr/opt/mqsi/xml4c/lib:/usr/mqm/lib:/usr/opt/mqsi/ODBC32/V5.3/lib:/usr/opt/mqsi/xlxpc/lib::/udbhome/wfinst2/sqllib/lib32
The problem is when I create a 32 bit EG and deploy a bar file, I get no response back until the configuration manager finally gets a timeout from the broker regarding the deploy.
BIP2066E: Broker 'MQB9004D' (UUID '05a873ea-2201-0000-0080-df02229d7234') was unable to retrieve an internal configuration response message for execution group 'TEST' within the 360 second configuration timeout.
Also, before I get this timeout message, if I try the deploy again, I get an error stating that the previous deploy has not been completed.
Has anyone else gotten a 32 bit execution group working with a 64 bit broker? |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Aug 07, 2009 2:58 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Did you check communications between broker and config mgr? It could be that this has nothing to do with the 32 bits egs...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
scottm |
Posted: Fri Aug 07, 2009 3:53 am Post subject: |
|
|
Apprentice
Joined: 13 May 2004 Posts: 44 Location: SE Tennessee
|
I'm able to create 64 bit EG's on that same broker with no problems and when I deply flows, they work as expected. But when I create a 32 bit EG and deploy a flow, it is unable to complete the action and eventually the config manager times out.
Have you managed to create a 32 bit EG on a 64 bit broker? If so, can you show me your odbcini files for both 64 and 32 bits so I can verify that I am on the right track with what I did?
Thanks |
|
Back to top |
|
 |
fschofer |
Posted: Fri Aug 07, 2009 4:16 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
Hi,
have you tried
Driver=/udbhome/wfinst2/sqllib/lib32/libdb2.a
instead of
Driver=/udbhome/wfinst2/sqllib/lib/libdb2.a
Greetings
Frank |
|
Back to top |
|
 |
scottm |
Posted: Fri Aug 07, 2009 5:17 am Post subject: |
|
|
Apprentice
Joined: 13 May 2004 Posts: 44 Location: SE Tennessee
|
Yes I did and I bounced the broker to make sure it took the new odbcini file, but it didn't make a difference.
I need to have an entry for my broker in the 32 bit file using the 32 bit libraries, right? Just like I have an entry in my 64 bit ini file for the same broker but using the 64 bit libraries.
The 64 bit side works great. I just have an issue getting a 32 bit EG working. And I don't have a choice to upgrade the UDB databases to 64 bits since there is another application that uses those DB's and they CAN'T run on 64 bit... yet... |
|
Back to top |
|
 |
fschofer |
Posted: Fri Aug 07, 2009 5:30 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
|
Back to top |
|
 |
scottm |
Posted: Fri Aug 07, 2009 7:13 am Post subject: |
|
|
Apprentice
Joined: 13 May 2004 Posts: 44 Location: SE Tennessee
|
My AIX admin did what was described in the chapter about the syslog, but I'm not getting any information in the user.log file.
Still no luck with the 32 bit EG's... |
|
Back to top |
|
 |
fschofer |
Posted: Sun Aug 09, 2009 8:31 am Post subject: |
|
|
 Knight
Joined: 02 Jul 2001 Posts: 524 Location: Mainz, Germany
|
Hi,
you should at least see some info logging about message broker start / stop within user.log.
Was the syslog daemon refreshed and did you restart the broker ?
Greetings
Frank |
|
Back to top |
|
 |
zpat |
Posted: Sun Aug 09, 2009 11:20 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Open a PMR with IBM, if a product feature does not work as it's meant to. |
|
Back to top |
|
 |
scottm |
Posted: Mon Aug 10, 2009 3:57 am Post subject: |
|
|
Apprentice
Joined: 13 May 2004 Posts: 44 Location: SE Tennessee
|
Frank - my admin told me she followed the instructions, which included restarting the syslog daemon and I stopped and restarted the broker. Something must be amiss... the user.log file is not being written to at all. I'll check with the Admin again. Thanks
Zpat - I will be opening a PMR today. It's got to be just something that I haven't configured properly so Iw as just checking here first to see if anyone else had this situation before. I'll reply back when I get it resolved. |
|
Back to top |
|
 |
|