-
Notifications
You must be signed in to change notification settings - Fork 77
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
Using xccProtocol in a CorbTask results in XCC_PROTOCOL instead of XCC-PROTOCOL #627
Comments
@hansenmc Would this require a code change, or does it just need a docs improvement to tell users how to do this? I'm having to do the docs change if so. |
I suspect it is a CorbTask code issue. |
Do you have an example project that demonstrates the issue? A task such as this works for me and I can run
I have noted some issues trying to set |
Trying to think back, but unsure. We do have multiple tasks, and some use a different protocol than others. Maybe that is part of the issue. This seems to work though. Note that we switched to
|
We have enabled https on certain ports, and needed to switch CorbTask to use xccs. I first tried to use xccProtocol property inside the task, but that resulted in a 403. It took a while before I remembered that you get a 403 Forbidden if you hit an https port in MarkLogic with http. Looking more closely at the JavaExec commandline, I noticed all other properties like xccUsername, xccHostname are correctly translated to XCC-..., but not xccProtocol.
Workaround is to use System.setProperty('XCC-PROTOCOL', 'xccs').
We are using:
mlDataHubVersion=5.5.5
mlCorbVersion=2.4.6
The text was updated successfully, but these errors were encountered: