Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

bootstrap failing on Windows in 1.7.7, but not 1.7.5 #830

Open
patrickmcelwee opened this issue Aug 14, 2017 · 9 comments
Open

bootstrap failing on Windows in 1.7.7, but not 1.7.5 #830

patrickmcelwee opened this issue Aug 14, 2017 · 9 comments
Assignees

Comments

@patrickmcelwee
Copy link

patrickmcelwee commented Aug 14, 2017

The issue

Short description of the problem:

What are the steps to reproduce the problem?

  1. Change the bootstrap port from 8000 on Windows in local.properties (because the prospect's laptop had an unchangeable port conflict):

    bootstrap-port-five=8010
    qconsole-port=8010

  2. Run java -jar roxy.jar local bootstrap

  3. Get error on setup:do-setup, expected 2 args, got 3, probably because the connection_string is being appended to the POST: https://github.com/marklogic-community/roxy/blob/master/deploy/lib/server_config.rb#L1637

Tech Specs

Which Operating System are you using?

Windows 7 (over WebEx with a prospect, so I have very little ability to further debug)

Which version of MarkLogic are you using?

9.0-2

Which version of Roxy are you using (see version.txt)?

Was using the 1.7.7 jar. Downgrading to 1.7.5 fixed it.

@grtjn
Copy link
Contributor

grtjn commented Aug 15, 2017

Hmm, more likely the jar is out of sync. setup:do-setup is only invoked from

r = execute_query %Q{#{setup} setup:do-setup(#{config}, "#{apply_changes},#{dointernals}", #{properties_map})}
..

@grtjn
Copy link
Contributor

grtjn commented Aug 15, 2017

@RobertSzkutak could you take a peek at this?

@patrickmcelwee
Copy link
Author

Thanks Geert ... that's actually the line I should have linked to. I could see the properties map being passed through

@patrickmcelwee
Copy link
Author

Ah, I understand now. Yep, it is definitely a version sync problem. I had an older version of Roxy in deploy/, but a newer version of the jar, and in the meantime, the function signature changed a couple months ago: 4abf5c6#diff-252a0a5c799a8b8a7d685b2f74202806R879

It makes sense. I'll just put a note in the wiki page on Roxy jars that you should grab the same jar version as your local Roxy (in version.txt).

@patrickmcelwee
Copy link
Author

I don't have wiki editing privileges ... here is the page: https://github.com/marklogic-community/roxy/wiki/Run-Roxy-as-a-Jar.

@grtjn
Copy link
Contributor

grtjn commented Aug 15, 2017

Not sure it is required to have same version of the roxy jar as you have local, as it is supposed to use lib files from within the jar. It would be like you upgraded Roxy basically, but without replacing all files.

I still suspect something is wrong with the jar.

@grtjn grtjn reopened this Aug 15, 2017
@grtjn
Copy link
Contributor

grtjn commented Aug 15, 2017

I gave you edit privs nonetheless..

@RobertSzkutak
Copy link
Contributor

FWIW I did do my JAR testing on Windows. My testing includes trying a suite of a combination of functions. I can't say I've tried a JAR with older Ruby files but offhand I would expect the JAR would act independent of those. I should be able to look into this and do some further testing tonight.

@grtjn
Copy link
Contributor

grtjn commented Nov 28, 2017

Another mention of this by Stephen Crook, trying to use roxy.jar 1.7.7 with RunDMC. He had the same error message, which went away when reverting to roxy.jar 1.7.5.

I think the culprit lies in the fact that roxy is taking server_config.rb from the jar, but setup.xqy from filesystem. The xqy file is included in the jar, but roxy is simply not looking there..

     0 Fri Aug 04 15:05:00 CEST 2017 roxy/lib/xquery/
 16696 Fri Aug 04 15:05:00 CEST 2017 roxy/lib/xquery/cpf.xqy
246216 Fri Aug 04 15:05:00 CEST 2017 roxy/lib/xquery/setup.xqy
  3618 Fri Aug 04 15:05:00 CEST 2017 roxy/lib/xquery/triggers.xqy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants