Can't Connect to Fuse Container after Rollup 3 Patch
Issue
-
After applying
Rollup 3patchFusestarts but we cannot connect to the container via client. -
Client connection previously worked without issue. Fuse was running base version with no patches prior to
rolluppatch 3.
fuse@fuse3-dev-pl bin]$ ./client -u admin -p ******
Logging in as admin
Failed to get the session.
- Also tried
./client -u admin -p ****** -a 8181
./client -u admin -p ****** -a 8183
./client -u admin -p ****** -a 8181 -h 129.127.73.143
./client -u admin -p ****** -a 8183 -h 129.127.73.143
- Trying to connect via client script on an unpatched Fuse server:
[fuse@fuse1-dev-pl bin]$ ./client -u admin -p ****** -a 8181 -h 129.127.73.143
Authentication failure
[fuse@fuse1-dev-pl bin]$ ./client -u admin -p ****** -a 8183 -h 129.127.73.143
Authentication failure
Environment
- Red Hat JBoss Fuse
- 6.1.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.