如何让 Websphere 将密钥库更改从部署管理器传播到节点？
我对这个有点难住了。
我有一个完全工作的 2 节点集群，更改了密钥库和信任库以使用不同的文件，保存了更改。
我的假设是部署管理器会在切换之前自动将这些更改传播到节点。
然而，根据部署管理器的说法，节点现在不再运行，并且查看日志，在尝试连接到它们时出现大量 ssl 错误。
现在我该怎么办？ dep mgr 甚至无法与节点代理对话，它将如何为他们提供新的 ssl 更改？
I'm a bit stumped on this one.
I had a completely working 2 Node cluster, changed the keystore and the truststore to use different files, saved the changes.
My assumption was that the deployment manager would automatically propagate those changes to the nodes before switching over.
However according to the deployment manager, the nodes are now no longer running, and looking at the logs it's getting a lot of ssl errors trying to connect to them.
Now how do I proceed? The dep mgr can't even talk to the node agents, how is it going to give them the new ssl changes?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
哎呀，看来我跳得太快了。
与许多 websphere 问题一样，重新启动节点和 dmgr 4 或 5 次即可解决问题。
Oop, Looks like I jumped on the lazyweb too quickly.
As with numerous websphere problems, restarting the nodes and the dmgr 4 or 5 times solved it.