Ah I’m glad you got that working.
Thanks for reporting back!
— Martijn
> On 14 Jan 2020, at 22:48, Arnold Bronley wrote:
>
> Thanks.
>
> The issue turned out to be little different that expected. My IntelliJ was
> on a Windows (my main operating system). Solr was running inside a docker
> cont
Thanks.
The issue turned out to be little different that expected. My IntelliJ was
on a Windows (my main operating system). Solr was running inside a docker
container inside Debian VM hosted on my Windows operating system.
Debug server that runs inside the docker container will accept connections
Hi,
I was able to connect my IDE to Solr running on a container by using the
following command:
command: >
bash -c "solr start -c -f -a
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005;"
It starts SolrCloud ( -c ) and listens on foreground ( -f ) so you don't
need to r
Thanks for your helpful replies, guys.
@Edward: you were correct. I forgot to export 5005 port in YAML. After
exporting this port, I am at least able to see the process with following
command (I was not able to see it before):
gnandre@gnandre-deb9-64:/sandbox/gnandre/mw-ruby-development-server$ s
I think you may have a quoting issue there: remove those inner ones. Not that
it should matter in this instance.
I’m not sure why you’re using “start”, which will run solr in the background,
or what you expect to happen after the wait-for-solr.sh — if it all worked as
you expected that would wai
Could you share the content of your docker-compose.yml file?
Did you export the 5005 port in the cited file YAML file?
Best,
Edward
Em sex, 10 de jan de 2020 20:43, Arnold Bronley
escreveu:
> Hi,
>
> I have a running dockerized instance of Solr which runs fine with the
> following setting for
