| Author |
Message
|
| reldb |
 Posted: Thu Nov 30, 2006 7:14 am Post subject: creating a new broker, successful but not able to see |
 |
|
Apprentice
Joined: 06 Sep 2006
Posts: 34
|
Hi,
On HP Unix, i already have 6 brokers up and running and i can see them in
a) using mqsilist command
b) /var/mqsi/BROKERS/<BROKERNAME>
c) there are couple of log files and nnsyreg.dat, NNSYMessageLog.nml file in <BROKERNAME>directory
Now i created a new broker
1) logged in as db2inst1 user
db2 start database manager
db2 create database myDB
db2 connect to myDB
db2 bind ./sqllib/bnd/@db2cli.lst grant public CLIPKG 5
2) as root, changed the (/var/wmqi/odbc/.odbc.ini) file for new database myDB
db2 update database configuration for myDB using dbheap 900
3) logged in as mqsi user
mqsicreatebroker myBROKER —i mqsi —a password —q myBROKER_QM —n myDB —u myqsi -p password
Till now there is no error
and when i do mqsilist i can see this new broker too
I am just wondering why there is no new directory for this new broker in BROKERS folder. Am i missing something?
Paths variables profiles are already set
Thanks
DB |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Nov 30, 2006 7:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe because you haven't mqsistart <brokername>.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Nov 30, 2006 7:40 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Did you create a Configuration Manager?
You can't talk to the broker without one...
And once you have a CM, then you need to register the broker with it (by creating a broker on the CM).
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| reldb |
| Posted: Thu Nov 30, 2006 10:09 am Post subject: |
|
|
Apprentice
Joined: 06 Sep 2006
Posts: 34
|
yes
As per the installation guide WebSphere MQ Integrator for HP UX V2.1
page 51
I added the broker to domain and deployed the empty execution group to the broker. it is done properly and i can see it in my broker using
mqsilist <BROKERNAME>
BIP8130I: Execution Group: default - 3386
BIP8071I: Successful command completion.
I created a broker on control center etc etc
when i use mqsistop command
mqsi@violin> mqsistop FRMT2006
BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.
mqsi@violin>
In actual it is not stopping the broker |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 30, 2006 10:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are you sure it started successfully?
If the mqsistart command says "successfull command completion", that doesn't mean that it started successfully.
mqsilist doesn't tell you anything about the status of the broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| reldb |
| Posted: Thu Nov 30, 2006 10:45 am Post subject: |
|
|
Apprentice
Joined: 06 Sep 2006
Posts: 34
|
mqsi@violin> mqsistart FRMT2006
WebSphere MQ queue manager running.
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
mqsi@violin>
mqsi@violin> ps -ef | grep bip | grep FRMT2006
mqsi 18526 1 0 12:43:49 ? 0:00 bipservice FRMT2006
mqsi 17324 1 0 11:48:45 ? 0:00 bipservice FRMT2006
mqsi 18532 18526 0 12:43:49 ? 0:00 bipbroker FRMT2006
mqsi 17325 17324 0 11:48:45 ? 0:00 bipbroker FRMT2006
mqsi 3282 3278 0 11:59:35 ? 0:00 bipbroker FRMT2006
mqsi 3278 1 0 11:59:35 ? 0:00 bipservice FRMT2006
mqsi@violin>
Everytime i start the broker 2 new bip process also started. mqsistop not killing these bip process. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Nov 30, 2006 11:02 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| reldb wrote: |
yes
As per the installation guide WebSphere MQ Integrator for HP UX V2.1
page 51
|
Hun? Are you using version 2.1? 
That product has reached its end of life and is not supported.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 30, 2006 11:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| reldb wrote: |
| check the system log to ensure that the component started without problem and that it continues to run without problem. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| reldb |
| Posted: Thu Nov 30, 2006 12:33 pm Post subject: |
|
|
Apprentice
Joined: 06 Sep 2006
Posts: 34
|
i created a new broker
but same problem while doing mqsistart and mqsistop
Let me try to configure this on CM if that matters but prev broker was giving error even after that too
/var/adm/user.log not showing anything specific for this error |
|
| Back to top |
|
|
| reldb |
| Posted: Thu Nov 30, 2006 1:54 pm Post subject: |
|
|
Apprentice
Joined: 06 Sep 2006
Posts: 34
|
I see this in /var/adm/user.log
Nov 30 15:36:06 violin syslog: TLG_SC_GEN Fauilure getting SYS_DATETIME in function NCSSC_Init_Msg
Nov 30 15:37:59 violin syslog: TLG_SC_GEN Fauilure getting SYS_DATETIME in function NCSSC_Init_Msg
I created a new broker called FRMTDIN2 and configured with channels to cc_qm and assignments etc
still getting error when i start the broker
Nov 30 15:51:41 violin WMQIv210[2475]: (FRMTDIN2.default)[1]BIP2201I: Execution Group started: process '2475'; thread '1'; additional information: brokerName 'FRMTDIN2'; executionGroupUUID '4d79b63a-0f01-0000-0080-9f5d367a753f'; executionGroupLabel 'default'; defaultExecutionGroup 'true'; queueManagerName 'FRMTDIN2'; trusted 'false'; dataSourceName 'FRMTDIN2'; userId 'mqsi'; migrationNeeded 'false'; brokerUUID '904cb63a-0f01-0000-0080-9f5d367a753f'; filePath '/opt/wmqi'; workPath '/var/wmqi'. : FRMTDIN2.4d79b63a-0f01-0000-0080-9f5d367a753f: /build/S210_P/src/DataFlowEngine/ImbMain.cpp: 215: main: : |
|
| Back to top |
|
|
|
|
