-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time out issue for restart option #3
Comments
Ar, good point. As a workaround, maybe you can issue stop/start command directly from the IIB command task. |
Yep I did do that. It does add a lot of extra tasks
Trent Bielejeski
Build Release Engineer
Work Hours : M-F 8:15am - 4:30pm office
W: (701) 353-7351
[Description: cid:image001.gif@01CA6C40.FA1B4B80]
From: Yang Cao <notifications@github.com>
Sent: Monday, November 26, 2018 10:02 AM
To: Microsoft/vsts-ibm-integration-bus-extension <vsts-ibm-integration-bus-extension@noreply.github.com>
Cc: Trent Bielejeski <trent.bielejeski@corelinksolutions.com>; Author <author@noreply.github.com>
Subject: Re: [Microsoft/vsts-ibm-integration-bus-extension] Time out issue for restart option (#3)
[External]
Ar, good point. As a workaround, maybe you can issue stop/start command directly from the IIB command task.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvsts-ibm-integration-bus-extension%2Fissues%2F3%23issuecomment-441693211&data=01%7C01%7Ctrent.bielejeski%40corelinksolutions.com%7C175d4b5ff8e8426f416a08d653b88b10%7C1e6d2a133fb14bd49bbc180e98ba70c4%7C1&sdata=g%2BD%2BQ2UYwTwhCCD6RzyTKBOhw3eYjwQo7saBmN7offk%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAZOSN4hpn4txmfGk2ew1D8eTmaIqtnsks5uzBCKgaJpZM4YmztJ&data=01%7C01%7Ctrent.bielejeski%40corelinksolutions.com%7C175d4b5ff8e8426f416a08d653b88b10%7C1e6d2a133fb14bd49bbc180e98ba70c4%7C1&sdata=TSaVs9egvUw50uprOPhyGFdk39HvWt7heCnk8pEmk%2Fc%3D&reserved=0>.
Confidentiality Notice: This communication and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message.
Confidentiality Notice: This communication and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message.
|
Help me how do I configure the task in windows plataform for iib ?? i have problems for conection as server IIB 2019-05-07T21:10:34.4414507Z ##[section]Starting: Run mqsi on IBM Integration Bus. |
Tannerjit: |
@tannergit |
When you select the restart intergration server check box and you have a value in the Timeout in Seconds for mqsideploy , You should add the -w option to the start and stop.
The only option now is the default 60 sec
[command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\IBM\IIB\10.0.0.12\server\bin\mqsistartmsgflow.bat" IIBDV01 -i tcp://:@entintdev.corelinkadmin.com -e Provider"
2018-11-16T16:46:50.3028326Z BIP1060I: Connecting to the integration node...
2018-11-16T16:46:50.3028898Z BIP1115I: Connected to the integration node 'IIBDV01'.
2018-11-16T16:46:50.5481008Z BIP1186I: Starting the integration server 'Provider'...
2018-11-16T16:47:51.1663996Z BIP1047E: The operation timed out waiting for a response.
2018-11-16T16:47:51.1666635Z
2018-11-16T16:47:51.1841878Z 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.
2018-11-16T16:47:51.1843163Z
2018-11-16T16:47:51.1844082Z 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.
The text was updated successfully, but these errors were encountered: