I have no control over which version one of the component jars is using. I will attempt using 8.1 and report on the handling of the starting/stopping the service on a non-default port.
From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: Tuesday, April 07, 2015 5:47 AM To: Bondeson, Carl Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] BaseX under JBoss 6.2
Hi Carl,
Does the problem persist with BaseX 8 or later? I invite you to also have a look at the latest snapshot [1].
Best, Christian
[1] http://files.basex.org/releases/latest
On Tue, Mar 31, 2015 at 4:12 PM, Bondeson, Carl <Carl.Bondeson@ct.govmailto:Carl.Bondeson@ct.gov> wrote: I have a deployment that is using 2 instances of BaseX. The first is using the default ports, then second is using alternate ports. Deploying the war goes smoothly, and both instances get along. When attempting to disable the deployment using the management console the process never completes. In looking at the log file the following error was noted.
10:00:31.159 SERVER admin OK Server was started. 10:02:19.876 SERVER admin Error: File 'C:/Users/DPHPIL~1/AppData/Local/Temp/BaseXServer1984' could not be deleted.
It seems that even though the second instance is using 1982 as the port, the default port is being in this transaction. The versions in use are 7.6 and 7.9. Is there something from a configuration standpoint that needs to be set in order for the shutdown process to use the correct, non-default port?
Carl R Bondeson Systems Developer Department of Public Health Data Processing 410 Capitol Ave Hartford, CT 06134 Phone: 860-509-7434 carl.bondeson@ct.govmailto:carl.bondeson@ct.gov [Description: DPH Logo - Keeping CT Healthy]http://www.ct.gov/dph
