| Author |
Message
|
| Sabina |
 Posted: Tue Jan 17, 2017 4:44 am Post subject: Bus can not deploy latest changes |
 |
|
Novice
Joined: 27 Sep 2016
Posts: 14
|
Hello everyone!
I have a problem with my integration bus... Somehow, when I deploy a project with some changes in its code, the project on the server remains the same after deployment.
I tried to clean the project. And to restart the integration node, where I deploy. And to delete the project from the server and then deploy a clean new version. But nothing works.
Interestingly, with other projects the behavior is different. With some deployment is successful and all the changes in the local code are present on the server. With others - depends on luck. It can deploy successfully from time to time.
Thanks for any help. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jan 17, 2017 5:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Are you sure you have rebuilt the BAR file?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jan 17, 2017 5:56 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Platform?
Version?
Fixpack level?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Sabina |
| Posted: Sun Jan 22, 2017 9:47 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2016
Posts: 14
|
Thank you all for your responses!
Yes, I tried to rebuild the bar file, and it didn't help. What worked is deletion of the bar file completely. Only after that the project deployed with the latest changes. |
|
| Back to top |
|
|
| timber |
| Posted: Mon Jan 23, 2017 1:32 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
I had a similar experience last year, but could not reproduce it reliably. I ended up using mqsipackagebar to script the BAR file building. But it should not be necessary; the toolkit should reliably update BAR files.
If you can reproduce this behaviour then you should open a PMR. |
|
| Back to top |
|
|
| Sabina |
| Posted: Mon Jan 23, 2017 3:54 am Post subject: |
|
|
Novice
Joined: 27 Sep 2016
Posts: 14
|
I also have had problems with launching debug for some time. I am not sure if they have the same root as my previous one...
When I try to debug, after some waiting I get this error in console:
[Test Client Info]Saving broker archive to disk...IB9NODE_default.bar
[Test Client Info]Transferring broker archive to execution group default.
[Test Client Error]No response was received from the Broker.
Check the Broker Administration Event Log Editor to
determine the current system state.
Seems like again something wrong is going on, but with ather bar file - IB9NODE_default.bar. |
|
| Back to top |
|
|
| timber |
| Posted: Mon Jan 23, 2017 4:09 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| That sounds like a problem with deployment of the BAR file. The other problem was a problem with building the BAR file. I think they are probalby separate issues. |
|
| Back to top |
|
|
| Sabina |
| Posted: Tue Jan 24, 2017 4:21 am Post subject: |
|
|
Novice
Joined: 27 Sep 2016
Posts: 14
|
| Interestingly, here again after deletion of IB9NODE_default.bar the problem resolved. But rebuild was unhelpful. |
|
| Back to top |
|
|
|
|
