Alex wrote:
I've got this, which is a slightly different but equivalent technique that
doesn't require the jvm-arg tag (applicable bits only, my startup script
does other things too):
Just for the benefit of understanding the use case: is this to support n
environments that are
I have a situation where different servers should have different
jvm-args, but I would like to have a single resin.xml.
I tried doing a resin:import on a jvm.xml file that has just jvm-args in
it, but I haven't found a combination that works. I have tried
surrounding the jvm-arg tags like
I have a situation where different servers should have different
jvm-args, but I would like to have a single resin.xml.
You should be able to achieve this by using jvm-arg inside the server
server id=a address=127.0.0.1 port=6800
jvm-arg-Dserver=A/jvm-arg
/server
server id=b
I have a situation where different servers should have different
jvm-args, but I would like to have a single resin.xml.
You should be able to achieve this by using jvm-arg inside the server
server id=a address=127.0.0.1 port=6800
jvm-arg-Dserver=A/jvm-arg
/server
server id=b
You should be able to achieve this by using jvm-arg inside the server
server id=a address=127.0.0.1 port=6800
jvm-arg-Dserver=A/jvm-arg
/server
server id=b address=127.0.0.1 port=6801
jvm-arg-Dserver=B/jvm-arg
/server
Regards,
Alex
Hmm, that's exactly what I tried first, as
You should be able to achieve this by using jvm-arg inside the server
server id=a address=127.0.0.1 port=6800
jvm-arg-Dserver=A/jvm-arg
/server
server id=b address=127.0.0.1 port=6801
jvm-arg-Dserver=B/jvm-arg
/server
Regards,
Alex
Hmm, that's exactly what I tried first,
No, none of those scenarios worked. It is with Resin 3.1.9. I was
trying to resin:import the jvm-args, so I guess that's why it was
failing. I have unique jvm-arg needs for different servers so I was
hoping I could pull that off.
The excerpt below should work and it will allow you to
The excerpt below should work and it will allow you to have all the
configuration in one file.
server id=a address=127.0.0.1 port=6800
jvm-arg-Dserver=A/jvm-arg
/server
server id=b address=127.0.0.1 port=6801
jvm-arg-Dserver=B/jvm-arg
/server
Thanks Alex. My problem
Hi Aaron,
Maybe I am missing something, but if you can pass in
-Dconfiguration=wherever to your individual machines (in your
/etc/init.d/resin script or wherever, I assume?), can't you pass in your
server specific JVM args there too?
Rachel
On Mon, Nov 30, 2009 at 12:08 PM, Aaron Freeman
Aaron,
Maybe I am missing something, but if you can pass in
-Dconfiguration=wherever to your individual machines (in your
/etc/init.d/resin script or wherever, I assume?), can't you pass in
your server specific JVM args there too?
Rachel
Probably. The configuration is passed in via
Well, they are JVM system variables so it isn't so much that
ResinWatchdogManager would pass them to the server, but that they're set in
the JVM when it's started and anything in that runtime instance will have
them available. My startup script uses this technique and it works great.
I suppose
Aaron,
Maybe I am missing something, but if you can pass in
-Dconfiguration=wherever to your individual machines (in your
/etc/init.d/resin script or wherever, I assume?), can't you pass in
your server specific JVM args there too?
Rachel
Probably. The configuration is passed in via
I've got this, which is a slightly different but equivalent technique that
doesn't require the jvm-arg tag (applicable bits only, my startup script does
other things too):
Just for the benefit of understanding the use case: is this to support n
environments that are identical but serve two
Hi,
This works with 3.1.9 but careful as it does not work with 3.1.5, I
think it was a new feature introduced later in 3.1 or a bug fixed. We
had to go back to 3.1.5 due to JPA issues and had to change our scripts
accordingly.
In our case, we use different Node.conf configuration files that
14 matches
Mail list logo
