[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [virgo-dev] bug 307737
|
| Both the startup and shutdown have been implemented for Windows. I have attached a zip archive that contains the modified dmk.bat and the four config files that require modification in each instance. The instance name I used for testing is 'instance_test' which should be created in KERNEL_HOME, the normal config folder needs to be copied into instance_test and the modified files dropped in.
I would very much appreciated if someone who works regularly on the Win platform would test this. I use OS X so my windows skills are limited and rusty. I used a VMware partition running Win XP Service Pack 2 to develop the code, so a spin on a more up to date windows is in order.
Thanks, Joel
|
Attachment:
dmk files ready for checking on windows.zip
Description: Zip archive
On 13 Sep 2011, at 14:11, Joel Rosi-Schwartz wrote: Okay this is all working now. A bit odd, but once I straightened out the last of the issues with tomcat the logging all went back to normal. This I do not understand, does anyone else have a reason or at least a guess.
The last thing I have to tackle is the shutdown side. There are some questions I have, but I will formulate them and send a followup email. On 13 Sep 2011, at 12:25, Joel Rosi-Schwartz wrote: Okay more progress. I found my error that was causing the serviceabilty not being relocated. I reverted back to to $ instead of %% for the two sets I added at the end which were controlling serviceability and tomcat. Now I have all logging to serviceability going to the new instance_test/serviceability including tomcat access logs.
However, I still do not see the way to inform tomcat to do its work in instance_test/work
Also logging is still a bummer. On 12 Sep 2011, at 20:26, Joel Rosi-Schwartz wrote: hi,
Finally made time to work on this. I have started with the Windows bat file. I have made progress, but I have some issues I do not understand. I have attached the modified files and the output from the console on a typical run.
The first thing that is causing me no small grief is the amount of output I am getting to the console. I appears that the logging is running at trace or close to it. The serviceability.xml is set to INFO, so I am at a loss how to quite it down. It really gets in the way :-(
At this juncture I have the server running from a specified instance directory. I picks up from instance_test/pickup and uses instance_test/work for everything but Catalina which still gets created in the normal work directory. Serviceability is still being created in the normal area even though I have changed all of the properties and the xml file.
Another pair of eyes on this would be appreciated.
Many thanks, Joel
On 26 Aug 2011, at 14:15, Glyn Normington wrote: The SAP committers use Windows and should be able to advise. (However, I've never met anyone who would admit to understanding all the corners of the Windows batch language, including the guys here who wrote those scripts!)
On 26 Aug 2011, at 14:08, Joel Rosi-Schwartz wrote: Thanks Glynn.
I am fine with getting the fixes in place in the shell files, but I may need some assistance/guidance with the .bat. Who on the team is good with them? Btw, Barbara runs on Win 7 so the bat files are not optional from her perspective either :-)
Have a great holiday.
Joel On 26 Aug 2011, at 13:55, Glyn Normington wrote: Hi Joel
I wasn't sure whether a bug could be assigned to a non-committer, but it seems to work and I've assigned the bug to you and marked it as assigned.
I will be going on vacation for two weeks after today, so please work with the other committers to get any patch integrated. Don't forget docs if these are impacted.
You should create a patch or clone the repo on e.g. github and make the change there. A committer will then need to ask you due diligence questions which you should answer in the bug such as "is the code all your own work?" and "do you have the rights (e.g. employer's permission) to contribute it?"
You won't be able to get a release with the official fix until 3.0.1 at the earliest, but I guess you can work with 3.0 plus your changes to the startup scripts until then.
I think the crucial missing piece in what's there already is being able to default the config dir when an instance dir is specified. Plus mapping the changes into the .bat files.
On 26 Aug 2011, at 13:37, Joel Rosi-Schwartz wrote: Hi,
As Barbara has mentioned in her post, she rather urgently needs this bug resolved. I have agreed to work on it with her over the next week to get it sorted. Can/should I assign this to myself and changed the state to ASSIGNED?
Cheers, Joel
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
|
