BaseX under JBoss 6.2

On Tue, Mar 31, 2015 at 4:12 PM, Bondeson, Carl <Carl.Bondeson at 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 at ct.gov > > [image: Description: DPH Logo - Keeping CT Healthy] > <http://www.ct.gov/dph> > > >

From: Christian Grün [mailto:christian.gruen at gmail.com] Sent: Tuesday, April 07, 2015 5:47 AM To: Bondeson, Carl Cc: basex-talk at 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 at ct.gov<mailto:Carl.Bondeson at 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 at ct.gov<mailto:carl.bondeson at ct.gov> [Description: DPH Logo - Keeping CT Healthy]<http://www.ct.gov/dph>

From: basex-talk-bounces at mailman.uni-konstanz.de [mailto:basex-talk-bounces at mailman.uni-konstanz.de] On Behalf Of Bondeson, Carl Sent: Tuesday, April 07, 2015 7:47 AM To: Christian Grün Cc: basex-talk at mailman.uni-konstanz.de Subject: Re: [basex-talk] BaseX under JBoss 6.2 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 at gmail.com] Sent: Tuesday, April 07, 2015 5:47 AM To: Bondeson, Carl Cc: basex-talk at mailman.uni-konstanz.de<mailto:basex-talk at 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 at ct.gov<mailto:Carl.Bondeson at 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 at ct.gov<mailto:carl.bondeson at ct.gov> [Description: DPH Logo - Keeping CT Healthy]<http://www.ct.gov/dph>

On Tue, Apr 7, 2015 at 2:23 PM, Bondeson, Carl <Carl.Bondeson at ct.gov> wrote: > The 8.1 upgrade required only some minor import changes. The start stop > on non-default ports is working. The other component jar is using default > ports. When deploying in JBoss 6.2 I am getting the following error: > > > > 0,162 INFO [stdout] (ServerService Thread Pool -- 53) - Initializing EIP > Servlet... context root is > C:\jboss-eap-6.2\standalone\tmp\vfs\temp\temp910712701f04460b\content-b7a13173f9ea23e1 > > 08:12:02,128 INFO [stdout] (ServerService Thread Pool -- 53) - Internal > configuration file from WEB.XML /MessageBus/conf/eipServer.conf is checked > > 08:12:02,143 INFO [stdout] (ServerService Thread Pool -- 53) Using > properties at file:/C:/MessageBus/conf/eipServer.conf > > 08:12:02,159 INFO [stdout] (ServerService Thread Pool -- 53) - Custom > Thread Factory is not defined. Using NTMThreadFactory. > > 08:12:02,159 INFO [stdout] (ServerService Thread Pool -- 53) - Starting > dashboard server... > > 08:12:02,611 INFO [stdout] (ServerService Thread Pool -- 53) - > EIPServer - launching ServerCore... > > 08:12:06,652 INFO [stdout] (ServerService Thread Pool -- 53) BaseX 7.6 > [Server] > > 08:12:06,652 INFO [stdout] (ServerService Thread Pool -- 53) Server was > started. > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) > java.lang.NoSuchMethodError: > org.basex.util.list.StringList.finish()[Ljava/lang/String; > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.basex.util.Strings.split(Strings.java:122) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.basex.util.Strings.split(Strings.java:101) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.basex.api.client.ClientSession.<init>(ClientSession.java:115) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.basex.api.client.ClientSession.<init>(ClientSession.java:85) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > gov.ct.dph.elr.basex.BaseXDictionary.staticStartup(BaseXDictionary.java:237) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > gov.ct.dph.elr.basex.BaseXDictionary.startup(BaseXDictionary.java:382) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.server.hook.HookManager.startup(HookManager.java:157) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.server.ServerCore.launchInternal(ServerCore.java:259) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.server.ServerCore.launch(ServerCore.java:109) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.server.ServerCore.launch(ServerCore.java:97) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.server.EIPServer.launch(EIPServer.java:30) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > com.pilotfish.eip.servlet.EIPServlet.init(EIPServlet.java:78) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > java.util.concurrent.FutureTask.run(FutureTask.java:262) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > java.lang.Thread.run(Thread.java:745) > > 08:12:06,745 ERROR [stderr] (ServerService Thread Pool -- 53) at > org.jboss.threads.JBossThread.run(JBossThread.java:122) > > The other component jar is using 7.6. > > > > *From:* basex-talk-bounces at mailman.uni-konstanz.de [mailto: > basex-talk-bounces at mailman.uni-konstanz.de] *On Behalf Of *Bondeson, Carl > *Sent:* Tuesday, April 07, 2015 7:47 AM > *To:* Christian Grün > > *Cc:* basex-talk at mailman.uni-konstanz.de > *Subject:* Re: [basex-talk] BaseX under JBoss 6.2 > > > > 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 at gmail.com > <christian.gruen at gmail.com>] > *Sent:* Tuesday, April 07, 2015 5:47 AM > *To:* Bondeson, Carl > *Cc:* basex-talk at 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 at 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 at ct.gov > > [image: Description: DPH Logo - Keeping CT Healthy] > <http://www.ct.gov/dph> > > > > >