| Author |
Message
|
| ammx |
 Posted: Mon Oct 15, 2018 12:11 pm Post subject: creating execution groups IIB v10 |
 |
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
Hi I tried to create the an execution group named ESH_EIDM_LIW_EG with the following command(under the iib user):
mqsicreaateexecutiongroup -n EIDM_BROKER10 -e ESH_EIDM_LIW_EG
and i got the following error message:
BIP1034E: Properties file 'EIDM_BROKER10' could not be read.
A utility was requested to read connection parameters from the properties file 'EIDM_BROKER10', but this file was not found, or contains invalid information.
Reissue the command specifying a valid path and file name. If such a file is not available, Use the Integration Toolkit to generate one, or supply the connection parameters individually.
I googled BIP1034E error code but didnt find any information. Where can I find the properties file and what can be done in case it is not there?
Thanks in advance |
|
| Back to top |
|
 |
| Phanikumar |
| Posted: Mon Oct 15, 2018 10:23 pm Post subject: Re: creating execution groups IIB v10 |
|
|
Apprentice
Joined: 29 Aug 2016
Posts: 25
Location: Kuwait
|
| ammx wrote: |
Hi I tried to create the an execution group named ESH_EIDM_LIW_EG with the following command(under the iib user):
mqsicreaateexecutiongroup -n EIDM_BROKER10 -e ESH_EIDM_LIW_EG
and i got the following error message:
BIP1034E: Properties file 'EIDM_BROKER10' could not be read.
A utility was requested to read connection parameters from the properties file 'EIDM_BROKER10', but this file was not found, or contains invalid information.
Reissue the command specifying a valid path and file name. If such a file is not available, Use the Integration Toolkit to generate one, or supply the connection parameters individually.
I googled BIP1034E error code but didnt find any information. Where can I find the properties file and what can be done in case it is not there?
Thanks in advance |
Command has typo mistakes and -n flag is wrong for broker.
Command is
mqsicreateexecutiongroup EIDM_BROKER10 -e ESH_EIDM_LIW_EG
_________________
Saying what you feel. It's not being rude, it's called being real. |
|
| Back to top |
|
|
| ammx |
| Posted: Tue Oct 16, 2018 6:48 am Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
Hi @Phanikumar
Thanks for your reply
I tried to run the right command once again to create a testing execution group this way:
mqsicreateexecutiongroup EIDM_BROKER7 -e TESTEG
and i got this timeout message
BIP1124I: Creating integration server 'TESTEG' on integration node 'EIDM_BROKER7'...
BIP1047E: The operation timed out waiting for a response.
The utility did not receive an expected response from the integration node within a designated amount of time. The operation might have completed successfully, even though the response was not received.
Ensure that the integration node is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.
apparently the broker is not responding, but i checked with ps -ef | grep bip and it is running under the right user, the httplistener is also started, so i dont know why it keeps timing out:
# ps -ef | grep bip
iibadmn 18415652 19726554 53 10:13:29 - 0:32 bipbroker EIDM_BROKER7
iibadmn 19726554 1 0 10:13:29 - 0:00 bipservice EIDM_BROKER7
iibadmn 20774996 18415652 0 10:13:32 - 0:00 biphttplistener EIDM_BROKER7
the mq qmgr is also running
Last edited by ammx on Tue Oct 16, 2018 7:12 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 16, 2018 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ammx wrote: |
| so i dont know why it keeps timing out |
I don't know why you're using EIDM_BROKER7 in one post and EIDM_BROKER10 in another.
Having settled on a broker, verify it's running v10, verify the command shell you're using is v10, verify it's running (ideally using the IIB logs rather than the ps command) and then retry creating an execution group. Then look in the logs to see what happened.
For the record, all the ps command proves is that the processes have not crashed out of the machine. They could easily be hung up.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ammx |
| Posted: Tue Oct 16, 2018 7:18 am Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
the broker 7 is the original, I created the 10 broker to check if i could create an eg with a different broker.
The only error messages on the logs are the following
Oct 16 10:35:23 xxxx user:err|error IIB[23331028]: IBM Integration Bus v100013 (EIDM_BROKER7.ESH_EIDM_WWRECON_EG) [Thread 1] (Msg 1/1) BIP4512S: java.lang.LinkageError: loading constraint violation when overriding method "org/w3c/dom/Element.getSchemaTypeInfo()Lorg/w3c/dom/TypeInfo;" during creation of class "org/apache/xerces/dom/ElementImpl": loader "com/ibm/broker/classloading/GroupedClassLoader@6da23dc4" of class "org/apache/xerces/dom/ElementImpl" and loader "com/ibm/oti/vm/BootstrapClassLoader@dced454b" of class "org/w3c/dom/Element" have different types for the method signature was thrown while loading Java user-defined node class org.apache.wml.dom.WMLAnchorElementImpl.
both brokers are using version IIB 10 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 16, 2018 7:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ammx wrote: |
| the broker 7 is the original, I created the 10 broker to check if i could create an eg with a different broker. |
Which OS?
Which exact version of IIB?
Which user is issuing the command to create the execution group?
Have you confirmed that both the broker and your command are running in the correct shell?
Because that error says "hosed up installation with mismatched versions" to me.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ammx |
| Posted: Tue Oct 16, 2018 7:54 am Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
OS version is AIX 7.1
IIB version: 10.0.0.13
# mqsiservice -v
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
BIP8996I: Version: 100013
BIP8997I: Product: IBM Integration Bus
BIP8998I: CMVC Level: S1000-L180612.10759
BIP8999I: Build Type: Production, 64 bit, rios_aix_4
to check the list of integration nodes created with this installation
# mqsilist -d 0
BIP8099I: Integration node: EIDM_BROKER10 - MQMEIDMD_IIB
BIP8099I: Integration node: EIDM_BROKER7 - MQMEIDMD_IIB
BIP8071I: Successful command completion.
user issuing command: iibadmn(this is the user associated with the broker installation)
i am not sure how to check the correct shell |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 16, 2018 8:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ammx wrote: |
| i am not sure how to check the correct shell |
Does this user, either automatically at log on or from you doing it manually, have the mqsiprofile for v10 sourced to it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ammx |
| Posted: Tue Oct 16, 2018 12:47 pm Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
yes, when i switch to iibadmn it is linked to the mqsiprofile:
root@xxxxxxx:/home/iibadmn $ su - iibadmn
/etc/profile[78]: TMOUT: This variable is read only.
MQSI 10.0.0.13
/opt/IBM/iib-10.0.0.13/server
in the .profile file of the iibadmn there is a line with the full mqsiprofile path of the iib installation
PATH=$PATH:$HOME/bin
export PATH
. /opt/IBM/iib-10.0.0.13/server/bin/mqsiprofile
at login the user shows TMOUT: this variable is read only, i am not sure if this could be the cause of the issue |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Wed Oct 17, 2018 12:20 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
|
| Back to top |
|
|
| ammx |
| Posted: Wed Oct 17, 2018 1:14 pm Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
Since this appears to be an installation issue I opted to reinstall the broker. Do you know if this is the right command to uninstall?
/install_dir/Uninstaller/Uninstaller -i silent
I searched in the IIB path for the Uninstaller but didn't find it. I also search it on the entire system but it is nowhere to be found
:/opt/iib-10.0.0.13 $ ls
common extensions ie02 iib license properties readmes server |
|
| Back to top |
|
|
| Phanikumar |
| Posted: Wed Oct 17, 2018 8:46 pm Post subject: |
|
|
Apprentice
Joined: 29 Aug 2016
Posts: 25
Location: Kuwait
|
| ammx wrote: |
Since this appears to be an installation issue I opted to reinstall the broker. Do you know if this is the right command to uninstall?
/install_dir/Uninstaller/Uninstaller -i silent
I searched in the IIB path for the Uninstaller but didn't find it. I also search it on the entire system but it is nowhere to be found
:/opt/iib-10.0.0.13 $ ls
common extensions ie02 iib license properties readmes server |
You can delete the mqsi directory under var and the installation directory as well where you untar the installable file, that uninstall the application.
_________________
Saying what you feel. It's not being rude, it's called being real. |
|
| Back to top |
|
|
|
|
